Most discovery calls follow the same pattern. I present my offering. I explain the features. I assume I know what matters to them. And the deal stalls because I never actually asked what would make them confident.

Last week I was working through a potential partnership structure with a prospect. My instinct was to walk through all the ways we could make it work: different fee structures, margin splits, service levels. Instead, I stopped and asked a single question: “What would a partnership roadmap need to show you to justify the value against the margin cut you’re considering?”

That question unlocked everything. Suddenly they articulated the real concerns. They needed proof the partnership would cover their COGS. They needed visibility that we could train their team to 70 percent readiness before the margin conversation even happened. They needed a clear milestone structure showing exactly when and how the partnership would generate return.

None of that came from my pitch. All of it came from them diagnosing their own objection when I asked the right question.

This is the difference between guessing and discovering. Most salespeople guess. We assume the price is the problem, or the implementation timeline, or the feature set. So we pitch against those objections before the prospect even mentions them. That approach closes some deals. But it misses the ones that fail silently because we never asked the right question.

Top performers I’ve studied work differently. They diagnose before they prescribe. They ask “how come” instead of offering solutions. “How come that doesn’t work for you?” “How come you’d need that in place before moving forward?” The answers separate real blockers from surface-level concerns.

The impact shows up in the close rate. When I shifted to this approach with discovery calls, our new contract structure (meeting-count-based pricing instead of a platform fee) started closing at 100 percent on the initial conversation. That’s not because the offer got better. It’s because we stopped guessing what they needed and started asking them to tell us.

The partnership example proves the point. Once I understood their real requirements (the roadmap, the training proof points, the margin justification), I could structure something that actually addressed those concerns instead of what I assumed they cared about. The deal moved forward because they felt heard, not pitched to.

This principle applies everywhere in sales. A contact goes quiet in your pipeline. You could assume they’re not interested, so you move on. Or you could ask: “What would need to change for this to feel like the right time?” Maybe they’re waiting on budget approval. Maybe they’re evaluating a competitor. Maybe they just forgot about the conversation. Without asking, you never know.

The lesson is simple but hard to execute. It requires patience. It requires resisting the urge to solve the problem immediately. It requires sitting with silence after you ask a question, letting the prospect think through their own objection instead of filling the gap with more talking.

But the payoff is massive. When a prospect articulates their own concern, they’re also articulating their own solution. They own the objection instead of dismissing yours. They feel like you understand them because you actually listened instead of performing a pitch.

Start with one question on your next discovery call: “What would need to be true for this to work for you?” Then shut up and listen. Let them tell you where the real deal-blocker lives. Build your proposal around what they said, not what you assumed.

The 100 percent close rate starts there.