SPIN Selling: the four question types, with examples and a worked call

This page is for account executives, account managers and founders whose sales take more than one conversation and involve a meaningful purchase. It explains the four question types, the idea of implied and explicit needs that sits underneath them, the four stages of a sales call, and how to check your own calls. The worked example follows a full call with the arithmetic the buyer ends up stating.

What SPIN Selling is and where it came from

SPIN Selling comes from Neil Rackham's book SPIN Selling, published by McGraw-Hill in 1988. Rackham founded the research and training firm Huthwaite. The publisher describes the research behind it as a study of more than 35,000 sales calls made by 10,000 salespeople in 23 countries over 12 years. The book's central finding is that methods built for small, quick sales often don't work in large ones, where the buyer meets you several times and has more to lose.

Rackham has since been careful about what the research proves. In a 2026 interview published by Huthwaite International, he describes how the work ran through productivity projects with Xerox, IBM and Motorola, with sales managers trained to code calls and coach their teams. Asked about the sales gains reported for early trainees, he credits the whole coaching process rather than "the four little questions". That's a useful warning: SPIN works when it changes how you plan, run and review calls, not when it's a list of questions on a card.

The four question types

The order matters. Situation questions set context, problem questions surface an issue, implication questions make it big enough to act on, and need-payoff questions turn it into value the buyer has put into words. You'll loop back through the sequence for each problem you find.

Implied needs and explicit needs

Underneath the four questions is the book's key distinction between two kinds of need.

In small sales, an implied need is often enough to sell. In large sales, Rackham argues, buyers act on explicit needs, and the work of the call is developing one into the other. That's why presenting your solution as soon as you hear a complaint is a mistake: you're answering a need the buyer hasn't yet decided is worth paying to solve.

Questions for each type

Do the situation work before the call. Company size, locations, systems and recent news are in the public record, and every question you ask about them spends the buyer's patience.

How is [process] handled today, and who owns it?
What has changed since [the fact you found, e.g. the two new locations]?
Which systems or suppliers are involved?

Where does [process] go wrong most often?
How happy are you with [current approach] as you grow?
What's the hardest part of [task] for your team?
What would you change about it first?

When that happens, what does it cost you, in money or time?
Who else feels it: patients, staff, customers, finance?
How often does it happen in a typical month?
Does that get better or worse as you add [locations / volume]?
What does it stop you from doing that you'd like to do?

If that went away, what would it be worth to you?
How would solving it help with [the goal they mentioned]?
Who else would benefit, and how?
What would a solution need to do for this to be worth changing?

Implication questions are the hardest to ask well and the ones that do the most work. Plan them before the call: for each problem you expect, write two or three consequences and the question that would reveal each.

The four stages of a SPIN call

Rackham divides a sales call into four stages, and argues that the second decides most large sales.

1. Preliminaries. Open the call and agree its purpose. Keep it short: buyers in large sales care about your questions more than your opener.
2. Investigating. The SPIN questions, where most of the call's time should go.
3. Demonstrating capability. Show how you meet the explicit needs the buyer has stated, and only those. Features matter here only when tied to a need the buyer has said out loud.
4. Obtaining commitment. Agree the next step.

On commitment, the book argues that pressure closing techniques work less well as the size of the sale grows. Instead of aiming for an order on every call, aim for an advance: an action the buyer agrees to that moves the deal forward.

Worked example: a call with a dental group

Illustrative example. Bayline Dental Supply, Seaview Dental Partners, the people and every figure are fictional, to show the method.

The seller: Bayline Dental Supply (baylinedental.example), a dental supply distributor offering a managed inventory program: scheduled restocking across all a group's practices, with one consolidated order. The account: Seaview Dental Partners (seaviewdental.example), a group of nine practices that each order supplies on their own. The buyer: Andrea, the group's operations director. The rep found the group's two newest practices on its website before the call, so skipped most situation questions.

Rep (situation): You've added two practices this year. Are they ordering the same way as the other seven?

Andrea: Each office manager orders for their own practice. It's always been like that.

