The most common mistake in a discovery call is moving to the pitch too fast. A rep who pitches before they've actually understood the problem is guessing — and prospects can tell.
Great discovery isn't about asking more questions. It's about asking the right questions in the right order, listening to what's under the answer, and building a clear picture of the pain before you ever reach for your product.
Here are 20 questions that do that, organized by what they're trying to surface.
Situational questions: understanding the current state
These establish context before you diagnose pain. The goal is to understand how things work today — not to pitch against it yet.
- "How does your team currently handle [X]?" — The baseline. You need to understand the existing process before you can find the gap in it.
- "How long have you been doing it that way?" — Tells you whether this is an entrenched process (harder to change) or something that's been evolving (more open to change).
- "How many people are involved in that process?" — Reveals the scope of the problem and the complexity of a potential change.
- "What does the typical workflow look like from start to finish?" — Opens up the full picture. Often the real pain isn't where they said it was.
- "What tools or systems are you using for that today?" — Tells you what you're competing with or complementing.
Problem questions: finding the friction
Once you understand the current state, these questions surface where it's breaking down.
- "What's the thing that frustrates your team most about how that works right now?" — The most direct path to pain. Ask it plainly — don't dress it up.
- "Where does the process break down?" — Slightly different angle. Some prospects answer "frustrations" with minor annoyances but will tell you the actual failures if you ask this way.
- "What happens when [the process] doesn't go right? What does that cost you?" — Connects the pain to business impact. Pain that has a cost attached to it is much easier to build a business case around.
- "Is this something you've tried to fix before? What happened?" — Critical question. If they tried and failed, you need to understand why before you pitch a solution.
- "How does this affect [adjacent team or person]?" — Often the biggest problems don't show up where the prospect expects them. This question surfaces downstream impact they might not have connected yet.
Implication questions: making the pain felt
These questions help the prospect fully articulate the consequences of the problem — which builds urgency without you having to manufacture it.
- "What would it mean for the team if this kept going the way it is for another year?" — Forces a forward projection. Prospects often haven't explicitly thought through the compound effect of the problem.
- "How is this affecting [specific outcome you know they care about — revenue, retention, time-to-close]?" — Makes the problem specific to something they're accountable for.
- "What's your read on how your leadership thinks about this?" — Tells you whether this is a priority at the level that makes decisions, or something that matters to the person you're talking to but not above them.
- "What does it cost you in [time / money / headcount] when this goes wrong?" — Quantification question. If they can put a number on it, the business case builds itself.
Need-payoff questions: building toward the solution
These are asked after you understand the pain. They help the prospect articulate what "fixed" looks like — in their own words.
- "If you could wave a wand and fix one thing about how this works, what would it be?" — The single most clarifying question in discovery. The answer tells you exactly what to pitch against.
- "What would a good outcome look like in six months?" — Gets specific about the future state they're trying to reach.
- "What would need to be true for you to feel like this was the right decision?" — Surfaces the evaluation criteria they'll use to judge any solution, including yours.
- "How are you thinking about priorities right now — is this something you're actively trying to solve, or more on the watch list?" — Tells you the urgency level. Critical for qualifying before you spend more time.
Closing the discovery: preparing the handoff
These questions close the discovery and set up a natural next step.
- "What am I missing? Is there anything about your situation I should understand that we haven't covered?" — Gives the prospect a chance to add what they held back. Often produces the most important piece of information in the call.
- "Based on what you've told me, does it make sense for me to show you how we'd approach this?" — A permission-based transition to the pitch. Asking instead of assuming respects the prospect's time and confirms you're talking about a real problem.
The order matters as much as the questions
These questions don't work in isolation. Asking an implication question before you've established the situation lands wrong — it feels presumptuous. Jumping to "what would fixed look like?" before the prospect has articulated the pain skips the step that makes the solution feel relevant.
Run them in order: situation → problem → implication → payoff. Each layer builds on the last, and by the time you get to question 20, the prospect has talked themselves into the business case for your product without you having to push.
Practice discovery before you do it live
Discovery is a skill, not a script. The questions above give you the framework — but the ability to use them naturally under real pressure, without losing the thread of the conversation, only comes from practice.
The fastest way to get there is repeated reps with immediate feedback: running calls, getting scored on whether you asked before you pitched, and seeing exactly where you moved too fast.