SPIN questions are the four kinds of discovery question Neil Rackham described in SPIN Selling: Situation, Problem, Implication and Need-payoff. You ask them roughly in that order. The buyer moves from facts to pain, then to what the pain costs, and finally says in their own words what a fix is worth. Below are B2B examples of each type, a worked Implication chain and a one-page call plan.
Most guides picture a seller meeting a total stranger. A meeting booked through cold email or LinkedIn, the way B2B lead generation works, usually looks different. Before you say hello, the buyer has read your profile and clicked around your site. People rarely buy straight from an email. They check you out first, and only then reply. So the call needs less fact-finding and more time on cost.
What are SPIN questions, in one minute?
SPIN questions come from Rackham's book SPIN Selling, first published in 1988, according to Huthwaite's guide. Each type has one job on a B2B discovery call:
- Situation questions collect the facts you still need about how the buyer works today.
- Problem questions find what the buyer is unhappy with.
- Implication questions follow that problem out to its real cost in money and staff time.
- Need-payoff questions let the buyer say, in their own words, what a fix would be worth.
| Type | Its job | A B2B example | A common mistake |
|---|---|---|---|
| Situation | Fill gaps in facts you could not find yourself | "Who signs off a proposal before it goes out?" | Asking what the website already says |
| Problem | Surface dissatisfaction | "Where does a proposal usually get stuck?" | Naming your product inside the question |
| Implication | Carry the problem to a cost | "When a bid goes out late, what happens to it?" | Stopping after the first answer |
| Need-payoff | Let the buyer state the value | "If a bid could leave in a week, what would that change?" | Describing your product instead of their outcome |
The order is a guide. Treat the four types as a way of thinking through a call. Read them top to bottom like a script and the call sounds like a form. If the buyer raises a problem in minute two, follow it and come back for facts later.
How to use SPIN well on a booked call
Why do Implication questions matter more than the other three types?
Implication questions show the widest gap between strong and average sellers. Salesforce's guide to SPIN reports that Rackham's study of 35,000 sales calls found top performers asked four times as many Implication questions as average performers. Salesforce is summarizing the research here, so treat the ratio as a direction. Huthwaite International, the firm behind Rackham's research, says SPIN was formed from over 35,000 sales calls.
Situation and Problem questions are easy to learn, so most sellers already ask plenty. The harder skill is staying with one problem long enough to trace what it knocks over next.
Can you skip Situation questions on a booked call?
Keep them few and specific. The Sales Blog notes that Situation questions do little for the prospect, yet a sales conversation still needs them. One simple habit helps. When you already hold a fact, state it and ask the buyer to correct you. That takes seconds and shows you prepared. Save open Situation questions for things only an insider knows, such as budget timing or internal politics.
How do you rehearse the questions before a real call?
Rehearse out loud with a colleague playing the buyer. Give the colleague a short brief with a hidden problem and a hidden cost. Then see whether your questions uncover both without naming your product. For the closing stretch, practice one open question in your own words, such as "If that were fixed, what would change first?", built on the fix your buyer just described.
How do you review a discovery call to improve your questions?
Play back the recording and tag every question you asked by type. Mark where you talked more than the buyer and where a promising answer got no follow-up. Then pick one habit to fix on the next call. Trying to fix five at once usually fixes none.
How do you run SPIN when several people from the buyer join?
Direct each question to the person closest to the answer. Operations staff usually know the process and its friction, while finance leads or partners know what it costs. If two attendees disagree about the problem, say so openly and ask each to describe their view.
That disagreement often tells you who will block or back the deal. Before the call, look back at your own won projects and note who actually signed them. That title is usually the person whose answers carry the most weight in the room.
What is worth asking in the Situation and Problem stages?
Before the call, cross off everything that two minutes on LinkedIn or the company website would answer: headcount, office locations, services, years in business, the logos on their client page, the buyer's own role. Asking those tells the buyer you did not prepare, and it spends minutes you need later. Your buyer looked you up before replying. Return the favor before the call.
Keep the Situation questions that nothing public can answer:
- "Who else has to agree before you change how you do this?"
- "How do you handle this today, step by step?"
- "What have you already tried, and what happened?"
- "What made you reply this month, and not last year?"
A good Problem question describes the buyer's world and leaves your product out of it. If a question only makes sense once they know what you sell, save it for later. A few examples by type of firm:
- Civil engineering consultancy: "Where does a proposal usually stall between the tender arriving and it going out?" and "Which tenders do you end up turning down, and why?"
- Marketing agency: "Which clients take the most account time compared with what they pay?" and "How much of your new work comes from things you actually control?"
- Software development company: "Where do projects most often run over the estimate?" and "How long does a new developer take to become billable?"
- IT consultancy: "Which part of a client renewal causes the most back and forth?" and "Where do your senior consultants spend time a junior could cover?"
How does an Implication chain work, question by question?
An Implication question takes one problem and asks what it touches next. A chain is five or so in a row, each built on a word or number from the last answer, until the buyer states a yearly cost.
Below is one worked chain. The firm, the seller and every number are invented to show the mechanics. It is an illustration, and no client sits behind it.
The seller offers proposal writing support to engineering firms. The buyer runs a 25-person civil engineering consultancy. Earlier in the call, a Problem question produced this answer:
"Our proposals take about 9 working days. Most clients give us 5."
Question 1: "What happens to the tenders you can't turn around in time?" Buyer: "We decline them. Around 12 last year." The question picks up "in time" from the answer. Now the buyer has a count.
Question 2: "Of the bids you do send, how many do you win?" Buyer: "About 1 in 4." There is now a rate to apply to the count, and the buyer supplied both.
Question 3: "Applied to those 12, what does that come to, roughly?" Buyer: "Maybe 3 jobs. A typical one is about $60,000, so that is a lot of work we never bid for." The seller did not do the sum. The buyer did, so the number belongs to them.
Question 4: "Who writes the proposals now?" Buyer: "Two of our senior engineers. In busy months it eats about a third of their week." The chain turns from lost revenue to people, which is often where the second cost hides.
Question 5: "What does that do to your hiring plans?" Buyer: "We're about to hire a third engineer, around $90,000 a year, mostly to take load off those two." The buyer has now named a second cost, in a number of their own.
Summary question: "So across the lost bids and the hire, what is this costing the firm a year?" Buyer: "Somewhere around $270,000, counting the lost jobs and the salary together. I've never added those two before."
A chain like this works when:
- Each question reuses something from the previous answer, so the buyer feels heard instead of processed.
- The buyer does every sum. A total you announce is your claim; a total they say out loud is their problem.
- You stop once they put the costs together themselves. Pushing past that point reads as pressure.
The same move works for other firms. A few Implication questions to start chains from the Problem answers in the previous section:
- "When a project runs over the estimate, who absorbs the extra hours?"
- "If those clients take that much account time, what work gets pushed aside?"
- "When a renewal drags on, what happens to the consultants waiting for the next project?"
- "If a new developer takes that long to bill, how many can you afford to hire this year?"
How do Need-payoff questions turn a cost into a reason to act?
A Need-payoff question asks the buyer to describe the fix and what it would earn them. The seller holds back on describing the product. The buyer states the benefit, and that sentence is what they will repeat to the partner or board they report to.
Leading questions push the answer into the buyer's mouth. Open ones let them build it:
| Leading wording (avoid) | Open wording (use) |
|---|---|
| "Wouldn't faster proposals save you money?" | "If proposals went out in 5 days, which of last year's tenders would you have bid?" |
| "Our service would free up your engineers, right?" | "If your two engineers got that time back, where would it go?" |
| "So you'd want to fix this quickly?" | "If you didn't need the third hire, what would you do with that budget?" |
| "Would you like to see how we do it?" | "Who besides you would care most if this changed?" |
The last question in that table does a second job: it names the next person to meet. Use the end of this stretch to agree one next step, such as a second meeting with the partner who signs off bids, dated before the call ends.
When discovery is done and you move to asking for the decision, the closing questions for each stage of a B2B call take over, including what to ask when a prospect says they need to think about it.
When is SPIN the wrong tool?
SPIN fits some meetings far better than others. Match the depth to the deal:
| Deal | Cycle | What the buyer knows | How the meeting came | What to do |
|---|---|---|---|---|
| Large, several people sign | Months | The problem, rarely its cost | Booked through outbound | Short Situation, full Implication chain |
| Large, procurement involved | Months, formal tender | Has written the requirement | Buyer invited you, spec in hand | Skip most discovery; bring a view on their spec |
| Small, one decision-maker | Days to weeks | Knows what they want | Inbound or outbound | Short SPIN: one Problem, one Need-payoff |
| Existing client, any size | Varies | Knows you well | Renewal or expansion | Skip Situation; ask what changed since last time |
| Founder to founder | Weeks | The problem and your name | Referral | Short Situation, one chain, then the next step |
The second row is the honest limit. A Harvard Business Review article from July 2012, "The End of Solution Sales," argued that solution selling worked because customers understood their problems but did not know how to solve them. It added that procurement teams with plenty of data now let companies define the solution themselves.
When the buyer has already written the spec, a chain of questions adds little. They want your view on it, as in consultative selling, where you show what the spec missed.
SPIN also cannot rescue a weak call process on its own. I tell founders that if they close too few of their calls today, more calls will drag the rate lower still. Whoever takes those calls needs to know where calls usually go wrong and how this type of buyer makes decisions. Good questions are one slice of that. Buying more calls to cover a weak close rate is a recipe for disaster. Fix the calls first.
Founders see the 2 or 3 contracts signed. I see the prospects lost on the calls in between.
My team books the meeting and the client's people run the call. For an SEO agency in Singapore we booked 78 sales meetings in the first 30 days. Booking and closing are two different jobs, and a booking only pays off if the call that follows goes well.
Can SPIN be used in a cold email or LinkedIn message?
Yes, as one line. A cold message has a single job: earning a short meeting. In the first message I sell the meeting and leave the service for later. Trying to close the whole sale in one message is buying a lottery ticket.
A workable rule: borrow one Problem or Implication line, write it as an observation about the buyer's world, and end with one small ask. Questions about their process belong on the call, where you can hear the answer and follow it.
An illustration, written for a UK engineering consultancy. First, the version that turns SPIN into an interrogation:
Subject: A few questions
Hi Sarah, how long do your proposals take? Who writes them? How many tenders did you turn down last year? What did that cost? Would a faster process help? Can we book a demo?
Five questions, each asking a stranger to do work, plus a demo request for a product she has never heard of. Now the same idea as one Implication line and one ask:
Subject: the tenders you had to turn down
Hi Sarah, when a consultancy your size needs longer to write a proposal than the client allows, the cost rarely appears in any report. It sits in the tenders nobody had time to answer. If that happens at your firm too, would a 15-minute video call next week be useful? I'd bring a one-page breakdown of where proposal days usually go, and you can keep it either way.
If you have a real result from a similar firm, add one line of it before the ask.
Follow-ups repeat the same small ask, each carrying one new thing, such as a piece of proof or a fresh angle on the cost. Keep new questions for the call itself. In our campaigns, the third follow-up usually wins. Space the touches out. Each one needs its own reason to reply.
Who sends the touches matters as much as the wording. If the buyer clicks the sender's name and finds only a title and a photo, even a sharp Implication line gets ignored. The booking side, sender profiles included, is the work behind our appointment setting.
What should a one-page SPIN call plan look like?
Fill this in a few minutes before the call, from the reply thread and any notes from whoever booked the meeting. Any field you cannot fill becomes your first Situation question.
| Field | What goes in it |
|---|---|
| Buyer and role | Name, title, and what that title usually decides |
| Handoff facts | The reply, the problem line they reacted to, anything they asked |
| Two Situation gaps | Only facts you could not find online |
| Problem hypotheses (2 to 3) | Written in their language, with no product named |
| Implication chain draft | The opening question for each hypothesis, and whether it should lead to lost revenue or staff time |
| Need-payoff prompt | One open question that lets them state the benefit |
| Agreed next step | Who joins and on which date, filled in during the call |
After the call, write the buyer's cost figure in their exact words and save the sheet in your CRM next to the deal. Whoever runs the second meeting starts from that sentence.
Try it on your next booked call. Fill the sheet using only the reply thread and the buyer's LinkedIn profile, then count how many of your usual Situation questions you no longer need to ask.
Want to try SPIN on your next booked call? Book a call and tell me what the buyer wrote in the reply. We can draft your first Implication chain together.
FAQ
How many SPIN questions should you ask in one call?
Count finished chains. A chain is finished when the buyer states a cost in their own words. If two-thirds of the slot has gone and no cost has come out, stop opening new problems. Spend what is left agreeing a dated next step, so the meeting still ends with a decision about what happens next.
Should an SDR use SPIN on a qualification call?
Lightly. An SDR (the junior rep who qualifies meetings before a senior seller takes them) only has to confirm there is a reason to meet and that the right person will attend. One Problem question usually covers it. Leave the Implication chain to whoever runs the full meeting, so the buyer does not tell the cost story twice and the senior seller hears the numbers first-hand.
How does SPIN compare with BANT and MEDDIC?
BANT and MEDDIC (metrics, economic buyer, decision criteria, decision process, identify pain, champion) are checklists for judging whether a deal is real; SPIN is the way of talking that gets those answers out. A finished Implication chain gives MEDDIC its metrics and pain in the buyer's own numbers. On meetings that came from cold outreach, some of budget, authority, need and timeline can be proven by the reply itself before the call.
What if the buyer won't put a number on the cost?
Ask for a unit they already track, such as hours per week or bids declined. People who will not guess money will often count things, and you can price the count together later. If they cannot name any unit at all, treat the problem as low priority for them and move to another before it eats the whole meeting.
SPIN or Challenger, which should a small B2B team learn first?
Pick by how your buyers arrive. If replies show people who know the problem but have never priced it, build SPIN's Implication skill first. If buyers turn up with a written spec, questions add little and you need a clear view of your own. Either way, the cost figures you collect on SPIN calls become the evidence behind that view later.