A plain-language breakdown of what actually drives the cost of a website up or down — and why the honest answer depends on what it has to do.
If you've been quoted two very different prices for a website, you're right to be confused. They're both called a website. They're often not the same product.
A cheap, templated website is usually filled in and handed over as-is. It exists. It will probably load slowly on a phone, it won't be measurable, and when something breaks you'll struggle to find the person who built it. That's not a criticism — it's just what that approach buys.
A website accountable for a business outcome is a different thing. It starts with a discovery call to define what outcome you're paying for — enquiries, bookings, orders. It's designed mobile-first because that's where your customers are. It's built to load fast on a 4G signal. It has analytics installed and events configured so you can see what's working. And it comes with a 60-day review that tells you, in numbers, whether it's doing its job.
What it actually costs depends on what it has to do. A straightforward site that establishes credibility and takes enquiries is a smaller project than a booking system, and a booking system is a smaller project than a full online store with inventory and payments. The honest way to price any of them is to scope the specific project, not to quote a number before anyone knows what's being built.
The honest answer to 'what does a website cost' is: it depends on what the website has to do — and anyone who gives you a number before understanding that is guessing. Tell us what you're building and we'll scope it properly, then send a fixed proposal before any work starts.