Discovery Call Questions That Surface Real Pain
Discovery goes shallow when it's a checklist of qualification questions. A framework for questions that get past the surface answer, the listening cues that tell you to dig, and how a demo sent as pre-work lets discovery start deeper.
Discovery goes shallow when it's a checklist of qualification questions and you accept the first answer. "We need better reporting" is a summary, not pain — the pain is the specific board meeting where someone got asked for a number nobody had. Good discovery gets from the summary to the scene: ask about recent, specific situations, follow every answer with "tell me more," and listen for the cues that say there's something underneath. Keep the call mostly the prospect talking. And rather than demoing before you understand the problem, send a short interactive demo as pre-work so the discovery call can start deeper.
The question framework
Anchor everything to specifics and recency:
- "What made you start looking at this now?" — surfaces the trigger. A trigger means urgency; no trigger means a "someday" deal.
- "Walk me through the last time this problem actually bit you." — gets you the scene, not the summary. This is the most valuable question on the call.
- "What have you already tried?" — tells you what won't work and how serious they are.
- "What happens if you don't solve this?" — sizes the pain. If the answer is "nothing much," it's not a priority.
- "Who else is affected by this?" — maps the stakeholders and the blast radius.
- "How would you know this was solved?" — defines success in their terms, which is what your demo and pilot should target.
Then, after almost every answer: "Tell me more about that."
Listening cues that say dig here
- Emotion. Frustration, resignation, a sigh. That's where the real pain is.
- Specifics volunteered. A name, a date, a number. They're reliving something — follow it.
- Hedging. "It's kind of a whole thing" usually means there's a story they haven't decided whether to tell. Ask.
- A workaround described in detail. People who've built an elaborate manual process feel the pain daily.
Let the demo be pre-work
If a prospect wants "just a quick look" on the discovery call, you're forced to show the product before you know what matters — the weakest kind of demo. Send a short interactive demo ahead of the call instead:
Now the call opens with "you've seen the overview — tell me about how your team handles this today" instead of a feature walkthrough.
Write down the prospect's exact phrases during discovery. When you follow up with a recap email or a tailored demo, using their words back to them is what makes it land.
Related: how to give a product demo, how to book more sales demos, how to handle "just send me more info".
Frequently asked questions
What questions should you ask on a discovery call?
Questions about specific recent situations rather than general opinions: what triggered them to look now, walk me through the last time the problem bit them, what have they already tried, what happens if they do nothing, who else is affected, and how they would know this was solved. Follow every answer with 'tell me more about that.'
What is the most common discovery call mistake?
Running through a qualification checklist (budget, authority, need, timeline) as a form to fill out, and accepting the first surface-level answer. 'We need better reporting' is not pain — it's a summary. The pain is the specific meeting where someone got asked for a number nobody had. Discovery is getting from the summary to the scene.
How long should a discovery call be?
Usually 20 to 30 minutes, and it should be mostly the prospect talking. If you are talking more than a third of the time, you are pitching, not discovering. Save the demo and the pitch for a follow-up once you know what matters.
Should you demo on a discovery call?
Generally no — or only a brief targeted glimpse if the prospect asks. A full demo before you understand the problem forces you to show everything, which is the least effective demo. Sending a short interactive demo as pre-work lets the prospect get the overview themselves, so the discovery call can go deeper.