How to Budget for a Website Redesign

A website redesign is rarely just a new visual layer. It may involve new templates, rewritten copy, content migration, redirects, tracking, accessibility work, platform changes and a safer maintenance process. Budgeting only for design creates a project that looks affordable at the start and becomes expensive when the missing work appears.

This guide shows how to build a realistic redesign budget for a UK small business without assuming that every existing page must be replaced.

Step 1: decide why the site is being redesigned

Write down the business problem before discussing colours or layouts. Common reasons include:

• the offer, audience or brand has changed;
• the site is difficult to use on mobile;
• content is inaccurate or hard to maintain;
• important forms, bookings or payments are unreliable;
• the platform is unsupported or insecure;
• ownership and access are unclear;
• the site no longer supports how customers buy.

A redesign should have a measurable purpose. If the only reason is that the site “feels old”, first identify the specific user or operational problem that age has created.

Step 2: audit before pricing

Record what can be retained, improved, merged, redirected or removed. The audit should cover:

• current URLs and pages receiving traffic or enquiries;
• content quality and ownership;
• forms, booking, payment and email delivery;
• domain, DNS, hosting and analytics accounts;
• plugins, licences and third-party services;
• mobile, performance and accessibility issues;
• backups and recovery capability.

Without this audit, suppliers must price uncertainty or make assumptions that later become change requests.

Step 3: divide the budget into workstreams

Redesign budget workstreams

Workstream	Typical deliverables
Discovery and planning	Audit, objectives, audience, page map, functional requirements and risks
Content	Inventory, copywriting, editing, migration, images and downloads
Design	Wireframes, visual system, templates, states and mobile behaviour
Development	CMS, templates, integrations, forms, structured data and account setup
Migration and SEO protection	URL map, redirects, metadata, sitemap and Search Console checks
Testing and launch	Functional, mobile, browser, accessibility, performance and recovery tests
Post-launch	Monitoring, fixes, training, documentation and maintenance

Step 4: estimate content separately

Content is often the largest hidden cost. For every page, decide whether it will be:

• kept with minor editing;
• rewritten;
• merged into another page;
• created from new evidence;
• removed and redirected;
• migrated unchanged for later review.

Include photography, diagrams, product data, case studies and legal review where relevant. “Client to supply content” is not a saving if no one has time to produce it.

Step 5: price migration and continuity

Existing websites carry history. Budget for:

• a complete URL inventory;
• 301 redirects from changed URLs;
• preservation of important titles and content intent;
• email and DNS protection during changes;
• analytics and Search Console continuity;
• backup and rollback before launch;
• monitoring after launch.

A redesign that loses high-value pages, enquiries or business email can cost more than the build itself.

Step 6: calculate recurring costs

Add the first-year and annual totals for:

• hosting or platform subscription;
• domain and email;
• paid extensions and licences;
• maintenance and backups;
• booking, payment or membership services;
• analytics, consent or monitoring tools;
• content and improvement work.

Step 7: hold a controlled contingency

A redesign of a well-documented site may use a 10–15% planning contingency. Old custom systems, unclear access or large migrations may justify more. The contingency should cover genuine discoveries, not undefined scope.

Compare options by outcome

Ways to control a redesign budget

Option	When it helps	Risk
Phased release	Core pages can launch before secondary content	Temporary gaps must be planned, not accidental
Retain sound content	Existing pages already serve users well	Old inaccuracies may survive without review
Use an established design system	Original art direction is not commercially necessary	Generic implementation if not adapted carefully
Owner supplies content	The business has time and editorial skill	Project delay if content is not ready
Separate discovery from build	Scope is uncertain	Discovery still needs a budget and defined output

What to check before approving the budget

• Does the quotation include content, migration and testing?
• Are old URLs and redirects covered?
• Are recurring costs listed?
• Is VAT included where applicable?
• Who owns accounts, files and licences?
• What is outside scope?
• What happens if the launch must be rolled back?

The next practical step is to create a page-by-page redesign inventory before requesting a fixed build quotation.