Discovery call question bank
Most discovery question lists are scripts: 40 questions in the order a rep should ask them, which produces an interrogation and a buyer who stops answering by question 12. Good discovery is organized by what you still do not know about the deal, not by what comes next on the page. This bank groups questions by the five things a rep must learn, gives the follow-up that gets past the first polite answer, and shows the weak version of each question so managers can hear the difference on a recording.
- Category:
- Enablement & Process
- Formats:
- PDF + web view
- Sections:
- 7
- Updated:
What you get
- Questions grouped by the five things a rep must learn: pain, impact, decision process, timing, and alternatives
- A follow-up for every question that pushes past the rehearsed first answer
- The weak version of each question and why it gets a useless answer
- A post-call gap check that tells the rep what to ask on the next call
- Guidance on how many questions to plan per call and when to stop asking
Who it's for
- AEs and SDRs who want better answers, not more questions
- Frontline managers coaching discovery from call recordings
- Enablement teams building discovery certification
What's inside
- 1
Pain: what is broken and for whom
4 columns, 4 worked example rows
- 2
Impact: what it is worth to fix
4 columns, 3 worked example rows
- 3
Decision process: who decides and how
4 columns, 4 worked example rows
- 4
Timing: what date matters and why
4 columns, 3 worked example rows
- 5
Alternatives: what they will do if not you
4 columns, 3 worked example rows
- 6
Post-call gap check
6 fields to complete
- 7
Why question lists produce bad discovery
Guidance notes
Preview of section 1
Pain: what is broken and for whom
You are trying to learn the specific problem, in the buyer's words, and who feels it. A category of problem ('reporting is hard') is not enough.
| Question | Follow-up | Weak version to avoid | Why the weak version fails |
|---|---|---|---|
| Walk me through what happens today when [process] goes wrong. | When did that last happen, and what did you have to do to fix it? | What are your biggest challenges? | Invites a generic list the buyer has recited to every vendor this year |
| Who on your team feels this most, and how do they work around it? | What does that workaround cost them each week? | Is this a problem for your team? | Yes/no question; the answer is always yes and tells you nothing |
The preview shows part of section 1. The full template has all 7 sections (6 not previewed here), with blank rows ready to fill in. Download the full template
How to use it
- 1
Plan around gaps, not a script
Before the call, look at what the CRM already tells you and mark which of the five areas are unknown. Pick two or three questions from those areas only. A first call rarely needs more than eight planned questions.
- 2
Ask the follow-up every time
The first answer to a pain question is the version the buyer has told every vendor. The follow-up ('what did that cost you last quarter?') is where the useful answer is. If you only have time for half your questions, ask half the questions with their follow-ups.
- 3
Stop yourself from asking the weak version
Read the weak-version column before the call. Leading questions ('wouldn't it help if...') and yes/no questions about budget feel efficient and teach you nothing. Managers should flag them when reviewing recordings.
- 4
Run the gap check within an hour of hanging up
Write down what you learned in each area in one sentence, using the buyer's words where you can. Anything you cannot write down is the agenda for the next call, and it should be named in the follow-up email.
- 5
Retire questions that do not earn answers
Each quarter, ask your top reps which questions reliably produce a useful answer and which get a shrug. Cut the shrugs. A bank of 30 questions that work is better than 80 that look thorough.
Frequently asked questions
What are good discovery call questions?
Open questions about a specific recent event ('walk me through the last time this went wrong'), followed by a question that asks for a cost, a date, or a person. Good questions are organized by what you still need to learn: pain, impact, decision process, timing, and alternatives.
How many questions should you ask on a discovery call?
Plan six to eight for a 30-minute first call and expect to get through fewer, because each good question needs a follow-up. Covering three areas well is better than touching all five lightly.
What should you avoid asking on a discovery call?
Leading questions ('wouldn't it help if...'), yes/no questions about priority or budget, 'what are your biggest challenges', and anything the buyer's website or your CRM already answers. They waste time and signal that you did not prepare.
How does this relate to MEDDIC or MEDDPICC?
The five areas map to the qualification fields most frameworks use: pain and impact to identified pain and metrics, decision process to decision process and criteria, alternatives to competition. This bank gives reps the questions; a qualification scorecard records what they learned.
Related templates
All sales ops templatesMEDDPICC deal qualification scorecard
Pipeline & Forecasting
A MEDDPICC template that scores each of the eight elements on verified buyer evidence, not rep opinion, with a worked deal example. Free PDF and CSV.
Sales call scorecard
Enablement & Process
A sales call scorecard with behavior-anchored ratings, so two managers scoring the same recording land on the same number. Free PDF and CSV.
Objection handling template
Enablement & Process
An objection handling template: each objection, what sits behind it, a clarifying question, a response that has worked, and proof. Free PDF and CSV.