GAP Selling, live on the call.
Current state, future state, and the gap between them. The problem-centric method that insists reps go deeper on how the buyer works today before describing anything better. Kairos listens for the depth of the current state and fires when the rep leaves it half-finished.
When a handoff slips, where does it actually break, and what did the last one cost you?
The problem is the product.
GAP Selling is Keenan's 2018 method built on one claim: buyers buy to close a gap between where they are and where they want to be, and most reps never establish where the buyer actually is. The framework forces a thorough current state, including the literal problems, the physical and emotional impact, and the root cause, before any talk of future state.
It is a problem-centric framework. Its strength is depth: a rep who has done the current state properly understands the buyer's business better than most of the buyer's colleagues do. Its weakness is that depth takes discipline, and discipline erodes the moment a buyer says 'just show me the product.'
Teams that run it well can state the buyer's problem, root cause, and cost back to them and get a nod. Teams that run it badly have a future-state slide and a current state they guessed.
The five components.
| Component | Abbrev. | What must be true | How reps miss it | What Kairos fires |
|---|---|---|---|---|
| Current state | CS | A full picture of how the buyer operates today: the literal process, the problems in it, and how those problems feel to the people in it. | Three questions deep. Rep moves on when the buyer gets vague. | "Walk me through what actually happens the day that goes wrong. Who finds out first?" |
| Root cause | RC | Why the problem exists, not what it looks like. The thing that, if changed, makes the symptoms stop. | The symptom gets treated as the cause. The solution solves the wrong thing. | "When it breaks, where does it actually break? What's upstream of that?" |
| Impact | I | What the problem costs, in the buyer's numbers, and who carries that cost. | Impact is described, never measured. No urgency, no business case. | "What did the last one of those cost you, roughly, in time and in money?" |
| Future state | FS | What the buyer's world looks like with the problem solved, in their terms, with their measures. | Rep describes the future state from the product's point of view before current state is done. | "If the root cause were gone, what would the team be doing with that time instead?" |
| The gap | G | The distance between current and future state, sized in the buyer's numbers. The gap is what they are buying. | Never sized. The buyer can't see why the change is worth the disruption. | "So from forty hours a week to maybe ten. Is that gap worth a project to you?" |
Where reps break it.
The shallow current state.
Keenan's whole argument is that reps stop too early. Three questions in, the buyer says 'it's fine, mostly,' and the rep believes them. Everything that follows is built on a current state that isn't real.
Symptom as cause.
'Reporting takes too long' is a symptom. The cause might be three systems that don't talk, or one person who owns the spreadsheet. A rep who sells to the symptom loses to the vendor who found the cause.
Future state first.
The buyer asks for a demo at minute five and gets one. The future state is now the rep's, not the buyer's, and the gap can't be sized because nobody measured where they started.
The deeper question, at the moment the rep would move on.
Kairos tracks the depth of the current state across the call: how many layers the rep has gone, whether a root cause has been named, whether impact has a number. When the rep accepts a vague answer, moves to future state early, or starts describing the gap without having sized it, it surfaces the question a senior rep would ask instead.
It is quiet while the rep is going deeper. GAP done well looks like a slow, patient conversation, and Kairos is built to protect that, not interrupt it.
Don't take 'mostly.' Ask about the last time it wasn't fine, and who had to deal with it.
When a handoff slips, where does it actually break, and what did the last one cost you?
Before the demo, one more: if the root cause were gone, what would the team do with that time?
GAP sizes the problem. Pair it with a framework for the deal or the conversation.
GAP Selling is a discovery discipline. Teams pair it with a date-and-decision frame or an enterprise checklist to carry the diagnosis through the rest of the cycle.
GAP + SPICED
Both diagnostic. GAP's depth on current state plus SPICED's critical event gives the deal both a business case and a date.
GAP + MEDDPICC
GAP finds the problem and its cost; MEDDPICC makes sure the right people have heard it and the process to buy is real.
GAP + your playbook
Your root-cause patterns by segment, your impact benchmarks, the current-state questions your best rep always asks.
GAP Selling with Kairos.
The GAP Selling current-state checklist.
One page. The four layers of current state, the root-cause test, the impact-has-a-number test, and the signals that mean you've moved to future state too early. Print it, pin it, run it on your next call.
Size the gap on the call, not in the proposal.
Free for individual reps. A demo for teams.