Website Redesign Discovery Phase Explained

The website redesign discovery phase is where the entire project is either set up to succeed or quietly undermined.

Most clients arrive excited and leave the phase exhausted, because nobody explained what was actually going to happen or what they needed to prepare.

This guide changes that. Discovery done well is the highest-leverage investment in a redesign. Projects with a formal discovery phase are two to three times more likely to be delivered on time and on budget.

This guide covers exactly what to expect, how to prepare, and what you should receive when it ends.

Key Takeaways

• Discovery Is Highest-Leverage: Decisions made in discovery shape every downstream deliverable; getting it wrong is expensive to correct later.
• Expect Two to Four Weeks: A thorough discovery phase for a mid-size site typically takes two to four weeks; rushing creates problems in design and build.
• Hard Questions Are Normal: Good discovery challenges your assumptions about your audience, competitors, and conversion goals.
• Defined Outputs Required: At discovery's end, you should receive a brief, sitemap, and requirements document, not just a meeting summary.
• Alignment Is the Goal: Discovery succeeds when agency and client share the same understanding of the problem, audience, and success metrics.

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

Where Discovery Fits in the Full Redesign

Understanding all phases of a redesign puts discovery in context as the foundation on which every subsequent phase depends. Discovery is phase one of a sequential process, not a standalone event or a preliminary formality.

Discovery as the Foundation of Every Phase

Every major decision made in later phases traces back to something established in discovery.

• Sitemap Origin: The agreed page structure produced in discovery determines the scope of wireframing, design, and development.
• Audience Definition: Personas and ICP profiles defined in discovery determine content hierarchy, messaging tone, and conversion architecture.
• Platform Choice: The technical requirements identified in discovery determine whether the current platform is retained or replaced.
• Success Metrics: The conversion goals set in discovery become the benchmarks against which the completed site is measured at 90 days.

Decisions made here without proper evidence create misalignment that compounds through every subsequent phase.

What Happens Before Discovery

Several actions must be completed before the first discovery session begins.

• Proposal and Contract: The scope of work, payment terms, and deliverable schedule must be signed before discovery starts.
• Onboarding: Agency and client teams introduced, communication channels established, and project management tools set up.
• Access Provisioning: GA4 viewer access, Google Search Console access, current CMS read-only access, and hosting details shared with the agency.
• Asset Compilation: Brand guidelines, previous briefs, customer research, and any existing site audit reports assembled for the agency.

Delays in access provisioning are one of the most common causes of discovery phase overruns.

What Comes After Discovery

Discovery produces the inputs that the design phase requires to begin.

• Brief to Wireframes: The approved brief becomes the brief for wireframe production; the sitemap defines which page templates need wireframes.
• Wireframes to Visual Design: Approved wireframes become the layout reference for high-fidelity design; no visual design should begin without wireframe sign-off.
• Design to Build: Approved high-fidelity designs become the reference for the development phase; no build should begin without design sign-off.

Readers should understand discovery as the gate that every subsequent phase passes through.

How to Prepare Before Discovery Starts

Preparing for a website redesign before the agency's first discovery session dramatically improves what both parties get from the process. Clients who arrive at discovery without preparation force the agency to spend session time collecting information rather than analyzing it.

Gather Access and Analytics Data

Before the first discovery session, compile the following minimum data set.

• GA4 Access: 12 months of traffic data, conversion events, and audience reports with viewer access granted to the agency.
• Search Console Data: Organic keyword performance, crawl status, and any manual actions or indexing issues from the past 12 months.
• Heatmap Reports: Hotjar, Microsoft Clarity, or similar session recording data showing where users click, scroll, and drop off.
• CMS Credentials: Read-only access to the current CMS so the agency can assess content volume, structure, and migration complexity.

These are non-negotiable starting points for any professional discovery process.

Identify and Brief All Stakeholders

Discovery involves people beyond the primary contact, and they need preparation before sessions begin.

• Marketing Lead: Traffic performance, campaign context, audience insights, and content strategy input.
• Sales Lead: Prospect feedback about the site, common objections, win/loss patterns, and conversion quality data.
• Senior Stakeholder: Strategic goals, business direction for the next 12 to 24 months, and non-negotiable requirements.
• IT or Technical Lead: Platform constraints, integration requirements, security standards, and hosting specifications.

Brief each stakeholder on what the discovery session will involve and what preparation they need to do before attending.

Document What's Working and What Isn't

Prepare a short internal brief before the first agency session.

• Top-Performing Pages: Which pages drive the most organic traffic, enquiries, and conversions based on GA4 data.
• Known UX Problems: Complaints received from users, observed drop-off points, and form abandonment issues you're already aware of.
• Content Gaps: Topics or questions that prospects ask regularly that are not addressed on the current site.
• Conversion Rate Baseline: Current form submission rate, phone click rate, and any e-commerce conversion data.

This brief gives the agency a head start on where to focus analyzis and avoids rediscovering problems you already know about.

