River
Y CombinatorBacked by Y Combinator

Free template

Discovery Call Questions Template

Discovery questions by buyer role, a call plan and a scorecard of what buyers said, plus sheets that test each question against won and lost deals.

Free download · No account needed

What you get

Pack of 8 files: 4 documents, 4 spreadsheets

Discovery Call Questions Template
  • Question Set by PersonaDocument
  • Call StructureDocument
  • Disqualification StandardDocument
  • Call to Outcome LogSpreadsheet
  • Qualification ScorecardSpreadsheet
  • Follow-up Summary FormatDocument
  • Question EffectivenessSpreadsheet
  • Discovery Gap RegisterSpreadsheet
RiverDiscovery Call Questions Template

Question Effectiveness, quarterly review

13 questions, 113 closed deals, minimum sample 30

Deals in the analysis113 closed, won and lost both
Kept, rewritten or cut11
Too few to judge2
Cut this quarter2

1. Kept, largest separation first

QuestionAskedWin askedWin notDiff
Why now, rather than six months ago7444%18%+26
What happens when it goes wrong8841%24%+17
What does success look like in 12 months4942%26%+16

2. Cut on evidence, 30 September

QuestionAskedDiffWhy
On a scale of one to ten, how painful is this61-1Answered every time, never varied
Are you the decision maker84-4Yes on 84% of calls, including the stalls

3. Too few to judge is a verdict, not a blank

Two questions draw promising answers on 7 and 11 deals. Both read too few to judge with the shortfall stated. A win rate computed on seven deals gets quoted in a pipeline review and never retracted.

The 12-month success question is asked mainly by the two most senior reps, who close more anyway. The confound is recorded beside the number.

Page 1 of 1195 words

How to run a discovery call

A discovery call is the first real conversation with a prospect. Its job is to learn whether they have a problem worth solving, what it costs them, why it matters now and how they buy. A good one is mostly the buyer talking, prompted by about a dozen open discovery call questions. It opens on how the work gets done today and closes on a dated next step.

The habit that matters most: write down what the buyer said, not what you concluded. "We'd have to make a case for the money" can be checked later. "Budget: yes" can't, and every forecast built on it inherits the guess.

A man in a shirt and tie talks on his phone while writing in a notebook, with a laptop and coffee on the table
Write the buyer's words down as they say them, not from memory later. Photo: Vitaly Gariev on Unsplash

Prepare three hypotheses

Research the account first, so you spend the buyer's time on what only they can tell you. Huthwaite International, the training firm behind SPIN Selling, says questions such as company size no longer need asking1 because the answers are online.

Then write down three hypotheses: what you think their situation is, what is going wrong, and what is forcing a decision now. Pick the questions that would test each one. Decide in advance which you'll drop if the call runs short, and never put the why-now question on that list.

An account research brief gives you material for all three. Check notes from earlier contact too, so the buyer never has to repeat themselves.

Plan the call, not a script

Agree on the purpose in the first two minutes: what you hope to learn, what they want and how long they have. Then take the parts below in order, since a question about cost lands better once the buyer has described the work.

The parts of a discovery call

PartWhat you're finding outA question that opens it
Current stateHow the work happens now, tools and handoffs included"Can you walk me through how your team does this today?"
ProblemWhat breaks, and how often"Which of those steps goes wrong most often?"
ImpactWhat it costs in money, time, people or customers"What happens when it goes wrong?"
Why nowThe date or event forcing a decision"Why now, rather than six months ago?"
ProcessWho decides, how, and what could stop it"Who else would need to be part of a decision like this?"
Next stepA dated action both sides agree to"Could we book an hour with your finance lead next week?"

In a 2017 analysis of 519,000 recorded discovery calls, Gong, which sells call-recording software, found that asking 11 to 14 questions correlated with the greatest success2. The most effective calls uncovered three or four business problems. Top sellers spread their questions evenly through the call, while average ones front-loaded them like a to-do list. So plan about 12 questions, not 30, and phrase them to draw long answers.

