Website Redesign Project Stages with an Agency

Knowing the website redesign project stages with an agency before the project begins is the single most effective way to avoid the delays that derail most redesigns.

Most clients arrive at an agency relationship unsure of what they are supposed to be doing at each stage. That uncertainty leads to slow approvals, missed deadlines, and projects that overrun.

Research suggests that 78% of project delays are caused by delayed client approvals rather than agency delivery issues. The agency can only move as fast as you approve.

Understanding your role at every stage, and committing to the timelines that role requires, is what separates a smooth project from a difficult one.

Key Takeaways

• Five core stages exist in every agency redesign: Discovery, design, build, QA and testing, and launch, each with defined inputs, outputs, and client responsibilities.
• Your role shifts significantly across stages: From information provider in discovery to approver in design to reviewer in build, each stage demands something different from you.
• Delayed approvals are the top cause of overruns: Most redesign timeline problems trace back to slow client feedback, not agency performance failures.
• Each stage ends with a formal gate: Moving from discovery to design, or design to build, without a formal sign-off creates costly late-stage reversals.
• Post-launch is an active phase: The 30 to 90 days after launch require monitoring, bug resolution, and early optimization, the project is not done at go-live.

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

Overview of Agency Redesign Stages

Understanding the redesign process explained at a high level before diving into each stage makes the full picture easier to navigate.

The Five Stages at a Glance

Every professional agency redesign follows the same five-stage structure, with scope and complexity determining the duration of each.

• Discovery (2 to 4 weeks): Stakeholder interviews, analytics audit, competitor review, sitemap development, and project brief sign-off.
• Design (3 to 6 weeks): Wireframes, visual design system, high-fidelity page mockups, and formal design sign-off.
• Build (4 to 8 weeks): CMS setup, template development, integration wiring, content loading, and staging environment preparation.
• QA and testing (1 to 2 weeks): Cross-device testing, form and integration testing, redirect verification, performance testing, and accessibility checks.
• Launch and post-launch (ongoing): DNS cutover, go-live verification, 30-day monitoring, and 90-day performance review.

These stages overlap where dependencies allow, content writing, for example, can begin during design and continue into build.

How Stages Are Gated with Sign-Offs

Each stage ends with a deliverable, a review meeting, and a formal client approval before the next stage begins.

• Discovery gate: Signed project brief and approved sitemap. No wireframes begin before this approval.
• Design gate: Approved wireframes and approved visual design for all page templates. No development begins before this approval.
• Build gate: QA-complete staging site review and client sign-off. No launch preparation begins before this approval.
• Launch gate: Launch checklist completion and client go-live confirmation. Not triggered until all technical verifications pass.

Post-sign-off design changes are the most expensive type of scope addition in any redesign. The gate structure exists to make sign-off meaningful, not ceremonial.

The Client's Time Commitment at Each Stage

Be honest with yourself about your availability before the project begins.

• Discovery (10 to 20 hours): Stakeholder workshops, briefing sessions, analytics access provision, and discovery output review.
• Design (4 to 8 hours per review round): Wireframe review, design feedback sessions, and consolidated sign-off at each design milestone.
• Build (2 to 4 hours per week): Content delivery, CMS training, and staging site review at the end of the build phase.
• Launch and post-launch (2 to 4 hours per week): Launch verification, monitoring review, and 90-day performance assessment.

Stage 1: Discovery and Strategy

Discovery is the stage where the project earns its brief. For context on how discovery fits into the overall phase structure, see our guide to website redesign phases.

What the Agency Does in Discovery

The agency conducts the research and analyzis that informs every subsequent stage decision.

• Stakeholder interviews: Structured sessions with your sales, marketing, leadership, and customer-facing teams to capture goals, constraints, and buyer intelligence.
• Analytics audit: GA4, Search Console, and any available CRM data reviewed to understand current traffic, conversion performance, and audience behavior.
• Competitor analyzis: Assessment of competitor positioning, content quality, UX patterns, and conversion architecture to establish a benchmark to exceed.
• Technical audit: Current site architecture, platform capabilities, integration inventory, and technical debt assessment to inform build decisions.

