How Agencies Handle Website Redesign Projects

Understanding how agencies handle website redesign projects makes you a better client. Clients who understand the agency's process structure, know what their own responsibilities are, and arrive at the project with realistic expectations consistently get better results than clients who encounter the process as a series of surprises.

The redesign process is a collaborative engagement, and your contribution to it is as important as the agency's.

This guide walks through how a professional agency structures a redesign project from kickoff to launch: the phase structure, project management practices, timeline management, deliverables, and the criteria you should use to evaluate whether an agency you are considering operates to professional standards.

Key Takeaways

• Agencies run phase-gated projects: Professional agencies follow a structured process, discovery through design through development through launch, with formal sign-off at each stage gate.
• Client involvement is active, not passive: Agencies need timely feedback, delivered content, and clear decisions from clients; a slow client is a slower and more expensive project.
• Communication structure is established at kickoff: Good agencies define how often they will report, where feedback should be submitted, and who the single point of contact is on each side.
• Agencies manage risk proactively: Professional agencies flag scope risks, content delays, and integration problems before they become launch-blocking crises, not after.
• You pay for judgment, not just hours: The value of an experienced agency is in the decisions they make and the problems they prevent, not simply in the time they spend building.

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

The Agency's Process Structure

A professional agency's agency redesign process overview is not improvised project by project. It is a documented, repeatable structure with defined phases, deliverables, and sign-off requirements that protect both the client's investment and the agency's time.

Understanding why this structure exists, not just what it looks like, helps clients engage with it productively rather than treating phase gates as bureaucratic obstacles.

Discovery: Where the Agency Earns Its Fee

Discovery is the most important phase of a redesign project and the one most frequently undervalued by clients who are eager to see design work begin.

• Discovery prevents expensive rework in later phases: Design decisions made without research, competitive analyzis, and stakeholder alignment must frequently be undone; discovery prevents the rework cost that results from designing before thinking.
• The brief produced in discovery governs every subsequent decision: A well-structured discovery phase produces a project brief that defines goals, audience priorities, success metrics, and design constraints; this brief is the project's reference document.
• Agency discovery includes both client and external research: Stakeholder interviews, analytics review, competitor analyzis, and current site audit all happen in discovery; the output reflects reality, not assumption.
• Clients who invest in discovery get better design faster: A designer working from a comprehensive brief can produce appropriate first concepts without multiple rounds of misdirected feedback.

Phase Gates and Formal Sign-Off

At the end of each project phase, the agency presents deliverables for client review and approval before the next phase begins.

• No phase begins without the previous phase being approved: This structure protects the client's budget from design work built on unapproved foundations and protects the agency from scope disputes about what was agreed.
• Sign-off is a binding commitment, not a formality: When a client signs off on wireframes, they are approving the information architecture for the site. Requesting changes to that architecture during visual design is a scope change, not a revision.
• Formal sign-off creates a documented decision trail: When disagreements arise later in a project, phase sign-offs provide a clear record of what was agreed at each stage, preventing "but I thought we agreed" conflicts.

Roles Within the Agency Team

Understanding who does what within the agency team prevents requests from going to the wrong person and expectations from being placed on people who cannot fulfill them.

• Account or project manager handles communication and coordination: This person is your primary contact, tracks milestones, manages the feedback cycle, and escalates issues to the relevant specialist.
• Strategist or UX lead handles discovery and information architecture: This person runs the discovery phase, produces the project brief, and defines the site structure that informs all design work.
• Designer owns visual design decisions: The designer translates the brief and wireframes into the visual experience; design decisions within the approved brief are the designer's professional judgment.
• Developer builds and configures the technical implementation: The developer translates approved designs into a functioning site; technical implementation decisions that do not affect the approved design are the developer's professional domain.

What Happens at Each Project Stage

Following the redesign stages with agency framework stage by stage clarifies the client's role and responsibilities at each point in the engagement.

Kickoff: Aligning Before Any Work Begins

The kickoff meeting is not a formality. It is the project's foundation, and the quality of the outcomes it produces determines how smoothly the engagement runs.

