Every list of sales discovery questions has the same problem. Reading twenty good questions does not make you able to ask them, because the difficulty was never in knowing the question.
The difficulty is asking a question that creates a short silence, then not filling that silence. That is a nerve problem, and nerve is built by repetition rather than by reading.
So this list does two things differently. Each question includes what a weak answer sounds like and what a strong one sounds like, so a rep knows whether the question landed. Then the last section covers how to actually get good at asking them.
Why discovery is where most deals are decided
Discovery sets the ceiling on everything that follows. A rep who leaves a first call without a quantified problem, a named stakeholder map, and a decision process is running the rest of the cycle on assumption, and no amount of presentation skill recovers that.
The time pressure is real. Gartner research has found that B2B buyers spend only around 17 percent of their total purchase consideration time meeting with potential suppliers, and where several vendors are competing, an individual rep may get five or six percent of the buyer's time. Gartner has also reported that 77 percent of B2B buyers describe their most recent purchase as very complex or difficult. Those two findings together explain why shallow discovery is expensive: there is no second window.
20 discovery questions by stage
The questions are grouped by where they sit in a first conversation. Work down the table in order, because impact questions land badly before a specific problem has been established, and criteria questions land badly before impact.
| Stage | Question | Why it works | Weak answer | Strong answer |
|---|---|---|---|---|
| Opening | What made you take this call today? | Opens with their motivation instead of your agenda. | "Just wanted to hear more." | "We are re-evaluating this in Q1 and your name came up." |
| Opening | What does your team do today when this comes up? | Surfaces the current process, which is your real competitor. | "We handle it internally." | "Our manager reviews a few calls a week and the rest go unreviewed." |
| Opening | Who else feels this problem besides you? | Maps stakeholders early rather than in week four. | "Mostly me." | "Me, the VP, and finance because it hits ramp cost." |
| Problem | Walk me through the last time this went wrong | Gets a specific incident instead of a generalisation. | A vague complaint. | A dated, named example with a cost attached. |
| Problem | How often does that happen? | Turns an anecdote into a frequency you can multiply. | "Fairly often." | "Two or three times a month." |
| Problem | What has it cost you so far? | Moves the conversation to numbers they own. | "Hard to say." | "Roughly one deal a quarter, so about 60k." |
| Problem | What have you already tried? | Prevents you pitching something they rejected last year. | "Nothing much." | "We ran a workshop in March, it faded by May." |
| Impact | If nothing changes, what does this look like in six months? | Builds cost of inaction without you asserting it. | "About the same." | "Worse, because we are hiring four more reps." |
| Impact | Who notices if this is not fixed? | Finds the executive whose problem this actually is. | "Just our team." | "The CRO, it shows up in ramp reporting." |
| Impact | What happens to you personally if this slips? | Uncovers the private stake behind the business case. | Deflection. | A named risk to their own goals. |
| Process | How did you buy the last tool like this? | Reveals the real decision process, not the org chart. | "The usual way." | "Pilot, security review, then a CFO sign-off over 50k." |
| Process | Who has to say yes, and who can say no? | Separates approvers from blockers, which are different people. | "My boss." | "My boss approves, IT can veto on security." |
| Process | What would have to be true for this to be a priority this quarter? | Tests urgency without asking about timeline. | "We will see." | A specific condition you can work toward. |
| Process | What is the alternative you are weighing this against? | Gets the real competitive set, which is often doing nothing. | "Just you." | "You, one other vendor, and building it internally." |
| Criteria | How will you decide? | Surfaces the scorecard before you are being scored on it. | "Best fit." | Three named criteria in priority order. |
| Criteria | What would make you rule us out? | Invites the objection early, while you can still address it. | "Nothing obvious." | A concrete disqualifier you now know about. |
| Criteria | What does success look like ninety days after go-live? | Defines the outcome you will be measured on. | "Things running better." | A metric with a number and a date. |
| Next step | What is the most useful next step from your side? | Lets them propose the step, which they then own. | "Send me something." | "Get my VP on a call next week." |
| Next step | What would you need from me before that meeting? | Makes you useful in advance instead of chasing. | "Nothing." | A named artefact you can prepare. |
| Next step | Is there anything I should have asked and did not? | Catches the thing they were waiting to be asked. | "No, that was thorough." | The real blocker, volunteered. |
The three that change calls the most
If a rep only improves at three of the twenty, make it these. Each one produces information that is difficult to obtain any other way, and each one requires the rep to tolerate a pause.
"Walk me through the last time this went wrong"
Specific incidents are what build a business case. Generalisations are not.
Buyers describe problems in the abstract because it is easier. A dated example with a name and a cost attached is the thing you will quote back in month two when the deal needs internal justification.
"What would make you rule us out?"
The objection you hear on call one is cheaper than the one you hear in week six.
Most reps avoid this question because it invites bad news. That is the point. A disqualifier surfaced early is something you can address. The same one surfaced after a proposal usually ends the deal.
"Is there anything I should have asked and did not?"
The highest-yield question in discovery, and the one asked least often.
It costs nothing, takes eight seconds, and regularly produces the real blocker. Buyers often hold something back simply because nobody created a place to put it.
How to actually get good at asking them
Knowing these twenty questions is a Tuesday afternoon of reading. Being able to ask number sixteen to a guarded CFO, then wait, is a different skill entirely, and it is built the same way any conversational skill is built.
Drill the pause, not the question
Have the rep ask a hard question and then say nothing for five full seconds. Most reps cannot do it on the first attempt. It is the single most common reason a good question produces a weak answer.
Score question count before question quality
Counting open questions per call is crude and it works, because the failure mode is usually too few rather than badly worded. Set a floor, then refine.
Practice against a buyer who deflects
Real buyers give the weak answer in the table above, and the skill is the follow-up. Practicing against a cooperative buyer trains the wrong reflex. Reps need a persona that answers vaguely so they learn to go again.
This is where practice earns its place. Reps can run these sequences dozens of times against a simulated buyer who deflects, and on real calls, guidance can prompt the follow-up when discovery stalls and the rep has moved on too early.
TL;DR
- Discovery sets the ceiling on the whole cycle, and buyers give you very little time
- Work the stages in order: opening, problem, impact, process, criteria, next step
- Judge a question by the answer it produces, not by how good it sounds
- The three highest-yield questions are the specific incident, the disqualifier, and "what should I have asked"
- The skill is tolerating the pause, and that is built by repetition
- Practice against a buyer who deflects, not one who cooperates
Where to go next
Discovery does not happen in isolation. The opening two minutes determine whether a buyer answers these questions properly at all, which is covered in the first two minutes of a discovery call. When the answers turn into pushback, the objection handling framework takes over. And real-time coaching explains how a stalled discovery call gets rescued while it is still live.