Website Redesign Process Explained

The website redesign process, when followed as a defined sequence of phases, produces better outcomes at lower cost than any approach that improvises as it goes.

Projects that follow a structured phase-gated process are 45% more likely to launch on time and within budget than those managed without formal phase gates. Understanding the process before you start is the first step to managing it well.

Each phase in a professional redesign has defined inputs, defined outputs, and a sign-off requirement before the next phase begins.

That structure is not bureaucracy, it is what prevents expensive rework, missed requirements, and the scope disagreements that derail most redesign projects.

Key Takeaways

• Five phases, defined outputs: Discovery, design, development, launch, and post-launch each have required deliverables and formal client sign-off before the next phase starts.
• Each phase gates the next: Design cannot start before discovery sign-off. Development cannot start before design approval. Skipping gates creates costly rework.
• Client involvement peaks in discovery and design: These phases require business knowledge, stakeholder alignment, and timely feedback to produce usable outputs.
• Content runs in parallel: Content writing and preparation must happen alongside design, not wait until development completes.
• Post-launch is a process phase: Monitoring, SEO continuity checks, and iteration in the first ninety days are deliverables, not afterthoughts.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

Phase 1: Discovery

Discovery is the phase that determines whether the entire project is built on evidence or assumption. Planning within the redesign process starts here, not at the wireframe stage.

What Discovery Involves

Discovery covers the complete audit of what exists, what is needed, and what success looks like. The output is a signed brief and project scope that gives every subsequent phase a clear mandate.

• Analytics audit: Current traffic sources, top-performing pages, conversion rates, and audience behavior patterns from GA4 and Search Console.
• Competitive analyzis: Assessment of competitor positioning, content depth, conversion architecture, and UX quality against an agreed benchmark.
• Stakeholder interviews: Structured sessions with sales, marketing, leadership, and customer-facing teams to capture goals and constraints.
• Audience research: Persona development and user journey mapping based on actual customer data, not assumptions.

The output of discovery is a signed project brief that documents goals, audience requirements, scope boundaries, and success criteria.

How Long Discovery Takes

For a typical small-to-mid business redesign, discovery runs two to four weeks.

Larger or more complex projects, enterprise sites, multi-language sites, or sites with significant integration requirements, require longer discovery. Compressing discovery to save time always costs more time in rework downstream.

What Clients Do During Discovery

Client responsibilities in discovery are active, not passive. Provide analytics access early, brief the agency on business goals in stakeholder sessions, and review and approve the discovery outputs before the project moves to Phase 2.

• Access provision: GA4, Search Console, current CMS, and any relevant CRM or marketing platform access must be granted at project kickoff.
• Stakeholder participation: Senior stakeholders who will approve designs should participate in discovery workshops, not receive summaries of them.
• Discovery output review: The project brief, sitemap draft, and requirements document should be reviewed carefully and signed off explicitly before design begins.

Phase 2: UX and Information Architecture

UX and information architecture is the phase that bridges discovery insights with visual design. The deliverables from this phase determine the structure of the entire site.

Sitemap and Navigation Design

The sitemap documents every page, its hierarchy, and its navigation placement. It is approved by the client before wireframes begin.

Changing site structure during design is expensive, approved sitemap changes trigger rework on any wireframes already completed.

• Page hierarchy: Every page is placed within the site hierarchy with its parent section, navigation label, and URL structure documented.
• Navigation architecture: Primary, secondary, and footer navigation are mapped with approved labels before any visual design begins.
• Page prioritization: The sitemap review is the right moment to rationalize the page count and eliminate low-value pages from scope.

Wireframing Key Page Templates

Low-fidelity wireframes define the layout, content blocks, and conversion flow for each page type. They are functional blueprints, not visual designs. Clients reviewing wireframes should focus on conversion architecture and content hierarchy, not visual style.

• Homepage wireframe: Maps the above-fold value proposition, primary navigation, conversion pathways, and featured content sections.
• Core service or product page: Defines the content hierarchy from problem context to solution detail to conversion trigger.
• Conversion page templates: Contact, booking, RFQ, and trial sign-up pages are wireframed with full conversion architecture detail.

User Flow Mapping

Key user journeys from landing to conversion are mapped and validated in this phase. See each redesign phase broken down for a detailed walkthrough of how UX outputs feed the subsequent design phase.

• Primary conversion paths: The two or three highest-value journeys are mapped end-to-end, from organic search landing to conversion.
• Secondary audience paths: If the site serves multiple audience segments, each segment's primary journey is validated before design begins.
• Mobile journey validation: Mobile user flows are validated separately, mobile users often follow different paths to conversion than desktop users.

