SPIN Selling is Neil Rackham's question sequence, developed from a 35,000-call Huthwaite study of what top-performing salespeople actually do in complex sales. The sequence — Situation, Problem, Implication, Need-payoff — does not pitch. It builds a structure inside the buyer's own thinking so that the buyer articulates the need before the seller names the solution. Implication questions are what separate high performers from average ones: they are the step that makes the cost of doing nothing feel real.

When to use SPIN

Use SPIN in complex, high-stakes sales or stakeholder conversations — where the buyer needs to convince themselves, and often others, before they can say yes.

Enterprise or B2B sales with multiple stakeholders
Internal pitches to leadership for budget or headcount
Consulting discovery calls
Any conversation where "we don't have budget" is the likely objection
Renewals where the buyer is evaluating alternatives

How to use it

Situation questions. Establish context — current state, what they're using now, who's involved. Keep these brief; buyers tolerate them but find them least valuable. Too many and you lose the room.
Problem questions. Surface the pain. "Where does the current process break down?" Problems that buyers name themselves are more powerful than problems you name for them.
Implication questions. Expand the consequence of the problem. "If the reporting is slow, how does that affect the board presentation?" Implication is the differentiator — it makes the cost of inaction feel concrete.
Need-payoff questions. Ask the buyer to describe the benefit of solving it. "How much would it help if you could close that loop in real time?" The buyer names the value of your solution in their own words.

Example

Them

We're managing the process manually right now, but it mostly works.

On your HUD

When it breaks down, where does it usually break first?
If that breakdown delays the monthly close, what does that mean for the finance team's week?
If that week was back — what would your team do with it?

What Kennan would surface in this moment, in the same first-person bullet format as the in-app HUD.

Common pitfalls

Too many Situation questions. They are necessary but low-value. Get through them quickly and move to Problem.
Skipping Implication. Problem questions surface the pain; Implication questions make it expensive. Without Implication, the buyer can nod at the problem and still feel no urgency.
Naming the solution before the Need-payoff. The Need-payoff question should come from the buyer, not the seller. If you answer it yourself, you lose the most powerful moment in the sequence.

Where it comes from

Rackham, SPIN Selling (1988), from a 35,000-call Huthwaite study

In your next meeting

Kennan watches for the conversational pattern this framework addresses and surfaces a first-person line you can read off your HUD, in the same shape as the example above. Frameworks are receipts; the user-facing output is a sentence, not a citation.