Forecasting with SPIN means placing each deal in a forecast category by the needs its buyers have stated and the commitments they have made. A frontline manager does it with each rep on the weekly forecast call, two or three minutes per deal. The test for every category is the same: whose explicit need do we have, in their words, and did the last call end with the buyer agreeing to act?
The reason is in the research behind the method. Huthwaite International, which owns SPIN, reports that in major sales the problems buyers describe, which it calls implied needs, have no relationship with success, while explicit needs, the wants buyers state, are a key indicator of it. A Need-payoff question is the one that invites the buyer to state that want. So the SPIN evidence a forecast should look for is a Need-payoff answer from the person who signs.
The sales methodology guide covers SPIN among other methods, the deal risk guide covers turning risk into the next conversation, and What is SPIN Selling? covers the basics. We describe the method from Huthwaite's published material and claim no partnership with them.
What forecasting with SPIN means
Most forecasts are built on the seller's progress: demo done, proposal sent, verbal yes. SPIN gives two signals from the buyer's side.
- PipelineAn implied need, with an example
- UpsideA champion's explicit need
- Best caseBudget holder met; last call an Advance
- CommitBudget holder's explicit need; two Advances
The first is the explicit need, stated by the right person. A user's explicit need gets a deal started. A budget holder's explicit need is what a commit forecast should rest on.
The second is the call outcome. Huthwaite says that in a major sale most calls end in 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 carries the work. A deal with three Continuations in a row is stalling even when every call felt friendly.
The gates
Use your own category names. The gates are buyer evidence the rep can quote.
| Category | Gate: all of these are true | Question on the forecast call |
|---|---|---|
| Pipeline | A Problem question has uncovered an implied need, with an example | "What problem did they describe, and what example did they give?" |
| Upside | A user or champion has stated an explicit need in a Need-payoff answer | "What did they say they want, in their words?" |
| Best case | The budget holder has been met and has described the cost of the problem; the last call was an Advance | "What did the budget holder say it costs them?" |
| Commit | The budget holder has stated an explicit need; the last two calls were Advances; the buyer has confirmed the close date and the remaining steps | "What did the budget holder say they want, and what did they commit to on the last call?" |
The procedure: eight steps
1. Agree the gates with the team
Write the table into the forecast template or the CRM, with a field for the budget holder's explicit need and a field for the last call's outcome. Good looks like: every rep able to say the gates from memory.
2. Start with commit
Review commit deals first. Good looks like: no upside discussed until every commit deal has been checked.
3. Ask for the budget holder's words
Say: "What did the budget holder say they want?" Good looks like: a quote with a date. A paraphrase from the champion is upside evidence.
4. Ask for the last two call outcomes
Say: "What did the buyer commit to do on the last two calls?" Mark each Advance or Continuation. Good looks like: two buyer actions, such as "booked the security review" and "sent the usage data."
5. Move the deal to the category its evidence supports
A deal sits in the highest category whose gates it meets. Good looks like: the category changed during the call, with the missing gate noted.
6. Check the close date against the buyer's steps
Ask which steps remain on the buyer's side and whether the buyer has confirmed the date. Good looks like: named steps and a date the buyer said.
7. Agree the next call for every deal that moved down
For each deal that dropped, agree who the rep needs to speak to, the Implication questions that will develop their problem, and the highest realistic commitment to propose. Huthwaite's research says top performers propose the highest realistic commitment the customer can give. Good looks like: a named meeting and a written ask.
8. Review the quarter's misses
After the quarter, list the commit deals that slipped and which gate was weakest. Good looks like: one gate made stricter for next quarter.
Worked example
This example is illustrative. A rep has a $45,000 deal for a learning platform with a regional bank, forecast as commit for this month.
Step 3: asked for the budget holder's words, the rep quotes the head of learning: "We need onboarding for branch staff down from six weeks to four." The budget holder is the chief operating officer, who has not been met. The quote is a strong explicit need from the champion. It is upside evidence.
Step 4: the last two calls ended with "we'll discuss it at our leadership meeting" and "send over a proposal." Both are Continuations.
Step 5: the deal moves from commit to upside. It has a champion's explicit need; it lacks a budget holder's need and an Advance.
Step 7: the rep will ask the head of learning for 30 minutes with the COO, which would be an Advance in itself. For that meeting the rep drafts Implication questions: "When a new branch hire takes six weeks to ramp, what happens to the branch's service targets?" and "How many hires did the branches make last year?" Then a Need-payoff question: "If new hires were productive in four weeks, where would that show up for you?"
If the COO answers that question with a want of her own and agrees to the next step, the deal returns to best case on evidence.
A gate check to paste into the forecast doc
Each rep answers these per deal the day before the call. A blank answer means the deal sits one category lower until the gap is closed.
- Who is the budget holder, by name, and when did the rep last speak with them?
- What did the budget holder say they want, quoted, with the date?
- What implied needs has the buyer described, and with what examples?
- What did the buyer commit to on each of the last two calls? Mark each Advance or Continuation.
- Which steps remain on the buyer's side, and who confirmed the close date?
- If the deal fails a gate, what is the next call, with whom, and what commitment will the rep ask for?
The manager reads the answers before the call and goes straight to the blanks. Deals with every line filled from the buyer's own words take seconds.
Where it goes wrong
The champion's need stands in for the budget holder's. A user who wants the product cannot sign for it. Ask whose words the explicit need is in.
Problems are forecast as needs. "They're frustrated with onboarding" is an implied need. It belongs in pipeline.
Continuations are counted as momentum. "Sent a proposal" is the seller's action. Ask what the buyer did.
The forecast call is a status meeting. If no deal ever moves down, the gates are decoration.
A dropped deal gets no next step. Moving a deal down without preparing the conversation that would move it back up only makes the forecast more pessimistic. The fix is the next call.
Forecasting every deal on SPIN evidence
The gates are easy to apply on the forecast call. The work that does not fit is preparing the next conversation for every deal that falls short. Our AI sales experts take that part. They stage each deal by buyer evidence, say which gate is missing, and take the rep straight into a call to prepare the conversation that closes it.
Caty works your own method, so a team running SPIN gets coached against SPIN (how methodology coaching works). The rep talks the deal through by voice; typing is the fallback when they cannot talk. Bryce shows the manager which gates fail across the team. A deal sitting in commit on a Continuation is the obvious first one to bring when you talk to us.
FAQ
How do you use SPIN selling for forecasting?
You use SPIN selling for forecasting by gating each forecast category on buyer evidence. An implied need qualifies a deal for pipeline, a champion's explicit need for upside, the budget holder met and describing the cost, with the last call an Advance, for best case, and the budget holder's own explicit need plus recent Advances for commit. Move deals down when a gate is missing.
What is a need-payoff question?
A need-payoff question is the SPIN question that asks the buyer to describe the value of solving a problem. An example: "If approvals cleared in two days, what would that change for you?" Huthwaite describes it as inviting the buyer to consider the benefits and express an explicit need. Given by the budget holder, the answer is the evidence a commit gate rests on.
Why are explicit needs a better forecast signal than problems?
Huthwaite's research found that in major sales, implied needs, the problems buyers describe, had no relationship with success, while explicit needs were a key indicator of it. A deal full of problems shows the buyer is unhappy. An explicit need from the budget holder shows they want something you can provide.
What does a Continuation mean for a forecast?
A Continuation means the buyer committed to nothing on the last call, so the deal did not move. One Continuation is common. Two or three in a row on a deal in commit is a reason to move it down and plan a call that asks for a real commitment.
Can SPIN replace a qualification framework like MEDDPICC?
SPIN is a questioning method and was not designed as a qualification checklist. Many teams run SPIN for the conversation and a framework like MEDDPICC for qualification. SPIN's evidence, explicit needs and Advances, still makes a strong forecast gate on its own or alongside one.