Phase 3: Visual Design

Visual design is where the approved structure gets its aesthetic form. For a step-by-step redesign breakdown of what this phase produces, the key outputs are a design system and high-fidelity page mockups.

Design System Development

Before individual page templates are designed, the design system is developed and approved. This ensures consistency across every subsequent design and development output.

• Color palette: Primary, secondary, and neutral colors defined with accessibility contrast ratios verified against WCAG 2.1 AA standards.
• Typography system: Heading and body type scales defined with responsive sizing specifications for mobile and desktop breakpoints.
• Component library: Buttons, cards, forms, navigation elements, and content modules designed as reusable components, not one-off page elements.
• Spacing system: Consistent vertical and horizontal spacing scales documented so development translates design to code precisely.

High-Fidelity Mockups for Key Pages

Desktop and mobile mockups for the homepage, primary service page, and conversion page templates are designed, presented, and approved before development begins.

• Homepage mockup: Full desktop and mobile designs for the page that establishes brand position and primary conversion pathway.
• Core template mockups: One design per agreed template type, service page, case study, blog, contact, not one design per page.
• Mobile-first consideration: Mobile mockups should be reviewed with the same rigour as desktop, responsive issues discovered in development are more expensive to fix than those caught in design review.

Design Review and Revision Cycles

Client feedback on designs must be consolidated, specific, and submitted within the agreed review window. Rounds of revision are defined in scope, typically two rounds per design output.

• Consolidated feedback: All internal stakeholders review designs before any feedback is submitted. Multiple separate feedback threads from different stakeholders cause confusion and delays.
• Reference the brief: All feedback should reference the approved brief. "I personally prefer blue" is not a design note. "The primary CTA does not meet our accessibility standard" is.
• Revision scope: Revisions should refine the approved direction, not explore a different one. Direction changes after the first approved mockup are scope additions, not revisions.

Phase 4: Development and QA

For how agencies manage redesign projects through the build phase, the key principle is that development begins only from formally approved designs.

Building From Approved Designs

Development against unapproved or partially approved designs is a scope risk. Any design change requested after build has begun requires a change assessment with timeline and cost implications.

• Design specification handoff: Developers receive complete design specifications including spacing values, font sizes, interaction states, and responsive breakpoints.
• Component build order: Components are built in order of complexity, with the design system elements and shared components built before page templates.
• CMS configuration: The CMS is configured to match the content model developed in discovery, editors should not encounter any content types not planned from the start.

Content Integration and CMS Configuration

Content is loaded, the CMS is configured for the editorial workflow, and all integrations are connected and tested during the build phase.

• Content loading: Approved copy and assets are loaded into the CMS to the agreed content brief, either by the agency or the client, per the scope specification.
• Integration wiring: CRM, analytics, email marketing, ad pixels, and form notification systems are all connected and tested during build, not at launch.
• Editorial training: CMS training for the client's editorial team is scheduled before launch, not after, editors should be comfortable with the system before they need to use it urgently.

Quality Assurance Before Client Review

QA covers: cross-device and cross-browser testing, all form submissions, all integrations, page speed, accessibility checks, and redirect implementation.

QA should be completed before the client sees the site on staging, clients reviewing a QA-complete site give better feedback than clients hunting bugs.

• Device and browser matrix: Testing across iOS Safari, Android Chrome, desktop Chrome, Firefox, and Edge covers the majority of real user environments.
• Form and integration testing: Every form submission is tested from end to end: submission confirmation, notification email, CRM record, and any follow-up automation.
• Performance benchmarking: Core Web Vitals scores are recorded on staging and compared against the pre-launch baseline documented in discovery.

Phase 5: Launch and Post-Launch

Launch Day Checklist

DNS cutover, SSL verification, redirect testing, analytics verification, and Search Console setup are all launch-day tasks. Missing any of them creates post-launch problems that are avoidable.

• DNS and SSL: Nameserver update, SSL certificate installation, and HTTPS redirect verification are the first tasks after cutover.
• Redirect verification: Every redirect in the approved redirect map is tested on the live domain, not assumed to be working from staging tests.
• Analytics confirmation: GA4 and any conversion tracking must be verified on the live domain immediately after cutover, before traffic builds.

The 30-Day Post-Launch Monitoring Window

The first thirty days post-launch require active monitoring. Problems found early are cheap to fix. Problems discovered at ninety days have accumulated impact.

