Gap Selling is a method from Keenan, a sales trainer and author, for selling to the distance between where a buyer is today and where they need to be. The part that makes it work is the part most teams skip: naming the root cause, which Keenan says is always a broken process or a broken tool. Buyers live with pain. They fix what’s broken.

What is Gap Selling?

Gap Selling comes from a 2018 book of the same name by Keenan, who founded the sales training firm A Sales Growth Company. His firm says the book has sold more than 150,000 copies.

The idea fits in one line from his firm: “People don’t buy products, they buy solutions to business problems they can’t ignore.” So the rep studies the buyer’s current state (how things work now and what that costs) and their future state (where they need to be). The gap is the distance between the two, and the job is to make it “so clear and so quantified that doing nothing stops being an option.”

Keenan puts the warning bluntly: “Never sell to need. If you only solve the problem your buyer thinks they have instead of the one they really have, you haven’t helped them at all.”

The root-cause test most teams skip

Keenan’s firm turns discovery into a three-column sheet, the Problem Identification Chart. It separates the problem, its impacts, and its root causes.

Keenan’s test for that last column is the part worth taping to every rep’s monitor: “A root cause is always a broken process or a broken tool. Never a business problem. Never an impact.” He adds that the columns are many-to-many. One root cause can feed several problems, and one problem can have several root causes.

He also names the usual failure. Teams learn current state and future state, have it “on the wall,” and stop there. “It does not stop there.”

His firm explains why pain alone won’t do it: buyers “get used to it. They adjust. They live with the limp.” A broken process has a fix and an owner, so there’s something to buy. Challenger’s research found that around half (40-60%) of all lost deals ended in no decision.

One deal’s Problem Identification Chart

Here’s the chart for one made-up deal. Your rep sells a renewals tool to the VP of customer success at a B2B SaaS company, and the first discovery call is done. The rep’s root cause, first draft: “They need better renewal reporting.”

That fails Keenan’s test. “Better reporting” is a need, and a need tells you what the buyer wants, not what’s broken. A second look at the call finds two broken processes the buyer can point at in their own systems.

One deal’s Problem Identification Chart, our exampleProblem: renewals lapse before anyone calls the customer. Impacts, in the buyer’s numbers: 9 renewals lapsed last quarter, about $210,000 a year in contracts; each customer success manager spends about 4 hours a week checking contracts by hand. Root causes: 1, contract end dates live in signed PDFs, not in the CRM, which drives both impacts; 2, the renewal task fires 30 days before whatever date was typed in, and many dates were never typed, which drives the lapsed renewals. Crossed out: they need better renewal reporting. That is a need, not a broken process or tool.Problem Identification Chart: one renewals dealProblemImpacts (the buyer’s numbers)Root causesRenewals lapse beforeanyone calls the customer9 renewals lapsed lastquarter: about $210,000 a yearfrom root causes 1 and 2About 4 hours a week perCSM checking contractsfrom root cause 11. End dates live in signedPDFs, not in the CRM2. The renewal task fires30 days before a datenobody typed inWhat the rep wrote firstThey need better renewal reportingA need, not a broken process or tool. It fails the test.Problem IdentificationChart: one renewals dealProblemRenewals lapse beforeanyone calls the customerImpacts (the buyer’s numbers)9 renewals lapsed last quarter:about $210,000 a yearfrom root causes 1 and 2About 4 hours a week perCSM checking contractsfrom root cause 1Root causes1. End dates live in signedPDFs, not in the CRM2. The renewal task fires 30 daysbefore a date nobody typed inWhat the rep wrote firstThey need better renewal reportingA need. It fails the test.
Our example. The impact numbers are the buyer’s, from the call.

Read the chart across. The lapsed renewals have two root causes, and the PDF dates feed both impacts. That’s the many-to-many link in practice. Fix the dates and both numbers move, which is a better case than “better reporting” ever was.

Discovery that walks the process step by step

You find a broken process by walking through the work, not by asking about pain. Here are the questions we’d ask on the renewals deal above. Each one moves one step down the process until a step or a tool breaks.

  1. “Walk me through the last renewal that lapsed. When did anyone first know it was coming up?” Start with one real case, not the process in general.
  2. “Where does that date live today?” The answer is usually a tool, a file, or a person’s memory.
  3. “Who copies it from there, and when?” Hand-offs between people are where processes break.
  4. “What happens when nobody does?” This is the step that broke. Write it down in the buyer’s words.
  5. “How many renewals went that way last quarter, and what were they worth?” Let the buyer count. A number they found themselves carries more weight than one you brought.

