How we structure a redesign: the four-phase process
Discover, design, build, launch and grow. What happens in each phase, what you get at the end of it, and why most sites take four to eight weeks.
On this page 5 sections
Key takeaways
- Redesigns usually fail on unclear goals, late content and decisions made from static mock-ups.
- Each phase ends with something you can hold: a brief, a prototype, a staging site, a live site.
- Most sites take four to eight weeks; shorter and content never arrives, longer and the brief drifts.
A redesign fails for predictable reasons: unclear goals, content arriving late, decisions made from static mock-ups, and launch treated as the finish line. Our process exists to remove each of those.
Phase one: discover (week one)#
A free fifteen-minute call, then a short discovery sprint. We interview stakeholders, review the current site’s analytics, content and accessibility, and agree a scope. You get a one-page brief, a sitemap and a fixed quote.
Phase two: design (weeks two to three)#
Wireframes become a design system, then high-fidelity pages with real content. We review together in the browser on actual devices. You get a Figma file, a prototype and a content plan with owners and deadlines.
Phase three: build (weeks three to six)#
A custom theme with hand-written CSS, custom blocks where they earn their place, and the editor configured for your team. Accessibility and performance are tested continuously, not at the end. You get a staging site, training and documentation.
Phase four: launch and grow (ongoing)#
Redirect map, a launch with no downtime, search console checked, forms tested on the live domain. Then thirty days of included care, and a monthly plan if you would like us to stay.
Why four to eight weeks#
Shorter and the content never arrives; longer and the brief drifts. Fixed scope, weekly check-ins and a shared backlog keep the middle from sagging.
Every phase ends with something you can hold: a brief, a prototype, a staging site, a launched site. No invisible progress.