Use it when
- You run discovery on larger, longer B2B sales.
- Buyers have not yet admitted a problem is worth solving.
- Your sellers jump to the pitch as soon as a problem is mentioned.
- You want a questioning structure under MEDDPICC or GPCTBA/C&I.
Questioning method
SPIN Selling is a questioning method for B2B discovery built on four question types: Situation, Problem, Implication and Need-payoff. It comes from Neil Rackham's research into 35,000 sales calls, published in 1988, and this guide gives you at least twelve B2B example questions for each type.
Quick answer
SPIN is a sequence of question types that moves a buyer from describing their situation to stating, in their own words, why solving a problem is worth it. Situation questions establish the facts. Problem questions find what is not working. Implication questions explore what those problems cause: cost, risk, lost time, missed targets. Need-payoff questions ask the buyer what solving the problem would be worth.
It is not a qualification checklist in the way BANT or MEDDIC are. SPIN tells you how to run discovery, not what you must know before you forecast. That is why many teams pair them: SPIN to ask the questions, MEDDPICC to record what the answers mean for the deal.
SPIN comes from research led by Neil Rackham and his firm Huthwaite, which he founded in the 1970s. Over 12 years, a team of researchers studied around 35,000 sales calls in more than 20 countries. The findings were published in the book SPIN Selling by McGraw-Hill in 1988.
The research set out to find what successful sellers did differently in large, complex sales, as opposed to small, quick ones. Its best known conclusions run against a lot of traditional sales training.
Twelve example questions for each type, written for B2B sales. Adapt the wording to your buyer and your product.
Questions that establish facts about the buyer's current situation. Necessary, but keep them few. Research what you can beforehand, from their website, LinkedIn and annual reports, and ask only what you could not find.
Listen for: Facts that point to a likely problem: manual processes, recent growth, a new system, a team that has changed size.
A 3 looks like: Three or four well chosen questions that confirmed the facts needed, with the rest researched beforehand.
Questions that explore difficulties, dissatisfactions and frustrations with the current situation. They uncover implied needs. Experienced sellers ask more of them than beginners, but in large sales they are a starting point, not an end.
Listen for: Complaints, workarounds, the word 'still', and moments where the buyer hesitates before answering.
A 3 looks like: At least one specific problem confirmed by the buyer with an example.
Questions that take a problem and explore its effects and consequences, making it larger and more urgent in the buyer's mind. They are the hardest to ask well and, in Rackham's research, among the most closely linked to success in large sales.
Listen for: Effects on money, time, risk, people and customers, and problems that connect to things the economic buyer cares about.
A 3 looks like: The buyer described at least one consequence with a cost or a number, linked to something senior people care about.
Questions that ask about the value or usefulness of solving the problem, so the buyer states the benefits instead of you. They turn implied needs into explicit needs and give your champion the words to sell internally.
Listen for: The buyer describing benefits in their own words, and benefits to other people in the business, which a champion can repeat.
A 3 looks like: The buyer stated the value of solving the problem in their own words, ideally with a number.
Signals that a deal is weaker than the notes suggest, and what to do about each.
The buyer spent their time educating you on facts you could have researched.
What to do: Research beforehand and cap situation questions at three or four per call.
Offering a solution to an implied need invites objections. The buyer has not yet agreed the problem is worth solving.
What to do: Ask at least two implication questions before talking about what you do.
Benefits stated by the seller are claims. Benefits stated by the buyer are reasons.
What to do: Use need-payoff questions and let the buyer describe the value.
That is a continuation, not an advance. The sale has not moved.
What to do: Plan the advance before the call and ask for it specifically, with a fallback.
Asked in a run without listening, they make buyers defensive.
What to do: Ask one, listen, summarise, then ask the next. Link each to something they said.
Score each element from 0 to 3 after the call. The total and verdict update as you go.
Print this page or copy the table into your CRM notes. Score each element from 0 to 3 in the last column.
| Element | What a 3 looks like | Score (0 to 3) |
|---|---|---|
| S: Situation questions | Three or four well chosen questions that confirmed the facts needed, with the rest researched beforehand. | |
| P: Problem questions | At least one specific problem confirmed by the buyer with an example. | |
| I: Implication questions | The buyer described at least one consequence with a cost or a number, linked to something senior people care about. | |
| N: Need-payoff questions | The buyer stated the value of solving the problem in their own words, ideally with a number. | |
| Total | Maximum 12 |
| Score | Meaning |
|---|---|
| 0 Unknown | Not discussed, or the buyer would not answer. |
| 1 Assumed | Mentioned vaguely, or it is your guess rather than the buyer's words. |
| 2 Confirmed | The buyer said it clearly, with gaps or from one source only. |
| 3 Evidenced | Confirmed in the buyer's words with specifics, and backed by a second person, a document or a date. |
| Share of maximum | Verdict | What to do |
|---|---|---|
| 75% or more | Qualified | Advance it. A critical element scored 0 caps this at Developing. |
| 50% to 74% | Developing | Book the next step with a plan to close every gap below 2. |
| 25% to 49% | Early | Go back for the missing answers or move it to nurture. |
| Under 25% | Unqualified | Disqualify or recycle, and record why. |
Critical elements for SPIN: P: Problem questions, I: Implication questions. If any of these scores 0, the verdict cannot be higher than Developing.
A fictional example: an outsourced SDR has booked a meeting and is handing it to the client's account executive.
The seller is an accounts payable automation company. Its outsourced SDR called the finance manager at a wholesale distributor in Melbourne with around 200 staff. The SDR asked two situation questions, one problem question and two implication questions before asking for the meeting.
SPIN on a cold call is deliberately short. The account executive uses the scores to see where to pick up.
| Element | Score | Evidence from the call |
|---|---|---|
| S: Situation questions | 2 of 3 | Three people process about 1,500 supplier invoices a month by hand from a shared inbox into the accounting system. |
| P: Problem questions | 2 of 3 | Invoices get missed in the inbox; suppliers chase late payments. Finance manager called it 'the bit of the job I dread'. |
| I: Implication questions | 1 of 3 | Mentioned a key supplier put them on stop for a week last quarter. Cost not quantified. |
| N: Need-payoff questions | 1 of 3 | Said it 'would be nice to close the month without the scramble'. No value stated. |
| Total | 6 of 12 | Developing. A clear problem. The account executive should quantify the supplier stop and the month-end effort. |
MEETING HANDOVER: wholesale distributor, Melbourne, about 200 staff Meeting: Monday 11am, 30 minutes, video Attending: Finance Manager. Reports to the chief financial officer. Why they agreed to meet (their words) "If you can stop me chasing invoices through an inbox, I am interested." SPIN notes Situation (2): three people key about 1,500 supplier invoices a month from a shared inbox. Problem (2): invoices get missed, suppliers chase late payments. Implication (1): a key supplier put them on stop for a week last quarter. Ask what that cost. Need-payoff (1): "would be nice to close the month without the scramble". Get the value in numbers. Score: 6 of 12 (Developing). What they expect: how other distributors their size handle supplier invoices. Watch outs: chief financial officer approved the current accounting system recently. Do not suggest replacing it.
SDRs use a slice of SPIN to earn the meeting. Account executives use all four types to build the case for change.
Copy, print or adapt. Highlighted placeholders are the parts to replace.
All qualification templatesA plan for a discovery call written before you dial, not a script.
SPIN CALL PLAN: {{prospect company}}, {{contact and title}} Call: {{date}}
Objective for this call: {{the advance you want, for example a meeting with the finance lead}}
Situation (keep to the few facts you could not research)
1. {{question}}
2. {{question}}
Problems you suspect, and how you will ask about them
Suspected problem: {{problem}} Question: {{problem question}}
Suspected problem: {{problem}} Question: {{problem question}}
Implications to explore if the problem is confirmed
{{problem}} could affect {{cost, time, risk, revenue, people}}.
Questions: {{implication question}} / {{implication question}}
Need-payoff questions to let them state the value
{{need-payoff question}}
{{need-payoff question}}
Advance to ask for at the end: {{specific next step with a date}}
Fallback advance: {{smaller next step}}Before any discovery call in a larger or longer sale, especially when the buyer has not yet admitted a problem.
Rackham's research found that successful sellers in large sales asked more implication and need-payoff questions. Planning them in advance is how you make sure you actually ask them.
The note an SDR sends with every booked meeting so the AE never starts cold.
MEETING HANDOVER: {{prospect company}}
Meeting: {{date and time}}, {{length}} minutes, {{video or phone}}
Booked by: {{SDR name}} Account executive: {{AE name}}
Who is attending
{{name}}, {{title}}. Reports to {{manager, if known}}.
Others invited or mentioned: {{names and titles}}
Why they agreed to meet (their words)
"{{the reason they gave, as close to verbatim as possible}}"
What they told us
Current situation: {{tools, team, process}}
Problem or goal: {{what is not working or what they want to achieve}}
Impact they mentioned: {{cost, time, risk, revenue}}
Timing: {{deadline, contract end, project start, budget cycle}}
Decision: {{who else is involved, how they buy}}
Budget: {{anything said, or "not discussed"}}
Qualification score: {{framework}} {{score}} of {{max}}. Gaps: {{elements scored below 2}}
What the prospect expects from the meeting
{{what the SDR promised: a conversation, a comparison, a specific question answered}}
Watch outs
{{objections raised, competitor mentioned, sensitivity, anything not to say}}Every time a meeting is booked, within a few hours of the call, in the CRM and in the calendar invite.
The first five minutes of a discovery call are often wasted repeating what the SDR already learned. A structured note lets the account executive open with the prospect's own words, which is the fastest way to earn trust.
SPIN questions read well on a page and can sound forced on a call. Three habits help. First, link every question to something the buyer just said: 'You mentioned invoices get missed. What happens when a supplier is not paid on time?' Second, summarise before moving on, so the buyer hears their own problem played back. Third, accept that the order is a guide. Real conversations jump around; what matters is that implications and need-payoff are covered before the call ends.
For more questions organised by call stage and buyer role, see the discovery call questions guide, and for buying signals to listen for, our post on discovery call questions that reveal buying intent.
MEDDIC vs BANT vs SPIN vs CHAMP vs GPCT, plus the Sandler and Challenger methods.
Which framework should my team use?| Framework | Stands for | Origin | Best for | Who runs it | Stage | Main weakness |
|---|---|---|---|---|---|---|
| MEDDIC / MEDDPICC | Metrics, Economic buyer, Decision criteria, Decision process, (Paper process), Identify pain, Champion, (Competition) | PTC, mid 1990s, Dick Dunkel and Jack Napoli | Complex B2B deals with a buying committee and a long cycle | Account executive, with SDR clues from the first call | Discovery to close, and pipeline reviews | Too heavy for a cold call or a small, quick sale |
| BANT | Budget, Authority, Need, Timeline | IBM, usually dated to the 1950s or 1960s | Fast first-pass qualification of inbound leads and simple sales | SDR or inside sales | First call | Asks for budget before value is shown; misses buying groups |
| SPIN Selling | Situation, Problem, Implication, Need-payoff | Neil Rackham and Huthwaite, book published 1988 | Discovery in larger sales where the buyer must build their own case | Account executive; SDRs use the problem and implication questions | Discovery | A questioning method, not a checklist; says little about sign-off |
| CHAMP | Challenges, Authority, Money, Prioritisation | A later rework of BANT; attribution varies | Outbound first calls where budget is not set yet | SDR | First call | Light on the decision process and competition |
| GPCTBA/C&I | Goals, Plans, Challenges, Timeline, Budget, Authority, Negative consequences, Positive implications | Developed by HubSpot for its own sales team | Consultative mid-market sales led by the buyer's goals | Account executive or senior SDR | Discovery | Eight elements is a lot for one call; easy to run as a script |
| Sandler Selling System | Bonding and rapport, Up-front contract, Pain, Budget, Decision, Fulfilment, Post-sell | David Sandler, founded Sandler in 1967 | Teams losing deals to stalls, free consulting and think-it-overs | Whole team; SDRs use the up-front contract and pain funnel | Every call | Needs training and practice; can feel blunt if done badly |
| The Challenger Sale | Teach, Tailor, Take control | Matthew Dixon and Brent Adamson, CEB, book published 2011 | Buyers who are happy with the status quo and complex sales | Account executive, with insight-led openers for SDRs | Opener to close | Needs a real insight; without one it reads as arrogance |
Situation, Problem, Implication and Need-payoff, the four types of question in Neil Rackham's method.
Neil Rackham, through research at his firm Huthwaite. The book SPIN Selling was published by McGraw-Hill in 1988.
Around 35,000 sales calls studied over 12 years in more than 20 countries.
Yes, especially for discovery in larger B2B sales. The core idea, that buyers convince themselves through implication and need-payoff questions better than sellers can convince them, still holds. Pair it with a qualification framework for forecasting.
An implied need is a statement of a problem or dissatisfaction, such as 'our reporting is slow'. An explicit need is a clear want, such as 'we need weekly reports without manual work'. Rackham found explicit needs were far more strongly linked to success in large sales.
A short version, yes: one problem question and one implication question, then the ask. The full sequence belongs in discovery with the account executive.
Not strictly. It is a questioning method. It helps you uncover and develop needs, but it does not tell you who decides, how they buy or when. Use it alongside BANT, CHAMP or MEDDIC.
Few situation questions, and as many problem, implication and need-payoff questions as the conversation supports. A forty-minute discovery call might have three situation questions and a dozen of the rest.
Our SDRs work in-house in Sydney, qualify on the phone and send a handover note with every meeting. Book a 30-minute call and we will map your market and buyers.
Starting at $7,000 a month. Exact fee quoted after a 30-minute call.