Most AEs ask discovery questions that sound like all the others. Here's how to dig for the real problem in 30 minutes.
Your discovery questions sound like everyone else's, which means your prospects have heard them a dozen times already. They answer them on autopilot—shallow, guarded, rehearsed. You get background noise instead of what you actually need: the specific problem that makes them willing to move.
The issue isn't the questions themselves. It's that most AEs ask them in the wrong order, at the wrong depth, and without a clear hypothesis about what they're actually looking for. You end up with a call that feels like a quiz show instead of a conversation.
Most AEs open discovery by asking "tell me about your current setup." That's too broad and invites a ten-minute monologue that goes nowhere. Instead, lead with context: the specific pressure point you know exists in this industry, this role, or this company size.
Come in with a point of view. "In your role, I typically see teams struggling with either visibility into pipeline coverage or coaching consistency—or both. Where are you landing?" That's not a question. It's a hypothesis backed by specificity. The prospect either agrees or corrects you—either way, you're now in a real conversation instead of an interview.
Specificity disarms the rehearsed answer. It signals you've done homework, so they don't need to explain their entire business from the ground floor. You've earned compressed time.
Once you've landed on situation, you move to pain—but most AEs skip the permission step. They jump straight into "what's your biggest challenge?" and hit a wall.
Instead: "Would it be worth spending a few minutes understanding where this breaks down for you?" You're asking to go deeper. That sounds small, but it changes everything. The prospect mentally shifts from "pitch mode" to "diagnosis mode." They're now volunteering to tell you what's broken.
Then you can ask the real question: "Walk me through what happens when visibility drops in your pipeline." Paint the scenario. Make them relive the problem. Real pain isn't abstract—it's specific. A rep misses a deal slip because forecast data was stale. A leader can't coach the deal because she doesn't know what happened on the call. That's pain.
Listen for the word "we" instead of "they." "We don't catch that in time" signals the prospect owns the problem. That's a strong signal the pain is real, not hypothetical.
After pain, most AEs ask "how much does that cost you?"—a dollars question that usually gets deflected. Impact is deeper than cost. Impact is what happens to their job, their team, their credibility, their year-end review if this doesn't change.
Ask: "When that happens, what's the ripple effect?" Let them connect the dots. A missed forecast means a rep misses quota, which means no bonus, which means that rep leaves in Q2, which means you're ramping someone new right into your biggest season. Impact chains through the organization in ways that matter to every stakeholder in the room.
Impact questions do the selling for you. They're the moment a prospect realizes they can't ignore the problem anymore. Your job is to ask the question and then sit in the silence while they think.
The SPICED framework includes "Critical Event"—the trigger that makes them willing to move. It's the difference between "we've had this problem for two years" (no timeline) and "we're in planning for next year and the CFO said we need to fix this or we're stuck with what we have" (timeline).
Instead of asking directly, embed it in your follow-up: "What's got to happen in the next 90 days that would make solving this a priority?" This does three things: it surfaces budget timing, it disqualifies deals stuck in perpetual motion, and it tells you whether the deal has oxygen or not.
If there's no critical event, there's no deal velocity. Move on.
Before you close, you need to know how they decide. Most AEs skip this or bury it so deep in the call that it comes out as "so who else needs to weigh in?" That's too late.
Instead: "Walk me through how you'd actually make a decision on something like this." You're not asking if they'll decide—you're asking how the process works. Who's involved? What do they need to see? How long does it take? This isn't a formality; it's your forecast.
A prospect who says "it'd just be me and my manager" has a clearer path than one who says "well, our engineering team would need to approve." You now know the complexity before you spend two months selling.
A discovery call should land in 30 minutes for mid-market deals and 45 minutes for enterprise. Shorter than 30 minutes doesn't give you enough time to surface real pain. Longer than 45 minutes erodes prospect attention.
That means each category—Situation, Pain, Impact, Critical Event, Decision—gets roughly 6 to 10 minutes. You ask 6 to 8 open-ended questions total. The rest is listening and following the thread where it leads.
Most AEs talk too much. The best discovery calls have a 30/70 split: you talk 30 percent, the prospect talks 70 percent. When you find yourself about to ask the next question and realize you already know the answer from what they just said, stop. Let them keep going.
The best signal isn't what they say—it's what they do with their face and body. When a prospect moves forward in their chair, when their tone shifts from guarded to invested, when they start asking you questions back—that's when pain has become real to them. That's when the call has worked.
The rest is logistics. You summarize what you heard in their words, confirm the critical event, align on next steps, and book the follow-up live. Send a personalized summary the next day. That's it.
Specificity up front. Permission before depth. Impact over cost. Critical events before you close. Decision frameworks before you leave. This is the system that moves deals instead of moving calls around.
The questions themselves aren't magic. The order is. The permission is. The hypothesis is. Run this structure on your next five calls and watch what changes in your forecast.
Ask 6 to 8 open-ended questions total on a discovery call. The rest is listening and following where the prospect takes the conversation. More questions means less time for them to talk, which defeats the purpose of discovery.
Aim for 30/70: you talk 30 percent, the prospect talks 70 percent. Most AEs dominate the call when they should be listening. The more they talk, the more you learn.
Thirty minutes for mid-market deals, 45 minutes for enterprise deals. Shorter than 30 minutes doesn't surface real pain. Longer than 45 minutes erodes prospect attention—most disengage around the 47-minute mark.
SPICED is a discovery framework: Situation (their current state), Pain (where it breaks), Impact (what it costs them), Critical Event (what drives timing), Decision (how they'll decide). It replaced BANT because modern B2B buying often allocates budget after pain is acknowledged, not before.
Cost questions get deflected. Impact questions get at what the problem costs them personally—missed quota, losing people, damaged credibility. Impact chains through the organization and makes them realize they can't ignore the problem.
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