Pulse - Value Added
Rent this Advertising Space
FRACTIONAL CRO · MARYLAND-BASED, NATIONWIDE · $0→$200M

Kory White

RevOps & Revenue Leadership

Get a 30-minute revenue checkup — Kory reviews your pipeline and forecast, then names the 1–2 fixes that move revenue fastest. 25 yrs scaling teams $0→$200M.

30-minute revenue checkup →
Hire a Fractional CROFree 30-Min Checkup$79 Expert OpinionLinkedInRésumé
← Library
Knowledge Library · bs

What’s the biggest mistake reps make during discovery calls that *Gap Selling* explicitly warns against?

Curated by · Fractional CRO · Maryland
PULSEKNOWLEDGE LIBRARY
pulserevops.com
Book SummariesWhat’s the biggest mistake reps make during discovery calls that *Gap Selling* explicitly warns against?
📖 2,301 words🗓️ Published Sep 5, 2026
Direct Answer

The biggest mistake Gap Selling explicitly warns against is leading with the solution — pitching product features, demos, or capabilities before fully diagnosing the customer's Current State and Future State. Keenan calls this "solution addiction": reps hear a vague pain point and immediately pitch, which kills credibility, commoditizes the deal, and prevents the rep from surfacing the financial and emotional weight needed to justify change.

The two options compared

Every discovery call is a fork between two competing strategies, and Gap Selling frames the choice starkly. The first, more common path is the solution-first approach: the rep listens just long enough to pattern-match a stated problem to a feature in their deck, then pivots into pitch mode. The second path — the one Keenan insists on — is the diagnostic-first approach, where the rep treats the first 70-80% of the call as pure investigation and refuses to mention the product until the gap between Current State and Future State has been mapped and both sides agree it's worth closing.

Solution-first selling feels efficient because it produces visible motion — a demo booked, a deck shown, a next step scheduled. But Keenan argues this motion is an illusion of progress. The customer hasn't yet articulated what the problem is actually costing them, so the rep has no leverage beyond "our product does X." That leaves the deal vulnerable to price comparison, feature-checklist evaluation, and stalled decision-making, because nothing about the conversation created urgency. The rep essentially asks the customer to self-diagnose their own pain and then trust that a stranger's product addresses it — a bet most buyers won't make without a compelling reason to act now.

What’s the biggest mistake reps make during discovery calls that *Gap Selling* explicitly warns against — figure 1

Diagnostic-first selling is slower up front and, in Keenan's telling, deliberately uncomfortable. It requires the rep to sit with ambiguity, ask a second and third follow-up question when the customer would rather move on, and resist the pull to "be helpful" by mentioning a relevant feature. The payoff is that by the time the solution is introduced, it isn't a pitch — it's the logical next step in a conversation the customer has already validated. The rep isn't selling a product; they're offering a bridge across a gap the customer has already agreed is real, costly, and worth crossing. This is the core strategy distinction the entire book is built around, and it's the dividing line Keenan uses to separate order-takers from top performers.

The trade-off is real: diagnostic-first discovery takes longer per call and requires reps to tolerate pushback ("can you just show me the product?"). Keenan's answer is that this discomfort is the cost of doing the job correctly — a rep unwilling to sit in that tension is, by definition, still solution-addicted.

What’s the biggest mistake reps make during discovery calls that *Gap Selling* explicitly warns against — figure 2

How to decide between them

Keenan doesn't present this as a judgment call reps make fresh on every call — Gap Selling treats diagnostic-first as the default and solution-first as a rare exception reserved almost entirely for the simplest, lowest-stakes transactions. The decision tree below reflects how the book actually expects reps to route a conversation the moment a customer surfaces a pain point.

The decisive test Keenan gives reps is simple to state and hard to execute: could you describe the customer's situation — the cost of their Current State and the shape of their desired Future State — from memory, without notes, well enough that the customer would say "yeah, that's exactly it"? If not, any solution talk is premature, no matter how far along the calendar says the deal is. This is why "how much time is left in the call" is explicitly not one of the decision inputs in Keenan's framework — a rep who runs out of runway is expected to book a second call rather than compress the pitch into an under-diagnosed conversation.

