The pain a buyer names first is rarely the one they'd actually write a check to fix. "We want to close more deals" is not a problem — it's a wish. The real problem is the broken thing underneath it, and finding that is the core of AE-depth discovery. Diagnose the problem behind the problem, and you'll know what to demo, what to put in the proposal, and why the buyer should care enough to act now.
Why the first answer is never the real one
Buyers describe symptoms because symptoms are what they've noticed. When a rep says "deals are taking too long," that's an outcome. The root cause — reps can't see deal status, data is scattered, no one owns the next step — is what your product actually fixes. Chase the root cause and you build a case that survives procurement; chase the symptom and you're selling against a vague hope.
The five lines of questioning
Use these to move from symptom to root in a discovery call:
- What's the outcome that's bothering them? ("What made you bring this up?")
- What's the cause underneath it? ("What do you think is driving that?") — keep asking until you hit something fixable.
- What has it already cost? Money, time, missed deals, broken forecasts — make the pain concrete.
- Who else feels it? The more people the problem touches, the more stakeholders will back a fix.
- What happens if nothing changes? The cost of inaction is what turns a nice-to-have into a priority.
The tell you're still at the surface
You're at the surface if you could replace your company's name with a competitor's and nothing about the conversation would change. You've found the real pain when the buyer describes a specific, fixable, expensive problem in their own operation — and you can name what it costs them to leave it alone.
Start here
Once you've diagnosed the real pain, the deal only moves if there's money behind it. The next lesson makes that concrete — qualifying the budget so you know a real opportunity from a polite conversation.