The Rebuild Budget Reality Check: What a UK Website Project Really Costs in 2026

Ask a UK marketing lead what their website rebuild cost and you will usually get the headline figure. Ask what it cost over three years and the conversation gets quieter. In 2026, with platform licences, consent tooling, accessibility expectations and integration sprawl all competing for budget, the build fee is only the opening act. The real number is a total cost of ownership — and the best proposals make that visible rather than burying it in an assumptions appendix.

The number on page one is rarely the number you will pay

A serious rebuild for a mid-market UK brand with multiple templates, a CRM, ecommerce or a complex product set commonly lands somewhere between £60,000 and £180,000 before ongoing support. At the top end you are paying for discovery, design systems, integrations, migration and proper QA, not just a prettier homepage. Agency day rates in the UK often sit between £650 and £1,200 for design and build, with strategy and senior technical work at the higher end.

None of that is outrageous. What is outrageous is a single line called build with no assumptions attached. A proposal that cannot explain what is included, what is excluded and what triggers a change request is not a fixed price. It is a starting position.

Discovery: the line item that decides whether the rest is guesswork

Discovery is where a good agency earns its keep and where a weak one hides its risk. You should expect stakeholder interviews, analytics review, content audit, technical audit, competitor review, measurement planning and a prioritised backlog. If discovery is missing, the fixed price that follows is built on sand.

Ask what you will actually receive. A slide deck is not discovery. A working content model, a redirect plan and a prioritised feature list are.

Design: rounds, components and the change-request treadmill

Design costs escalate when scope is described in mood rather than deliverables. Ask how many concepts you get, how many revision rounds are included, whether a design system is part of the deal and how responsive states are handled. Unlimited design sounds generous until you realise it usually means unlimited meetings and a moving target.

Content design is another quiet cost. Who writes the pages, who checks the tone of voice, and who handles image rights? Those questions belong in the proposal, not in week six.

Build and CMS: licences, environments and the plugin tax

Whether you choose WordPress, Shopify, Umbraco or a headless setup, ask about licences, hosting environments, staging, deployment pipelines and plugin subscriptions. A CMS licence may be modest. The plugin stack, search tool, form platform and image optimisation service can add up quickly.

Also ask who owns the code and the accounts. If the agency controls the hosting, the domain or the CMS licence, you need to know what happens when you leave.

Integrations: where the quiet doubling happens

CRM, ERP, payment, PIM, warehouse, marketing automation and consent tools all need to talk to each other. A native integration can mean a supported connector, a plugin or a developer writing custom code at £900 a day. Ask which systems are in scope, who owns the API keys, what happens when a rate limit is hit and whether an integration platform is included or extra.

This is the line item most likely to turn a comfortable budget into an uncomfortable board conversation.

Migration and content: the unglamorous 30%

Migration is rarely just moving pages. It means redirect mapping, SEO preservation, content inventory, copywriting, metadata, structured data and checking that images have the right licences. If the proposal says content migration as required, treat that as an invitation to scope creep.

Ask how many pages or products are included, what happens beyond that number and who signs off redirects. A missing redirect plan can undo years of SEO work in a fortnight.

Accessibility and QA: not a badge

Accessibility is not a nice-to-have in 2026. UK brands should be asking for WCAG 2.2 AA alignment, manual testing with keyboard and screen reader, clear focus states and accessible forms. A automated scan is not an audit. Ask who tests, what evidence you receive and whether accessibility is checked again after launch.

QA should also cover browsers, devices, performance, analytics events and consent behaviour. If QA is a line item called testing, ask what that actually means.

Support, hosting and the renewal you did not budget for

Launch is not the end of the cost curve. Ask for the care plan, the SLA, hosting, CDN, backups, security updates, CMS updates and the retainer rate. A support plan that covers updates but not content changes is not the same as one that covers both. Get the annual figure in writing.

How to read the proposal like a grown-up

Look for assumptions, exclusions, day rates, change-request process, ownership and exit terms. Red flags include vague integration language, unlimited design, accessibility described only as best practice, hosting included but unspecified, and content migration with no page count. A good proposal will make you slightly less excited and considerably better informed.

Building the business case without fantasy maths

Do not justify a rebuild on looks alone. Build the case on conversion, reduced maintenance, faster pages, better content operations, accessibility risk and the cost of doing nothing. Show the total cost over three years, not just the build fee. Approve discovery separately if you need to test the agency before committing to the full programme.

At Klood Digital, we would rather see a marketing lead challenge a proposal properly than sign one they do not understand. The right agency will welcome the questions. The wrong one will call them scope creep.