The output of discovery is a project brief, an approved sitemap, and a requirements document.

What the Client Does in Discovery

Your contribution in discovery determines the quality of the brief the agency produces.

• Attend every workshop: Discovery sessions are not optional, your perspective and business context cannot be documented without your participation.
• Provide honest performance data: Share what is working and what is not on the current site. Agencies that only hear the positives build briefs on incomplete information.
• Grant access promptly: GA4, Search Console, CMS, and CRM access requested by the agency should be provided within 48 hours of the request.
• Review discovery outputs carefully: The project brief and sitemap are the foundation of the entire project. Read them carefully before signing off.

Key Deliverables at the End of Discovery

At minimum, the agency should deliver a project brief, approved sitemap, and requirements document before design begins.

• Project brief: Documents business goals, audience requirements, competitive context, success criteria, and scope boundaries.
• Sitemap: Every page, its hierarchy, navigation placement, and URL structure, the architectural map of the new site.
• Requirements document: Functional, technical, and content requirements captured from discovery workshops and stakeholder input.
• Optional deliverables: Personas, user journey maps, technical specifications, and competitive analyzis reports are delivered by more thorough agencies at this stage.

Stage 2: Design and Wireframes

How you behave in the design stage has the largest impact on whether the project stays on schedule. For context on how agencies handle redesigns through this stage, the key principle is structured, consolidated, specific feedback.

Wireframe Review: Reviewing Structure, Not Style

Wireframes show page structure and content hierarchy. They are not visual designs.

• What to review: Are the conversion paths correct? Is the content hierarchy logical? Are all required page elements present? Is the navigation architecture consistent with the approved sitemap?
• What not to review: Do not comment on fonts, colors, or visual style at this stage. Those decisions happen in the visual design stage.
• Consolidate before submitting: Collect all internal stakeholder feedback on wireframes before submitting a single consolidated response.
• Review against the brief: Every piece of wireframe feedback should reference the project brief. "This doesn't match the conversion goal we agreed in discovery" is a valid note. "I just don't like this layout" is not.

Visual Design Review: The First Look at the Real Site

The visual design presentation, mood boards, component designs, and page mockups, is where the site starts to look real.

• Evaluate against the brief: Does the visual design communicate the brand position and audience tone agreed in discovery?
• Be specific in feedback: "I don't like the hero section" is not actionable. "The hero headline font reads as too casual for our enterprise audience, can we try a geometric sans-serif?" is actionable.
• Distinguish preference from necessity: Personal aesthetic preferences are not design notes. Business-critical changes, accessibility failures, brand standard violations, are.
• One round at a time: Review the complete design, collect all feedback, submit once. Do not send incremental revisions as you notice more things.

Feedback Best Practices to Avoid Redesign Cycles

Poor feedback in the design stage is the most common cause of revision cycles that waste time and budget.

• Reference the brief explicitly: Every design note should connect to an objective, a brief requirement, or a success criterion.
• Consolidate all stakeholders: One person collects, reviews, and submits all feedback. Individual stakeholders do not contact the agency directly.
• Prioritize must-change vs nice-to-change: Mark each feedback item as critical or preference. The agency addresses critical items in revision; preferences may be considered but are not guaranteed.
• Avoid "can we try something different": Open-ended exploration requests are not design revisions, they are new design briefs and require scope assessment.

Design Sign-Off: Why It Must Be Absolute

A final design sign-off before build begins is the most important gate in the entire project.

