SPIN Selling examples work best followed through one deal: a Situation question opens a topic, a Problem question finds the difficulty, Implication questions give it a cost, and a Need-payoff question lets the buyer state the value.
Most lists of SPIN questions give twenty unrelated examples per type. That shows the wording and hides the part that matters, which is how each question builds on the buyer's last answer. This guide follows a single illustrative deal from the first question to the agreed next step, so each example shows what it changed in the conversation.
What the job is, and who does it
The job is discovery: one conversation, usually 30 to 45 minutes, in which the rep helps the buyer turn a problem they live with into a need they want to act on. The account executive does it, often with a manager reviewing the recording afterward.
SPIN Selling comes from Neil Rackham's research at Huthwaite International, which owns the method and says the research observed 35,000 business-to-business sales interactions. Huthwaite separates two kinds of need. "An implied need is a problem or dissatisfaction. An explicit need is a want or desire." Problem questions find implied needs. Implication questions develop them. Need-payoff questions turn them into explicit needs, which the buyer states in their own words.
Preparation takes about 20 minutes per call: the research that removes needless Situation questions, and two or three likely problems to probe. The questions themselves cannot be scripted in full, because each one depends on the answer before it. For the method in short, see the SPIN Selling book summary.
How to build SPIN questions for one deal
Build the call around one or two topics, and run each topic through all four question types before moving on. The steps below are the order a rep prepares and then asks.
- 01SituationOne fact the rep could not look up
- 02ProblemWhere the current way breaks down
- 03ImplicationTwo or three questions, each one step further
- 04Need-payoffThe buyer states what fixing it is worth
- 01SituationOne fact the rep could not look up
- 02ProblemWhere the current way breaks down
- 03ImplicationTwo or three questions, each one step further
- 04Need-payoffThe buyer states what fixing it is worth
- Do the Situation research before the call. Look up headcount, systems, recent news and the buyer's role. Every fact found in advance is a Situation question the buyer does not have to answer. Huthwaite notes that successful sellers limited their Situation questions.
- Pick the problems worth probing. From the research, choose two or three difficulties buyers like this one tend to have. They are guesses to test, so frame them as questions.
- Ask one Situation question per topic. Ask only for what could not be researched, such as how a process runs inside the buyer's team.
- Ask a Problem question and wait. Ask where that process breaks down, how often, and who notices. Let the buyer describe it fully before moving.
- Follow the problem with two or three Implication questions. Each one pushes the problem one step further out: into cost, into another team, into the buyer's own targets. This is the step reps skip most.
- Ask a Need-payoff question. Invite the buyer to say what solving the problem would be worth or change. The answer is the explicit need.
- Summarize in the buyer's words and ask for an advance. Play back the need as the buyer stated it, then ask for a specific next step with a date and the people involved.
Implication questions carry the most weight in a large sale. The implication question entry has more examples of following a problem into its cost.
A worked example: one deal, all four types
This example is illustrative. Arrowmere is an invented 600-person logistics firm, and Sam is its head of fleet operations. The rep sells fleet maintenance software and has 40 minutes booked.
Research before the call. The rep already knows Arrowmere runs about 200 vehicles from three depots, because the firm's careers page and a trade press interview say so. That removes three Situation questions.
Situation. "How do your depots decide when a vehicle goes in for servicing today?"
Sam: "Each depot manager keeps a spreadsheet. They book services by mileage."
Problem. "Where does that process cause trouble?"
Sam: "Vehicles miss services when a depot manager is out. And we get breakdowns we should have seen coming."
The rep resists the urge to mention the product. Sam has named an implied need. It is a problem Arrowmere has lived with for years.
Implication, first step. "When a vehicle breaks down on a route, what happens to the deliveries on it?"
Sam: "We send a second vehicle, so the drops are late. Some customers have penalties in their contracts for late delivery."
Implication, second step. "How often did that happen last quarter?"
Sam: "About 30 breakdowns. Our finance team flagged the penalty line in the last board pack."
Implication, third step. "When the board sees that line, who is asked to explain it?"
Sam: "Me."
Three questions took the problem from a spreadsheet habit to a cost on a board report with Sam's name next to it. Sam supplied every fact.
Need-payoff. "If the depots booked services before a breakdown was likely, what would that mean for you?"
Sam: "Fewer late drops, and I would stop defending that penalty line every quarter. If we cut breakdowns by half, that alone pays for a system."
That answer is the explicit need: Sam wants servicing booked by risk, and has put a value on it in their own words.
Summary and advance. "So the goal is fewer breakdowns on route, so the late-delivery penalties fall and you are not explaining them to the board. Would it make sense to look at last quarter's 30 breakdowns with your finance lead, and see how many a risk-based schedule would have caught?"
Sam agrees to a meeting with the finance lead in two weeks. In SPIN terms that is an advance: an agreed action that moves the sale forward.
What each question changed
Each question type left something new on the table. Reading the example back by type shows where the deal moved.
| Type | Question in the example | What it produced |
|---|---|---|
| Situation | How depots decide on servicing | The current process: spreadsheets, by mileage |
| Problem | Where that causes trouble | Missed services and avoidable breakdowns |
| Implication | Deliveries on a broken-down route | Late drops and contract penalties |
| Implication | How often last quarter | About 30 breakdowns, flagged by finance |
| Implication | Who explains it to the board | A personal stake for the buyer |
| Need-payoff | What fixing it would mean | The buyer's own value: half the breakdowns pays for a system |
The example is short on Situation questions and long on Implication questions, which is the balance Huthwaite describes in successful sellers.
Where it goes wrong
Most SPIN calls go wrong in one of five places. Each shows up clearly on a recording.
- Too many Situation questions. Ten fact questions in a row feel like a form. Huthwaite warns that buyers can feel interrogated. The fix is research before the call.
- Jumping from Problem to pitch. The buyer names a problem and the rep starts describing the product. The buyer has not felt the cost yet, so the pitch lands as a feature list. Ask "what happens when that goes wrong?" first.
- Need-payoff asked too early. "Wouldn't it be great if..." before the cost is clear reads as a leading question. Ask it only once the buyer has described the consequences.
- Implication questions that turn into a cross-examination. Six linked questions about one problem start to feel like pressure, and buyers push back by playing the problem down. Two or three, each built on the last answer, usually make the point. In the Arrowmere call the third question was about Sam personally, and that was the right place to stop and move to Need-payoff.
- No advance at the end. The call ends with "let's touch base next month", which is a continuation. Close each call by asking for a specific action with a date.
Coaching this on live deals
A manager can coach SPIN from one question in the 1:1: what did the buyer say the problem costs, in their words? If the rep can only paraphrase, the Implication questions were not asked or not answered.
Sam's answer, "Me," is what a manager wants in the rep's notes. Caty, our AI sales expert for SPIN, works from the team's own playbook and talks each deal through with the rep by voice or video on a call, before and after the buyer meeting (master your sales methodology). Replicate Labs has no partnership with Huthwaite International. See the sales methodology guide for other methods, or talk to us.
FAQ
What is an example of a SPIN Selling question?
An example of an Implication question is "When a vehicle breaks down on a route, what happens to the deliveries on it?" It takes a problem the buyer named and follows it to a cost.
What are examples of Situation questions in SPIN Selling?
Situation questions ask about the buyer's current setup, such as "How do your depots decide when a vehicle goes in for servicing?" Keep them few and ask only what research could not tell you.
What is an example of a Need-payoff question?
A Need-payoff question asks the buyer what solving the problem would mean, such as "If the depots booked services before a breakdown was likely, what would that mean for you?"
How many SPIN questions should you ask on a call?
SPIN sets no fixed number of questions, and a topic usually needs one Situation question, one or two Problem questions, two or three Implication questions and one Need-payoff question before moving on.
Do SPIN questions have to be asked in order?
SPIN questions follow a rough order within each topic, from Situation to Need-payoff. Huthwaite describes SPIN as a framework that sellers adapt, so a rep can loop back as new problems appear.