Run the test on every deal, not just the big ones

Your best rep probably does this on instinct on their top five deals. On the rest, the root cause stays whatever got typed after the first call.

A check like this belongs in your playbook. In Arrows, that’s the Agentic Playbook: how your team works its best deals, written in plain language as milestones with targets, when each agent action runs, and rules. We build it with you at the start, from how your reps already sell. Arrows uses it to keep a gameplan for every deal: a path to close, built from your playbook and from what’s actually happening on that deal.

A team that runs Gap Selling might write rules like these:

  • “After discovery, the recap names the root cause in the buyer’s words, as a broken process or a broken tool. If the call didn’t find one, the recap asks the question again.”
  • “Before the next call, the brief lists every impact that still has no number from the buyer.”

Every time something happens on a deal (a call ends, an email arrives, a new person shows up on a thread), Arrows reads your playbook and decides the best next action for that deal. With those rules in place, the Post-call follow-up and the Pre-call brief arrive with Keenan’s test already applied. Your rep doesn’t have to remember it, nobody fills in a Gap Selling form, and by default nothing goes out until they approve it.

Gap Selling with MEDDPICC, SPIN, or your own list

Gap Selling is a way to find the problem. MEDDPICC is a way to qualify the deal around it, so you can run both: the impact number the buyer gave is what MEDDPICC’s Metrics asks for. SPIN selling is a question sequence, and it can do the same discovery work. Gap Selling pays off most where a deal needs a business case. On quick, small sales it’s more than you need.

Plenty of teams run nothing at all. In an Arrows survey (November 2026) of 815 people in sales, 43% said their team uses no sales methodology, and about a quarter of the write-in answers described their own method or a blend.

Teams that blend methods have the right idea. You don’t need every part of Gap Selling to use its best idea. Look at what your won deals had in common, build a short list your team can actually remember, and put the root-cause test on it. For how the named methods compare, see our guide to sales methodologies.

How a sales leader checks the gap on every deal

We love our reps, but they don’t always tell it straight. They’re not lying (mostly). They want to close, so every deal sounds a little better than it is, and “they’re feeling the pain” is easy to say about any of them.

So ask one question per deal in your pipeline review: “What’s broken, a process or a tool, and who on the buyer’s side said so?” A rep who can answer has found a gap. A rep who answers with a need or a feeling has more discovery to do.

A pipeline review sheet with the root cause as each rep wrote it, our exampleFive deals. Northwind, proposal: contract end dates live in PDFs, not the CRM. A broken process. Kestrel, discovery: they need more visibility. A need, ask again. Brightline, evaluation: quote approvals wait on one finance manager. A broken process. Halden, proposal: lots of pain around reporting. Pain, ask again. Marlow, discovery: support tickets never reach the account owner’s inbox. A broken tool.Monday’s review: what’s broken on each deal?DealStageRoot cause, as the rep wrote itPasses?NorthwindProposalEnd dates live in PDFs, not the CRMProcessKestrelDiscovery“They need more visibility”Need: ask againBrightlineEvaluationQuote approvals wait on one personProcessHaldenProposal“Lots of pain around reporting”Pain: ask againMarlowDiscoveryTickets never reach the owner’s inboxToolMonday’s review: what’sbroken on each deal?Northwind · ProposalEnd dates live in PDFs, not the CRMProcessKestrel · Discovery“They need more visibility”Need: ask againBrightline · EvaluationQuote approvals wait on one personProcessHalden · Proposal“Lots of pain around reporting”Pain: ask againMarlow · DiscoveryTickets never reach the owner’s inbox · Tool
Our example. Two of five “root causes” are a need and a feeling.

Seeing the gap is half of it. In Arrows, you say what you know about a deal in your own words during the review (“get Halden’s ops lead on the next call and walk through how that report gets built”). Arrows queues those actions on the deal’s gameplan, the rep reviews and sends them, and next week you can see whether they got done. Prepping the review in Claude? The free weekly pipeline review skill puts what’s moving and what’s at risk on one shareable page.

The team version

Put one gameplan to work across every deal.

See how Arrows turns your sales process into deal work your reps can review and run.