Prepare Your Competitor Landscape

Compile five to eight competitor or aspirational sites with notes before the first session.

• Direct Competitors: Sites competing for the same audience, keywords, and deals that you are.
• Aspirational Examples: Sites in adjacent industries or markets whose design, content, or structure you admire and want to emulate.
• Specific Notes: For each site, note what you like and dislike so discussions are anchored to concrete examples rather than abstract preferences.
• Positioning Context: Note where each competitor positions relative to you on price, quality, specialism, and geography.

The Kickoff Meeting in Discovery

Redesign kickoff meeting structure sets the tone for the entire engagement. A poorly run kickoff creates confusion that costs time at every subsequent stage.

The kickoff meeting is a formal working session, not a casual introduction. Treat it as the first billable deliverable of the engagement.

The Kickoff Agenda: What to Expect

A professional kickoff covers six areas in a structured sequence.

• Introductions: Agency and client teams introduced with roles, responsibilities, and decision-making authority clarified.
• Project Overview: The agreed scope, deliverables, and timeline reviewed and confirmed by both parties.
• Communication Protocols: Agreed channels for feedback, updates, and approvals, with response time expectations for each.
• Timeline Walkthrough: Phase milestones, client review windows, approval deadlines, and dependency points reviewed together.
• Risk Identification: Known risks to timeline and scope identified upfront, with mitigation approaches agreed.
• Open Questions: Any unresolved questions about scope, deliverables, or approach surfaced and assigned to specific owners.

A kickoff that doesn't cover all six areas has left unresolved ambiguity somewhere in the project.

Project Goals and Success Metrics

The kickoff must define what success looks like in measurable terms.

• Conversion Targets: Specific improvement goals for form completion rate, phone enquiries, or e-commerce conversion by 90 days post-launch.
• Traffic Goals: Organic traffic improvement targets, expressed as a percentage increase against the prior year baseline.
• Business Goals: The commercial objective behind the redesign, such as increasing lead volume by 30% before a target date.
• Measurement Plan: How each goal will be tracked, by whom, and at what reporting frequency.

Both parties must sign off on the success metrics during the kickoff; they cannot be added later without a change request.

Communication and Approval Workflows

Clear workflows prevent the approval delays that extend redesign timelines and inflate costs.

• Feedback Channel: Single agreed channel for all formal feedback, whether that is email, a project management tool, or a shared document.
• Approval Sign-Off: Who has final approval authority for each phase deliverable, named and confirmed in writing at kickoff.
• Response Time: Agreed turnaround time for client feedback at each review stage, typically 48 to 72 hours for most deliverables.
• Escalation Path: Who to contact if a decision is blocked, a deliverable is disputed, or the timeline is at risk.

Ambiguous approval workflows are one of the leading causes of project delays in redesign engagements.

Establishing the Project Timeline

The kickoff produces a shared, agreed timeline with milestones and dependency points documented.

• Phase Milestones: Discovery completion date, wireframe delivery date, design sign-off date, staging delivery date, and launch date.
• Dependency Points: Client deliverables such as content, images, and legal copy that must be received before specific agency milestones can be met.
• Buffer Periods: 10 to 15% time buffer built into the timeline to absorb revision rounds and approval delays.
• Launch Criteria: Defined conditions that must be met before the site goes live, including QA completion, redirect testing, and analytics configuration.

Stakeholder Interviews and Research

Stakeholder interview questions should surface conflicting priorities and institutional knowledge that no brief document captures. Research activities in discovery are what differentiate a professionally structured engagement from one that guesses at audience needs.

Internal Stakeholder Interviews

Agency discovery includes structured interviews with internal stakeholders for several reasons.

• Priority Conflicts: Different functions often have conflicting priorities for the site; discovery surfaces these before they create design disputes.
• Institutional Knowledge: Sales teams know what prospects complain about; service teams know what clients misunderstand; these insights shape content decisions.
• Constraint Identification: IT, legal, and compliance constraints that affect the build are more reliably surfaced through interviews than through a brief document.
• Alignment Building: Stakeholders who are interviewed feel ownership of the project outcomes; this reduces resistance during review cycles.

Customer and User Research

Where possible, good discovery includes direct input from customers and users.

• Customer Interviews: Three to five short interviews with representative customers about how they found the business, what persuaded them, and what the site didn't answer.
• User Surveys: A short survey to existing customers or site visitors asking which pages they use, what they find confusing, and what information is missing.
• Session Recording Review: Analyzis of existing Hotjar or Clarity recordings to identify real navigation patterns and drop-off behavior.
• Search Behavior: Search Console data reviewed to understand what queries people use before landing on the site.

Competitor and Market Analyzis

The competitive audit contextualizes design and positioning decisions.

