An 18-page B2B website can launch in 12 weeks. The same site can take 24 weeks when six stakeholders review every screen, product copy waits on subject experts and CRM access arrives during testing.
For most £1m–£50m B2B companies, a credible B2B website redesign timeline is 12–16 calendar weeks from kick-off to launch. Eight to ten weeks is possible for a tightly controlled scope. A rebrand, complex migration or custom integration pushes the work towards 18–26 weeks.
These are planning ranges, not a universal industry average. The standard band sits inside the 8–16-week range in our guide to what a conversion-led redesign must achieve. That guide covers performance; this one stays with the calendar, dependencies and delay maths.
The realistic B2B website redesign timeline
The useful answer depends on what “redesign” contains.
| Project type | Launch range | What must be true |
|---|---|---|
| Focused refresh | 8–10 weeks | 5–12 core pages, settled brand and positioning, standard forms, little migration |
| Standard B2B redesign | 12–16 weeks | 12–35 core pages, 5–8 reusable templates, partial copy rewrite, one CMS and routine CRM integration |
| Complex rebuild | 18–26 weeks | Replatforming, 35–100+ pages, substantial new copy, custom integrations or several approval groups |
| Multi-market programme | 26+ weeks | Several languages, regional owners, regulated content or product-level functionality |
Page count is only a proxy. A 60-page site using six templates can be quicker than a 20-page site with a pricing calculator, gated portal and three CRM workflows. Template count, copy readiness, legacy URL volume, integration uncertainty and approval speed predict the date better.
Before allocating four months, separate the signs that an ageing B2B site needs a full rethink from issues that one focused release can solve. If a paid campaign has the urgent deadline, a dedicated campaign page for paid traffic can often ship while the main redesign continues.
B2B website redesign timeline, phase by phase
These phases overlap. Adding every duration produces more weeks of activity than the project takes in calendar time. The launch date follows the critical path: the longest chain of dependent work.
| Phase | Typical duration | Calendar window in a 14-week plan |
|---|---|---|
| Mobilisation and scope | 3–5 working days | Week 1 |
| Evidence, structure and messaging | 2–3 weeks | Weeks 1–3 |
| Wireframes and copy | 3–4 weeks | Weeks 3–6 |
| Visual design | 2–3 weeks | Weeks 5–8 |
| Development, integrations and content population | 4–6 weeks | Weeks 7–12 |
| QA, migration and launch | 1–2 weeks | Weeks 13–14 |
Phase 1: mobilisation and scope — 3–5 working days
Week one turns a proposal into a working project. The team confirms the launch scope, page and template estimates, owners, review dates, CMS, integrations and access requirements.
The exit condition is specific: one approved scope, one accountable approver and no unknown owner for analytics, DNS, CRM or legal review. A kick-off meeting alone does not complete this phase.
Phase 2: evidence, structure and messaging — 2–3 weeks
The team reviews existing performance evidence, content and paid-traffic destinations, then produces the sitemap, page-template list and message hierarchy. This is enough analysis to brief the build; it is not a full conversion-audit exercise.
An unresolved identity changes the schedule. If leadership is still debating whether the company should sound technical, provocative or reassuring, settle how the brand’s personality should affect B2B buyers before treating visual design as a two-week task.
Phase 3: wireframes and copy — 3–4 weeks
Wireframes and copy should move together. A wireframe without realistic copy hides hierarchy problems; finished copy created before a page structure exists usually needs rewriting.
The efficient sequence is to approve the homepage and two or three priority page types first. Supporting pages can then follow the same rules while visual work begins. Copy does not need to be complete across the whole site, but the headline, proof, calls to action and objections on every launch-critical template do.
Phase 4: visual design — 2–3 weeks
Visual design applies the brand to an approved structure. For a typical B2B site, that means a component system plus representative desktop and mobile designs for roughly five to eight templates—not a bespoke composition for every URL.
Two review gates are normally enough: the core visual direction, then the representative templates and states. A request to compare three new creative directions at the second gate is new brand exploration, not routine refinement, and should change the date.
Phase 5: development, integrations and population — 4–6 weeks
Development can begin once the core components and priority templates are approved. It covers responsive behaviour, CMS collections, forms, CRM routing, analytics events, consent tools and content population.
A useful scope for a full B2B design-and-build engagement should name the CMS, every form destination, the tracked events and who supplies each credential. “Connect HubSpot” is not an acceptance criterion.
Standard forms may take days. A calculator with conditional logic, an account portal, ERP data or single sign-on can add two to eight weeks because discovery, security review and acceptance testing sit outside normal page development.
Phase 6: QA, migration and launch — 1–2 weeks
QA is scheduled production work, not spare time at the end. It includes browser and device checks, forms, CRM delivery, analytics, accessibility, metadata, redirects, content accuracy and CMS permissions.
Launch preparation adds backups, DNS changes, a rollback route and named people to verify production forms. Allow five working days after release for stabilisation and monitoring. That period is separate from longer-term optimisation.
What stretches a B2B redesign schedule
The allowances below are planning effects, not fixed tariffs. Several can overlap; add time only where a dependency lands on the critical path.
| Dependency | Sensible allowance |
|---|---|
| Positioning or visual identity still unresolved | +3–6 weeks |
| Priority copy depends on five or more subject experts | +2–5 weeks |
| 100+ legacy URLs need individual keep, merge or redirect decisions | +2–4 weeks |
| Custom CRM, ERP, portal or calculator integration | +2–8 weeks |
| Each additional language with local review | +2–6 weeks |
| Security, legal or compliance review starts late | +1–4 weeks |
| Photography or video required before design sign-off | +2–4 weeks |
Approval latency deserves its own calculation. Suppose the plan includes three sequential review gates, each allowing two working days. If consolidated feedback actually arrives after five days, the delay is:
(5 days − 2 days) × 3 gates = 9 working days
That is nearly two calendar weeks added without one extra page being designed or built. The team cannot recover all of it by working faster because development was waiting for approved inputs.
A worked 14-week redesign timeline
Take a composite £8m UK compliance consultancy. Its scope includes 28 marketing pages, seven reusable templates, one language, an established identity, ten priority-page rewrites, editing and migration of 18 supporting pages, 86 legacy URLs and standard HubSpot forms. One marketing lead consolidates feedback within two working days.
| Weeks | Work completed |
|---|---|
| 1–2 | Scope, evidence review, page inventory and access |
| 2–3 | Sitemap, template list and message hierarchy |
| 3–6 | Priority copy and wireframes |
| 5–8 | Visual system and representative templates |
| 7–12 | CMS build, HubSpot routing and content population |
| 13 | Redirects, QA and user acceptance testing |
| 14 | Production launch and stabilisation |
The copy workload is about 16 writer-days: ten priority pages at one day each, plus six days to edit and migrate the remaining 18. It fits because writing overlaps design and development rather than waiting for a separate “content phase” to end.
QA still has volume. Seven templates across three viewports and three browsers create 63 baseline layout checks before anyone tests forms, CRM routing or tracking.
If the three approval gates take five days rather than two, the launch moves towards week 16. If leadership also reopens the identity during visual design, an 18–20-week outcome is more honest than compressing QA to protect an obsolete date.
How to keep the launch date credible
A deadline becomes reliable when decisions are treated as deliverables.
- Name one approver and require one consolidated response at each gate.
- Book subject experts, legal, IT and leadership reviews during week one.
- Give reviews a two-working-day service level and record slippage immediately.
- Freeze the sitemap, priority copy and visual system at explicit gates.
- Separate launch-critical requirements from a documented post-launch backlog.
- Hold 10–15% contingency against known uncertainty; do not hide it as unused production time.
Define launch as a stable production site with working forms, tracking and redirects. It is not the end of improvement. New hypotheses and experiments belong in a measured post-launch improvement programme, where they can be assessed against a clean baseline rather than squeezed into launch week.
FAQ
How long does a B2B website redesign take?
Allow 12–16 calendar weeks for a standard mid-market site with an established brand, partial copy rewrite, routine CMS and CRM work, and prompt consolidated feedback. Use 18–26 weeks for a rebrand, replatforming, extensive migration or custom functionality.
Can a B2B website be redesigned in eight weeks?
Yes, if the scope is narrow: few templates, settled messaging, ready copy, standard integrations and one fast approver. Eight weeks is not credible for a strategic rewrite, new identity and complex build disguised as one project.
Which phase takes the longest?
Development and content population usually occupy the largest block at four to six weeks. The critical path may still be copy or approvals: a five-week activity that can proceed independently does less damage than a three-day decision that blocks the whole build.
Does all website copy need to be finished before design starts?
No. Priority-template copy must be sufficiently mature to test hierarchy and layout. Supporting copy can continue once those patterns are approved, provided it follows the same content model and arrives before population and QA.
How much internal team time should a company reserve?
A marketing lead should expect roughly two to four hours a week, with more during content review and UAT. The accountable approver needs four or five focused review slots of 45–60 minutes. Subject experts commonly need one 60–90-minute interview plus a factual review.
Summary
- A standard B2B redesign needs 12–16 calendar weeks from kick-off to launch.
- Eight to ten weeks works only for a narrow scope with ready inputs and fast decisions.
- Rebrands, custom integrations, large migrations and multiple markets push the plan towards 18–26 weeks or more.
- Phases overlap, so the critical path—not the sum of every task—sets the date.
- Reserve 1–2 weeks for QA and launch, plus 10–15% contingency for known uncertainty.
Actualyse designs and rebuilds B2B websites that turn research visits into qualified pipeline. Book a call to talk through where yours stands.