What’s the biggest mistake reps make during discovery calls that *Gap Selling* explicitly warns against — figure 3

The one legitimate exception the book carves out is deal complexity. For low-ticket, single-stakeholder, largely self-evident purchases, the gap is often already obvious to the buyer, and heavy diagnostic discovery is overkill — Keenan is explicit that Gap Selling is built for complex B2B sales, not commodity transactions. Reps should use deal size, number of stakeholders, and switching cost as the filter for how much diagnostic weight a given call needs, not gut feel or time pressure.

Concrete numbers behind each option

Keenan's framework translates into a few practical, quantifiable rules reps can hold themselves to on every call. As a rule of thumb, the book pushes reps toward spending roughly three-quarters of discovery time — Keenan's practitioners commonly cite a 70-80% split — in Current State and Future State exploration before the product is mentioned at all, leaving only the remaining fraction of the call for positioning the solution as a bridge.

What’s the biggest mistake reps make during discovery calls that *Gap Selling* explicitly warns against — figure 4

Within that diagnostic window, the question mix matters more than the raw time spent. Keenan sorts discovery questions into three tiers: Type 1 (fact-finding, e.g., "how many reps are on your team?"), Type 2 (pain-finding, e.g., "what's your biggest challenge with reporting?"), and Type 3 (gap-widening, e.g., "what does that cost you if it's not fixed by next quarter?"). The operating rule is that every single Type 2 answer should trigger at least two to three Type 3 follow-ups before the rep moves on — a ratio Keenan uses to keep reps from treating one vague pain admission as sufficient justification to pitch. A rep who asks one Type 2 question and zero Type 3 follow-ups has, by this standard, done zero real discovery no matter how many minutes the call lasted.

The "Why Now?" line of questioning gets its own numeric discipline: Keenan recommends reps never accept a stated timeline (e.g., "we want to decide by Q3") at face value on the first pass — it should be probed with at least one direct follow-up ("what happens if you wait six more months?") before it's logged as a real, cost-driven deadline rather than an arbitrary or internally-political one.

What’s the biggest mistake reps make during discovery calls that *Gap Selling* explicitly warns against — figure 5

On the demo side, the practical number is zero: no product screen should be shared in the first meeting unless the deal is transactional. Keenan's guidance is that the demo is earned, not scheduled by default — many complex-deal discovery processes run across two or more calls specifically so the diagnostic work isn't compressed to fit a single 30-minute slot. Reps under quota pressure to "show the product" in call one are, in Keenan's framing, trading a small short-term appearance of progress for a much larger risk of a stalled or price-shopped deal later.

Finally, the emotional layer has its own test rather than a number: if a rep can complete an entire discovery call without ever asking a question that makes them personally a little uncomfortable — about how the problem makes the buyer look to their boss, or what solving it would do for their career — Keenan's rule is that the call stayed in the "safe zone" and almost certainly under-diagnosed the deal.

What’s the biggest mistake reps make during discovery calls that *Gap Selling* explicitly warns against — figure 6

Implementation details and sequencing

Turning "don't lead with the solution" into a repeatable habit requires a specific sequence, and Keenan is prescriptive about the order of operations rather than leaving it to feel. The sequence below is the practical, step-by-step version of the no-demo rule.

First, before the call, the rep should explicitly plan to withhold the pitch — Keenan recommends going in with the private goal of not mentioning the product at all in a first meeting for a complex deal. Second, on the call, the rep opens with broad Type 1 and Type 2 questions to locate where the pain lives, then immediately pivots into Type 3 gap-widening questions on every pain point the customer raises, chasing financial impact, emotional toll, and operational friction in turn. Third, the rep must map the Future State with equal rigor — asking the customer to describe, in their own words, what a solved version of their day or quarter looks like, and which metric would visibly change. Critically, Keenan insists the customer must own this vision; a rep who supplies the Future State themselves ("so basically you'd want a dashboard like ours") has quietly slipped back into solution-first mode.