Write discovery call questions for each role

Group your questions by who is on the call. An operational owner knows how the work gets done, a technical evaluator what a product must pass, and an economic buyer where the money comes from. Under each question, note its purpose, what a good answer contains and one follow-up for a thin answer.

Skip "Are you the decision maker?" It invites a polite yes, and few purchases have only one. Forrester's State of Business Buying 2026 report found that a typical buying decision involves 13 internal stakeholders and nine external influencers3. Procurement staff were among the decision makers in 53% of buying cycles.

Phrase questions as if the problem exists. Julia Minson of Harvard Kennedy School and three colleagues tested this in a 2018 study. Questions that presupposed a problem got people to disclose more undesirable information4 than ones that presupposed none or asked generally. Stick to common problems, though: assuming an uncommon one made people judge the asker more negatively.

Weak questions and better ones

TopicWeakBetter
Approval"Are you the decision maker?""Walk me through how a purchase like this gets approved here."
Impact"On a scale of 1 to 10, how painful is this?""What happened the last time it went wrong?"
Budget"Do you have budget for this?""Where would the money for this come from?"

Listen, and write down their words

Let the buyer talk. Don't answer your own questions, don't rush to fill a pause, and don't demo. If they ask to see the product, make that the next step and spend the call learning what to show.

Label every answer by how you know it. Quoted: they said it, and their words go in your notes. Paraphrased: they said something that plainly means it. Inferred: nobody said it, so it's an open question, not a score. Not asked: a gap worth counting.

ExampleOne question, asked and recordedAn illustrative example written for this guide

Rep: "What happens when an order goes wrong?"

Buyer: "It's a headache. We shipped about 40 wrong orders last quarter, and each one costs around $900 to fix."

Recorded: Impact, quoted. About $36,000 a quarter, on their numbers.

  • Assumes the problem. It asks what happens when orders go wrong, not whether they do.
  • Their numbers. The cost comes from the buyer's own figures, so anyone can check it.

A recording makes quoting easy, but get consent right. In the US, federal law lets a party to a call record it5. The Reporters Committee for Freedom of the Press counts about 11 states that mainly require every party's consent6, including California, Florida and Pennsylvania. Its guide, written for journalists, advises assuming the stricter law applies when a call crosses state lines.

Check before you record

This is general information, not legal advice. If you call buyers in other states or countries, ask a lawyer or your legal team whose consent you need.

Close on a next step

End by proposing the step that follows from what you heard, with a date and names. If it's a demo, build it from the call: a demo script built from your discovery call gives the most minutes to what the buyer raised most.

Before you hang up

  • You know how the work gets done today
  • At least one problem has a cost attached
  • You asked why now and noted the answer
  • You know who else decides, and how
  • The next step has a date and named people
  • Anything inferred is noted as an open question

Walk away if the buyer confirms any of these in their own words:

  • Nothing they described has a cost or consequence attached
  • No budget line, and nobody willing to create one
  • The event that made it urgent has already passed
  • A must-have you can't provide and won't build
  • Your one contact won't introduce anyone else after two asks

Send a short recap the same day: what you heard, in their words, the agreed next step and what you still need. Write it so they can forward it to someone who missed the call. Keep your CRM note separate, with commitments quoted exactly; the sales call to CRM notes tool drafts it from the transcript.

Test your questions against outcomes

A question list is guesswork until you check it against results. Once deals start closing, compare the win rate on deals where each question was asked with the rate where it wasn't. Keep the losses in, because wins alone can't show what the losing deals lacked.

On 30 deals, one deal moves a win rate by more than 3 points, so agree on a minimum and write "too few to judge" below it. Look for other explanations too: a question only your best rep asks will look powerful, because that rep wins more anyway.

When a question keeps going unanswered, find out why. If calls run out of time first, fix the structure. If buyers dodge it, fix the wording. If one rep never asks it, that's coaching, not the question's fault.

