Discovery Call Questions: 40 to Uncover Real Pain
Discovery call questions grouped by goal: situation, pain, impact, decision process and next step, plus how many to ask and how to follow up on answers.
What questions should you ask on a discovery call?
Ask open questions about the buyer's situation and problem, follow up until they put a number or consequence on it, find out who decides and on what budget and timeline, and end by agreeing a dated next step. Gong's call data points to about 11 to 14 well-spaced questions, not a long list.
The 11 to 14 figure comes from Gong's 2017 analysis of more than 519,000 B2B sales calls, which found success fell back to average beyond that range (Gong). It is vendor data. The 40 questions below are a bank to choose from before a call, not a checklist to read out.
A 20-minute discovery call structure
Six stages. Most of the time goes on pain and impact, because that is where the business case comes from.
| Time | Stage | Example line |
|---|---|---|
| 0 to 2 min | Agenda | “We have 20 minutes. I would like to understand how you handle [area] today, then decide together whether a next step makes sense. Anything you want to add?” |
| 2 to 6 min | Situation | “Walk me through how [process] works today.” |
| 6 to 12 min | Pain | “What is the hardest part of that?” |
| 12 to 15 min | Impact | “What does that cost you in a typical month?” |
| 15 to 18 min | Decision, budget, timeline | “If you decided to fix this, who else would be involved?” |
| 18 to 20 min | Next step | “Would it make sense to put 30 minutes in next Tuesday with [person] to look at [specific thing]?” |
Discovery questions by goal
Pick two or three from each group that fit this buyer. Replace the brackets with their process and words.
Situation
- Walk me through how [process] works today, from start to finish.
- Who is involved day to day?
- What tools do you use for it now?
- How long has it worked this way?
- What prompted you to take this meeting?
- What does a good week look like for your team?
- What has changed in the last six months?
Listen for: The words they use for the process. Repeat them back later.
Pain
- What is the hardest part of [process]?
- Where does it break down most often?
- Tell me about the last time it went wrong.
- What workarounds has your team built?
- What do people complain about most?
- What have you already tried to fix it?
- If you could change one thing tomorrow, what would it be?
Listen for: Emotion and specifics. "Annoying" is a start; "we lost a customer" is a pain.
Impact
- How often does that happen?
- What does it cost you in hours, money or customers?
- Who else feels it when it goes wrong?
- What happens if nothing changes this year?
- How does this affect the goals you are measured on?
- Have you put a number on it internally?
- What would fixing it be worth to you?
Listen for: A number, a cost or a consequence. Without one, there is no business case.
Decision process
- If you decided to fix this, how would that decision get made?
- Who else would need to be involved?
- Whose budget would this come from?
- How have you bought something like this before?
- What would make the decision easy for your boss?
- Is there a sign-off level that changes who approves?
- What could stop this from going ahead?
Listen for: Names and steps. "I decide" is rarely the whole answer.
Timeline and budget
- Is there a date by which this needs to be solved?
- What is driving that timing?
- Have you set aside budget for this, or would it need to be found?
- What happens to your plans if it slips a quarter?
- Are you looking at other options at the moment?
- Is anything else competing for the same budget?
Listen for: Real dates tied to events, not "soon".
Next step
- Based on what you have told me, what would be a useful next step?
- Who should be in the next conversation?
- Can we put a time in now?
- What would you need to see to move forward?
- Is there anything that would stop you taking that step?
- What should I prepare for that meeting?
Listen for: A yes to a date, not "send me something".
Layered follow-ups
The best discovery question is usually the second or third one on the same topic.
A layered sequence follows the buyer's answer down until it reaches a cost. It sounds like this:
- “What is the hardest part of scheduling right now?” Opens the topic.
- “What happens when that goes wrong?” Moves from process to consequence.
- “How often?” Gives you frequency.
- “What does that cost you?” Turns it into a number.
- “Who else feels it?” Finds the other people in the decision.
Gong's 2019 discovery article reported that top performers spread questions evenly through the call rather than front-loading them (Gong). Layering does that naturally: each question comes from the last answer.
When the buyer says the current way works
The status quo is your real competitor. Do not argue with it; ask what it costs.
| Buyer says | Weak answer | Stronger answer |
|---|---|---|
| "Honestly, our spreadsheets work fine. Why would we change?" | Listing features the spreadsheets cannot do. | They might be the right answer. When they work, what does that take from your team each week? |
| "We tried something like this last year and nobody used it. What is different?" | "Our product is much easier to use." | That is useful to know. What got in the way: the tool, the rollout, or the timing? |
| "I am not sure this is a priority right now." | Pushing for the next step anyway. | Fair. What is the priority this quarter, and does [problem] touch it at all? |
Talk less: what call data says
The best-known number in sales research is also the one most often misquoted.
Gong's 2016 research proposed a “golden ratio” of about 43% talking to 57% listening. Its 2025 update, across 326,000 calls of at least ten minutes, found an average of 60% seller talk time, with 57% in won deals and 62% in lost ones (Gong Labs). Gong itself says the gap is not large.
The more useful findings are about shape. In the same update, lost deals had longer seller monologues, and won calls averaged 15 to 16 questions against about 20 in lost ones. So: ask open questions, stop talking when they answer, and do not turn discovery into an interrogation. These are vendor figures from its own customers' calls.
Practise with a sceptical VP of Operations
Question lists are easy to read. Following up on an answer you did not expect takes practice.
The sales discovery scenario on VirtualInterview.ai puts you in a first meeting with Marcus Lee, a VP of Operations who agreed to 20 minutes as a favour to a colleague. He is polite, busy and sceptical of vendors. He opens with “I have about twenty minutes. What did you want to cover?” and, depending on the pressure you choose, may say the spreadsheets work fine or that a past tool went unused. He has a real problem, but only describes it, and what it costs, if you ask.
The report scores Questioning (30%), Pain and impact (30%), Qualification (20%) and Next step (20%), and labels the outcome “Qualified opportunity”, “Interested, not committed” or “Stalled”. Pitching before you ask about his situation scores low on questioning.
Scores are an AI coach's estimate. The camera self-view is not recorded or analysed, and it is a rehearsal tool, not live help on a real call. To book the meeting in the first place, see the cold call script examples; for the pricing conversation later, see how to handle price objections. The same structured questioning helps in a case interview.
Frequently asked questions
- How many questions should you ask on a discovery call?
- Gong’s 2017 analysis of more than 519,000 B2B calls (vendor data) found success was highest at 11 to 14 targeted questions, spread through the call. Its 2019 article found successful C-suite meetings averaged about four questions. Fewer, better questions beat a long list.
- How long should a discovery call be?
- Twenty to thirty minutes is common for a first discovery call, and executives often give less. Agree the time at the start, keep to it, and leave the last few minutes for the next step.
- What is the goal of a discovery call?
- To find out whether the buyer has a problem worth solving, what it costs them, who decides and when, and whether a next step makes sense for both sides. It is not a demo or a pitch.
- What are good pain questions?
- Open questions about specific moments: "What is the hardest part of that?", "Tell me about the last time it went wrong", "What workarounds has your team built?". Follow each with a question that puts a number or consequence on it.
- How do you end a discovery call?
- Summarise the problem and its cost in their words, propose a specific next step with the right people, and book the date before you hang up. "I will send something over" with no date is a missed next step.
- What is a good talk-to-listen ratio?
- Gong’s 2016 research suggested about 43% talking and 57% listening. Its 2025 update across 326,000 calls found won deals averaged 57% seller talk time against 62% in lost deals. Treat both as guides: avoid long monologues and keep the buyer talking.