A SPIN deal review is a 20 to 30 minute conversation between a rep and a manager about one open deal, checked against two things the SPIN research ties to success: whether the buyer has stated explicit needs, and whether recent calls ended with the buyer committing to act. It ends with the Implication questions the rep will ask next and the commitment they will propose.
SPIN is usually taught as a discovery technique. Huthwaite International, which owns the method, also describes a coach's job as helping reps "plan, execute and review their sales approach," and its coaching material covers call planning, live call observation and call reports. A deal review is where those meet a live opportunity. The sales methodology guide covers SPIN among other methods, the deal coaching guide covers deal reviews in general, and What is SPIN Selling? covers the basics. We describe the method from Huthwaite's published material and claim no partnership with them.
What a SPIN deal review checks
Two findings from Huthwaite's research do the work.
- The buyer commits to nothing
- The seller does the work
- "They'll get back to us"
- The buyer commits to an action
- It moves the sale forward
- Huthwaite counts it a successful call
The first is about needs. An implied need is a problem the buyer describes; an explicit need is a want the buyer states. Huthwaite reports that in major sales, implied needs have no relationship with success, and explicit needs are a key indicator of it. A deal full of buyer complaints can feel strong and still have no explicit need behind it.
The second is about commitment. In a major sale, Huthwaite says, most calls end in either an Advance, where the buyer commits to an action that moves the sale forward, or a Continuation, where the buyer commits to nothing and the seller does the work. Huthwaite counts Advances as successful calls and Continuations as unsuccessful ones. A deal whose last three calls ended "they'll get back to us" is drifting, whatever the CRM stage says.
When SPIN fits the deal
SPIN was built for major sales: high-value decisions with several people involved, a long cycle and a buyer who will live with the choice for years. Rackham's case was that techniques that work in small sales, closing pressure in particular, backfire in large ones.
That gives a simple test before you start. If the deal is a quick decision by one buyer on a known need, the needs map adds little; check the call log for an Advance and move on. If the deal has several stakeholders, a budget holder the rep has not met, or a close date that keeps moving, run all eight steps. Most deals on a forecast that worry a manager are the second kind.
SPIN in one minute
SPIN names four kinds of question, and a deal review uses all four to decide what the rep asks next.
| Question type | What it does | Example from a field service deal |
|---|---|---|
| Situation | Gathers facts about the buyer's world | "How many crews do you schedule each day?" |
| Problem | Surfaces difficulties and dissatisfaction | "How often does a job get double-booked?" |
| Implication | Connects a problem to its wider effects, so it feels bigger | "When a job slips a day, what does that do to billing and overtime?" |
| Need-payoff | Invites the buyer to state the value of solving it | "If rescheduling dropped by half, where would that show up?" |
Problem questions produce implied needs. Implication and Need-payoff questions are how an implied need turns into an explicit one, which is why the review ends by writing them. Situation questions are necessary but cheap: a rep who has done their research needs only a few, and a senior buyer quickly tires of answering questions the rep could have looked up.
How SPIN works across the four stages of a call
SPIN comes from Neil Rackham's research at Huthwaite International, built on more than 35,000 sales calls and published in the 1988 book SPIN Selling. Huthwaite describes a call as four stages: preliminaries, investigating, demonstrating capability and obtaining commitment. The question types live in the second stage, but a deal review touches all four.
| Call stage | What happens in it | What the review checks |
|---|---|---|
| Preliminaries | The opening: who the rep is and why the call is happening | Whether the rep had a reason for the call the buyer cared about |
| Investigating | Situation, Problem, Implication and Need-payoff questions | Which needs on the map are still implied, per stakeholder |
| Demonstrating capability | Showing how the offer meets the explicit needs | Whether anything was shown that no stated need called for (step 5) |
| Obtaining commitment | Asking the buyer to take an action | Advance or Continuation, from the call log (step 4) |
Read the table from the bottom. A run of Continuations usually traces back up the stages: the rep asked for little because there was little to ask for, because the capability shown answered no explicit need, because investigating stopped at Problem questions. The review fixes the earliest stage that broke, which is usually investigating.
The needs map and the call log
Fill both from the rep's account and the call notes.
Needs map
| Stakeholder | Implied needs (problems they described) | Explicit needs (wants they stated, in their words) | Evidence |
|---|---|---|---|
| Name, role | Call date, quote |
Call log
| Date | Who | What the buyer committed to do | Advance or Continuation |
|---|---|---|---|
The procedure: eight steps
1. Pick the deal
Choose an open deal in this quarter's forecast or above your size threshold. Good looks like: the rep chose it or agreed it was the one they were least sure of.
2. Let the rep tell the deal out loud
Say: "Tell me what each person on their side wants, in their words." Do not open the CRM yet. Good looks like: the rep quoting buyers, and saying "I think" where they are guessing.
3. Fill the needs map
For each stakeholder, sort what the rep heard into implied and explicit needs. Good looks like: the explicit-needs column holding only sentences a buyer said.
4. Fill the call log
List the last three to five buyer interactions and what the buyer committed to do. Mark each Advance or Continuation. Good looks like: an honest log, with "sent them the deck" written as a Continuation.
5. Check where capability was shown
Ask which capabilities the rep has presented, and to whom. Huthwaite found that offering a solution the buyer has not expressed interest in is the easiest way to create an objection. Good looks like: every capability shown tied to an explicit need on the map; objections in the deal traced to any that were not.
6. Choose the stakeholder and the need to develop
Pick the stakeholder whose explicit need the deal most depends on, usually the budget holder, and the implied need most likely to become one. Good looks like: one person, one problem, agreed with a reason.
7. Write the next call's questions
Draft two or three Implication questions that connect the problem to what that person cares about, and one Need-payoff question that invites them to state the value. Good looks like: questions in the rep's own words, specific to this account.
8. Agree the highest realistic commitment
Huthwaite's research says top performers propose the highest realistic commitment the customer can give. Agree what the rep will ask for at the end of the next call. Good looks like: an action the buyer takes, with a date, that would count as an Advance.
Worked example
This example is illustrative. A rep brings a $60,000 deal for a field service platform with a utilities contractor, in the forecast for next month.
Step 2: the rep says the operations manager "is desperate to fix scheduling" and the CFO "will sign off if ops wants it."
Step 3, the needs map:
| Stakeholder | Implied needs | Explicit needs | Evidence |
|---|---|---|---|
| Operations manager | Crews double-booked; overtime on weekends | "I need every job scheduled the day before, by 4pm" | Discovery call, week 2 |
| CFO | None heard | None | Never spoken to |
| IT lead | Worried about another integration | None |
Step 4, the call log: the demo ended with the operations manager agreeing to share job data (Advance). The next two calls ended with "let me check internally" and "send over pricing" (Continuations).
Step 5: the rep presented the mobile app and the reporting suite to the IT lead, who had expressed no need for either. The integration objection came on that call.
Step 6: the deal depends on the CFO, who has stated nothing. The implied need with a cost attached is weekend overtime.
Step 7: the Implication questions, for a meeting with the CFO: "How much of last quarter's overtime came from rescheduled jobs?" "When a job slips a day, what does that do to billing?" The Need-payoff question: "If rescheduling dropped by half, where would that show up in your numbers?"
Step 8: the commitment the rep will ask the operations manager for: 30 minutes with the CFO this month, with the overtime figures on the table. The deal stays out of the forecast until that meeting happens and the CFO states a need.
Using call recordings in the review
When calls are recorded, the review gets faster and more honest. Before the meeting, the rep or manager pulls three short moments: the last time the budget holder spoke, the end of the last two calls, and any point where the rep presented a capability. Those three clips fill most of the needs map and the call log with the buyer's own words.
Listen for the type of each question the rep asked. A call with a long run of Situation and Problem questions and no Implication questions explains a deal with plenty of complaints and no stated want. Listen to the last two minutes of each call for the commitment: what did the rep ask for, and what did the buyer agree to do? Many Continuations come from a rep who never asked for anything specific.
Adjusting the review for the rep
A newer rep usually struggles with step 7. Writing Implication questions that connect to what a specific person cares about takes practice, so spend more of the session there. Have the rep say each question out loud and ask whether the buyer would feel it was about their business.
An experienced rep usually has the questions and skips steps 3 and 4. They know the deal feels strong and resist sorting it into implied and explicit needs. That is the step that catches their blind spot, so hold them to it, especially for stakeholders they have not met.
Where SPIN reviews get criticized, and what to do about it
The common criticisms of SPIN are about how it is taught, and they show up in reviews too.
It turns into a script. Reps memorize question types and fire them in order. In the review, check whether the questions are specific to this account. A generic Implication question ("What impact does that have?") rarely produces an explicit need.
Buyers arrive having done their research. In step 7, strike any question the buyer could answer from your website, and keep only Implication questions that show the buyer an effect they had not connected.
It says little about the buying committee. SPIN was built around the conversation with one buyer. The needs map in this review handles that by asking for each stakeholder's needs separately, and the deal usually depends on the person with the emptiest row.
After the review
The review is only useful if the next call changes. The same day, the rep sends the meeting request for the call the review planned, while the reason for it is fresh. After that call, the rep updates the needs map with any new explicit need and logs the outcome as an Advance or a Continuation, in the buyer's words. And the next review of the deal opens with that log entry: did the buyer commit to what the rep asked for? If not, the review starts with why.
Where it goes wrong
Complaints counted as needs. "They hate their current system" is an implied need. Until the buyer says what they want, the deal has nothing to forecast on.
Continuations logged as progress. "Sent pricing" and "they're reviewing" are seller actions. Ask what the buyer committed to do.
One stakeholder's need covers the deal. A strong explicit need from a user does not tell you what the budget holder wants. Map each person.
Pitching to fix a stalled deal. The urge after a weak review is to send more capability. Huthwaite's finding on benefit statements says that creates objections. Go back to Implication questions.
Running more reviews to fix a skill gap. More frequent reviews from a manager who has not learned to run them tend to make results worse, so get the eight steps right on a few deals before adding more.
Reviewing every deal with SPIN
A manager can run this review on a handful of deals a week. Our AI sales experts run it on the rest of the rep's live deals; Caty works your own method, so a team running SPIN gets coached against SPIN (how methodology coaching works).
The rep brings the deal to Caty on a call, talks it through and leaves with the Implication questions and the commitment to propose; typing is the fallback when they cannot talk. After the buyer call they come back and the needs map moves on the buyer's words. Bryce shows the manager which deals across the team are running on Continuations, which is the list to review first next week. To set it up for a SPIN team, talk to us.
FAQ
How do you use SPIN selling in a deal review?
Use SPIN in a deal review by checking two things: which stakeholders have stated explicit needs in their own words, and whether recent calls ended in Advances. Then pick the stakeholder the deal depends on, write Implication questions that develop their problem, and agree the highest realistic commitment for the next call.
What is the difference between an Advance and a Continuation?
An Advance is a call outcome where the buyer commits to an action that moves the sale forward, such as introducing a decision maker. A Continuation is an outcome where the buyer commits to nothing, such as "send me some information." Huthwaite treats Advances as successful calls and Continuations as unsuccessful.
Is SPIN a qualification framework?
SPIN is a questioning and selling method. It was not designed as a qualification checklist like MEDDPICC. Its research findings still make a useful qualification test: a deal with no explicit need from the budget holder and a run of Continuations is a weak deal, whatever stage it sits in.
Why do explicit needs matter in a deal review?
Explicit needs matter because Huthwaite's research found they are a key indicator of success in major sales, while implied needs, the problems buyers describe, showed no relationship with success. A deal review that counts complaints overstates the deal. One that counts stated wants is closer to what the buyer will do.
How long should a SPIN deal review take?
A SPIN deal review should take 20 to 30 minutes per deal. Allow five minutes for the rep to tell the deal, ten to fill the needs map and call log, and the rest to choose the stakeholder, write the questions and agree the commitment for the next call.
What are the four types of SPIN questions?
The four types are Situation, Problem, Implication and Need-payoff. Situation questions gather facts, Problem questions surface difficulties, Implication questions connect a problem to its wider effects, and Need-payoff questions invite the buyer to state the value of solving it. In a deal review, the last two are the ones the rep plans for the next call.
Can you run a SPIN review on a team that uses another method?
A SPIN review works on a team that sells with another method, because its two checks, explicit needs per stakeholder and Advances on recent calls, sit comfortably beside MEDDPICC or Gap Selling. Use the team's own words for the deal stages and add the needs map and call log as a lens. Keep one vocabulary on the CRM, so reps are not asked to describe the same deal two ways.