Rep (problem): How well is that working now that there are nine?

Andrea: Honestly, not great. Someone's always running out of something.

Rep (implication): When a practice runs out, what happens?

Andrea: They place a rush order. I see them on the invoices: maybe six a month per practice, about $28 extra each in shipping.

Rep (implication): And if the rush doesn't arrive in time?

Andrea: Then we reschedule. Last month three procedures moved because an impression material didn't arrive. Those average around $1,100.

Rep (implication): Who deals with all of that?

Andrea: The office managers. Each rush order is maybe 40 minutes of calls and paperwork.

Rep (need-payoff): If rush orders dropped to about one a month per practice, what would that mean for you?

Andrea: Fewer reschedules, for a start. And my office managers could spend that time on the front desk, which is where I need them.

After the call, the rep wrote up the numbers Andrea gave, as a monthly cost of the problem:

The $24 hourly rate is the rep's assumption, to confirm with Andrea, and rescheduled procedures aren't always lost revenue, so the summary email shows that line separately. Even without it, the shipping and time cost is $2,376 a month, about $28,500 a year. Andrea stated the explicit need herself: "one order across all nine practices, with stock that doesn't run out". The call ended in an advance: a two-practice trial for 60 days, with Andrea sharing last quarter's invoices so both sides can measure rush orders before and after.

What made this work: the rep asked one situation question, found the problem in the second, spent most of the call on implications, and let Andrea say what solving it was worth. The product was barely mentioned until she'd stated the need.

Rules of thumb for running SPIN

These are practical guidelines, not rules from the book:

• Don't ask an implication question until the buyer has admitted the problem. "What does it cost you?" lands badly if they haven't agreed anything is wrong.
• Get at least one number per problem. Frequency times cost is the arithmetic the buyer's finance team will ask for.
• Don't present until you hear an explicit need. If you catch yourself describing features after a complaint, go back to implication questions.
• End every call with a proposed advance. Decide before the call what the best realistic next step is.

Check your own calls

Take one recorded call a week and tally every question you asked. It takes 15 minutes, and it's the fastest way to see whether you're actually using SPIN.

Call: [account, date]   Length: [minutes]

Situation questions:   tally ____
Problem questions:     tally ____
Implication questions: tally ____
Need-payoff questions: tally ____

Implied needs heard (buyer's words):
Explicit needs stated (buyer's words):
Did I present before an explicit need?  yes / no
Outcome: order / advance / continuation / no sale
The advance agreed (action, owner, date):
One implication question I should have asked:

If situation questions outnumber the rest, do more research before calls. If you hear plenty of implied needs but few explicit ones, you need more implication questions. If calls end in continuations, decide the advance you'll propose before you dial.

When SPIN fits and when it doesn't

It fits consultative B2B sales with several meetings, a meaningful price and a buyer who has to justify the purchase internally. It's especially strong in discovery, which is why many teams pair it with a qualification framework such as MEDDPICC: SPIN questions fill in the pain and metrics that MEDDPICC asks you to prove.

It's weaker when the sale is small and quick (the book itself says small sales behave differently), when the buyer already knows exactly what they want and is comparing prices, or when the buyer hasn't noticed the problem at all. In that last case, the Challenger Sale approach of teaching a new insight can create the problem SPIN then explores. For the broader approach SPIN fits within, see consultative selling.

Common mistakes

• Interrogating with situation questions. Research the facts. Every one you ask is one fewer implication question.
• Leading need-payoff questions. "Wouldn't you agree that saving money is important?" isn't a need-payoff question. "What would that be worth?" is.
• Treating SPIN as a script. The sequence is a map, not a running order. Follow the buyer, then return to the next problem.
• Pitching at the first complaint. An implied need isn't a buying decision.
• Counting friendly calls as progress. A call without an advance is a continuation.

Situation research at volume is the slow part of call preparation. Bebop researches each account and writes a playbook covering what's happening at the company and the angle to open with, so you can spend the call on problems and implications.

Next step: plan your next discovery call, with the implication questions written in advance, using the free sales call planning template.