• Project goals must be agreed and documented at kickoff: Ambiguous goals, such as "improve the website," must be converted into specific, measurable objectives before any design brief can be written.
• Client responsibilities must be assigned with deadlines at kickoff: Content delivery dates, feedback response timeframes, and approval authority must be explicitly agreed and written into the project plan at the first meeting.
• Communication protocols must be established at kickoff: Where feedback is submitted, who the single client-side decision-maker is, and how change requests are handled must all be agreed before any work begins.
• The first deliverable and its due date must be confirmed at kickoff: Leaving the kickoff without a next-action date and a named responsible person on both sides creates the ambiguity that delays projects from their first week.

Discovery: Information Gathering and Brief Production

The discovery phase transforms the agreed goals from the kickoff into a researched, structured brief that governs the design work.

• Stakeholder interviews gather institutional knowledge the agency cannot access otherwise: What the business does, who it serves, what competitors it faces, and what the previous site failed to achieve are all inputs that only come from people inside the organization.
• Analytics review reveals how the current site actually performs: Traffic patterns, high-performing pages, conversion paths, and exit points tell the agency where the current site succeeds and fails before any design assumptions are made.
• The project brief must be client-approved before design begins: The brief is the agency's mandate; design work built on a brief that the client has not reviewed and approved is design work that may need to be redone.

Design and Review Cycles

Design moves through wireframes before visual mockups, and each stage has a defined review process that clients must engage with specifically and promptly.

• Wireframes define information architecture before visual treatment: Reviewing and approving wireframes confirms that the page structure, navigation, and content hierarchy are correct before visual design is applied.
• Visual mockups represent the approved visual direction for the site: Feedback on visual mockups should address whether the design achieves the agreed brief goals; aesthetic preference that conflicts with the brief is a scope change.
• Consolidated feedback accelerates the review cycle: Feedback from one person representing all stakeholders, submitted in the agreed format within the agreed timeframe, allows the design team to progress; fragmented feedback from multiple sources stalls the project.
• One to two formal review rounds per output is the professional standard: More than two rounds of revision on any single output typically indicates either a brief problem, a feedback quality problem, or a design problem; all three have solutions.

Development, QA, and Client Preview

After design approval, development produces the staging site that represents the completed implementation of the approved designs.

• Agency QA is completed before client preview: A professional agency conducts its own quality assurance review before presenting the staging site to the client; the client preview is for final approval, not for bug discovery.
• Client preview is for validation, not testing: The client's job at the preview stage is to verify that the site accurately reflects the approved designs and agreed functionality, not to test edge cases or find technical errors.
• Launch approval is the final formal sign-off: The client's explicit approval to launch the site represents the end of the agency's delivery obligation and the beginning of the post-launch support period.

How Agencies Manage the Project

Agency project plan structure at a professional agency uses dedicated project management tools, regular reporting, and formal change management to keep projects on track and keep clients informed.

Project Management Tools and Dashboards

Professional agencies use project management platforms to track tasks, deadlines, and deliverables in a way that provides both the agency and the client with accurate, real-time visibility.

• Client access to the project dashboard eliminates status uncertainty: Read access to the project's Asana, Notion, Monday, or ClickUp board allows clients to check progress without requesting status updates from the project manager.
• Task-level tracking catches delays before they become risks: A project manager monitoring individual task completion against deadline can identify a slipping deliverable days before it affects the phase milestone.
• Shared tooling creates a single source of truth: When both agency and client use the same project management system for decisions, approvals, and feedback, there is no ambiguity about what was agreed or when.

Milestone Reviews and Progress Reporting

Professional agencies provide scheduled progress updates that keep clients informed without requiring constant follow-up communication.

• Weekly or bi-weekly reports cover completed work, upcoming milestones, and identified risks: A standard progress report format prevents the "what's happening with my site?" problem that frustrates clients and consumes agency project management time.
• Milestone reviews provide a formal check-in at each phase gate: These reviews confirm that the completed phase meets its objectives before the team moves forward, and give the client the opportunity to raise concerns before they become late-project problems.
• Risk escalation should happen immediately when a risk is identified: A professional agency flags a content delivery risk or integration complexity issue when it is discovered, not at the next scheduled review meeting.

