Compelling Reason to Buy (Not to Sell)
In the bowling alley it is never about you — close the laptop and collect problem domain knowledge.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 95%
The single most common chasm-crossing error is polishing your compelling reason to SELL — a better demo, a sexier deck — when the pragmatist only moves on a compelling reason to BUY: a deteriorating, expensive problem that forces them to act faster than they would like. The sales motion inverts accordingly: no demo, no vision, no laptop. You run a diagnostic and take notes.
Origin
Geoffrey Moore, from the Crossing the Chasm sales playbook; he names 'compelling reason confusion' as one of his seven deadly sins of crossing the chasm. He connects it to April Dunford's point that buying software is now harder than selling it.
Core principles
- 01Pragmatists default to 'if it ain't broke, don't fix it'. Only duress overrides that inertia.
- 02The compelling reason to buy belongs to the customer, not to you: it is their pain, their risk exposure, their churn, their regulatory clock.
- 03Pragmatists rarely say no. They say 'come back and demo this to our team' — and never say yes. Encouragement is not progress.
- 04The gold you are mining on every call is problem domain knowledge, not a closed deal.
- 05You must reach the economic buyer, not the end user. The end user will happily agree they are oppressed; if their boss will not sponsor it, nothing happens.
- 06The buying committee is designed to keep you out. Only a sponsor under duress has the energy to fight their own company's decision inertia.
How to run it
- 1
Define the problem, not the pitch
Before any outbound, articulate the specific compelling problem in your segment: what it costs, why the current fix is deteriorating, what risk it exposes. Ask what the cost of NOT solving it is — usually risk exposure, a gate on growth, or churn.
Pro tip Commit to learning more about that one problem than anyone alive, including how THIS customer's version of it differs from the generic version.
- 2
Build lead-gen around symptoms
Run demand generation on the symptom list rather than the product: 'do you have any of these seven symptoms of fatal churn?' Respondents are pre-qualified by their own pain.
Pro tip A BDR then confirms the symptoms and, critically, confirms who owns the problem — 'actually that's Harry, not Mary.'
- 3
Open with a hypothesis, then shut up
Start every conversation identically: 'we've been working with some people in your industry and we understand there's this really serious problem around X — we believe your company might have it. Is that true?' You get one of two responses: 'are you kidding me, we have that' or 'well, not exactly' — and the second one leads straight into them telling you what the real problem is.
Pro tip People want therapy. If you are willing to listen, they will talk about their problems.
Watch out Shut the laptop. Do not open it. The demo is not the meeting.
- 4
Run the diagnostic and be seen taking notes
Do a diagnostic call with the economic buyer: 'before we tell you how great our solution is, let's make sure we understand your challenges.' Your goal is to make them talk as much as possible while you write down their words. Use a pen so they can SEE you writing — it signals you are listening.
Pro tip On Zoom, angle the camera so your hands are visible and lean in.
Watch out Do not ask to record. They will say things about colleagues they do not want on tape, and the request kills candour.
- 5
Over-commit to the outcome, and do not discount
Close on a near-guaranteed commitment to solve the problem: we are taking this off the table and we are not leaving until you are satisfied. Price on value — nobody wants a coupon for heart surgery.
Pro tip The doctor analogy: you do not want the surgeon to open with a movie of their last operation. You want them to ask good questions about the pain in your side.
Watch out Discounting pre-chasm increases perceived risk (what did they cut? support? scope?), and risk is precisely what the chasm is made of.
In the wild
The deal moves when the sponsor in the room is thinking: I already gave this problem to everybody here and our answer sucks. My boss's boss's boss now knows my name — which is very bad. I am getting the message that either I fix this or they find someone who can.
→ That duress is what gives the sponsor the energy to push against the inertial momentum of their own company's decision process.
Cybersecurity used to be dismissible — attackers only went after companies with resellable data. Cryptocurrency changed that: ransomware can be monetised against anyone, so everybody is now vulnerable.
→ The problem became urgent enough to force pragmatists to act faster than they wanted to — the textbook shape of a compelling reason to buy.
Common mistakes
Answering a stalled pipeline with a better demo
When chasm deals stall, founders conclude the product is not attractive enough and build a sexier demo or a new deck. The sales rep comes back saying 'that was a great presentation, this is the deck we should be using.' All of that is a compelling way to sell, not a compelling reason to buy.
Selling to the end user instead of the economic buyer
End users will validate the pain enthusiastically. If their boss will not sponsor a budget-redirecting, risk-bearing decision, the enthusiasm converts to nothing.
Reading a non-no as a maybe
Pragmatists do not say no. They take the meeting, encourage you, and never say yes. Treating that engagement as pipeline is how founders burn a year in the chasm.
Is it for you?
Best for
Founders and first sales hires selling a new, risky product into pragmatist B2B buyers in a chosen beachhead
Not ideal for
Tornado-phase or Main Street selling, where budget already exists and the pitch legitimately can be about you
From the transcript
“it's the compelling reason to buy is not a compelling reason to sell which people often think about is the pitch”
“in the bowling alley it's never about you”
“shut the goddamn laptop”
“got to realize the gold at this point is problem domain knowledge”
“I think you need to talk to the economic buyer as opposed to the end user”
“chasms are based on risk bearing decisions”
“discounting does not reduce risk”
From the episode
Geoffrey Moore on finding your beachhead, crossing the chasm, and dominating a market