How to prepare a discovery call that builds on account facts
Learn how to prepare a discovery call from account notes, draft neutral questions, and build a 30-minute agenda with a clear next step.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What it means to prepare a discovery call
When you prepare a discovery call, you turn what your team knows about an account into a plan for what to learn next. The call itself is a conversation about how the buyer works today, where that work breaks down, and whether a change is worth exploring. Use your account records to decide what to ask, what to listen for, and how different answers would shape your next step.
A discovery call template gives you places to record questions and answers. Fill those slots with facts, open questions, and choices grounded in the buyer's situation. Suppose earlier notes say requests go to a shared inbox. Walk through a request from arrival to sign-off and learn who picks it up when the usual approver is away. This tests whether backup coverage deserves another conversation.
What it does for the business
- Use buyer time to learn something newWhen you bring forward facts from previous conversations, the buyer can start where the team left off. Use the time to trace a handoff or learn who handles exceptions.
- Decide which opportunities deserve more workA specific example and its consequences give you a basis for sales qualification, the judgment about whether an opportunity is worth pursuing. You can decide when to involve a specialist, when a missing fact needs a check, and when to free up time for other accounts.
- Plan a demonstration around the buyer's workIf discovery shows that backup approvals are the problem, a later demonstration can focus on routing an urgent request when its usual approver is away. Bring the people who run that handoff and agree on what they would need to see to judge the approach.
- Give the next seller a clear recordUse the buyer's wording and record the source of each important fact. A colleague can see why you proposed the next step and which assumptions need checking before they scope a solution.
How to prepare a discovery call, step by step
Scope the call and gather current account evidence
The purpose of the meeting tells you which account facts belong in the guide.
What to do
- Record the account, expected attendees and known roles, meeting length, and reason for the call. Name the decision you want to make, such as whether to schedule a workflow review with the operations lead.
- Do account research using the most recent relevant discovery notes, account records, and buyer messages you have permission to consult. Record the source and date for each item you use, and make sure it refers to the team and workflow on the agenda.
- Use the clearest current evidence when details disagree. If an older overview describes a portal and a recent note describes a shared inbox, check whether they cover different request types before using either as your starting point.
- Use the buyer's reason for meeting to narrow the scope. If the invitation covers approval delays, save topics unrelated to that handoff for later. If you have only an invitation and a company name, leave time to establish the workflow.
Why
Teams within an account can work differently. Pinning down the scope keeps a fact about one team from becoming a faulty premise about another and helps you choose sources that can change the agenda.
Separate known facts from gaps worth probing
A discovery question earns its place when the answer can change a decision.
What to do
- List confirmed facts, assumptions, and unknowns. For each fact, record who reported it, where to find it, and when it was true. Use the buyer's terms for roles and workflow steps.
- Use known facts to pick up the thread. If a recent note says the request arrives in a shared inbox, start from the last actual request and ask the attendee to describe who picked it up and what happened after that.
- Convert assumptions into neutral discovery questions. If you suspect slow approvals, ask how the last request compared with what the buyer expected. If they confirm a delay, ask where it occurred.
- Rank the gaps by what the answers would change. If access to request details determines whether a workflow review is possible, ask who can share a redacted example before using the remaining time to collect a full list of tools.
Why
A short list puts the conversation where the evidence is weakest and the consequence of being wrong is highest. Visible assumptions also give teammates a place to pick up if the call changes hands.
Build a timed discovery agenda with neutral questions
A recent case gives you something concrete to follow through the workflow.
What to do
- Use the first three minutes to confirm the purpose and invite additions. Give the next seven minutes to the current workflow. Ask the buyer to walk through a recent request from intake to sign-off and capture the people, tools, and handoffs they name.
- Spend the next eight minutes on failure and impact. Ask how the case compared with what the buyer expected. If they describe a failure, ask what happened next and tie any rework, missed deadline, or customer impact to the case or period.
- Set aside seven minutes for constraints and the decision process. Ask how changes to this workflow are evaluated, who would need to review them, and which requirements a change would have to meet. Use follow-up questions about approvals, access, or timing when those details affect feasibility.
- Use the last five minutes to recap what you heard, check what remains open, and ask whether a next step would help. Prepare branches keyed to the answer. A repeat problem with a known owner may justify a workflow review. A single exception without a wider effect may justify closing the loop after a recap.
- Prepare a note-taking template with space for the case, buyer wording, source or date, frequency, impact, constraints, decision roles, and open questions. Add a place for the proposed action, its owner, and timing. Leave an explicit spot for what still needs checking.
Why
A time budget protects the close and gives the buyer room to describe a real case. The workflow gives impact and constraint questions a shared reference. Decision branches help you respond when the buyer raises a different issue or sees little reason for change.
Check the agenda against the evidence and the clock
Every scheduled question should help you establish a fact or choose an action.
What to do
- Read each question alongside the prior notes and check the facts it assumes. If a manager reports that one request was late, ask about the case and its consequence and keep the wider frequency open.
- Identify what each question and probe would help you decide. Cut repeats, put optional probes after the main question, and mark which details can wait if the buyer needs more time on an example.
- Add the minutes and read the agenda out loud. Check that you can fit introductions, listening, notes, and the recap into the slot. Ask a teammate to read for loaded wording, including questions that assume the buyer has a problem, a budget, or a buying plan.
Why
Even an open question can steer the buyer toward your theory. Reading questions against the evidence exposes unsupported premises. A timing check gives you a better chance of reaching the recap and deciding whether to follow up.
Hand the guide to the person running the call
The host needs the first question and the closing decision where they can find both at a glance.
What to do
- Share the call objective, opening prompt, and timed blocks with the host and note taker. Keep source references beside the claims they support so either person can check a detail during the call.
- Flag conflicting evidence and unconfirmed attendee roles before the meeting. Put the essential gaps near the top of the agenda if they affect whether the rest of the conversation can proceed.
- Plan to note which next step the buyer agrees to, who owns it, and when it is due. Leave each field open until the buyer confirms it, and record a decision to stop or wait when that is the outcome.
Why
A guide the host can scan is easier to use while listening. Including unresolved questions helps the host explain follow-up and gives the rest of the team a record of what still needs checking.
Common mistakes
- Repeating intake questionsAsking which tool handles requests when the buyer already told you uses time you could spend tracing a handoff.
- Leading with your diagnosisA question about how much the approval bottleneck costs assumes it exists and has a cost the buyer can estimate.
- Treating one story as a patternCapture when the failure happened and how often the buyer has seen it before drawing a conclusion about the workflow.
- Equating interest with intentA buyer can want to understand an option while having no active review or plan to change the process.
- Letting the agenda fill the callA packed list leaves little time to hear how a case unfolded or to agree on any follow-up.
What a good result looks like
- One account, one call objective, and a clear link from each main question to a decision.
- Current account facts with source references, plus labeled assumptions and unresolved gaps.
- Time blocks that total 30 minutes and leave room for a recap.
- Open questions, concrete probes, and a place to capture the buyer's evidence.
- A closing question that lets the buyer agree on an action, defer, or stop.
And then what? Using the result
- Use the guide to run the call and mark which facts the buyer confirms, corrects, or leaves open.
- Send the buyer a concise recap of what you heard and the action you agreed on, with the owner and date when available.
- Bring the person who owns the workflow into a follow-up if their input is needed to test fit or clear a constraint.
- Use an agreed case and success criteria to brief the team for a later demonstration or evaluation.
- Update your account record with the actual decision and move the opportunity forward, defer it, or close it on that basis.
When to run it
- After a referral or email exchangeUse the introduction and replies to establish why you are meeting. Leave time to learn how the work happens.
- Before a call with a new team at an existing accountCarry forward relevant account facts and verify which ways of working apply to the new team.
- Before bringing in a specialistIdentify the case or constraint to assess, then decide which specialist should join the follow-up.
Questions people ask
How do you prepare a discovery call?
Read your current account notes, choose the unknowns that affect fit or the next step, and turn them into a timed agenda with open questions. Leave room to check assumptions as you listen.
What should a 30-minute discovery agenda cover?
Cover the call objective, current workflow, a concrete failure and its impact, constraints and the decision process, and a short recap with a proposed next step. Give each block a time limit and keep extra probes in reserve if the buyer's example leads somewhere unexpected.
What are good discovery questions for a first sales call?
Good discovery questions ask the buyer to describe actual work, give an example, and explain what happened as a result. Try 'Can you walk me through the last request that needed approval?' and, if a delay comes up, 'What did the team have to do next?'
How do you ask about budget on a discovery call?
Ask how a change like this would be evaluated and funded if the buyer decided it was worth pursuing. If they describe an active project, ask which resources have been set aside and who approves them. If funding is still open, record it as open.
How do you end a discovery call?
Summarize the workflow, the example, and any open question, then ask the buyer whether you captured it accurately and what follow-up would help. If you agree to another step, confirm who will do what and when.
Can you use the same discovery call template for every account?
Yes, you can reuse the structure and adapt the questions, evidence, and next-step branches to each account. Use prior notes to skip settled topics.
More jobs in Sales & outbound
Prepare a discovery call, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac