Skills / Sales

Gap Selling

No problem, no sale. If there's no problem, there's no reason to change, and if there's no reason to change, there's no sale.

Gap Selling is a problem-centric B2B sales methodology that replaces feature pitching with structured problem diagnosis. Built around the Problem Identification Chart (PIC), it guides salespeople to deeply map a prospect's Current State, root causes, impact, and desired Future State before presenting any solution. When the gap is fully understood and emotionally felt, the solution sells itself as the bridge.

By Keenan (Jim Keenan)  ·  Free

Use this skill See it in action

Specimen 01 · Live diagnosisGap Selling

Input

“It's a mid-market logistics company. Their VP of Ops says they're losing visibility into shipments once they hand off to third-party carriers.…”

Diagnosis

Let's build your Problem Identification Chart.

Full transcript ↓

Calibrated referenceagent-skills.ai

The gap

No problem, no sale — map the gap that makes buyers move

Gap Selling holds that buyers only purchase to close a gap — the distance between a painful Current State and a desired Future State. The methodology's central tool is the Problem Identification Chart (PIC), a four-quadrant diagnostic mapping: (1) Current State — the prospect's existing conditions and stated problems; (2) Root Causes — the underlying drivers behind those problems; (3) Impact — the financial, organizational, and emotional consequences of staying in the current state; and (4) Future State — the ideal outcome the buyer is trying to reach. Salespeople are trained to complete a hypothesized PIC before every call through pre-call research, then use discovery questions to confirm, deepen, and quantify the map. The solution is only presented after the gap is fully established — and framed explicitly as the bridge that closes it. Deal health is measured by gap clarity, not relationship warmth.

The problem

Most B2B sales reps pitch features before they understand problems, creating low-urgency conversations that stall in evaluation. Without a clearly mapped gap — Current State problems, root causes, quantified impact, and a co-created Future State — there is no compelling reason for the buyer to change anything. Keenan's foundational axiom makes the failure explicit: no problem, no sale.

The solution

Stop guessing at what might resonate and start diagnosing the gap that makes change feel urgent. You'll leave every discovery conversation with a completed PIC that reveals not just what hurts, but why it hurts and what it's costing — making the solution sell itself.

You bring

A deal, prospect, or account you're actively working
What you know about the prospect's current situation and stated challenges
Discovery call notes, emails, or meeting transcripts (if you have them)
Your product or service and the problems it solves

You get

A completed Problem Identification Chart (PIC) for your specific deal
Hypothesis-driven discovery questions tailored to your prospect's industry and role
A quantified impact statement covering financial, organizational, and emotional dimensions
A deal health score assessing whether your gap is defined clearly enough to close

In action

Watch the methodology work.

Three specimens from a single real session: the same situation, unaided and calibrated, the full transcript, and the skill answering live in the channel where the work happens.

Fig.01  —  The same situation, two ways

Specimens A · B

Specimen AVague

Unaided

“You have a second call scheduled with a VP of Operations tomorrow. Your notes say 'they have visibility issues and want better tracking.' You've prepared a demo of your platform's real-time dashboard. You're not sure why the last two calls felt flat, but you're hoping the demo will generate some excitement.”

×Vague — nothing concrete to act on.

Specimen BCalibrated

With Gap Selling

“You enter the call with a hypothesized PIC: you've researched their TMS vendor, guessed at the carrier connectivity gap, and estimated impact ranges. Your first 20 minutes are discovery questions that confirm and deepen the map — not a product walkthrough. By the end, you've co-created their Future State with them. When you present the solution, you frame every feature as a direct answer to a root cause they named. The VP says, 'This is exactly what we've been trying to solve' — because it is.”

◦Specific, grounded, and ends with one clear next step.

Fig.02  —  A real session, unedited

In-app · assistant

Gap SellingClaude

Gap Selling

Let's build your Problem Identification Chart. Before we think about your solution at all, I need to understand the gap. Tell me about the deal — what's your prospect's current situation, and what problem did they tell you they're trying to solve?

It's a mid-market logistics company. Their VP of Ops says they're losing visibility into shipments once they hand off to third-party carriers. Customers complain, they spend hours manually tracking things down.

