Most AEs ask what prospects think their problem is. Top performers ask what's actually happening, then verify it before moving forward.
You ask about their situation, their pain, their timeline. The prospect gives you an answer. You nod, take a note, and move to the next question. Three days later you're prepping for the demo and you realize you never actually confirmed whether what they told you was real.
Discovery calls fail not because you ask the wrong questions, but because you treat the answers as facts instead of hypotheses. A prospect can tell you they have a budget, a timeline, and stakeholder alignment—and still walk away from a deal because none of it was actually true. The problem is discovery that stays in the conversation and never moves into the world.
When a prospect says they have a pain, your next move should not be the next question on your framework. It should be: "What does that look like in practice?" Then, crucially: "Can you show me?"
If they say approval takes too long, ask them to pull up their last sign-off chain and walk you through it. If they say their current tool doesn't integrate with their stack, ask which specific systems and whether they've tried to build a connector. If they claim budget is approved, ask to see it in their procurement calendar or forecast.
Most AEs skip this step because it feels aggressive or because they assume the prospect is telling the truth. But this is exactly where qualification actually happens. A prospect who can show you the problem is qualified. A prospect who can't is either lying, exaggerating, or hasn't done the work yet.
Here's what happens in a typical discovery call:
Prospect: "Yeah, our current process is manual and it's killing our team."
Rep (next question): "How many people does that affect?"
What actually needs to happen:
Prospect: "Yeah, our current process is manual and it's killing our team."
Rep: "Walk me through how you do it right now. From start to finish."
Prospect: "Well, we get a request in email, someone manually logs it in our system, then we..."
Rep: "Okay, show me your email right now. I want to see what that actually looks like."
The second version takes longer. It's also the one where you find out whether the pain is a minor inefficiency or a breaking process. You find out whether the prospect has actually thought about fixing it or whether they're just venting. You find out whether they're the person who can fix it or whether they're complaining about someone else's job.
A discovery call should end with a clear binary outcome: you either have evidence that this deal has legs, or you don't. If a prospect can't pull up their tech stack to discuss integration. If they can't articulate which specific workflows are broken. If they can't name the person who actually owns the budget. You have your answer—and it's not a qualified opportunity, it's a tire-kicker.
The instinct is to keep pushing: "Okay, no worries, we can circle back when you have that information." But that's wasted energy. A truly qualified prospect will hunt for a way to show you the problem because they want the solution.
If the pain is about speed: ask them to show you a recent example of the slowdown and how long it took.
If the pain is about accuracy: ask them to pull the last time they caught an error and what it cost.
If the pain is about visibility: ask them to show you the current dashboard or report they're using and point out what's missing.
If the pain is about integrations: ask them to name the three systems that need to talk and whether they've documented how they currently don't.
If the pain is about compliance: ask them to show you the audit findings or the gaps in their current controls.
In each case, you're not being difficult. You're being thorough. And you're separating prospects who have actually felt the pain from prospects who've just heard it mentioned in a meeting.
When you end a discovery call without pulling in evidence, your next step is a guess. You're sending a demo to someone who said they had a problem, but you've never seen it.
When you end a discovery call with proof—a screen they showed you, a number they cited from a real document, a workflow they walked you through—your next step is a conversation between someone who understands the problem and someone who can solve it. That's when a deal actually moves.
The frameworks you're using—SPICED, SPIN, MEDDPICC—all work. But only if you move past the words and into the proof. The best discovery isn't the one with the most questions answered. It's the one where you've verified enough to know whether you're moving forward or moving on.
Frame it as curiosity, not skepticism: 'I'd love to see how you currently handle this—can you pull up an example?' Most prospects appreciate the genuine interest. If they push back, that's signal that the problem isn't as real as they said it was.
A truly motivated prospect will make time to find it during the call or immediately after. If they can't or won't, they're either not the right person or the pain isn't actually driving urgency. Move forward cautiously—their next no will cost you more time than stopping now.
Pulling up one or two screens takes 2-3 minutes per proof point. That's time saved later, because you're not chasing a deal that was never qualified. One screen shown beats ten questions answered about a problem you've never seen.
You have enough when you could describe their problem to a colleague without relying on what they told you—when you've seen the workflow, the data, or the impact yourself. If you can only repeat what they said, you need one more screen or example.
Part of our guide to Discovery calls.
Repwing listens to your discovery calls and puts the next question on your phone while you are still in the conversation. Fourteen days free, no card.
Start free trial