• Post-sign-off change cost: Any design change after development begins requires the affected component or template to be rebuilt, not just updated. This adds cost and time.
• Sign-off authority: Only the project sponsor should hold final sign-off authority. Team members who were not in the design review process cannot reverse a signed approval.
• Pre-sign-off check: Before signing off, confirm that every requirement in the project brief has been addressed in the approved designs.
• Written sign-off: Design sign-off must be provided in writing, email or formal approval document. Verbal approvals are not sufficient for this gate.

Stage 3: Build and Development

The build stage is where the most technical work happens. For a complete picture of what this stage involves as a project management task, see our building the redesign project resource.

What Developers Are Building in This Stage

Clients often underestimate the volume of work happening simultaneously during build.

• CMS setup: Platform configuration, user roles, content types, custom fields, and editorial workflows are all set up before any content is loaded.
• Template development: Each approved page template is built to match the design specification, responsive across all agreed breakpoints.
• Integration wiring: CRM, analytics, email marketing, ad pixels, form notifications, and any custom integrations are connected, configured, and tested.
• Content loading: Copy, images, PDFs, and metadata are loaded into the CMS to populate the templates for staging review.

Content Migration and Population

Content is the most common cause of build stage delays.

• Content brief: The agency provides a content brief early in the build stage, a structured document specifying what content is needed, in what format, and by what date.
• Client delivery responsibility: Most agencies scope content as client-supplied unless explicitly stated otherwise. If you are responsible for copy, treat your delivery dates as seriously as you treat agency deadlines.
• Asset preparation: Images, PDFs, team headshots, and brand assets should be prepared and ready to deliver before the build stage begins.
• Late content consequences: A one-week content delivery delay typically causes a two-week build stage extension, as content loading and testing cannot proceed without it.

Staging Site Review: The Client's QA Moment

When the build is complete, the client reviews the staging environment, this is your quality control step before launch.

• Structured review checklist: Review every page, every form, every navigation item, and every CTA. Use a checklist rather than a casual scroll-through.
• Cross-device checking: Review the staging site on a mobile device and tablet, not just your desktop. Responsive issues caught on staging are cheaper to fix than those caught after launch.
• Form testing: Submit every form on the site and verify that notifications arrive correctly and CRM records are created.
• Content accuracy: Verify that all copy is final and correct, staging sign-off is the last opportunity to catch content errors before they go live.

Stage 4: Launch and Post-Launch

For expectations on timing, see the website redesign timeline guide for a realistic picture of how long the post-launch period runs.

Launch Day: Technical Go-Live Process

Launch day involves a sequence of technical steps that must be completed in order.

• DNS change: The domain's nameserver records are updated to point to the new hosting environment. This change propagates globally over 24 to 48 hours.
• SSL certificate: HTTPS is verified on the live domain, both the www and non-www versions must resolve correctly with a valid certificate.
• Redirect verification: Every redirect in the approved redirect map is tested on the live domain immediately after DNS propagation.
• Analytics confirmation: GA4 and any conversion tracking are verified on the live domain before public traffic builds, not assumed to be working from staging.

The 30-Day Post-Launch Window

The first thirty days post-launch are when the site earns its initial organic standing and when technical problems surface.

• Search Console monitoring: The GSC Coverage report is checked daily in the first week and weekly for the following three weeks.
• Ranking tracking: Primary keyword positions are tracked from week one. Small movement in the first two weeks is expected; significant drops require investigation.
• Conversion rate monitoring: Daily conversion rate comparison against the pre-launch baseline identifies performance problems early.
• Bug resolution: Minor bugs that surface post-launch are fixed promptly. A defined bug-fix turnaround time should be agreed as part of the agency engagement scope.

Measuring Early Performance Against Goals

The redesign's success against pre-agreed goals is evaluated in stages, not on day one.

• 30-day check: Traffic patterns, crawl health, and conversion rate trends. Too early for definitive conclusions but useful for identifying problems.
• 90-day review: The first reliable performance comparison against pre-launch baselines. Primary keyword rankings, organic traffic, and conversion rate are the primary metrics.
• Six-month review: Rankings and organic traffic from a rebuilt site often take three to six months to reflect the full impact of the new architecture.
• Goal achievement documentation: Each success criterion from the project brief is formally evaluated at the 90-day review and documented for project close.