• Positioning Review: How each competitor positions on the five key dimensions: price, quality, specialism, audience, and geography.
• Feature and Content Gaps: What competitors offer on their sites that the client does not, and vice versa.
• Visual Standards: The design quality threshold that the new site needs to meet or exceed to compete credibly in the market.
• Differentiation Opportunities: Where the client has genuine advantages that are not reflected in the current site's messaging or structure.

Technical Audit of the Existing Site

Technical discovery identifies constraints that affect platform and architecture decisions.

• Site Speed: Current Core Web Vitals scores and page speed data across key page templates.
• Crawl Audit: Broken links, redirect chains, duplicate content, and indexing issues that need to be resolved in the redesign.
• Security Review: Certificate validity, mixed content warnings, and any known vulnerabilities in the current platform.
• CMS Assessment: Platform version, plugin compatibility, maintenance cost, and extensibility for future requirements.

Discovery Outputs: What You Should Receive

After reading the creative brief for redesign guidance, you will understand exactly what the discovery brief should contain and how to evaluate whether it meets professional standards.

A professional discovery phase produces at least four formal deliverables. Meeting summaries and emails do not count.

The Project Brief

The discovery brief is the most important single document in the entire redesign engagement.

• Audience Definition: ICP profiles with buying triggers, decision-making patterns, and content preferences documented.
• Conversion Goals: Specific measurable targets for each primary conversion action on the site.
• Messaging Hierarchy: The key messages the site must communicate, in priority order, informed by customer research.
• Design Direction: Visual references, tone of voice guidelines, and competitive positioning context for the design phase.

The brief becomes the brief for every design decision made in the subsequent phases. For a full checklist of what the requirements document should capture alongside the brief, see capturing redesign requirements.

The Sitemap

The sitemap is the first structural deliverable and the document that defines the scope of all subsequent design work.

• Complete Page List: Every agreed page with its URL path, content type, and parent-child hierarchy in the navigation.
• Navigation Architecture: How pages are grouped into primary and secondary navigation, including any mega-menu or dropdown structures.
• Content Status: For each page, whether it is new, migrated, rewritten, or removed, with the content responsibility assigned.
• Sign-Off Requirement: The sitemap must be formally approved before wireframing begins; verbal agreement is not sufficient.

The Requirements Document

The requirements document captures functional and technical specifications that the design and build must meet.

• Functional Requirements: Forms, calculators, booking systems, search functionality, and interactive elements with their behavior specified.
• Integration Requirements: CRM, marketing automation, analytics, and third-party tools with their integration scope defined.
• Content Requirements: What needs to be written, what needs to be migrated, and what needs to be created as new assets.
• Technical Standards: Hosting requirements, security specifications, performance targets, and accessibility compliance level.

The Discovery Presentation

A professional agency presents discovery findings in a structured session before handing over documents.

• Research Summary: Key findings from stakeholder interviews, customer research, and competitive analyzis.
• Strategic Recommendations: Positioning, messaging, and structural recommendations based on the research findings.
• Scope Confirmation: The agreed page list, timeline, and success metrics reviewed and confirmed before design begins.
• Decision Points: Any outstanding decisions that need client input before the design phase can begin, surfaced and resolved in the session.

Conclusion

Discovery done properly is the most valuable investment in a redesign. It is where expensive mistakes are caught, where alignment is built, and where good projects are separated from great ones.

A discovery phase that produces a brief, sitemap, and requirements document has done its job. One that produces only a meeting summary has not.

Request a discovery phase agenda from any agency you are evaluating. How they structure discovery reveals how they will structure the rest of the project.

An agency that cannot describe their discovery deliverables clearly is one that has not formalized the process.

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's Discovery Phase Is Structured, Documented, and Yours to Keep

LOW/CODE Agency runs a formal, deliverable-based discovery phase on every redesign engagement.

You receive a written project brief, a reviewed and approved sitemap, a functional and technical requirements document, and a discovery presentation before any design work begins.

We are a strategic product team, not a dev shop. Our discovery phase is typically charged separately from design and build, which is a sign of professional practice, not an upsell.

It produces documents you own, can share internally, and use to evaluate our subsequent work against.

• Discovery Brief: Audience profiles, conversion goals, messaging hierarchy, and design direction documented and signed off before design begins.
• Sitemap and Architecture: Complete page inventory with navigation hierarchy, content status, and redirect requirements.
• Requirements Document: Functional, technical, and content requirements specified to the level needed for accurate development estimation.
• Kickoff Meeting Facilitation: Structured kickoff with roles, timeline, approval workflows, and success metrics agreed and documented.
• Stakeholder Interview Program: Structured internal interviews designed to surface priorities, constraints, and institutional knowledge.
• Competitive Analyzis Report: Five to eight competitor sites audited against positioning, content, design quality, and differentiation opportunity.
• Discovery Presentation: Formal findings presentation covering research insights, strategic recommendations, and confirmed scope before design begins.

We have delivered over 350 digital products for clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku. Explore our full-service redesign discovery to understand exactly what our discovery phase produces. Start with a scoping call