The client discovery process is how an agency learns what a new client actually needs before scoping and starting the work: who decides, what success means, what has been tried, and what constraints exist. Skip it, and you find out in month two, usually when a stakeholder nobody met arrives with a different definition of success.
A common failure looks like this: the kickoff is a 45-minute call with no pre-work, nothing is written down, and the person who signed the contract is not the person who judges the results. The team works hard on the wrong goal for weeks. Every part of the process below exists to prevent that.
Key Takeaways:
- A complete discovery process has four phases (intake, stakeholder mapping, kickoff call and synthesis) and produces a written discovery document the client confirms
- The 90-minute kickoff call has a fixed agenda; ad-hoc calls miss critical information and waste the most valuable hour of the engagement
- Service-specific question banks (SEO, paid, design, content, dev) surface the nuances that universal questions miss
- Discovery findings should flow directly into scope: every scope item should trace back to a documented finding
- Many problems that look like delivery failures start as discovery gaps, so the fix is often a better intake process
This guide is the complete discovery framework: the intake form template, the stakeholder mapping exercise, the 90-minute kickoff agenda with timing, service-specific question banks, the document template, and the handoff that turns discovery into scope without losing context.
How discovery gaps turn into project problems
Agencies tend to blame failed projects on delivery: quality gaps, missed deadlines, scope creep. Trace those problems back and many start in discovery. In agency engagements, discovery gaps show up like this:
| Discovery Gap | Downstream Symptom |
|---|---|
| Missing decision-maker in early conversations | Scope changes from late-arriving stakeholder |
| No documented success criteria | Disagreement at month 3 about "what we agreed to" |
| Skipped historical context (previous agency, past attempts) | Repeating their previous agency's mistakes |
| No technical or access prerequisites identified | Project stalls waiting for credentials |
| Unstated brand or compliance constraints | Late-stage rework |
| Vague timeline expectations | Pressure to compress mid-project |
| Unclear approval process | Bottlenecked deliverables |
For most engagements, half a day of agency time on discovery is small next to the rework a wrong assumption causes. Many agencies spend far less and absorb the cost later in margin.
The four-phase discovery framework
Discovery is not a meeting. It is a process with four phases, each with a specific output.
| Phase | Duration | Output |
|---|---|---|
| 1. Intake (pre-call) | 30 min for client, 1 hour for agency | Completed intake form, research brief |
| 2. Stakeholder mapping | 15 min | Who decides, who influences, who executes |
| 3. Kickoff call | 90 min | Discovery notes, agreed success criteria |
| 4. Synthesis and confirmation | 2 to 4 hours | Discovery document, scope draft, client sign-off |
Skip a phase and the later work suffers. The most commonly skipped is Phase 1: the agency goes into the kickoff without an intake form and spends a third of the call collecting basic facts the client could have written down in advance.
Phase 1: The intake form
A well-designed intake form does three things. It collects basic information before live time is used. It signals to the client that the agency is professional and prepared. And it gives the discovery team material to research against before the call.
Intake form sections
A workable intake form has these sections. Total completion time: 20 to 35 minutes for the client.
1. Company basics. Name, industry, size, revenue band, primary product or service, primary customer.
2. Project context. What service is needed, why now, primary goal in one sentence, budget range, timeline expectations.
3. Current state. What is being done today in this area, what tools and platforms are in use, what is working and not working.
4. Stakeholders. Primary contact, decision-maker (if different), other involved parties, approval process.
5. Previous attempts. Have they worked with an agency before in this area, what did and did not work, what is different this time.
6. Success definition. What does success look like at 90 days, 6 months, 12 months. Specific metrics if possible.
7. Access and prerequisites. What systems will the agency need access to (analytics, ad platforms, CMS, etc.). Confirmed access lead time avoids week-one stalls.
8. Communication preferences. Preferred channels (email, Slack, portal), meeting cadence, response expectations.
A client portal is a good home for the intake form: clients complete it on their own schedule, and the answers sit alongside the rest of the engagement. In AgencyPro, client onboarding forms are included on every plan. Pair this with structured client onboarding for the full intake-to-kickoff workflow.
Phase 2: Stakeholder mapping
Before the kickoff call, the agency should know who the actual stakeholders are. A stakeholder who appears late is one of the most common causes of late scope changes.
The stakeholder map
A simple four-row table:
| Role | Person | Authority | Engagement Level |
|---|---|---|---|
| Decision-maker | Who has final budget and direction authority? | Approves scope and budget | Should attend kickoff |
| Influencer | Who has informal influence on the decision? | Can derail or unlock | Strongly recommended at kickoff |
| Executor | Who will work with the agency day-to-day? | Implements and approves work | Required at kickoff |
| End user | Who consumes the output? | Quality verdict | Optional at kickoff |
The person who signs the contract is not always the person who decides direction. Buying groups are large: Forrester's State of Business Buying 2026 found the typical B2B buying decision involves 13 internal stakeholders and nine external influencers. Find out up front and get the real decision-maker into the kickoff.
How to surface hidden stakeholders
Three questions, asked of the primary contact during intake:
- Who else needs to be in the room when we set direction? Why?
- Who would be unhappy if a decision was made without them? Why?
- Who has the authority to pause or redirect this project?
The third question is the most important. If the answer is a person not yet involved in the conversation, get them on the kickoff call.
Phase 3: The 90-minute kickoff call
The kickoff call is the most valuable 90 minutes of most engagements, and a free-flowing conversation wastes it. A fixed agenda keeps every important topic covered.
The 90-minute agenda
| Time | Topic |
|---|---|
| 0 to 5 min | Introductions and meeting purpose |
| 5 to 15 min | Business context: their company, customers, market |
| 15 to 35 min | The problem: current state, what's not working, attempts |
| 35 to 55 min | Success definition: goals, metrics, timelines, what good looks like |
| 55 to 70 min | Constraints: budget, technical, brand, compliance, stakeholders |
| 70 to 80 min | Process and communication: cadence, channels, approval flow |
| 80 to 90 min | Recap, open questions, next steps and timeline |
The agenda is fixed. The questions inside each block are tailored to the service type. The facilitator manages time firmly. Kickoffs usually overrun because the early blocks expand and the constraints and process blocks get rushed, and those two blocks are where most engagement risk lives.
Facilitation principles
Two roles, two people. A facilitator who asks questions and manages time, and a note-taker who documents everything. One person cannot do both well.
Open questions. "Tell me about" and "walk me through" produce richer information than yes/no questions.
Follow the thread. When a client says something interesting, probe two or three layers deeper before returning to the agenda. The agenda is a guide, not a script.
Listen for what is not said. Hesitation, qualifications, vague answers and glances at another stakeholder are all signals to probe.
Restate periodically. "So what I'm hearing is..." confirms understanding, shows you are listening and surfaces misunderstandings immediately.
Manage politics. When stakeholders disagree, surface the disagreement explicitly rather than papering over it. "I'm hearing two perspectives. Let's talk through which one we're solving for."
Service-specific question banks
Universal discovery questions get you basic context. Service-specific questions surface the nuances that determine engagement success. The banks below are the questions worth asking for each major service type.
SEO discovery questions
- What keywords or topics drive your business today?
- Do you currently rank for anything that matters? Which pages drive organic traffic?
- Have you had traffic drops in the past two years? What happened?
- Who are your top three SEO competitors? Are they the same as your business competitors?
- Do you have an existing content strategy or editorial calendar?
- Who has access to Google Search Console and Analytics?
- Have you done link building in the past? Any manual actions or penalties?
- What CMS are you on? Do you have developer resources for technical changes?
- Is local search important? Do you have multiple locations?
- What is your content production capacity: in-house writers, freelancers, or do you need us for all of it?
PPC and paid media discovery questions
- What platforms are you running on, and what is monthly spend per platform?
- What is your target CPA, and what is a customer worth to you over their lifetime?
- Is conversion tracking properly configured (pixels, server-side, offline conversions)?
- What audiences have you targeted, and what performed best?
- Do you have creative assets, or will the agency produce them?
- Are there dedicated landing pages for campaigns, or do ads drive to the homepage?
- What offers or value propositions have you tested?
- Is there seasonality in your business?
- Is there a CRM, and can we connect ad performance to actual revenue?
- What reporting do you receive today, and what metrics matter most?
Web design and development discovery questions
- What are the primary goals of the site (lead gen, e-commerce, brand, information)?
- Who are the primary users, and what do they need to accomplish?
- Do you have brand guidelines, a style guide, or an existing design system?
- Are there sites you admire, and what specifically appeals?
- What content will be on the site, and who creates and maintains it?
- What integrations exist (CRM, email, payment, inventory)?
- What is your current tech stack, and are there constraints on technology choices?
- Do you need multilingual support, accessibility (WCAG), or specific security requirements?
- Who maintains the site after launch, and what is their technical level?
- What does the approval process look like for designs and functionality?
Content and social media discovery questions
- How would you describe your brand voice: formal, casual, authoritative, playful?
- Do you have documented messaging guidelines or a messaging framework?
- Who is your target audience, and what content do they consume?
- What topics does your audience care about most?
- Where will this content be distributed (blog, social, email, paid)?
- What content has performed well or poorly in the past?
- Are subject matter experts available for interviews and input?
- What is your approval process, and how many rounds of review do you expect?
- Are there topics, angles, or competitors you want to avoid?
- How do you measure content success today?
Strategy / consulting discovery questions
- What is the underlying business question this engagement is supposed to answer?
- What decisions are downstream of this work?
- Who will use the final output: the board, investors or the internal team?
- What format does the final output need to take?
- What prior strategy work or research exists?
- What is sacred and not up for discussion?
- What is your team's bandwidth to participate in research and workshops?
Phase 4: Synthesis and confirmation
The discovery call is not the end of discovery. The synthesis phase (turning raw notes into a structured discovery document and confirming it with the client) is where discovery either becomes scope or evaporates.
The discovery document template
A workable discovery document has seven sections:
1. Client overview. Company, industry, size, business model, growth stage.
2. Current state. What they are doing today, what is working, what is not, tools and platforms in use.
3. Goals and success metrics. Specific objectives, KPIs, target numbers, timelines, and the client's verbatim definition of success.
4. Audience and market context. Target audiences, competitive landscape, seasonality, positioning.
5. Constraints. Budget parameters, hard deadlines, technical limitations, brand guidelines, compliance, approval processes.
6. Risks and assumptions. Potential obstacles, dependencies on client resources, assumptions the scope is built on.
7. Recommendations and next steps. Initial strategic recommendations, recommended scope and phasing, immediate next steps.
The document should be sent to the client within 48 hours of the kickoff call with a request to confirm or correct within 5 business days. This produces a documented agreement before scope is built.
From discovery to scope
The scope of work should directly cite discovery findings. For each deliverable:
| Scope Component | Connection to Discovery |
|---|---|
| What (the deliverable) | Maps to a stated goal or pain point |
| Why (the rationale) | References discovery insight |
| How (the approach) | Reflects constraints surfaced in discovery |
| When (timeline) | Honors deadlines and dependencies from discovery |
| Not included | Explicit exclusions to prevent scope creep |
This linkage matters because it lets you handle scope changes objectively later. When a client requests something out of scope, the answer is not "no". It is "here's what we agreed to in discovery; this is new, and here's what it would cost."
Store discovery documents in your project management system attached to the client record so any team member joining the engagement has full context.
Common discovery mistakes
Treating discovery as a one-time event
Discovery should not end after the kickoff. The best agencies build ongoing discovery into quarterly business reviews, monthly check-ins, and casual conversations. Client businesses evolve; what you learned in month one is partially obsolete by month six.
Asking questions without listening
Some agencies treat discovery as a checklist: ask the questions, write down the answers, file the document. The value is not in the data; it is in the synthesis. Discovery documents that read like transcripts are usually documents that produced no real insight.
Failing to involve the decision-maker
The most expensive discovery error. When the actual decision-maker is not in the kickoff, you build scope on a secondary contact's version of the priorities, and a month later the decision-maker arrives with different ones and overrides the work. Always confirm and involve the decision-maker explicitly.
Over-promising during discovery
Discovery is for listening, not pitching. Resist the urge to propose solutions on the call. Give yourself a few days between discovery and recommendations so the synthesis is real, and so you do not commit to something you have not scoped.
Not documenting verbal agreements
Anything agreed verbally during discovery that does not make it into the document might as well not have been discussed. If a client mentions something that shapes the engagement (a constraint, an expectation, a stakeholder), write it down and confirm it in the document.
Skipping stakeholder mapping
The agencies that get burned on scope are typically the ones that learned about the influential stakeholder in month two. A 15-minute stakeholder mapping exercise in Phase 2 surfaces hidden stakeholders before they become hidden problems.
What discovery costs and what it saves
The full process takes roughly a working day of agency time per new engagement: an hour reviewing the intake form, 15 minutes on the stakeholder map, 90 minutes on the call for two people, and a few hours writing the discovery document. For example, at a $75 loaded hourly cost, about 8 hours is $600.
Compare that with one avoided failure: a single redesign round caused by a missed brand constraint, or a month of work against the wrong success metric. Track revision rounds, mid-project scope changes and margin per engagement before and after you standardize discovery, and you will have your own numbers.
Discovery as competitive advantage
Clients notice when an agency invests real effort in understanding their business before pitching a solution. A thorough discovery process signals strategic partnership rather than vendor-for-hire. In a market where most agencies rush to proposals and deliverables, the agency that slows down to listen wins disproportionately.
If you want intake forms, client files and the discovery document in one place instead of scattered across email and documents, book a demo of AgencyPro. Client onboarding and the client portal are on every plan; lead intake forms and the leads pipeline are on Pro.
Frequently asked questions
How long should an agency discovery process take?
A complete process (intake form, research, stakeholder mapping, 90-minute kickoff, synthesis and confirmation) typically takes 4 to 8 hours of agency time over one to two weeks, and about two hours of the client's time. A single 45-minute call with no pre-work and no written summary is where many engagement problems start.
What should be in a client intake form before the discovery call?
A workable intake form covers eight areas: company basics, project context, current state, stakeholders, previous attempts, success definition, access and prerequisites, and communication preferences. Total completion time should be 20 to 35 minutes for the client. The intake form lets the kickoff call focus on depth rather than basic data collection.
Who should be in an agency kickoff call?
At minimum, the decision-maker (who has budget and direction authority), the day-to-day executor on the client side, and an influential stakeholder if there is one. From the agency, the account lead and the discipline lead (e.g., creative director for design work). Four to six people total is typical. Calls with eight or more attendees usually become political theater rather than discovery.
How do you turn discovery findings into a scope of work?
Every scope item should trace back to a documented discovery finding. The chain is: discovery insight, the goal it supports, the recommended approach, the specific deliverable, and what is not included. This lets you handle scope-change requests objectively later ("here is what we agreed to in discovery; this is new") rather than negotiating from gut feel.
How does discovery differ for retainer vs project engagements?
Project discovery focuses on a single defined outcome and works in a fixed scope. Retainer discovery is broader: it must surface the client's changing needs, recurring rhythms and how the agency fits into their operations. Retainer discovery should also include a quarterly re-discovery cadence built into the engagement, because the client's needs at month 1 and month 7 are usually different.
