An enterprise website redesign in the UK will usually cost between £35,000 and £200,000+. Here is what you should expect at each budget, what changes the price and how to compare agency proposals properly.
Vimalan Vijayasekaran
An enterprise website redesign in the UK will usually cost between £35,000 and £200,000+, depending on the size of the site, how much strategy and copywriting is needed, the platform, integrations, localisation and the amount of content being migrated.
For a B2B marketing website with around 30 to 100 core pages, a realistic full-service budget is often £50,000 to £90,000. That should cover strategy, messaging, copywriting for priority pages, UX, visual design, development, CMS setup, SEO migration, QA and launch support.
That is the short answer. The more useful answer is understanding what you are paying for.
These are ViDesigns scoping ranges for UK and international B2B website projects. They are not a market-wide average, and they do not include VAT, paid media, ongoing content production or the platform licence.
Page count alone does not make a website enterprise.
A 500-page site with one language and three templates can be easier to rebuild than a 60-page site with several regions, strict publishing permissions, custom forms, CRM routing and five teams approving every decision.
We normally treat a project as enterprise when it includes several of the following:
The number of people and systems involved usually affects the cost more than the number of pages.
This range can work when the business already has clear positioning, approved content and a sensible sitemap.
A typical scope might include:
The project stays within this range by limiting new strategy, copywriting, languages and custom technical work.
It is not realistic to expect a complete repositioning, 100 rewritten pages, several integrations and a large migration for £40,000. If an agency says it can do all of that, ask what is being templated, outsourced or left out.
This is the range we most often see for a serious B2B website project where the company is changing how it presents itself, not just replacing the design.
The work may include:
At this level, the agency should be able to manage the whole website, not just accept finished Figma files and build them.
Budgets move into six figures when the project includes things such as:
This does not mean every large site should cost £200,000. A well-planned CMS can migrate hundreds of similar items efficiently. The cost rises when pages, teams and systems all behave differently.
If the business is moving upmarket, entering a new category or changing its offer, the website cannot start with wireframes.
Someone first needs to answer:
If those answers are already agreed, the project is cheaper. If they are not, budget for proper strategy before design starts.
Copy is often underestimated because teams assume they can write it internally during the project.
That can work, but late copy delays design and usually creates more revision rounds.
Costs depend on whether the agency is:
A useful middle ground is to have the agency write the pages that define the story, then give the internal team a clear structure for lower-priority pages.
“We have 80 pages” does not tell an agency enough.
The better question is how many unique layouts and content types exist.
Eighty pages built from ten reusable templates can be efficient. Thirty pages with a different layout, interaction and approval group for each page may take longer.
Ask agencies to price around:
This makes proposals much easier to compare.
A migration is not copying text from one CMS into another.
The team needs to decide what should be kept, rewritten, merged or removed. It also needs to protect the pages that already bring in traffic, backlinks and leads.
Google recommends mapping old URLs to new destinations, using permanent redirects, updating internal links and monitoring both sites after launch. It also advises keeping redirects for at least one year. See Google's site-move guidance.
If organic traffic matters to the business, the proposal should include:
If none of that appears in the proposal, SEO migration is probably not included.
Common integrations include:
A simple form connection is very different from a two-way data flow with custom rules. List every integration before comparing quotes, including who owns it and what should happen when it fails.
Translation is only one part of a multilingual website.
The project may also need:
This can add design, development, content and QA work. It should be scoped early, even if some languages launch later.
Enterprise projects often lose more time in approvals than in production.
If ten people can comment but nobody has final authority, the project will drift. A good plan names one decision-maker for each workstream and sets a time limit for feedback.
More approval groups also mean more project management, documentation, training and handover work. That time should be visible in the proposal.
A short deadline does not automatically make the project impossible, but it changes how the team must work.
A fast enterprise launch normally needs:
Trying to fit the full wish list into a rushed launch usually increases cost and risk.
Most full enterprise website projects take three to six months.
A focused project can launch in 8 to 12 weeks when the strategy, content and approvals are ready. A larger migration with several languages, integrations or business units may take 6 to 12 months.
PhaseTypical durationDiscovery and strategy2 to 4 weeksSitemap, UX and copy3 to 6 weeksVisual design4 to 8 weeksDevelopment and CMS setup5 to 10 weeksMigration, QA and launch2 to 5 weeks
These phases can overlap. The timeline usually slips because content or feedback is late, not because the homepage took an extra day to build.
Usually not.
The agency fee pays for the work required to plan, write, design, build, migrate and launch the site. Webflow's own subscription is a separate contract.
Webflow Enterprise uses custom pricing. The final licence depends on the organisation's sites, traffic, content, users, governance and support needs. Some teams may be able to use Webflow's self-serve or Team plans instead. Check the current Webflow pricing and speak to Webflow before assuming Enterprise is required.
Enterprise plans can add features such as custom roles, SSO and SCIM, staging controls, activity logs and other security or governance controls. Webflow lists its current certifications and platform controls on its security page.
Do not accept a proposal that combines the platform licence and agency work into one unexplained figure. You should know what you are paying Webflow and what you are paying the agency.
The headline price is not always the final cost. Check whether the quote includes:
If the proposal says “SEO included”, ask exactly what that means. The same applies to accessibility, migration and integrations.
These are sample scopes, not published client fees.
Scope: 35 core pages, one language, existing brand, copy edits, new UX and design, Webflow build, one resource CMS, HubSpot forms and SEO migration.
Expected budget: £30,000 to £55,000
Expected timeline: 10 to 14 weeks
Scope: 50 core pages, stakeholder interviews, messaging, copywriting for priority pages, full design system, Webflow build, several CMS collections, CRM integration, SEO migration and training.
Expected budget: £60,000 to £90,000
Expected timeline: 14 to 22 weeks
Scope: Several sites or regions, 200+ URLs, multiple languages, content cleanup, localisation, custom integrations, formal governance, accessibility testing and phased launch.
Expected budget: £100,000 to £200,000+
Expected timeline: 6 to 12 months
Do not compare the total figure until you know whether the scopes match.
Use this checklist:
A £50,000 proposal may be better value than a £35,000 proposal if the cheaper option leaves your team to handle copy, migration, SEO and project management.
Yes, if the scope is genuinely smaller.
The cleanest ways to reduce cost are:
Cutting QA, SEO migration or CMS planning is not a sensible saving. Those are the areas where rushed work causes expensive problems after launch.
No.
Webflow is often a strong fit for an enterprise marketing website when the marketing team needs more control, reusable components, structured content and less reliance on engineering for everyday changes.
It may not be the right main platform when the website must handle complicated commerce, protected health information, deep application logic or unusual hosting requirements. In those cases, Webflow may still run the marketing site while a separate system handles the product or regulated data.
The platform should follow the business and technical requirements. It should not be chosen because an agency only knows one tool.
For a full B2B enterprise marketing website, a sensible starting range is £50,000 to £90,000. Focused redesigns may start around £35,000, while large, multilingual or integration-heavy migrations can exceed £100,000.
A 50-page website will often cost £45,000 to £90,000 when strategy, UX, design, development, content support, CMS setup, SEO migration and QA are included. The number of unique layouts and the state of the content matter more than the raw page count.
A Webflow migration may cost £35,000 to £100,000+ depending on whether the work is a straight rebuild or includes a redesign, new copy, content restructuring, integrations and localisation. Webflow's subscription is normally priced separately.
The cost is not just for design and development. Enterprise projects also require stakeholder alignment, content planning, CMS architecture, integrations, permissions, SEO protection, testing, training and project management across several teams.
Yes, if the scope is controlled, decision-makers are available and content is delivered on time. A 12-week launch often needs a smaller first release, parallel workstreams and lower-priority pages moved into a second phase.
Sometimes, but it adds risk because the design, content, CMS and URLs may all change together. For large sites, a phased move can be safer. Google also recommends changing one thing at a time where possible during a site move.
That depends on how often the website changes. Some teams need only occasional support. Others keep an agency for new pages, CRO, design, development and content. Treat post-launch work as a separate operating budget rather than hiding it inside the build cost.
You do not need a finished RFP to get an initial budget range.
Send us your current website, sitemap, target launch date, languages and known integrations. We can review the scope, flag the areas most likely to affect cost and tell you which budget bracket the project is likely to fall into.
