In short
A focused website refresh may take 4–8 weeks, while a custom redesign commonly takes 10–20 weeks. Content-heavy, multilingual, ecommerce, or deeply integrated projects may need 20–36 weeks or more. The reliable schedule depends on discovery, content, templates, migration, integrations, review time, and launch risk.
Planning ranges
| Project | Typical range |
|---|---|
| Focused visual/content refresh | 4–8 weeks |
| Small custom redesign | 8–14 weeks |
| Typical custom company site | 10–20 weeks |
| Content-heavy or multilingual site | 16–28 weeks |
| Ecommerce or integrated platform | 20–36+ weeks |
These ranges assume an available decision-maker and a managed content process. A ten-page redesign can run late when every page is unique or nobody owns the copy.
A phase-by-phase timeline
Baseline and discovery: 1–3 weeks
Capture analytics, search performance, content, URLs, accessibility, performance, integrations, and operational constraints. Agree on audiences, outcomes, scope, and risks.
Architecture and content: 2–6 weeks
Create the sitemap, page outlines, content model, migration decisions, and representative copy. This work often overlaps discovery and design, but priority templates need real content before final layout.
UX and visual system: 3–6 weeks
Resolve journeys and hierarchy, establish the visual direction, then extend it across templates, components, responsive behaviour, and important states.
Development and CMS: 4–10 weeks
Build components and templates, model content, connect integrations, implement analytics, accessibility, performance, and technical SEO. Development can overlap later design when the system is stable and the disciplines work closely.
Migration, QA, and launch: 2–5 weeks
Enter or migrate content, implement redirects, test journeys and devices, train editors, deploy, and monitor production.
The dependencies that move dates
- copy approval;
- photography, video, or translation;
- stakeholder availability;
- domain and system access;
- CRM, payment, identity, or product-data integration;
- legal, security, or procurement review;
- legacy-content condition;
- redirect mapping;
- unresolved brand decisions.
A schedule should name these alongside agency production. They are project work even when performed by the client.
How to shorten the schedule responsibly
- Appoint one final decision-maker.
- Inventory content and URLs before design.
- Draft the highest-priority pages early.
- Reduce unique templates.
- Separate launch-critical scope from phase two.
- Test integration access immediately.
- Consolidate feedback on scheduled dates.
- Reuse sound technology and components.
Do not shorten the schedule by deleting migration planning, accessibility, QA, or production monitoring. Those omissions borrow time from after launch.
Fixed date, flexible scope
If a product launch or event creates a real deadline, define the smallest complete release. Protect priority journeys, content, accessibility, performance, analytics, and redirects; move lower-confidence sections or features into an explicit second release.
Fixed date, budget, scope, and unresolved requirements cannot all remain fixed. Decide which variable can move before pressure makes the decision accidentally.
Common questions
Can a website be redesigned in one month?
Yes, for a focused scope with ready content, few templates, available stakeholders, and straightforward technology. It is not a reliable default for a custom migration.
What takes longest in a redesign?
Content, stakeholder decisions, migration, and integrations often create more calendar risk than interface production. Their ownership should appear in the plan.
Can design and development overlap?
Yes. Development can begin after representative templates and the component system stabilise, provided designers and engineers resolve changes together.
When should copy be ready?
Page strategy and representative copy should exist before templates are finalised. Remaining final copy can progress alongside design under firm deadlines.
How much time should launch QA receive?
Reserve at least one to two focused weeks for a small custom site and more for complex migration, languages, transactions, or integrations.
