The Short Answer
| Project Size | Typical Timeline |
|---|---|
| Small site (5–10 pages) | 6–10 weeks |
| Medium site (10–30 pages) | 10–16 weeks |
| Large site (30+ pages, complex integrations) | 16–24+ weeks |
These timelines assume a reasonably smooth process: client content is delivered on time, feedback rounds stay within agreed windows, and there are no major pivots mid-project. Each of those assumptions is worth examining.
Phase-by-Phase Timeline Breakdown
Phase 1: Discovery and Strategy (1–3 weeks)
This is where you establish the foundation: what the site needs to do, who it serves, what content exists vs. what needs to be created, and what the technical requirements are.
What happens in this phase:
- Stakeholder interviews and goals alignment
- Site audit (what stays, what changes, what gets cut)
- Sitemap and information architecture
- Content inventory and gap analysis
- Technical requirements: CMS, integrations, hosting
What slows it down: stakeholder availability, unclear goals, disagreement about site structure among client-side decision makers.
Phase 2: Design (2–5 weeks)
Design typically starts with wireframes — structural layouts without visual design — and moves to high-fidelity mockups once structure is approved.
Timeline factors:
- Number of unique page templates (a 10-page site with 10 unique templates takes longer than a 30-page site using 5 templates)
- Number of feedback rounds included
- Whether the brand is established or needs development alongside the site
Most projects run two design feedback rounds. Each round takes 1–3 business days on the agency side and requires 2–5 days for client review. Build both into your timeline.
Phase 3: Development (3–6 weeks)
Development time scales with the number of unique page builds, the complexity of integrations, and the CMS platform.
What takes longer than clients expect:
- Form logic, conditional fields, and CRM integrations
- Blog/news section setup with custom post types
- Mobile optimization and cross-browser QA
- Performance optimization and page speed work
A standard 10-page Webflow or WordPress site with a contact form and blog takes roughly 3–4 weeks to build. Add an e-commerce layer or complex data integrations and that stretches to 6–8 weeks.
Phase 4: Content and QA (1–3 weeks)
This is the phase most projects underestimate. Before launch, all content needs to be loaded, all pages need to be proofed, and every link, form, and integration needs to be tested.
If content is client-provided, the agency is dependent on the client to deliver it — and late content is the single most common cause of delayed launches. A content freeze date in the contract is not optional.
Phase 5: Launch (1 week)
DNS transfer, hosting migration, final cross-device testing, and redirects from old URLs to new. Most launches take 3–5 business days when everything is ready. Surprises that add time: domain registrar complexity, redirect mapping for large sites, and post-launch content changes.
What Actually Causes Projects to Run Long
In practice, most website redesign delays come down to one of four things:
- Late client content. The site is built and waiting. The copy and images are not ready.
- Feedback lag. Clients take longer than agreed to review designs, which telescopes the entire schedule.
- Scope expansion. New pages and features get added mid-project without formal timeline adjustments.
- Too many decision makers. Design feedback that has to travel through three levels of internal approval adds weeks.
Address all four in your scope and contract before work begins. Specify content deadlines, feedback windows, the change order process, and who has final sign-off authority.
How to Build a Realistic Project Timeline
When you scope a website redesign, build the timeline from the phase durations above — then add buffer. A good rule: add 15–20% to your internal estimates, then set that as the client-facing timeline.
Where buffer matters most:
- After content freeze date: allow for late content
- After each design round: allow for revision requests that require more than one response
- Before launch: allow for last-minute stakeholder changes
ScopeStack lets you build modular scope templates that include timeline estimates per phase — so when a new web redesign project comes in, you are not starting the estimate from scratch. The project scope and proposal Gems give you a consistent baseline that accounts for these real-world variables.
The Scope Is What Determines the Timeline
The most accurate answer to "how long does a website redesign take?" is: as long as the scope requires, plus however long client delays add.
A tight scope with clear deliverables, defined feedback windows, and explicit content deadlines will almost always finish faster than an equivalent-sized project with loose scope — not because the work is less, but because there are fewer variables for the timeline to absorb.
Define the scope clearly. Set the timeline from that scope. Hold both sides to it.
Build Your Timeline
From a Real Scope
ScopeStack's Timeline Builder Gem creates phase-by-phase project schedules from your scope brief — with built-in buffer and milestone dates your clients can actually hold you to.
Get the Toolkit →