"How much does a website cost?" is the question I'm asked most, and the honest answer is that it depends on a handful of decisions you control. I won't quote figures here, because any number without your scope attached is misleading. Instead, here's what actually moves the price, so you can budget properly and recognise a good quote when you see one.
Why do website quotes vary so much?
Send the same one-paragraph brief to five people and you'll get five very different quotes. Usually that isn't because someone is overcharging. It's because each person has silently filled in the gaps differently. One imagined a theme with your logo on it. Another imagined custom design, copywriting and a CMS. A third quoted the build but not the content, hosting or support.
The fix isn't to hunt for the lowest quote. It's to remove the gaps, so everyone is quoting the same project.
What actually drives the cost of a website?
1. Scope: unique templates, not page count
A site with forty product pages that share one layout can be less work than a site with eight pages that are all different. What matters is how many unique page templates and components need designing and building, and how many states each one has: mobile, empty, error and loading.
2. Custom design vs a template
A template gives you a proven layout quickly, with limits on how far you can bend it. Custom design starts from your brand, your audience and the action you want visitors to take, and is designed and prototyped before any code is written. It costs more because more decisions are being made specifically for you.
3. Content
Content is the most underestimated cost and the most common cause of delays. Who writes the copy? Is there photography, product imagery or video? Does anything need translating? If content arrives late, the project waits, whoever is building it.
4. CMS and editing needs
If you only change a few lines a year, a simple setup is enough. If a marketing team publishes every week, schedules posts, works in several languages and needs previews and user roles, that means a content model, a CMS and editor training. More flexibility for editors means more to design and build.
5. Integrations
Every connection to another system adds work: CRM, email marketing, booking, payments, analytics, search, a customer portal or an internal API. Well-documented services are quicker to connect. Older or custom systems with patchy documentation are where estimates get risky, and a careful quote will account for that.
6. E-commerce
Selling online multiplies scope: catalogue, variants, inventory, checkout, tax, shipping, order emails, refunds and the legal pages that go with them. A hosted platform covers much of this out of the box. A custom or headless storefront gives you more control and speed, with more to build.
7. Animation, motion and 3D
Tasteful micro-interactions are a small line item. Scroll-driven storytelling, custom illustration, product animation or real-time 3D in the browser is a craft of its own. It needs design, asset production and performance work so it stays smooth on mid-range phones. Because I direct the motion and build the site myself, I can tell you early which effects earn their place and which are just weight.
8. Performance, accessibility and SEO groundwork
A fast, accessible, indexable site is built that way from the start: optimised images and fonts, lean JavaScript, semantic markup, metadata, structured data, sitemaps and redirects. Google's Core Web Vitals give clear targets: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint within 200 milliseconds and Cumulative Layout Shift of 0.1 or less. Meeting them takes deliberate work, and so does accessibility. Both cost less to build in than to retrofit, which is why fixing Core Web Vitals on an existing site is a project in its own right.
9. Migration from an existing site
Replacing a site isn't just building a new one. Old URLs need mapping and redirecting, content needs moving and cleaning, and analytics needs reconnecting so you don't lose search rankings or data. The bigger the old site, the more this matters.
10. Maintenance and running costs
Launch day is not the last bill. Budget for hosting, domain renewal, paid plugins, CMS seats, third-party services, security updates and someone to make changes. Ask every supplier which ongoing costs exist and who pays them.
Template vs custom website vs web app
These are different products, not different price tiers of the same product.
Template or theme site
- Fastest to launch, because the layout decisions are already made.
- Best for validating an idea, a small business with standard needs, or a hard deadline.
- Trade-off: it looks similar to other sites and gets harder to extend the further you move from the template.
Custom-designed website
- Designed around your brand, your audience and the action you want visitors to take.
- Best when the site is a primary sales channel or your brand needs to stand apart.
- Trade-off: more upfront time for discovery, design and review.
Web application
- Has logged-in users, data, permissions, dashboards or business logic. Think SaaS products, client portals and booking systems.
- Best when the website is the product, or does real work for your business.
- Trade-off: it's software, not a brochure. It needs architecture, testing and ongoing development.
Plenty of businesses need a mix: a custom marketing site with one or two app-like features. That combination is most of the web development work I do, and naming which parts are which helps any developer quote accurately. If you're launching a product, my SaaS landing page page shows what the marketing side usually involves.
How do you get an accurate fixed quote for a website?
A fixed quote is only as good as the brief behind it. Before you ask for one, prepare:
- The goal. What should the site achieve, and how will you measure it?
- A sitemap. A simple list of pages, grouped by which ones share a layout.
- Features. Forms, search, booking, accounts, payments, languages, blog.
- Integrations. Every tool it must connect to, with links to their documentation if you have them.
- Content status. What exists, what needs writing, and who's responsible for it.
- References. Two or three sites you like, and what specifically you like about each.
- Deadline. And whether it's fixed, such as a launch event, or flexible.
- Maintenance. Who will look after the site after launch: your team, the developer, or nobody yet.
- A budget range. Sharing it isn't a weakness. It lets a good developer tell you what's realistic and suggest what to phase.
Then ask for the quote to list deliverables, assumptions and exclusions in writing. The assumptions section is where you find out what you're actually buying.
How should you compare website quotes?
Put every quote against the same questions:
- Does it include design, or only development?
- How many revision rounds, and at which stages?
- Is copywriting, imagery or content entry included?
- Which CMS, and will your team be trained on it?
- Are hosting, domain and third-party licences included or separate?
- Who owns the code, the design files, the domain and every account?
- What performance, accessibility and SEO work is included?
- How are change requests handled once work starts?
- What support is included after launch, and for how long?
- How are payments split across milestones?
A quote that's lower because it leaves out content, SEO or support isn't cheaper. It's just shorter.
How to budget for a website in 2026
- Separate build from running costs. Budget the launch and the first year of hosting, licences and updates as two separate lines.
- Keep a contingency. Something always surfaces: a missing integration, extra content, a legal page nobody mentioned.
- Phase it. Launch the pages and features that bring in revenue or leads first, then add the rest using real usage data.
- Spend where visitors decide. Your homepage, key landing pages and checkout or contact flow deserve the most care.
- Pay for ownership. Make sure you own the domain, the code and the accounts, so you're never locked in.
Key takeaways
- Quotes differ mainly because each supplier imagines a different project, so close the gaps before you compare.
- The biggest cost drivers are unique templates, custom design, content, CMS needs, integrations, e-commerce, and motion or 3D.
- Template sites, custom websites and web apps are different products with different trade-offs.
- A clear brief with a sitemap, features, integrations and a budget range gets you a realistic fixed quote.
- Compare quotes on inclusions, ownership, revisions and support, not on the headline number.
- Budget for running costs and a contingency, and phase anything that doesn't need to launch on day one.
Planning a project? Book a free discovery call — I'll tell you honestly what it needs.