• Ranking monitoring: Track primary keyword rankings weekly from day one. Small drops in the first two weeks are normal. Significant drops require investigation.
• Crawl error monitoring: Search Console Coverage report should be checked daily for the first week and weekly for the following three weeks.
• Conversion rate tracking: Daily conversion rate comparison against the pre-launch baseline identifies performance issues before they accumulate.

90-Day Performance Review

At ninety days, a formal performance review compares conversion rates, traffic, and rankings against the pre-launch baseline.

For redesign timeline expectations and what the post-launch period looks like in practice, the review at ninety days is the first reliable point at which redesign impact can be measured.

• Traffic and rankings: Organic traffic and primary keyword positions compared against the equivalent ninety-day period from the previous year.
• Conversion rate comparison: Contact form submissions, demo bookings, or other primary conversion events compared against pre-launch rates.
• Goal achievement assessment: Each success criterion from the project brief is evaluated against available data at ninety days.

Managing the Process as a Project

For context on building and maintaining the formal project document that tracks all of this, refer to our project plan for redesign guide.

Your Responsibility as the Client

Client responsibilities at each phase are as critical to the project timeline as agency deliverables. Feedback delays are the primary cause of timeline overruns in redesign projects.

• Feedback turnaround: Agree a feedback window for each phase gate, three to five business days is standard. Missed windows push the timeline and may affect the agency's resource allocation.
• Single point of contact: One client contact collects, consolidates, and submits all internal feedback. Multiple feedback threads from multiple stakeholders at different times cause delays.
• Content delivery: Content scheduled for delivery by a specific date must arrive on that date. Content delays have a direct cascade effect on every subsequent phase.

How to Manage Feedback Rounds

Feedback must be consolidated before submission. Multiple stakeholders sending separate notes to the agency at different times causes confusion and creates version control problems.

• Internal consolidation session: Schedule a feedback session with all reviewers before the agency feedback deadline, not a series of individual email threads.
• Written, specific notes: Feedback should be specific and actionable: page, element, required change, and reason. General impressions are not buildable instructions.
• One submission per round: Submit one consolidated document per round, per agreed format. Feedback addendums after submission are scope risks.

What to Do When the Project Stalls

The two most common stall causes are content not being ready and stakeholders being unavailable for sign-off decisions.

• Content delay protocol: If content delivery is delayed, the timeline is reviewed immediately. A content delay that isn't acknowledged and planned for causes a compressed build phase.
• Stakeholder unavailability: A nominated deputy with authority to approve at each phase gate prevents the project from pausing every time the primary decision-maker travels.
• Formal timeline update: When a stall occurs, the project plan is formally updated with the new timeline communicated to all parties in writing.

Conclusion

The website redesign process is a structured, phase-gated project. Understanding the process before it starts makes you a more effective client, and more effective clients consistently produce better outcomes.

Every phase produces defined deliverables; every gate requires explicit sign-off; every stall has a documented response.

Map your current redesign plans against the five phases in this article. Identify which phases lack adequate time, resources, or approval processes. Those gaps are your highest-priority risks before the project begins.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

LOW/CODE Agency Runs a Defined Process on Every Redesign, No Improvisation

Every LOW/CODE Agency redesign follows a documented five-phase process with phase gates, defined deliverables, and client responsibilities at every stage.

There is no improvising the process to save time, the structure is what makes the timeline reliable and the outcome predictable.

We work as a strategic product team, not a dev shop. Your project gets a dedicated account manager, a written project plan before work begins, and weekly status reporting throughout.

• Discovery workshops: Structured stakeholder sessions, analytics audits, and brief development completed within a defined two-to-four-week discovery phase.
• Phase-gated design process: Sitemap, wireframes, design system, and high-fidelity mockups each go through formal client review and sign-off before the next phase opens.
• Development from approved designs: Build begins only from signed-off designs, with QA completed before client review of the staging site.
• Redirect map and SEO continuity: Every URL change is mapped and implemented before launch, with post-launch ranking monitoring built into the engagement.
• Content workstream management: Content brief, schedule, and review process managed alongside the design and build phases as a parallel workstream.
• Launch day checklist: DNS, SSL, redirects, analytics, and Search Console are all verified on launch day before the site opens to public traffic.
• Post-launch performance review: 30-day monitoring and 90-day performance review against the brief's success criteria are standard project deliverables.

LOW/CODE Agency has delivered 450+ digital products for clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku. We are a structured redesign process agency that delivers against a defined process, not a creative free-for-all.

Start with a scoping call