Good — that's the stated problem, which goes in the Current State quadrant. But 'losing visibility at handoff' is a symptom. Let's get to the root cause before we go further. When a shipment goes dark after carrier handoff, what's actually breaking down? Is it a data integration issue between their TMS and carrier APIs? A process gap where tracking data isn't being passed? Or is it that carrier relationships vary wildly and some just don't provide real-time data?

Mostly the data integration piece — their current TMS only connects to their two main carriers. The 12 other carriers they use are completely manual.

Perfect — now we have a real root cause: fragmented carrier connectivity in the TMS, with 12 of 14 carriers requiring manual tracking. That's the second quadrant of the PIC filled in. Now the most important quadrant: Impact. What is this actually costing them? I need you to think financial, operational, and emotional. You mentioned customer complaints — do you have any sense of how many? And the hours spent manually tracking — have they put a number on that?

They said their ops team spends about 15 hours a week on manual tracking. And they've had three enterprise customers escalate in the last quarter over late delivery surprises.

Now we're building real impact. 15 hours/week of ops labor — at fully-loaded cost that's probably $25-40K annually just in wasted time. Three enterprise escalations in a quarter is significant: at their deal size, even one churn event likely exceeds your entire contract value. And there's an emotional layer here too — their VP of Ops owns that relationship damage personally. That's the kind of pain that makes someone want to move fast.

Here's where you stand on the PIC:• Current State: No real-time visibility into 12 of 14 carriers post-handoff• Root Cause: TMS only integrates with 2 carriers; rest is fully manual• Impact: ~$30K/yr ops labor + enterprise customer churn risk + VP credibility exposure• Future State: Not yet defined — you need to ask them what 'good' looks like

Do you know what their ideal future state is? If not, that's your most important question for the next call.

I haven't explicitly asked that. I assumed it was just 'fix the visibility problem.'

That assumption is exactly where most deals go soft. 'Fix the visibility problem' is your framing, not theirs. Their Future State might be 'customers proactively notified before they call us' or 'my team focused on exception handling, not manual tracking' or 'zero enterprise escalations this year.' Each of those leads to a different conversation about solution fit and value. Your next call should open with: 'If we solved this completely, what would your operation look like six months from now?' That answer completes your PIC — and tells you exactly how to position the solution as the bridge.

Reply to Gap Selling…

What the skill is doing

01Problem Identification Chart (PIC) Builder

02Pre-Call Hypothesis Formation

03Root Cause Drill-Down

Fig.03  —  The same skill, in the channel you already use

WhatsApp · live

9:41

GSGap Sellingtyping…

Messages are end-to-end encrypted. No one outside of this chat can read them.

Today

It's a mid-market logistics company. Their VP of Ops says they're losing visibility into shipments once they hand off to third-party carriers. Custome…9:14✓✓

Let's build your Problem Identification Chart.9:14

Before we think about your solution at all, I need to understand the gap.9:15

Tell me about the deal — what's your prospect's current situation, and what problem did they tell you they're trying to solve?9:15

Message

The same skill, where the work happens.

No new app to learn. The methodology runs over the WhatsApp Business API, so the answer lands as a reply in the thread you’re already in — same rigour, zero context-switch.

◦Reads the situation, names the pattern, returns one concrete next move.

◦Delivered in seconds, inside a conversation that already exists.

Specimen · WhatsApp Business API · live

Capabilities

What it does, specifically.

Each capability is a distinct move drawn straight from the source methodology — not a generic assistant guessing.

CapabilityC-01

Problem Identification Chart (PIC) Builder

Walks you through completing all four quadrants of the PIC for a specific deal: Current State (conditions and problems), Root Causes (why those problems exist), Impact (financial, organizational, emotional consequences), and Future State (where the buyer wants to be). The finished chart becomes a shareable diagnostic artifact you can use directly with the prospect.

◦ MethodBased on Keenan's Problem Identification Chart — the central framework in 'Gap Selling' that structures every discovery conversation and deal qualification decision.

CapabilityC-02

Pre-Call Hypothesis Formation

Before any discovery call, helps you research the prospect and hypothesize their Current State, probable problems, and likely impact. You enter the call as a problem expert with informed guesses to confirm — not a blank notepad fishing for information.

◦ MethodDirectly implements Keenan's mandatory pre-call planning discipline: salespeople must hypothesize the buyer's PIC before the call to transform discovery from reactive Q&A into a consultative, hypothesis-driven conversation.

CapabilityC-03

Root Cause Drill-Down

Takes a stated problem and systematically uncovers the underlying root causes through structured probing questions. Surfaces the real drivers behind surface-level symptoms so the discovery conversation reaches genuine depth — and the solution can address the true source of pain.

◦ MethodImplements Gap Selling's root cause analysis discipline: Keenan prescribes that discovery must move past stated problems to understand *why* those problems exist before any solution is credible.

CapabilityC-04

Impact Quantification

Helps you map and articulate the full cost of the prospect's Current State — financial losses, operational inefficiencies, and the emotional toll on the people involved. Converts vague pain into specific numbers and feelings that make the gap feel real and urgent.

◦ MethodBased on Keenan's impact mapping framework: Gap Selling requires quantifying impact across three dimensions (financial, organizational, emotional) because the size of the gap determines the strength of the motivation to buy.

CapabilityC-05

Deal Health Scoring

Evaluates an active deal against Gap Selling criteria: Is the Current State clearly documented? Are root causes identified? Is impact quantified? Has a Future State been co-created with the buyer? Returns a diagnostic score with the weakest quadrants flagged for follow-up.

◦ MethodImplements Keenan's principle that deal health should be measured by gap clarity — not relationship warmth or stage progression — because a well-mapped gap is the only reliable predictor of close.

Tested

Graded before it shipped.

Every skill is scored against independent scenarios for methodology fidelity before it goes live — not vibes, a rubric.

What it produces

OutputD-01

Problem Identification Chart (PIC)

A completed four-quadrant map of your deal: Current State conditions, Root Causes, quantified Impact, and co-created Future State. Built during the session and shareable directly with the prospect as a diagnostic summary.

OutputD-02

Pre-Call Hypothesis Brief

A structured one-page prep document with your hypothesized PIC quadrants, industry-specific problem assumptions, and 8-12 hypothesis-confirmation discovery questions — ready before you pick up the phone.

OutputD-03

Deal Gap Health Scorecard

A scored assessment of how clearly the gap is defined in an active deal, with a quadrant-by-quadrant breakdown and specific questions to fill in the weak spots before your next conversation.

OutputD-04

Impact Statement

A concise written summary of the financial, organizational, and emotional consequences of the prospect's Current State — suitable for inclusion in a follow-up email, executive summary, or proposal introduction.

The source

Grounded in the original work.

Every answer traces back to a real source and the practitioner who wrote it — not a secondhand summary. Here is the source of record.

Source authorA-01

Keenan (Jim Keenan)

Keenan is the CEO/President and Chief Antagonist of A Sales Growth Company, a sales consulting and training firm. He is the author of 'Gap Selling: Getting the Customer to Yes' (2018) and a top-ranked Forbes contributor on sales. His Gap Selling methodology is used by B2B sales teams worldwide and has spawned a certified practitioner program and active coaching community.

Status · Inspired by Keenan (Jim Keenan)’s work — not yet claimed. Are you Keenan (Jim Keenan)?

Primary sourceS-01

Gap Selling: Getting the Customer to Yes

by Keenan (Jim Keenan)

CEO of A Sales Growth Company; Forbes sales contributor; author of 'Gap Selling' (2018); certified Gap Selling training programs in use globally.

Read the original ↗

Citationgapselling.com

In the build queue

Be first to run it.

Gap Selling is being built right now. Leave your email and we’ll tell you the moment it goes live.

Notify meEmail

At launchI have a discovery call tomorrow and I want to build a Problem Identification Chart before I go in. My prospect is a [company type] and I think their problem is [stated issue]. Can we hypothesize the full PIC and generate discovery questions to confirm it?