How Much Should a Website Cost, and What Are You Actually Paying For?
Ask five agencies for a website and you will get five quotes that differ by a factor of twenty, all for what sounds like the same thing. The variation is real, but almost none of it is about design. It is about what happens after launch, and who carries the risk.
What actually drives the number
The page count barely matters. What drives cost is the number of distinct page types, because each one has to be designed, built, made responsive and tested. Forty pages using four templates is a far smaller job than eight pages that all look different.
The bigger multipliers are integrations and custom logic. A brochure site that submits a form to an email address is one kind of project. A site that takes payment, syncs stock with a warehouse system, calculates shipping by weight and region, and pushes orders into an accounting package is a different discipline with an order of magnitude more that can go wrong.
Content is the most consistently underestimated line. Writing, editing, photography and migration frequently take longer than the build. Projects that stall usually stall here, waiting on copy that nobody was assigned to write.
The cheap quote is usually a scope difference
A very low quote is rarely someone doing the same work for less. It is normally a different scope. Common omissions: content is assumed to be supplied, only one round of revisions is included, testing covers one browser on a desktop, and accessibility, performance work and search fundamentals are not in scope at all.
The other pattern is the low build price attached to a high recurring fee, or to a platform you cannot leave. Ask directly whether you will own the code and the content, and whether the site can be moved to another host or another supplier. If the answer is unclear, the low price is a lease.
Ask what happens when something breaks after launch, who fixes it and at what rate. The difference between a good and a bad supplier shows up in month three, not at handover.
Custom, template, or platform
Three broad routes exist. A website builder is cheapest and fastest, and suits a small brochure site where nothing unusual is needed. A content management system with a well-chosen theme sits in the middle and covers most business requirements. A custom build costs most and is justified when the site does something specific to your business that no template anticipates.
The honest advice is that most businesses do not need a custom build, and many that commission one are paying for flexibility they never use. The reverse mistake is also common: forcing genuinely custom logic into a template, then paying for plugins and workarounds indefinitely.
Whichever route, insist on the fundamentals being in scope: it must be fast on a mid-range phone, work with a keyboard and a screen reader, and have proper titles, descriptions and structured data. Retrofitting these is more expensive than including them.
Budget for after launch
A website is not a one-off purchase. Hosting, a domain, certificates, platform and plugin updates, backups and security patching all continue, and neglecting them is how sites get compromised. Set aside an annual figure for this at the start.
Beyond maintenance, budget for change. The most valuable period of a website is the first year after launch, when real data arrives and you learn which pages fail. A site that cannot be changed without a quote for every edit will not be improved, and an unimproved site loses to competitors that iterate.
Before commissioning anything, get clear on what the site is for and what a success would look like in numbers. Our website development service starts from that question, and our redesign guide covers the specific risks of replacing a site that already ranks.
Key takeaways
- Cost is driven by distinct page templates, integrations and custom logic, not by page count.
- A very low quote is usually a narrower scope: content, testing, revisions and accessibility left out.
- Ask explicitly whether you own the code and content, and whether the site can be moved elsewhere.
- Most businesses do not need a custom build; most that force custom logic into a template regret it.
- Budget for hosting, updates and backups annually, and for changes in the first year when the real data arrives.
Frequently asked questions
Why do website quotes vary so much?
Because the quotes are usually for different work, even when the description sounds identical. Variation comes from how many distinct page templates are designed, whether content and photography are included, how many revision rounds are allowed, how much testing is done across devices and browsers, whether accessibility and performance are in scope, and what happens after launch. Ask each supplier the same specific questions about those areas and the apparently wild price range usually resolves into a clear picture of what each one is actually offering.
Is a custom website worth it over a template?
Only when your site has to do something a template does not anticipate. For a brochure site, a service business or a simple shop, a well-chosen theme on an established platform delivers what you need faster and cheaper, and stays maintainable. A custom build earns its cost when you have unusual workflows, a specific integration, or performance requirements a general-purpose theme cannot meet. The expensive mistake in the other direction is forcing genuinely custom logic into a template and paying for plugins and workarounds indefinitely.
What ongoing costs should I expect after launch?
At minimum: hosting, domain renewal, certificate renewal if it is not included, platform and plugin updates, backups and security monitoring. On top of that, budget for actual changes, because the first year after launch is when you learn which pages fail and fixing them is the highest-return work available. Treat maintenance as a fixed annual line rather than something to react to, since the sites that get compromised are almost always the ones that stopped being updated.
Do I own my website?
It depends entirely on the contract, so ask before signing rather than after. Establish who owns the code, the design files and the content, whether you have full administrative access to the hosting and the domain, and whether the site can be moved to a different supplier or host. Some arrangements price the build low and retain ownership, which makes leaving expensive or impossible. That may still be an acceptable deal, but you should know you are making it.
How long does a website take to build?
For a straightforward business site with a handful of templates, several weeks of actual work is typical, but calendar time usually runs longer because of content and feedback. Larger sites with integrations, custom functionality or migration from an existing site take months. The most common cause of delay is not development but content: copy, photography and product data that nobody was explicitly assigned to produce. Naming an owner and a deadline for content at the start removes most of the risk.
Should I pay for SEO as part of the website build?
The technical fundamentals should be included rather than sold separately: proper titles and descriptions, clean URLs, structured data, fast loading on mobile, working internal links and a sitemap. If a proposal treats those as an optional extra, it is proposing to build something that will need fixing. Ongoing SEO work such as content production, keyword targeting and link building is genuinely a separate continuing service, and it is reasonable for that to be priced apart from the build.