A SPIN discovery call is a buyer meeting where the rep uses four kinds of question, Situation, Problem, Implication and Need-payoff, to help the buyer state in their own words a need the rep's solution can meet. An account executive runs it in 30 to 60 minutes, and it ends with a commitment from the buyer to do something that moves the sale forward. Preparing the questions takes 20 to 30 minutes. Ready-to-adapt questions of each type are in the question bank below, with a table of SPIN questions for finance, operations, sales and IT buyers.
SPIN comes from research led by Neil Rackham at Huthwaite International, built on more than 35,000 sales calls. Huthwaite describes the four question types as "a logical persuasive framework" and the call as four stages: preliminaries, investigating, demonstrating capability and obtaining commitment. The sales methodology guide covers where SPIN sits among methods, the discovery call guide covers discovery as a whole, 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 discovery call is
The research behind SPIN found a difference between two kinds of need. An implied need is a problem or dissatisfaction ("our month-end close is slow"). An explicit need is a want or desire for a solution ("we need to close in three days"). Huthwaite reports that in major sales, implied needs have no relationship with success, while explicit needs are a key indicator of it. A discovery call that collects complaints has found implied needs. The SPIN questions exist to turn them into explicit ones.
- 01PreliminariesPurpose and permission
- 02InvestigatingSituation, Problem, Implication, Need-payoff
- 03Demonstrating capabilityAgainst the need just stated
- 04Obtaining commitmentAim for an Advance
Huthwaite also found that benefit statements made too early are a major cause of objections. Showing how you meet a need the buyer has just expressed rarely draws one. That is why the investigating stage comes before any capability.
The four question types and what each is for
| Type | What it does | Example | Watch for |
|---|---|---|---|
| Situation | Gathers facts and context | "How is the maintenance budget allocated?" | Huthwaite found successful sellers ask fewer of these and keep them focused |
| Problem | Uncovers difficulties and dissatisfactions | "How often do operational problems occur?" | A problem the buyer lives with is still only an implied need |
| Implication | Develops a problem by exploring its effects elsewhere in the business | "How does that problem affect your team's productivity?" | The question that builds urgency, and the hardest to ask well |
| Need-payoff | Has the buyer state the value of solving it | "How would resolving this contribute to your goals?" | The buyer, speaking about value, turns an implied need into an explicit one |
The examples are adapted from Huthwaite's own question bank.
The procedure: eight steps
1. Prepare so Situation questions are few
Research the account before the call, and use Situation questions to confirm what you found. List two or three problems your solution solves and draft Implication questions for each. Good looks like: no more than three Situation questions on the plan.
2. Open with the preliminaries
State the purpose of the call and ask permission to explore the buyer's situation. Say: "I'd like to understand how this works today and where it causes trouble. Is that a good use of the time?" Good looks like: the buyer agreeing and adding something they want covered.
3. Ask focused Situation questions
Confirm the context you need to progress the sale. Good looks like: two or three minutes, with each question tied to a problem you plan to explore.
4. Ask Problem questions to find implied needs
Ask about difficulties and dissatisfactions in the areas you prepared. Write down the buyer's words. Good looks like: at least one problem the buyer describes with an example.
5. Ask Implication questions to develop them
Take the strongest problem and explore its consequences: cost, delay, risk, knock-on effects in other teams. Huthwaite notes that people can live with problems; Implication questions make the cost of living with this one visible. Good looks like: the buyer connecting the problem to something their boss cares about.
6. Ask Need-payoff questions
Ask the buyer what solving the problem would be worth. Good looks like: the buyer saying, in their own words, what they want, which is the explicit need.
7. Demonstrate capability against that need only
Show how your solution meets the need the buyer just stated. Skip capabilities they did not ask about. Good looks like: no objections, because you are offering something they just asked for.
8. Obtain commitment: aim for an Advance
Huthwaite distinguishes an Advance, where the buyer commits to an action that moves the sale forward, from a Continuation, where the buyer commits to nothing and the seller does the work. Propose the highest realistic commitment: a meeting with the budget holder, internal data shared, a trial scoped. Good looks like: the buyer agreeing to do something, with a date.
Worked example
This example is illustrative. A rep sells accounts payable automation to a distribution company. The meeting is with the finance controller.
Situation: "I saw you moved to a new ERP last year. Are invoices still coming in on paper and email?" Mostly email, about 3,000 a month.
Problem: "Where does the process slow down?" Approvals. Invoices sit with budget holders for days.
Implication: "When approvals sit, what happens at the supplier end?" Late payments; two suppliers put the company on hold last quarter. "And what did that do to operations?" A shipment was delayed and a customer order slipped. "Who heard about that?" The CFO, in the operations review.
Need-payoff: "If approvals cleared within two days, what would that change for you?" The controller says: "We'd stop losing early-payment discounts, and I wouldn't be explaining supplier holds to the CFO. I need approvals under 48 hours before our audit in March."
That last sentence is the explicit need, with a deadline.
Demonstrating capability: the rep shows approval routing and reminders, and stops there.
Commitment: "Could we take your last month's invoices and show you where the approvals stalled, with your CFO in the room?" The controller agrees to send the data and book 30 minutes with the CFO. That is an Advance.
A discovery question bank by type
These are our own examples for a B2B software sale, written in the four types. Rewrite them in your buyer's vocabulary before the call; a question that sounds borrowed gets a borrowed answer.
Situation (confirm, do not survey)
- "I read that you opened a second warehouse this year. Does it run on the same system as the first?"
- "Who owns this process today, and who else touches it?"
- "What are you using now, and how long has it been in place?"
Problem
- "Where does this process take longer than it should?"
- "What happens when someone is out? Who covers it?"
- "What did you try last time this came up, and how did it go?"
- "Which part of it do you hear the most complaints about?"
Implication
- "When that happens, what does it do to the team downstream?"
- "How does that show up in the numbers your boss looks at?"
- "If this is still the case next year, what does that mean for the plan you mentioned?"
- "Who else in the business feels this, even if they do not know the cause?"
- "What has it cost you the last time it went wrong?"
Need-payoff
- "If that were fixed, what would you do with the time?"
- "Who else would notice if this went away?"
- "What would it be worth to get this done before the date you mentioned?"
- "How would that help with the goal you described earlier?"
The Need-payoff questions only work after the Implication answers are on the table. Asked early, they sound like a pitch with a question mark.
SPIN questions for different people on the buyer's side
The same problem looks different from each seat, so the questions should change with the person in front of you. These are our own examples for a sale that touches operations, written for four common roles.
| Buyer | Problem question | Implication question | Need-payoff question |
|---|---|---|---|
| Finance lead | "Where do costs in this area come in above plan?" | "When that happens, what gets cut to make the quarter?" | "If those costs were predictable, what would you approve that you hold back now?" |
| Operations manager | "Which part of the week does your team spend firefighting?" | "What does that firefighting push back, and who notices?" | "What would your team do with those hours if the firefighting stopped?" |
| Sales leader | "Where do deals slow down after the customer says yes?" | "How does that delay show up in the forecast you send upward?" | "What would a reliable handover be worth to your number this year?" |
| IT lead | "Which requests from this team take the longest to support?" | "What other projects wait while your people handle them?" | "If those requests went away, what would you move up the list?" |
Use the role table to prepare, then follow what the buyer says. A finance lead who answers the Problem question with a staffing story has told you where the Implication question should go next.
Following an answer into the next question
Most of the skill in a live SPIN call is in the follow-up. A buyer gives a short answer to a Problem question, and the rep either moves to the next prepared question or follows the answer one step further. The second gets the call to an explicit need.
Three follow-ups work in almost any call. Ask for an example: "When did that last happen?" Ask who else felt it: "Who had to deal with that?" Ask what it led to: "And then what?" A buyer who can describe a specific event can usually put a cost on it.
Listen for the moment the buyer starts adding detail without being asked. That is usually the problem worth developing. When the answers get shorter, the problem is one they can live with, and it is time to try another.
How to write your own Implication questions
Implication questions are the hardest to improvise, so draft them before the call.
- List the problems your solution solves, in the words a buyer would use, two or three of them.
- For each problem, follow it one step outward. Slow approvals lead to late payments. Late payments lead to supplier holds. Supplier holds lead to delayed shipments.
- Find who feels each step. Finance feels the late payment, operations the hold, the customer the delay, the CFO the review.
- Write one question per step, aimed at the person who feels it. "When approvals sit, what happens at the supplier end?"
- After the call, keep the ones that drew a long answer and cut the ones the buyer brushed off.
The worked example above is this chain asked live.
When SPIN fits, and when it is too much
SPIN was built from research on major sales: several stakeholders, a considered decision and a cost of change. It fits discovery in complex B2B deals, where the buyer has to build a case internally and an explicit need gives them the words for it.
It is heavy for a transactional sale with one decision maker who already knows what they want. Asking Implication questions of a buyer comparing two prices feels like stalling. It also struggles when the buyer does not yet see a problem at all; Problem questions need something to find.
Using SPIN alongside another method
Many teams run SPIN as the questioning skill inside a broader method. With MEDDPICC, SPIN's explicit need feeds the identified pain field, and the Advance at the end of the call is often the route to the economic buyer. With Gap Selling, Problem and Implication questions map onto the buyer's current state, and Need-payoff onto the future state; the gap between them is what the buyer has just described. Whichever method is the team's standard, keep its field names in the CRM and use SPIN for how the questions are asked.
Where it goes wrong
Too many Situation questions. They feel safe to the seller and bore the buyer. Huthwaite warns buyers can feel interrogated. Do the research first.
Jumping from Problem to pitch. The buyer mentions a problem and the rep demos the fix. The need is still implied and the buyer objects to the price.
Implication questions that sound like a script. "What is the impact of that?" asked five times is an interrogation. Follow each answer to the team or the number it points at.
Leading Need-payoff questions. "Wouldn't it be great if...?" puts words in the buyer's mouth. The need only counts if the buyer says it.
Ending on a Continuation. "Send me some information" commits the buyer to nothing. Propose something the buyer does.
Running SPIN discovery for every rep
The debrief after a SPIN call is a short conversation, and it runs as a call. Ask two questions: what explicit need did the buyer state, in their words, and what did the buyer commit to do? Write the standard for each down before anyone marks a call. In our research on AI call scoring with PeerLab's blind human marking, trained experts disagreed with each other on 18% of scores.
A manager cannot debrief every discovery call. Our AI sales experts work on 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 talks the call through with Caty by voice and leaves with the next Implication question to ask and the Advance to propose; typing is the fallback when they cannot talk. Managers see the pattern across the team through Bryce; the one to look for is reps leaving discovery with implied needs and no explicit one. To hear the debrief run on one of your own calls, talk to us.
FAQ
What are the four SPIN selling questions?
The four SPIN question types are Situation, Problem, Implication and Need-payoff. Situation questions gather context, Problem questions uncover difficulties, Implication questions explore the consequences of those problems, and Need-payoff questions have the buyer state the value of solving them. Neil Rackham developed them from research on more than 35,000 sales calls.
Do you have to ask SPIN questions in order?
No, you do not have to ask SPIN questions in a fixed order. Huthwaite describes SPIN as a logical persuasive framework. In practice most calls start with some Situation questions and build through Problem and Implication questions to Need-payoff, but a rep may loop back when a new problem comes up.
What is the difference between an implied need and an explicit need?
An implied need is a problem or dissatisfaction the buyer describes, such as slow approvals. An explicit need is a want the buyer states, such as approvals under 48 hours. Huthwaite's research found implied needs had no relationship with success in major sales, while explicit needs were a key indicator of success.
How many Situation questions should you ask?
Ask as few as you can. Huthwaite's research found successful sellers asked fewer Situation questions, and more focused ones. Research the account beforehand and use Situation questions to confirm what you found, so the call time goes to Problem and Implication questions.
What is an Advance in SPIN selling?
An Advance is a commitment from the buyer to take an action that moves the sale forward, such as introducing a decision maker or sharing internal data. A Continuation is a next step where the buyer commits to nothing. Huthwaite counts Advances as successful calls and Continuations as unsuccessful ones.
How long should a SPIN discovery call take?
A SPIN discovery call usually takes 30 to 60 minutes. Keep Situation questions to a few minutes, spend most of the call on Problem and Implication questions, and leave ten minutes for Need-payoff questions, a short demonstration against the stated need and the commitment.