WEB DESIGN & DEVELOPMENT / A PRACTICAL ANSWER
How long should a website redesign take?
The short answer
A useful redesign timeline follows the work, dependencies and decisions needed for launch. Page count alone cannot determine it. Content preparation, integrations, stakeholder approvals and migration checks can each become the critical path. Ask for a milestone plan with responsibilities and assumptions rather than an unexplained delivery date.
What to agree
Separate discovery, content, design, development, testing and release. Some tasks can overlap, but the plan should show what each stage depends on. A design review cannot resolve an offer that has not been agreed, and an integration cannot be checked without access.
How to decide
Identify who approves each milestone and how feedback will be consolidated. Record holiday periods, unavailable specialists and fixed campaign dates. If the deadline cannot move, agree which scope can change and what a smaller first release would still need to accomplish.
ILLUSTRATIVE EXAMPLE / NOT A CLIENT RESULT
Make it concrete.
For a booking-site redesign, room information might be ready while booking-engine access is delayed. The plan should expose that dependency early instead of assuming the new design can be connected on launch day.
Before you commission
- Name an owner for every approval.
- Confirm access and content readiness before scheduling.
- Agree the effect of late changes on scope and dates.
A plain-text worksheet. Downloading does not send us your details.
FROM THE QUESTION TO THE WORK
A useful next step.
Bring the decision, the existing situation and the information you have. We can help define a scope before you commit to a wider project.
Explore the relevant service