Change Management Protocols

Any scope change requested after a phase sign-off must be evaluated for its impact on timeline and budget before it is executed.

• The change request process exists to protect the client's budget: A change that adds two weeks to the development phase and $3,000 in cost should be approved by the client before the work begins, not discovered on the final invoice.
• Every change is documented with impact assessment and client approval: A professional change management protocol documents the request, the impact on timeline and cost, and the client's written approval before any work begins.
• Changes requested during development are more expensive than changes requested during design: The earlier in the project a change is made, the lower its cost; the further into the project, the higher the cost of implementing it.

Agency Timeline Management

The typical agency project timeline varies by project scale and complexity, but professional agencies manage timeline risk proactively rather than discovering slippage when it is too late to recover.

Typical Timelines by Project Size

Timeline expectations should be calibrated to the scope of the project and the content delivery capacity of the client.

• Small business sites of 5 to 10 pages typically take 8 to 12 weeks: This assumes on-time content delivery from the client and timely feedback at each design review stage.
• Mid-size redesigns of 10 to 30 pages typically take 12 to 18 weeks: Greater content volume, more complex integrations, and more stakeholders at each review stage extend the timeline proportionally.
• Enterprise and platform migration projects typically take 18 to 30 weeks: Large-scale projects with complex technical integrations, extensive content migration, and multi-level approval requirements require extended planning and execution timelines.
• All timelines assume compliant client behavior: Client-side content delays, late feedback, and stakeholder approval bottlenecks extend every timeline; the ranges above reflect on-schedule client behavior.

The Most Common Causes of Agency Timeline Slippage

The majority of website redesign timeline overruns are caused by client-side factors, not agency-side failures.

• Content delays are the most common cause of timeline extension: Waiting for client-provided copy, images, and assets delays development; a professional agency builds content deadlines into the project plan with explicit timelines.
• Late feedback extends the design review cycle: When clients take two weeks to provide feedback on wireframes that were due a review response within five days, the delay cascades through every subsequent phase.
• Scope additions after sign-off require rescheduling: Any addition to the agreed scope creates work that was not planned; adding features during development extends the development timeline by more than the feature alone would suggest.

How Agencies Protect Launch Dates

Professional agencies front-load risk management rather than discovering launch-blocking problems in the final weeks of a project.

• Content planning must begin at kickoff, not at development: An agency that does not establish content deadlines and content templates at the kickoff meeting is planning to discover a content delay during development.
• Hard content deadlines in the project plan create accountability: A specific date by which all client-provided content must be delivered, written into the project plan and accepted at kickoff, makes content delays a named risk rather than a surprise.
• Early integration scoping prevents late-project technical surprises: An agency that scopes all required integrations in discovery and tests integration connectivity in early development prevents the launch-blocking integration failures that result from late-stage technical discovery.

What the Agency Delivers

Redesign deliverables from agency engagements include design assets, technical implementation, and documentation that the client owns and can operate independently after the project closes.

Design Deliverables

Design deliverables belong to the client and should be formally handed over as part of project close.

• Figma design files include all components and states: The complete design system, all page templates, component states, responsive designs, and any brand assets created during the engagement should be delivered in an organized, labeled file.
• Design system documentation captures design decisions: A design guide documenting the typography scale, color system, component usage rules, and spacing standards enables future design work to maintain consistency without accessing the original designer.
• Brand assets created during the project are client property: Logos, icons, illustration systems, and photography art direction that were produced during the engagement belong to the client; the handover package should include all source files.

Technical Deliverables

Technical deliverables represent the complete, functional implementation of the approved design.

• The fully built and launched website is the primary technical deliverable: The site is delivered live, with all integrations connected and tested, redirects implemented, and analytics configured.
• CMS configuration for client editorial workflow is a required deliverable: The CMS should be configured so that the client's editorial team can create, update, and publish content without developer involvement for standard content tasks.
• Redirect map implementation and verification is a required deliverable: Every redirect from the old site to the new site should be implemented and tested before launch; a post-launch redirect audit confirms coverage.