To skip the setup, open this template with Edit with AI. River drafts the question set for each role and scores your past calls from their transcripts.

How to use this template

Fill in the files yourself, or open them in River. River asks for the questions you use now and for transcripts of past calls, with how each deal ended. It scores every call from what the buyer actually said, then shows which questions your won deals had in common and which ones nobody on the team asks.

No recordings yet? River still builds a question set for each buyer role, with a purpose and a follow-up for every question. Comparing wins with losses needs transcripts from closed deals; a saved prompt runs that comparison once you have them.

  1. Download it or open it in River

    Download four Word documents and four CSV sheets with no signup, or open the template in River to work with AI.

  2. Send your questions and calls

    Share the questions you ask now and past call transcripts, with each deal's outcome. Lost deals count as much as wins.

  3. River scores each call

    Each topic is marked quoted, paraphrased, inferred or not asked, and only what the buyer actually said counts toward a score.

  4. Act on what you learn

    See which questions to keep, rewrite or cut, and what nobody asks. Edit the files or ask River for changes anytime.

What's in the template

The questions your wins had in common, and the ones nobody is askingQuestion Effectiveness with its sample sizes, the Qualification Scorecard scored from quoted evidence, and the Discovery Gap Register ranked by value at risk.
Discovery Call Questions Template
RiverQuestion Effectiveness

Question Effectiveness

Illustrative rows for a fictional logistics software team of four reps and 113 closed deals. Every number carries its sample.

QuestionAskedNot askedSubstantiveDiffVerdict
Why now rather than six months ago74390.81+26Keep
What happens when it goes wrong88250.66+17Keep
Where would the money come from80330.48+2Rewrite
Who else has been burned by this internally71060.86n/aToo few to judge
On a scale of one to ten, how painful61520.94-1Cut
Are you the decision maker84290.96-4Cut

Rewrite is not cut. The budget question is asked on 80 deals and deflected on half of them. That is a wording failure rather than an irrelevant element, so it gets rewritten and re-measured.

Cut carries a date and a sample. Are you the decision maker was answered yes on 84% of calls, including deals that later stalled on a stakeholder nobody had met.

RiverQualification Scorecard

Qualification Scorecard

One row per element attempted. The evidence column carries the prospect’s own words or the row is not scored.

DealElementAskedStateEvidenceScored
D-1180ImpactYesQuoted“We shipped 41 wrong loads last quarter and each one is roughly 900 dollars to put right.”Yes
D-1180Critical eventYesQuoted“Peak starts in September and we cannot run peak on the Friday reconciliation again.”Yes
D-1180BudgetYesParaphrasedSaid operations has a systems line and this would come out of it. No amount named.Yes
D-1207BudgetNoInferredNobody said it. Scored from company size in the original notes.No
D-1207Critical eventNoNot askedNo
D-1270BudgetYesQuoted“There is no line for this and I would not be the one to create it.”Yes

The inferred row is the important one. D-1207 carried a budget score derived from headcount. Downgraded to an open item with an owner, and the deal later stalled with no date behind it either.

Quoted, paraphrased, inferred, not asked. Only the first two are scored. D-1270 was disqualified on the sentence sitting in its evidence cell.

RiverDiscovery Gap Register

Discovery Gap Register

What the team keeps failing to ask, ranked by the value of the open deals it affects.

ElementMiss rateGap typeMost missed byOpen dealsValue at risk
Champion94%Never askedAll except S. Aluko11$504,000
Critical event35%Ran out of timeAll four reps9$412,000
Risk49%Never askedAll four reps8$377,000
Metrics57%Never askedJ. Marek, T. Bergen7$331,000
Decision criteria54%Never askedT. Bergen6$288,000
Budget29%Asked and deflectedAll four reps4$196,000

Three gap types, three different owners. Ran out of time is a call structure problem. Asked and deflected is a wording problem for enablement. Never asked by one named rep is coaching, and it should not be presented to the whole team as a set problem.