Managing Your Role as Client

Managing a redesign project from the client side is primarily about decision quality and decision speed.

Consolidate Feedback Before Submitting

Serial feedback is the most damaging pattern in agency relationships.

• Internal consolidation: Run an internal feedback session before submitting anything to the agency. One list, one submission, per review round.
• One contact point: All feedback routes through a single client project lead. The agency should never receive conflicting instructions from multiple client contacts simultaneously.
• Hierarchy of feedback: Make it clear which feedback items are mandatory changes and which are preferences. Mandatory changes are addressed in the current round; preferences are considered.
• Submission deadline: Agree a date by which feedback will be submitted. Feedback that arrives after the deadline may affect the timeline.

Respect the Brief as the Decision Framework

When internal stakeholders push for changes that contradict the agreed brief, the brief is the decision tool.

• Brief as authority: "This was agreed in discovery because of X reason" is the most effective way to handle internal scope creep requests.
• Brief amendment process: If a genuine business change requires the brief to be updated, that is a formal change request, not an informal addition to the agency's next task list.
• Stakeholder alignment: If your organization's internal stakeholders disagree about direction, resolve that disagreement internally before submitting feedback. The agency is not a mediator.
• Brand consistency: The approved design system is the standard for every new decision. Requests that deviate from it require a change request, not a quick email.

Make Decisions Promptly

An agency can only move at the pace of the slowest client decision.

• Decision authority in place: Before the project starts, confirm who can approve at each stage and ensure that person is available throughout the project.
• Deputy approval authority: Name a deputy for every approval stage. If the primary approver travels or is unavailable, the project does not stall.
• Agreed review windows: Commit to feedback windows in the project plan, three to five business days per review round, and treat those windows as actual deadlines.
• Decision protocol: For any decision that could affect scope or timeline, agree a decision-by date upfront. Open-ended decisions are a timeline risk.

Conclusion

Agency redesign projects succeed when clients and agencies are clear on roles, responsibilities, and gates at every stage. The process itself is the project management.

When both parties understand what is expected of them, when it is expected, and what happens if those expectations are not met, the project runs as designed.

Before signing with any agency, ask them to walk you through exactly what happens at each stage and what they need from you at every step.

The clarity and specificity of that answer tells you exactly how organized their process is.

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 Keeps Clients Informed at Every Project Stage

LOW/CODE Agency runs every redesign project through a structured five-stage process with dedicated client communication at each stage. You always know where the project is, what is coming next, and what we need from you.

We operate as a strategic product team, not a dev shop. Every client has a dedicated account manager, a written project plan from kickoff, and clear expectations documented at every stage gate.

• Pre-project scoping: Complete scope documentation, RACI matrix, and project plan delivered before any design work is commissioned.
• Structured discovery stage: Stakeholder workshops, analytics audit, brief development, and signed sitemap, all completed with client collaboration within a defined two-to-four-week window.
• Design stage management: Wireframe review sessions, consolidated design feedback process, and formal sign-off at each design milestone before development begins.
• Build stage reporting: Weekly status reports during build, content brief delivery, and a structured staging site review process with a checklist.
• QA and testing coordination: Full pre-launch QA across devices and browsers, form and integration testing, and redirect verification before client staging review.
• Launch day management: DNS, SSL, redirect verification, analytics confirmation, and Search Console setup all handled and verified on launch day.
• Post-launch monitoring: 30-day monitoring and 90-day performance review against agreed success criteria as standard project deliverables.

LOW/CODE Agency has delivered 450+ digital products for clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku. Our agency redesign services include a structured stage-by-stage process that keeps clients informed and projects on track.

Start with a scoping call