Documentation and Training

Documentation transforms the delivered site from an agency dependency into a client-owned asset.

• CMS user guide must be specific to the client's installation: A generic CMS documentation link is not a CMS user guide; documentation specific to the client's content types, fields, and editorial workflow is what enables independent site management.
• Content update documentation prevents developer reliance: Clear instructions for every content update task the client will perform, including adding new pages, updating team profiles, and publishing blog posts, prevents every minor update from requiring an agency ticket.
• Training session must include the actual editorial team: Training delivered to a manager who then attempts to train their team is less effective than a live session with the people who will actually maintain the site post-launch.

How to Evaluate an Agency's Approach

Choosing the right redesign agency requires asking the right questions before signing a contract. A professional agency can describe its process clearly, specifically, and without hesitation.

Ask for Their Process Document

A professional agency has a documented process that they share with prospective clients as a standard part of the sales conversation.

• A process document demonstrates that the agency has thought through delivery: An agency that cannot produce a process document and describe its phases, deliverables, and sign-off requirements clearly operates informally and will deliver informal results.
• The document should be specific about client responsibilities: A process document that only describes the agency's tasks without specifying client responsibilities is incomplete and likely to create accountability disputes during the project.

Ask How They Handle Content Delays

How an agency answers this question is a direct test of whether they have managed real projects or only described theoretical ones.

• A professional answer describes a specific protocol: Content deadlines set at kickoff, written into the project plan, with an agreed process for timeline adjustment if deadlines are missed is a professional answer.
• A vague answer reveals no process: "We work with clients to manage content timing" is a non-answer that indicates the agency has no formal content management protocol and will absorb delays without escalation.

Ask What's Included in Post-Launch

Post-launch support is where the quality of an agency's commitment to outcomes is revealed.

• Redirect verification, 30-day monitoring, and a 90-day review are professional minimums: An agency that does not mention post-launch coverage without prompting has likely not included it in scope.
• Post-launch monitoring is how agencies catch organic traffic issues: A 30-day monitoring period that includes redirect verification, analytics validation, and form testing catches the problems that always emerge after launch before they become significant.

Conclusion

Professional agencies run redesigns as structured projects with defined phases, formal sign-off requirements, and clear deliverables at every stage.

Understanding this structure makes you a better client because you know what to expect, what your responsibilities are, and what a professional standard looks like when you see it. The client's primary responsibilities are showing up prepared, providing feedback on time, and delivering content when it is due.

Before your next agency conversation, prepare these three questions: What is your phase structure? How do you handle content delays?

What does post-launch support include? The quality of the answers will tell you whether the agency is worth a proposal request.

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 Every Redesign as a Professional Project

LOW/CODE Agency operates as a strategic product team, not a dev shop.

Every engagement we run follows a documented, phase-gated process with clear deliverables, formal sign-off requirements, and post-launch monitoring included as standard scope. We do not improvise project management.

You can work with LCA on your redesign knowing exactly what the process looks like from kickoff to handover.

• Documented phase process shared at proposal stage: We provide our full process document, including phase structure, deliverable list, sign-off requirements, and client responsibilities, before any engagement begins.
• Dedicated project manager on every engagement: Every LCA project has a named project manager who is the client's primary contact and is responsible for milestone tracking, risk escalation, and feedback cycle management.
• Content planning built into kickoff: We establish content deadlines, content brief templates, and content delivery protocols at the first meeting on every project.
• Consolidated feedback protocols: We specify how feedback should be submitted, from whom, and within what timeframe at kickoff, ensuring the design team receives clear, consolidated direction at each review stage.
• Formal change management process: Every scope change request is assessed for timeline and cost impact and approved in writing before any work begins, preventing surprise invoice additions.
• Post-launch monitoring included as standard: Every LCA engagement includes redirect verification, analytics validation, form testing, and a 90-day performance review as standard post-launch scope.
• Training and documentation delivered at handover: We deliver a specific CMS user guide, content update documentation, and a live training session with the client's editorial team as part of every project close.

We have delivered 450+ digital products for clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku. Start with a scoping call to see how we would structure your redesign project.