What’s the biggest mistake reps make during discovery calls that *Gap Selling* explicitly warns against — figure 7

Fourth, the rep explicitly names the gap back to the customer and asks for agreement that it's worth closing — a verbal checkpoint before any mention of a fix. Fifth, and only after that agreement, the rep introduces the solution strictly as a bridge across the specific gap just agreed upon, not as a generic feature tour. If a customer asks for a demo before this sequence is complete, the scripted response Keenan recommends is a version of: "I want to make sure I understand your situation well enough that the demo is actually useful to you — let me ask a few more questions first." This isn't a stall tactic; it's positioned as evidence the rep is taking the engagement seriously.

Sequencing failures tend to cluster around two points: reps skipping straight from Type 1 to a pitch without ever reaching Type 3 depth, and reps building the Future State vision on the customer's behalf instead of eliciting it. Both failures are explicitly named in Gap Selling as symptoms of the same root mistake — the rep's discomfort with silence and ambiguity, resolved by retreating to the safety of a rehearsed pitch.

What’s the biggest mistake reps make during discovery calls that *Gap Selling* explicitly warns against — figure 8

Related questions

Why does Gap Selling call solution-first pitching an addiction rather than just a habit?

Keenan uses "addiction" because the behavior is reinforced short-term — pitching feels productive and relieves the rep's discomfort with silence — even though it damages close rates and cycle length over the long run.

What is the single question Gap Selling says most reps never ask?

"Why now?" — followed by "what happens if you wait?" — to test whether a stated buying timeline is cost-driven and real or arbitrary and easily pushed.

Does Gap Selling apply to every type of sale?

No. Keenan scopes the methodology to complex, multi-stakeholder B2B sales; for simple transactional purchases the gap is often self-evident and heavy diagnostic discovery is unnecessary.

How many Type 3 follow-up questions should a rep ask per pain point?

Keenan's practical guidance is two to three gap-widening follow-ups for every Type 2 pain admission, enough to surface financial, emotional, and operational dimensions before moving on.

What replaces the traditional "discover, demo, close" sequence in Gap Selling?

A "diagnose, agree on the gap, then bridge" sequence, where the demo is withheld until the customer has explicitly agreed the gap is real and worth closing.

FAQ

Isn't leading with the solution sometimes necessary to hold the customer's attention? No — Keenan argues solution-first pitches reduce attention because the customer hasn't felt the pain yet, which makes the rep interchangeable with any other vendor showing similar features.

How do I avoid sounding like I'm interrogating the customer during discovery? Frame questions as curiosity rather than a checklist — phrases like "help me understand" or "what's the impact of that on your team?" keep the tone conversational, and repeating back what you heard signals genuine listening rather than data collection.

What if the customer insists on seeing the product immediately? Push back politely: "I want to make sure I show you the right things — can we spend a bit more time on your situation first?" Keenan frames this as building authority, not stalling.

Does Gap Selling work for transactional, low-ticket sales? Not really by design — the book targets complex B2B deals with multiple stakeholders; for simple purchases the gap is usually obvious and the full methodology is overkill.

What's the fastest way to tell a rep is still solution-addicted? They can't describe the customer's Current State cost and Future State vision from memory without notes, or the customer's response to their pitch is a noncommittal "that makes sense" rather than "when can we start?"

How should a manager train a team out of solution-first habits? Run call reviews specifically scored on Type 3 question frequency and Future State ownership, and use role-play drills where the only allowed response to a stated pain point is another question.

Sources

flowchart TD S["What’s the biggest mistake reps make d"] S --> N0["The two options compared"] N0 --> N1["How to decide between them"] N1 --> N2["Concrete numbers behind each option"] N2 --> N3["Implementation details and sequencing"]
flowchart LR C["What’s the biggest mistake reps make d"] C --> H0["The two options compared"] C --> H1["How to decide between them"] C --> H2["Concrete numbers behind each option"] C --> H3["Implementation details and sequencing"]

Related on PULSE

Download:
Was this helpful?