“If this doesn't get solved, what does it lead to?”
From Neil Rackham · Author of SPIN Selling; founder of Huthwaite
Why it works
Rackham's 35,000-call study found that in larger sales, top performers don't win by listing features — they win by enlarging the buyer's sense of the problem first. Huthwaite's own framing is that Implication questions 'focus on the effects and consequences of a customer's problems,' tipping the cost-of-change calculus in the seller's favour. The mechanism is that the buyer, not the seller, voices the downstream damage: a problem you describe is resisted, but a consequence the buyer reasons their own way to is believed. 'What does it lead to?' chains an admitted small problem into the meeting it derails, the customer it loses, the overtime it forces — until inaction has a price tag the buyer set themselves.
When to ask
After a problem is on the table but before you pitch anything. Reach for it the moment a buyer acknowledges a pain but treats it as minor — the Implication question is how you find out whether it's actually minor or whether they just haven't followed the consequences forward yet.
Good follow-ups
- And when that happens, what's the knock-on effect on the rest of the team?
- How often does that play out — once a quarter, or every week?
- If nothing changes over the next year, where does this end up?
Watch out for
Asking it once and stopping. A single 'what's the impact?' gets a shrug; the power is in the chain — each answer becomes the next question's input until the real cost surfaces. The opposite failure is interrogation: stacking implications on a problem the buyer doesn't actually care about feels manipulative and earns resistance. Earn the right with a genuine problem first, then follow the consequence honestly — if it bottoms out at 'nothing really,' that's a real finding, not a cue to invent stakes.
Where to ask
- Sales callgreat
SPIN's native habitat — live on a discovery call you can keep escalating the consequence ('and then what does that cost you?') until the buyer feels the size of the problem, which is the entire point of the Implication question.
- User interviewgreat
Works just as well in a problem interview to size urgency — once someone names a pain, this is how you learn whether it's a papercut or a fire without putting words in their mouth.
- In-product surveypoor
Asynchronous, you can't chain the implication forward, and a one-line answer rarely reaches the real downstream cost; the value is in the live escalation, which a survey field can't carry.
Reworded for this context: “If this problem keeps happening, what does it end up costing you downstream?”
- Long-form surveypoor
The Implication question is built to compound across several turns; flattened into a single survey item it collapses back into a generic 'what's the impact?' that respondents answer in the abstract.
Pairs well with
Stage: Consider · A question popularized by Neil Rackham
Source: https://www.huthwaiteinternational.com/blog/spin-selling-questions