Ranked on money rather than on rate. Critical event has the lowest miss rate of the top five and the second largest exposure, because it is missed on 9 open deals, more than any gap but Champion.

  • Question Set by PersonaQuestions grouped by buyer role, each with its purpose, what a good answer contains and one follow-up.
  • Call StructureThe shape of a first call, from preparing hypotheses to proposing the next step.
  • Disqualification StandardFive reasons to drop a deal, confirmed in the buyer's words, plus four warning signs to flag.
  • Follow-up Summary FormatTwo write-ups from one call: a same-day recap for the buyer and a separate note for your CRM.
  • Call to Outcome Log sheetOne row per call, with its deal, buyer role, recording consent and how the deal ended.
  • Qualification Scorecard sheetOne row per topic per call, with its answer state and the buyer's words as evidence.
  • Question Effectiveness sheetWin rates on deals where each question was asked and where it wasn't, with the deal count beside each.
  • Discovery Gap Register sheetWhat the team keeps failing to ask, why it happens, and the value of open deals affected.

Common questions

What questions should you ask on a discovery call?

Ask open questions that follow the buyer's story: how the work gets done today, what goes wrong, what that costs, why they're acting now and how they'll decide. "Can you walk me through how you handle this today?" and "What happens when it goes wrong?" are good openers. Plan about a dozen, each with a follow-up ready.

How long should a discovery call be?

Plan on 30 minutes for a first call. That's enough to agree on the purpose, explore three or four problems properly, ask why now and settle a next step. Confirm at the start how long the buyer actually has, and finish on time even when it's going well.

What are common discovery call mistakes?

The biggest is pitching before you understand the problem. Others: asking what their website already answers, asking "Are you the decision maker?", skipping why now, and noting your conclusions instead of the buyer's words. Most leave a gap you only find when the deal stalls.

Does this template work with BANT or MEDDICC?

Yes. Each question in the set names the element it establishes, such as budget, decision process or critical event, so it maps onto either framework. To keep a running score on every open deal, pair it with the MEDDICC deal qualification scorecard. This template doesn't borrow point values; any weights come from your own won and lost deals.

How many deals do you need to know which questions work?

Enough closed deals, won and lost, to clear a minimum you agree on in advance. The template's example wants a question asked on 30 closed deals before it gets a verdict, and marks anything less "too few to judge." With a dozen transcripts you can still score calls and spot gaps.

Is this discovery call template free?

Yes, it's free. The download is a zip of four Word documents and four CSV sheets, with no signup. The sheets come filled with example rows for a made-up sales team, so you can see how each works before you clear it. Edit with AI opens the same files in a free River workspace.

What does Edit with AI do?

It opens the template in a free River workspace. River asks for the questions you use now and for past call transcripts with their outcomes. It builds a question set by buyer role and scores each call from what the buyer said. Then it reports which questions separated wins from losses and what nobody asks.

Sources

  1. Huthwaite International. “SPIN Selling: A Complete Guide to Sales Success.” huthwaiteinternational.com (opens in a new tab)

  2. Gong. “Mastering discovery calls to close deals effectively.” gong.io (opens in a new tab)

  3. Forrester. “The State Of Business Buying, 2026.” forrester.com (opens in a new tab)

  4. Harvard Kennedy School. “Eliciting the Truth, the Whole Truth, and Nothing but the Truth: The Effect of Question Phrasing on Deception.” hks.harvard.edu (opens in a new tab)

  5. Cornell Law School. “18 U.S. Code § 2511 — Interception and disclosure of wire, oral, or electronic communications prohibited.” law.cornell.edu (opens in a new tab)

  6. Reporters Committee for Freedom of the Press. “Introduction to the Reporter's Recording Guide.” rcfp.org (opens in a new tab)

Written by

Chandler Supple

Co-founder & CEO, River

Chandler has spent the last six years working in AI, building tools for millions of users and Fortune 100 companies. In 2025, he co-founded River to build a new kind of operating system for AI agents.

Reviewed by

Brian Joseff, Co-founder, River