Prospects bury their real problems under surface answers. Here's how to ask the follow-up question that surfaces what actually keeps them up at night.
Most discovery calls fail not because you asked the wrong question, but because you accepted the first answer.
A prospect tells you "our process is manual" and you nod. But manual compared to what? Manual enough to fire someone over? Manual enough they've already lost a deal? Manual enough to justify buying? You don't know—and neither does the prospect, yet. You stopped digging.
Real pain lives one layer deeper than the symptom. Your job on discovery is to find the contrast between where they are and where they need to be, and then quantify why that gap matters.
When a prospect answers your opening question about their current situation, they give you a symptom, not a problem. "We're doing a lot of manual work." "Our data lives in spreadsheets." "We can't see the full pipeline." These are true statements, but they're not the reason they'll buy.
The reason they'll buy is that the manual work costs them revenue, or reputation, or peace of mind. Your job is to name that cost explicitly so the prospect can feel it.
After they describe the symptom, ask: "Walk me through what that actually costs you." Not hypothetically—what has it cost them already? A deal lost? A customer complaining? A quarterly miss? A hire they had to make just to manage the spreadsheets?
Make them tell you a story with a number in it. "We missed quota by $300K last quarter because our VP didn't see the deal slip until it was too late." Now you have a real problem.
Most AEs ask yes/no questions on discovery because they're fast and feel safe. "Do you have budget?" "Is timeline an issue?" You get a binary answer and nowhere to go. The prospect gives you nothing to grab.
Instead, ask open-ended questions that force them to explain, not confirm. Replace "Is budget a constraint?" with "Walk me through how budget gets approved in your org." Replace "Do you have a timeline?" with "When does this need to be solved by, and what happens if it's not?"
The open-ended question does two things at once: it surfaces real constraints (because they have to explain them instead of hiding behind "yes" or "no"), and it shows you whether they've actually thought about the problem. If they haven't, that's a disqualify. If they have, you've found someone worth your time.
After they answer, do not immediately ask the next question. Pause for two seconds.
In that silence, one of two things happens. Either they have nothing more to say (which is useful information—they haven't thought it through), or they keep talking. And when they keep talking, they almost always go deeper. The first answer was the surface. The second answer is where the real pain lives.
This is reflective listening: you listen, you pause, and you let discomfort work for you. Most AEs hate silence and fill it with the next question. You're training the prospect to feel safe giving you the short version. Instead, train them to give you the long version by simply waiting.
Once you have the symptom and the cost, probe for the consequence. Ask: "If this doesn't get fixed, what happens next?"
Then ask it again. "And then what?"
The prospect says: "We'll miss quota." You ask: "And if you miss quota?" They say: "I might not hit my bonus." You ask: "And then?" They say: "I might not make my mortgage payment."
You've moved from a business problem to a personal one. Now you know what's actually at stake. That's the lever you'll pull in the email that gets the meeting back on track. That's the thing they'll remember when a competitor also shows up.
This chain of whys isn't manipulation. It's clarity. The prospect often hasn't articulated to themselves why they should move. Your job is to help them see it.
Probing too long turns a discovery call into an interrogation. You have 30 to 45 minutes. If you've asked the opening situation question, dug into pain, understood the impact, and identified when they need to fix it, you've done your job. Stop. Move to next steps.
The mistake AEs make is thinking they need to understand everything on the first call. You don't. You need to understand enough to know if there's a real problem, if they can afford to solve it, and when they need to solve it by. Everything else you learn after they say yes to the next meeting.
Prospects haven't been forced to think deeply about their problem yet, and surface answers are the easiest to give. They expect you to accept the first answer and move on, so they do. Your job is to show them you won't move forward until they've explained the real cost.
Follow the conversation. If the prospect is explaining a real problem in depth, let them finish. Your prepared questions are a backup if they're not giving you detail. A real conversation beats a checklist every time, and prospects can tell the difference.
Stop when you understand the pain, the cost, and the timeline. If you keep probing past that, you'll feel the energy shift—the prospect gets defensive or rushed. You have enough. The goal isn't to understand everything; it's to understand enough to know if they should stay in the pipeline.
That's a successful discovery call. You've disqualified them without wasting either of your time. Write it down, move on, and call someone else. Not every conversation ends in a demo, and that's fine—it means your pipeline has less noise.
Yes, the structure stays the same—symptom, cost, consequence—but the specific words should match their situation. If they mention spreadsheets, ask about spreadsheets. If they mention team frustration, ask about turnover. Match their language so they feel heard.
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