Most AEs ask questions but don't listen for the pain beneath the answer. Here's how to spot it, dig deeper, and turn it into qualification.
You ask what looks like a good discovery question, the prospect answers, and you move on. Meanwhile, the real problem—the one that would justify a contract—stays buried under a polite surface answer.
The difference between a question that collects data and a question that surfaces pain is what happens after they answer. Most AEs hear the words, check a box, and pivot to the next item on their list. What they miss: the hesitation, the specificity, the frustration hiding in how the prospect answered.
SPICED (Situation, Pain, Impact, Critical Event, Decision) is the framework most enterprise teams run in 2026, and it's built around pain. But pain doesn't come out as a single sentence. When you ask "What's your current process?" a prospect might say, "We use a spreadsheet." That sounds like a process. It's not. It's a symptom.
The pain is in the follow-up: "How long does that take?" (Three days a month.) "Who does it?" (One person, manually.) "What happens when they're out?" (We miss data.) "How often does that cost you?" (We've lost two deals to bad forecasting this year.)
That last bit is pain. That's what justifies budget.
Your initial discovery question should be open-ended. Don't ask "Do you use a forecasting tool?" Ask "Walk me through how you forecast pipeline." Wait for the full answer. Then ask one follow-up that digs into the cost or consequence.
Prospect: "We build a forecast every Friday based on our sales manager's gut and what's in the pipeline."
You could say: "Thanks. Do you think you'll change that process?" (Weak—they'll just say maybe.)
Instead: "When the forecast doesn't match actual close, what happens to your planning?" (Stronger—this invites them to describe the ripple effect of the problem.)
The second approach forces them to think about impact. Impact is what creates urgency.
When a prospect repeats a word or phrase, stop and mark it. If they say "manual," "slow," "frustrated," or "scrambling" more than once, that's a pressure point. That's where they have language for the pain already.
Example:
Prospect: "We end up doing a lot of manual work at the end of the quarter."
Later: "The manual entry is where we introduce the most errors."
You now have two mentions of "manual." That's your next question: "Of all the manual work, what's the most time-intensive part?" You're not guessing what hurts—you're following where they already told you it hurts.
Most objections and deflections in a discovery call aren't what they look like on the surface. "We're happy with our current solution" doesn't mean they're happy. It means they haven't thought about switching, or they're protecting themselves from looking wrong if they admit a problem.
When you hear a deflection, don't argue. Rephrase it as a question that lets them explore what's underneath.
Prospect: "We're actually pretty satisfied with what we have."
Bad response: "I understand, but many teams find we solve X." (This dismisses what they said.)
Good response: "Makes sense. I'm curious—what would need to change for you to reconsider something else?" (This respects the surface answer while inviting them to talk about gaps.)
At the end of discovery, you need two commitments: agreement that the pain is real, and agreement that it's worth solving. Most AEs skip this and go straight to "Let's set up a demo."
Instead, try this close:
"Here's what I'm hearing: You're spending about three days a month on manual forecasting, and when the forecast misses, it directly impacts your budget decisions. Did I get that right?" (They confirm or correct.)
"And if we could cut that down to a few hours a month and improve accuracy, that would be worth a conversation?" (They either say yes or surface a new objection you need to dig into now, not later.)
This gives you certainty. You're not guessing whether they have pain. You've confirmed it together.
A discovery call for mid-market deals should run 30 minutes; enterprise deals, 45. Prospect attention drops after 47 minutes, so respect the boundary. This means your job in discovery is to ask fewer questions better, not to fill time.
Three good questions that surface pain are better than ten questions that collect data. Spend 70% of the call listening. Ask a question. Sit in the quiet while they think. Don't fill the silence with a follow-up question before they've finished thinking.
That silence is where pain emerges.
A good discovery question prompts a specific answer about how the prospect's current state differs from their ideal state, or reveals a consequence they're tolerating. If they answer with a single sentence and you have no obvious follow-up, the question didn't dig deep enough.
BANT (Budget, Authority, Need, Timing) qualifies out deals where budget doesn't exist yet. SPICED (Situation, Pain, Impact, Critical Event, Decision) uncovers pain first, then builds budget justification from that pain. Modern B2B buying allocates budget after acknowledging pain, so SPICED is the default for enterprise teams in 2026.
Ask one follow-up question that digs into cost or consequence. More than that and you sound like an interrogation. One good follow-up per answer trains you to listen for what they said versus what you expected to hear.
They do—it's just not explicit. Listen for frustration, repetition, or workarounds they mention. If they describe manually doing something monthly, that's pain. Your job is to connect the dots: "You mentioned you're doing that manually—how much time does that actually cost you per month?"
Notes kill listening. Record the call or use a notetaker tool so you can stay present. You'll pick up on hesitation, tone shift, and what they repeat—the real signals that surface pain. You can review the transcript after.
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