Use 'What Would Need to Be True' to Close More Discovery Calls

Most sales reps fumble the finish. They get through discovery, present a solution, and then hit a wall. Prospects say, "Sounds good, I'll think about it," and disappear into the ether. This isn't a problem with your product; it's a problem with your process. Specifically, it's a problem with how you handle the transition from discovery to commitment. The 'What Would Need to Be True' question is your sledgehammer for that wall. It's a precise tool to uncover explicit conditions for moving forward, revealing where the deal really stands.

This isn't about manipulation. It's aggressive qualification. You're giving the prospect a chance to define their success metrics and show their hand. When they tell you what needs to be true, they're handing you the roadmap to the close. You either meet those conditions, or you know precisely why the deal won't happen. No more chasing ghosts or hoping for the best.

Why 'What Would Need to Be True' Cuts Through Noise

Traditional closing questions often generate vague responses. "Do you like it?" "Are you interested?" They're too soft, too easy to sidestep. The 'What Would Need to Be True' question forces specificity. It shifts the burden of defining the next step from you to the prospect. They have to articulate the conditions under which they would proceed.

This question acts like a diagnostic tool. If they can't answer, it tells you they're not bought in yet, or you haven't uncovered enough pain. If they do answer, those answers become your checklist for a successful close. It uncovers hidden stakeholders, budget constraints, timing issues, or integration headaches that a weaker discovery process might miss entirely. Stop guessing and start getting the hard facts about their decision-making process.

Quick pause. If any of this is landing, the fastest way to actually run these plays is a 10-minute call with a Fat Wallet Sales operator. No pitch. No obligation.

"The 'What Would Need to Be True' question transforms 'maybe later' into 'here's exactly what it takes.' It's not a closing technique; it's a commitment-defining mechanism." - Fat Wallet Sales Pro

Structuring the WWNTBT Question

The most effective way to ask "What would need to be true?" is to preface it with an assumption of their positive intent, even if you suspect otherwise. For example: "Assuming we could solve [Problem X] and deliver [Benefit Y], what would need to be true internally for you to move forward with a solution like ours by [Date Z]?" This isn't just about asking the question, but the setup around it. You're framing it as a logical next step, not a confrontational demand.

Another approach is to attach it to a specific outcome: "If we hit every mark you laid out in discovery, what would need to be true for you to feel confident signing off on this?" This version reinforces that you've been listening and that their input is driving the process. The key is making sure they are defining the conditions, not you. This gives you a clear path to follow in negotiating concessions or defining your 3-tier offer stack.

Actionable Implementation Strategies

Once you get those conditions, your job is to either meet them or address why they can't be met. If a prospect says, "We'd need to have budget approval from finance," your next step isn't to send a proposal; it's to ask, "Okay, what's that process look like? Who needs to be involved, and can we schedule 15 minutes with them next week to outline the ROI?" Never accept a condition as a roadblock without trying to dismantle it.

This question is also phenomenal for uncovering true objections versus vague brush-offs. A prospect might say, "We just need to think about it." Rather than accepting that, you can hit them with: "I understand you need time. To help me understand, what specifically would need to be true about our solution, or your internal situation, for 'thinking about it' to turn into 'let's do this'?" This forces them to articulate the actual barrier, allowing you to handle the real objection instead of guessing.

::: script title=