Most discovery calls confirm that a problem exists and then move to pitching the solution. Gap Selling argues that this is exactly backwards. The problem is not the decision point, the consequence of the problem is. A buyer who says “our proposal turnaround is too slow” has given you awareness. A buyer who says “our proposal turnaround is costing us roughly three deals a month, which at our ACV is about $90K in annual recurring revenue” has given you a business case. Implication questions are how you get from the first statement to the second.
The Gap Selling Sequence
Keenan’s Gap Selling framework maps the discovery conversation as a movement through three states: current state (where the buyer is now), future state (where they want to be), and the gap (why they haven’t crossed it yet). Implication questions live at the bridge between current state and gap, they make the gap feel costly rather than merely inconvenient.
Without implication questions, the gap is theoretical. The buyer knows it’s there. They’ve lived with it for months. Familiarity dulls urgency. The implication question interrupts that familiarity by asking: “And what does living with this gap cost you?”
Eight Implication Questions
These eight questions are mapped to different consequence categories. You don’t use all eight. You pick the two or three that fit the problem you’ve just confirmed.
Revenue and growth impact: “If this doesn’t get resolved in the next two quarters, what does that do to your growth targets?” Makes the buyer connect operational friction to the number their boss cares about.
Team and capacity cost: “How much of your team’s time is going into working around this right now?” Converts inefficiency into headcount cost, often the first time the buyer has done this math.
Customer experience risk: “Has this problem touched any customer relationships yet? What’s the exposure if it escalates?” Surfaces churn risk the buyer may be minimizing.
Competitive position: “Are competitors solving this in a way that affects how prospects choose?” Makes the problem a market-position issue, not just an internal one.
Decision delay cost: “What’s already been delayed or deprioritized because this is still unresolved?” Shows opportunity cost the buyer is absorbing while the status quo holds.
Leadership visibility: “Does your leadership see this as a blocker, or is it below the radar right now?” Surfaces political implications, budget risk if it stays invisible, pressure if it’s visible.
Cumulative timeline: “You mentioned this has been going on for about eight months. What has that cost cumulatively?” Forces arithmetic on duration, not just current state.
Future state blockade: “What’s the next initiative that can’t move forward until this is solved?” Ties the problem to something the buyer already wants, making resolution feel like unblocking progress rather than solving a past problem.
The buyer who says the number out loud has already sold themselves. Your job in implication questioning is to be the guide who hands them the calculator, not the one who reads them the total.
The Self-Justification Mechanism
Why do implication questions work so reliably? Because of a principle Gap Selling borrows from behavioral economics: self-generated conclusions carry more persuasive weight than externally delivered ones. When you tell a buyer “this problem is costing you $40K a quarter,” they discount it. When they say it themselves in response to your question, they believe it completely.
This is why the structure of implication questions matters. “Your slow proposals are losing you deals” is a statement. “If your proposals are taking 5 days longer than competitors, how does that affect win rate in competitive bids?” is a question. The buyer does the reasoning. The conclusion lands differently.
Booking the Next Meeting at 80%
The step that follows strong implication work is a natural pivot to future state. “Given all of that, the revenue at risk, the team hours, the deals delayed, what would solving this open up for you?” The buyer describes the upside. You’ve now mapped both sides of the gap: cost of staying and value of crossing.
From this position, the call close almost writes itself: “I can show you specifically how we’d address [the two implications they named]. Would a working session next week be worth your time?” When the buyer has just quantified what staying put costs them, “yes” is the easy answer. That’s why post-implication booking rates run significantly higher than calls where the pain was identified but never made financially real.
What to Avoid
Two common mistakes kill implication work. First: piling on too fast. If a buyer describes a painful consequence and you immediately jump to the next implication question, you signal that you’re running a script. Pause, reflect it back (“that’s significant, $90K a quarter is not a rounding error”), then continue. The pause signals that you’re actually listening.
Second: manufacturing implications the buyer doesn’t recognize. If you push “surely that’s costing you customer satisfaction?” and the buyer says “not really, customers haven’t noticed,” drop it. Move to a different implication category. Fighting the buyer’s assessment of their own situation destroys trust faster than any price objection.
The Two-Question Minimum
Even on a 20-minute qualifying call, use at least two implication questions: one financial, one strategic. Financial makes the cost visible. Strategic connects it to something the buyer cares about beyond the immediate number, their roadmap, their position, their team’s credibility. Two questions, answered in the buyer’s own words, transform a problem conversation into a business case. That’s the call that books the next call.
