Why "how much does a website cost" is the wrong question

"How much does a website cost?" is one of the first questions almost every business asks, and it's almost always the wrong one to lead with. It's a bit like asking "how much does a vehicle cost" without saying whether you need a courier van or a compact car. The number is meaningless without knowing what the thing actually has to do for you.

The more useful question is: what does this website need to achieve, and what does it cost to keep achieving that over time?

A website is not a purchase, it's an ongoing asset

A website that just sits there looking presentable is a cost with no return. A website that's actively found, trusted, and used to generate enquiries is an asset that pays for itself. The difference between the two has very little to do with the upfront build price and almost everything to do with what happens after launch: whether it's kept current, whether it's optimised for search, whether anyone is paying attention to how it performs.

This is exactly why comparing two quotes purely on headline price so often leads to a bad decision. A cheaper build with no ongoing care can end up costing more in lost enquiries over three years than a more considered, properly maintained option.

What the upfront price usually doesn't include

When a quote focuses solely on the build, it's worth asking directly what happens the day after launch:

• Who updates the content when your services, pricing, or team change?
• Who patches security issues and keeps the software current?
• Who is watching whether the site still loads quickly and ranks well as competitors and algorithms move?
• Who actually owns the site if the relationship ends? Do you walk away with everything, or are you locked into a platform you don't control?

A low build price with no answer to these questions isn't actually cheap. It's a cost deferred, not avoided.

A better framework for comparing options

Rather than comparing two numbers, compare what each option gets you over a realistic time horizon, say, three years:

1. Total cost over the period. Build price plus hosting, plus any maintenance, plus the cost of a redesign if the site becomes unworkable.
2. What's actually included. A static brochure site versus one with ongoing content, SEO, and reporting are not the same product, even if they look similar on day one.
3. What you own at the end. Some cheap platforms make switching or leaving expensive by design.
4. Who's accountable when something breaks or underperforms. A one-off build has no one watching after handover; a managed arrangement does.

Viewed this way, the "expensive" option is often the cheaper one once you account for what it actually delivers.

The real question to ask a web provider

Instead of "how much for a website," try: "what will this cost me over three years, and what happens if something needs to change along the way?" Any provider worth working with should be able to answer that clearly, without dodging into a single upfront number.