Closing the Deal: Mastering the 'What Needs to Be True' Question

Forget the aggressive, pushy closes. The "what would need to be true" question is pure leverage, pure insight. It's not about forcing a 'yes,' but about uncovering every 'no' before it derails your deal. This question, dropped at the right moment, makes the prospect outline their own path to buying. Execute it wrong, and you'll sound like every other sales drone. Execute it right, and you'll expose every blocker, every doubt, and every stakeholder you didn't even know existed.

Unpacking the "What Needs to Be True" Framework

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" (WWNBT) framework is a negotiation and sales superpower. It's essentially asking the prospect to define the conditions under which they would move forward. This isn't a commitment ask; it's a diagnostic tool. Your goal isn't to get them to agree to buy right now, it's to get them to articulate the full scope of their decision-making process. Done correctly, it shifts the burden of problem-solving from you to them, creating a collaborative path forward instead of a confrontational one. This isn't financial advice, but understanding decision frameworks can clarify your path to earning and investing.

This question is best deployed after you've presented your proposed solution and the prospect indicates some level of interest, but isn't quite ready to commit. Maybe they're hesitant, have unspoken concerns, or are simply unsure of the next steps. It's your job to identify those hesitations and bring them to light. Too many closers think they need to talk prospects into a 'yes' when, in reality, they just need to help clear the path.

Strategic Deployment of the WWNBT Question

Timing is everything with the WWNBT question. Don't blast it out immediately. Build rapport, establish value, and present your solution first. Once you've laid that groundwork, and you sense a subtle hesitation or a need for more information, that's your cue. Your tone should be collaborative, not inquisitive. You're trying to help them think through their own process, not interrogate them.

For example, after a demo, if a prospect says, "This looks really promising, but I need to think about it," instead of pressing for a commitment, you'd deliver the WWNBT. It sounds something like, "I appreciate that. To help you think through it, what would need to be true for you to feel confident moving forward with a [Your Offer/Solution] rollout by [Proposed Date]?" Or, "Okay, based on what we've seen today, what would need to be true for your team to be excited about adopting this solution?" The specific wording can vary, but the intent remains the same: uncover the real conditions.

checklist title=