All qualification frameworks

    Questioning method

    SPIN Selling explained

    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

    What is SPIN Selling? A method of running sales conversations with four types of question: Situation questions gather facts, Problem questions uncover difficulties, Implication questions explore their consequences, and Need-payoff questions get the buyer to state the value of solving them. Neil Rackham developed it from research at Huthwaite and published it in the book SPIN Selling in 1988.

    What SPIN Selling is

    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.

    Where SPIN came from: Rackham's research

    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.

    • Implied needs are not enough. In large sales, a buyer's vague dissatisfaction (an implied need) was a weak predictor of success. Successful sellers developed implied needs into explicit needs: clear statements of a want or a requirement.
    • Implication and need-payoff questions matter most in larger sales. Successful sellers in large sales asked more of them. Situation questions, the type most sellers overuse, did little for success and could bore buyers.
    • Closing techniques can backfire in large sales. Rackham reported that pressure closes, which may work in small sales, were linked with lower success in large ones.
    • Calls end in an advance or a continuation. An advance is a step forward the buyer commits to, such as a meeting with their finance lead. A continuation, such as 'send me some information', keeps the sale alive without moving it. Successful sellers planned for advances.
    • Calls have four stages. Preliminaries, Investigating, Demonstrating capability and Obtaining commitment. The research found Investigating, where SPIN questions sit, had the strongest influence on call success.

    When to use SPIN, and when not to

    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.

    Do not use it when

    • You need a pass or fail qualification decision. SPIN does not tell you who signs or when.
    • The sale is small and quick. Rackham's research itself found the method matters most in large sales.
    • You would run all four types in full on a cold call. An SDR has time for one problem and one implication question.
    • The buyer already knows exactly what they want and is comparing quotes.

    The four SPIN question types, with B2B examples

    Twelve example questions for each type, written for B2B sales. Adapt the wording to your buyer and your product.

    S: Situation questions

    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.

    Questions to ask (12)

    1. How is your team set up to handle {{process}} today?
    2. Which systems do you use for it?
    3. How many people are involved?
    4. How long have you worked this way?
    5. Who owns the process?
    6. How does work get from {{team A}} to {{team B}}?
    7. How has the volume changed over the last year?
    8. Which locations or business units does this cover?
    9. What do you report on, and to whom?
    10. How do you handle peaks, such as end of month or end of financial year?
    11. Which suppliers or partners are involved?
    12. What has changed in the business since you set this up?

    A 3 looks like: Three or four well chosen questions that confirmed the facts needed, with the rest researched beforehand.

    P: Problem questions

    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.

    Questions to ask (12)

    1. What is the hardest part of {{process}} at the moment?
    2. Where does it break down?
    3. How satisfied are you with how {{system}} handles that?
    4. What takes longer than it should?
    5. Where do errors creep in?
    6. What do your team complain about most?
    7. Is it harder now than it was a year ago?
    8. What workarounds have people built?
    9. Where do you rely on one person who knows how it works?
    10. What do customers or other teams say about it?
    11. What does your manager ask you about it?
    12. If you could fix one thing about it, what would it be?

    A 3 looks like: At least one specific problem confirmed by the buyer with an example.

    I: Implication questions

    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.

    Questions to ask (12)

    1. What does that delay mean for the rest of the team?
    2. How does that affect your customers?
    3. What does it cost when that goes wrong?
    4. How much time does your team spend fixing it each week?
    5. What does that do to your ability to hit {{target}}?
    6. Has it ever caused a compliance or audit issue?
    7. How does it affect staff turnover or morale?
    8. What happens at peak times when volume doubles?
    9. If it keeps growing at this rate, what does next year look like?
    10. Has it held back any other projects?
    11. How does leadership see the impact?
    12. What would happen if the one person who knows the workaround left?

    A 3 looks like: The buyer described at least one consequence with a cost or a number, linked to something senior people care about.

    N: Need-payoff questions

    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.

    Questions to ask (12)

    1. If that took half the time, what would your team do with the hours?
    2. How would it help if errors were caught before they reached customers?
    3. What would it mean for {{target}} if this were solved?
    4. Why is fixing it important to you?
    5. Who else would benefit if it worked properly?
    6. How would it help you at the next board or leadership meeting?
    7. What would it be worth to have that visibility every week?
    8. Would it be useful to handle peaks without extra staff?
    9. How would your customers notice the difference?
    10. If you could show leadership the savings, what would that do for the project?
    11. What would you be able to start that you have had to delay?
    12. What would success look like six months after a change?

    A 3 looks like: The buyer stated the value of solving the problem in their own words, ideally with a number.

    Red flags

    Signals that a deal is weaker than the notes suggest, and what to do about each.

    Most of the call was situation questions

    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.

    The seller pitched as soon as a problem came up

    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.

    The benefits came from the seller, not the buyer

    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.

    The call ended with 'send me some information'

    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.

    Implication questions felt like an interrogation

    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.

    SPIN qualification scorecard

    Score each element from 0 to 3 after the call. The total and verdict update as you go.

    S: Situation questions

    A 3 looks like: Three or four well chosen questions that confirmed the facts needed, with the rest researched beforehand.

    P: Problem questions

    A 3 looks like: At least one specific problem confirmed by the buyer with an example.

    I: Implication questions

    A 3 looks like: The buyer described at least one consequence with a cost or a number, linked to something senior people care about.

    N: Need-payoff questions

    A 3 looks like: The buyer stated the value of solving the problem in their own words, ideally with a number.

    Printable SPIN scorecard

    Print this page or copy the table into your CRM notes. Score each element from 0 to 3 in the last column.

    SPIN scorecard
    ElementWhat a 3 looks likeScore (0 to 3)
    S: Situation questionsThree or four well chosen questions that confirmed the facts needed, with the rest researched beforehand. 
    P: Problem questionsAt least one specific problem confirmed by the buyer with an example. 
    I: Implication questionsThe buyer described at least one consequence with a cost or a number, linked to something senior people care about. 
    N: Need-payoff questionsThe buyer stated the value of solving the problem in their own words, ideally with a number. 
    TotalMaximum 12 
    What each score means
    ScoreMeaning
    0 UnknownNot discussed, or the buyer would not answer.
    1 AssumedMentioned vaguely, or it is your guess rather than the buyer's words.
    2 ConfirmedThe buyer said it clearly, with gaps or from one source only.
    3 EvidencedConfirmed in the buyer's words with specifics, and backed by a second person, a document or a date.
    How the total becomes a verdict
    Share of maximumVerdictWhat to do
    75% or moreQualifiedAdvance it. A critical element scored 0 caps this at Developing.
    50% to 74%DevelopingBook the next step with a plan to close every gap below 2.
    25% to 49%EarlyGo back for the missing answers or move it to nurture.
    Under 25%UnqualifiedDisqualify 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.

    Filled SPIN example: an SDR call handed to the account executive

    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.

    SPIN scores for the example
    ElementScoreEvidence from the call
    S: Situation questions2 of 3Three people process about 1,500 supplier invoices a month by hand from a shared inbox into the accounting system.
    P: Problem questions2 of 3Invoices get missed in the inbox; suppliers chase late payments. Finance manager called it 'the bit of the job I dread'.
    I: Implication questions1 of 3Mentioned a key supplier put them on stop for a week last quarter. Cost not quantified.
    N: Need-payoff questions1 of 3Said it 'would be nice to close the month without the scramble'. No value stated.
    Total6 of 12Developing. A clear problem. The account executive should quantify the supplier stop and the month-end effort.

    The handover note the SDR sent

    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.

    How SDRs and account executives use SPIN

    SDRs use a slice of SPIN to earn the meeting. Account executives use all four types to build the case for change.

    SDR on the first call

    • Skip most situation questions. Research the company before you dial.
    • Ask one problem question tied to a challenge common in their role.
    • Ask one implication question to make the problem worth a meeting.
    • Write the buyer's words down for the account executive.
    • Ask for an advance, a meeting with a named person and a time, not 'can I send something'.

    Account executive from discovery

    • Plan the call with the SPIN call plan, including the advance you want.
    • Pick up from the SDR's implication notes rather than starting again.
    • Develop implied needs into explicit needs before presenting anything.
    • Use need-payoff answers as the language for the proposal and for the champion to repeat.
    • Record what you learn against MEDDPICC for larger deals.

    Templates

    Copy, print or adapt. Highlighted placeholders are the parts to replace.

    All qualification templates

    SPIN discovery call plan

    A 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}}

    When to use it

    Before any discovery call in a larger or longer sale, especially when the buyer has not yet admitted a problem.

    Why it works

    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.

    Variations

    • For an SDR call, keep one problem question, one implication question and the advance. Skip the rest.
    • For a follow-up call, open with a summary of the implications they gave last time and check they still hold.

    Common mistakes

    • Spending ten minutes on situation questions you could have answered from LinkedIn and their website.
    • Jumping from problem straight to your product before exploring implications.
    • Ending the call with 'I will send some information' instead of an advance.

    SDR to account executive handover note

    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}}

    When to use it

    Every time a meeting is booked, within a few hours of the call, in the CRM and in the calendar invite.

    Why it works

    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.

    Variations

    • For a CHAMP qualified meeting, replace the 'What they told us' block with the four CHAMP headings.
    • For an outsourced SDR team, add the campaign name and the list source so the client can trace the meeting.
    • For a short version in the calendar invite, keep only 'Why they agreed to meet' and 'What the prospect expects'.

    Common mistakes

    • Paraphrasing the prospect's reason into sales language. Keep their words.
    • Promising a demo when the prospect agreed to a conversation. The AE then opens with the wrong agenda.
    • Leaving out the watch outs. A competitor mention or a bad past experience changes how the AE opens.

    Making SPIN sound natural

    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.

    SPIN compared with other frameworks

    MEDDIC vs BANT vs SPIN vs CHAMP vs GPCT, plus the Sandler and Challenger methods.

    Which framework should my team use?
    Sales qualification frameworks compared
    FrameworkStands forOriginBest forWho runs itStageMain weakness
    MEDDIC / MEDDPICCMetrics, Economic buyer, Decision criteria, Decision process, (Paper process), Identify pain, Champion, (Competition)PTC, mid 1990s, Dick Dunkel and Jack NapoliComplex B2B deals with a buying committee and a long cycleAccount executive, with SDR clues from the first callDiscovery to close, and pipeline reviewsToo heavy for a cold call or a small, quick sale
    BANTBudget, Authority, Need, TimelineIBM, usually dated to the 1950s or 1960sFast first-pass qualification of inbound leads and simple salesSDR or inside salesFirst callAsks for budget before value is shown; misses buying groups
    SPIN SellingSituation, Problem, Implication, Need-payoffNeil Rackham and Huthwaite, book published 1988Discovery in larger sales where the buyer must build their own caseAccount executive; SDRs use the problem and implication questionsDiscoveryA questioning method, not a checklist; says little about sign-off
    CHAMPChallenges, Authority, Money, PrioritisationA later rework of BANT; attribution variesOutbound first calls where budget is not set yetSDRFirst callLight on the decision process and competition
    GPCTBA/C&IGoals, Plans, Challenges, Timeline, Budget, Authority, Negative consequences, Positive implicationsDeveloped by HubSpot for its own sales teamConsultative mid-market sales led by the buyer's goalsAccount executive or senior SDRDiscoveryEight elements is a lot for one call; easy to run as a script
    Sandler Selling SystemBonding and rapport, Up-front contract, Pain, Budget, Decision, Fulfilment, Post-sellDavid Sandler, founded Sandler in 1967Teams losing deals to stalls, free consulting and think-it-oversWhole team; SDRs use the up-front contract and pain funnelEvery callNeeds training and practice; can feel blunt if done badly
    The Challenger SaleTeach, Tailor, Take controlMatthew Dixon and Brent Adamson, CEB, book published 2011Buyers who are happy with the status quo and complex salesAccount executive, with insight-led openers for SDRsOpener to closeNeeds a real insight; without one it reads as arrogance

    Frequently asked questions

    What does SPIN stand for?

    Situation, Problem, Implication and Need-payoff, the four types of question in Neil Rackham's method.

    Who created SPIN Selling?

    Neil Rackham, through research at his firm Huthwaite. The book SPIN Selling was published by McGraw-Hill in 1988.

    How many sales calls was SPIN based on?

    Around 35,000 sales calls studied over 12 years in more than 20 countries.

    Is SPIN Selling still relevant?

    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.

    What is the difference between an implied and an explicit need?

    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.

    Can SDRs use SPIN on cold calls?

    A short version, yes: one problem question and one implication question, then the ask. The full sequence belongs in discovery with the account executive.

    Is SPIN a qualification framework?

    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.

    How many SPIN questions should I ask in a call?

    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.

    Want qualified meetings handed over properly?

    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.