What does a website actually cost?

The bands, and what puts you in one

These are broad, and they overlap. What matters is the boundary conditions, because a single requirement can move you a whole band.

• A few thousand: a handful of pages, your content, a contact form, a template design adapted to your brand.
• Five to fifteen thousand: custom design, a content system you can edit, a dozen or more pages, basic integrations like a mailing list or a booking widget.
• Fifteen to forty thousand: visitors have accounts, or you sell something with non-trivial rules, or it must talk to a system you already run.
• Above forty thousand: it is not really a website any more. It is software with a web interface, and it should be estimated as such.

What moves you up a band

Certain requirements sound small in a conversation and are not. Each of these can shift a quote by a whole band on its own.

• Anyone logging in, which brings accounts, resets, permissions and security.
• Taking payment, which brings refunds, failures, receipts and reconciliation.
• More than one language, which affects every page and every piece of content forever.
• Connecting to an existing system, particularly one that is old or undocumented.
• Anything that has to comply with a regulation.

Where cheap sites become expensive

The low band is genuinely fine for many businesses, and there is no virtue in overspending. The trouble comes when a cheap build is asked to grow into something it was not structured for.

The commonest version is a template site with functionality bolted on through plugins until nobody can tell which plugin does what, and every update risks breaking checkout. Rebuilding at that point costs more than building properly would have.

The dividing question is whether the site is a brochure or part of how the business runs. Brochures can be cheap indefinitely. Operational systems cannot.

The costs after launch

Budget for these from the start. They are not large, but they are permanent, and discovering them later feels like being overcharged when it is simply how software works.

• Hosting and domain, typically modest monthly amounts.
• Third-party services: email delivery, payment fees, any paid integrations.
• Updates to the platform and its dependencies, which are security work rather than optional polish.
• Someone available when it breaks, whether a retainer or an agreed hourly arrangement.