SPIN Selling is a way to run sales calls with four kinds of questions, asked in order: Situation, Problem, Implication and Need-Payoff. The buyer ends up explaining their problem, what it costs and what fixing it is worth, in their own words.
Neil Rackham built the method from a study of more than 35,000 sales calls and published it in SPIN Selling in 1988. His finding still holds: in large deals, the sellers who win ask better questions, and they ask about consequences, not only problems.
This guide covers each question type with examples, a cheat sheet, a SPIN call to learn from, and how to train your team and check SPIN on real calls.
What each letter means
| Stage | What you learn | Example question |
|---|---|---|
| Situation | Facts about how the buyer works today | "How do new hires get onboarded today?" |
| Problem | What is hard, slow or not working | "How are the new hires ramping?" |
| Implication | What the problem costs if nothing changes | "What did two missed quotas cost you last quarter?" |
| Need-Payoff | What solving it would be worth to the buyer | "What would faster ramp mean for the three Q4 hires?" |
The order matters. Situation and problem questions find the issue. Implication questions make it big enough to act on. Need-payoff questions let the buyer describe the value, so you don't have to pitch it.
S: Situation questions
Situation questions collect facts about the buyer's team, tools and process. You need them for context, but each one costs the buyer time and gives them nothing back.
Do your research first and only ask what you can't find out yourself. Two to four situation questions is usually enough.
- Could you walk me through how [process] works today?
- How long has your team been using [current system]?
- What tools do you use to handle [task]?
- Who is involved in decisions about this area?
- How many people work on this process?
- How does your current setup connect to your other systems?
P: Problem questions
Problem questions find what is hard, slow or frustrating. They turn a general conversation into a specific issue you can help with.
Ask about the area your product solves, and follow up until you have a concrete example ("Tell me about the last time that happened").
- What is the hardest part of your current process?
- Where does your team lose the most time?
- What stops you from getting the results you want?
- What frustrates your team most about the current tool?
- Which problems keep coming back?
I: Implication questions
Implication questions explore what the problem costs: in revenue, time, people or risk. This is the stage that moves a buyer from "that's annoying" to "we need to fix this now".
It's also the stage most sellers skip. Once the buyer names a problem, the urge is to jump to the demo. Stay on the problem and ask what it leads to. Keep the tone curious, not accusatory.
- How does this affect your team's ability to hit its number?
- What happens to customer retention if this continues?
- What did this cost you last quarter, roughly?
- If nothing changes, what does this look like in a year?
- How does this affect your plans to grow the team?
- Who else feels the effect of this problem?
N: Need-Payoff questions
Need-payoff questions ask the buyer what solving the problem would be worth. When the buyer says the value out loud, they believe it more than if you claimed it, and they repeat it to the people who sign.
Need-payoff question examples
Each example below follows a problem the buyer already named:
| Problem the buyer named | Need-payoff question |
|---|---|
| New hires take five months to ramp | "If they ramped in three months, what would that mean for your Q4 target?" |
| Managers have no time to review calls | "If every call were reviewed for you, what would your managers do with that time?" |
| Deals stall after the first meeting | "How would a clear next step on every call change your forecast?" |
| Reports take a day to build each week | "What would your team do with that day back?" |
| Errors in quotes cause rework | "If errors dropped by half, who would notice first?" |
| Churn is concentrated in the first year | "What would keeping five more first-year customers be worth?" |
A good need-payoff question is open, refers to the buyer's own problem, and asks about their outcome, not your product.
A SPIN call, start to finish
Here is a short discovery call between Ivy, a seller, and Ben, a sales director at Brightline Dental.
Ivy (Situation): How do new outbound hires get onboarded today?
Ben: My managers onboard each one themselves. We hired five this year.
Ivy (Problem): How are they ramping?
Ben: Not great. Two of the five missed quota last quarter.
Ivy (Implication): What did those two missed quotas cost you?
Ben: Roughly a third of the team's new-business target. And my managers spent weeks on it.
Ivy (Implication): What happens if the three people you're hiring in Q4 ramp the same way?
Ben: Then we miss the year.
Ivy (Need-Payoff): If they reached quota a month sooner, what would that mean for you and your VP?
Ben: It would cover the gap. That's the case I'd need to make.
Many sellers would go straight to the demo after "two of the five missed quota". The two implication questions are what turn that problem into a reason to buy, and the need-payoff question gives Ben the words for his VP.
SPIN cheat sheet
| Stage | Goal | Ask | Avoid |
|---|---|---|---|
| Situation | Context you can't research | 2 to 4 questions about process, tools and people | A long list that feels like a form |
| Problem | A specific problem you can solve | "What's hardest about...?", "Tell me about the last time..." | Pitching as soon as a problem comes up |
| Implication | The cost of doing nothing | "What does that cost?", "What happens if nothing changes?" | Sounding like you're blaming the buyer |
| Need-Payoff | The value, in the buyer's words | "What would it mean if...?", "Who else would benefit?" | Questions about your features |
Who SPIN works for
SPIN works best in complex B2B sales: several decision makers, a long cycle, and a buyer who needs to justify the purchase internally. Implication and need-payoff answers give your champion the words to make that case.
It works less well for:
- Simple, low-cost products where people decide in one call
- High-volume transactional sales with a fixed script
- Inbound buyers who already know what they want and need a price
SPIN combines well with other methods. Many teams use it to run discovery and use GPCT or MEDDICC to check whether the deal is qualified. The Challenger Sale adds an insight you bring to the call, where SPIN draws the insight out of the buyer.
Common mistakes
- Too many situation questions. The buyer feels interviewed. Research first.
- Skipping implication. The problem stays small, so there's no urgency. It's the stage people skip most.
- Leading questions. "Wouldn't it be great if...?" is not a need-payoff question. Let the buyer describe the value.
- Treating SPIN as a script. The order is a guide. Follow the buyer, then return to the stage you skipped.
- Answering objections too early. If the buyer pushes back before you've explored the problem, go back to problem and implication questions. See how to handle common objections.
- No next step. A good SPIN call still needs a date and an owner for what happens next.
How to train your team on SPIN
People learn SPIN by asking the questions, not by reading about them.
- Teach one stage at a time. Start with implication questions, since most people skip them.
- Practice in pairs. One person plays the buyer from a card with a clear problem and its real cost. The other has 10 minutes to find the cost with implication questions, without pitching. Swap roles and change the card each week.
- Review real calls against SPIN. Pick two recorded calls a week per person. For each stage, mark met, partial or missed, and write down the question they asked (or should have). Here is how to turn that into a scorecard.
- Coach the pattern. In 1:1s, pick the stage a person misses most and play a moment from one of their calls.