A VP of Sales at a Series A company sent me a call recording last month and asked why his new reps kept losing deals they should have won. I listened to the first ten minutes. The rep opened with "So tell me a bit about your setup, how many people are on your team, what tools are you using today?" The buyer answered flatly. Then the rep asked three more questions exactly like that. By minute eight the prospect had that polite, checked-out tone people use when they have already decided the call is a waste of time.
The rep was running SPIN selling. He had been to the training. He had the four question types written on a sticky note next to his monitor. And he was losing because he treated it as a script to recite instead of a way of thinking about the buyer's problem.
That gap, between the framework on paper and the framework in practice, is where most sales teams lose the value of SPIN. So I want to write about what SPIN selling actually is, why it still works forty years after the book came out, and the part almost nobody covers: how to build a system around it so your reps run it the same way every time instead of freelancing.
What SPIN selling actually is
SPIN selling came out of the largest research project ever done on what makes salespeople effective. Neil Rackham and his team at Huthwaite watched more than 35,000 sales calls across twelve years and twenty-plus countries, then looked at what the top performers did differently from average ones.
The finding surprised people at the time. In small, simple sales, closing techniques and pitching benefits worked fine. In large, complex sales, the ones with multiple stakeholders and long cycles, those same techniques hurt win rates. What separated the best reps was not how they closed. It was the questions they asked, and the order they asked them in.
SPIN is the acronym for the four question types they found:
The core idea is that you do not tell the buyer they have a problem or how much it costs them. You ask questions that lead them to say it themselves. People argue with your conclusions. They do not argue with their own.
Why implication questions are the whole game
If you take one thing from Rackham's research, take this: the difference between average reps and top reps was mostly implication questions.
Average reps found a problem and jumped straight to the pitch. "You said onboarding is slow? Great, our product cuts onboarding time in half." Top reps found a problem and then made it bigger before they said a word about their product. "Onboarding is slow, okay. How long does a new customer wait before they see value? And when they wait that long, how many of them churn in the first ninety days? What is that costing you in lost revenue a year?"
By the time a top rep finished, the buyer had done the math on their own problem and arrived at a number. That number, not the demo, is what moves a deal. A buyer who has quantified their own pain at $400K a year will find budget for a $60K solution. A buyer who thinks the problem is a minor annoyance will not, no matter how good your product is.
You are not selling a product. You are helping the buyer price their own problem.
Implication questions turn a vague pain into a dollar figure the buyer says out loud. Once that number is bigger than your price, the deal sells itself. Skip this step and you are just quoting.
Here is the part that connects to modern selling. Buyers now do most of their research before they ever talk to you. Studies of B2B buying put it at 70 to 80 percent of the journey done before a sales conversation. So the buyer often already knows they have a problem. What they do not know is how big it is in their specific, messy situation, and whether it is worth fixing now versus next year. Implication questions are exactly the thing a buyer cannot do alone from a website. That is why SPIN did not die when buyers got informed. It got more useful.
Why most teams run SPIN wrong
The framework is sound. The execution is usually broken, and it breaks in the same three ways every time.
First, reps burn the call on situation questions. This is the mistake from the recording I opened with. Situation questions are the easiest to ask because they require no skill, so nervous or junior reps ask a pile of them. But they are the lowest-value part of the call, and worse, they annoy an informed buyer. If a prospect has already read your site and booked a demo, opening with "so what does your company do?" tells them you did not prepare. The average B2B discovery call has shrunk to about 30 minutes, down from 45 to 60 a decade ago. You cannot spend fifteen of those minutes on questions you could have answered from LinkedIn.
Second, reps treat the four letters as a rigid sequence. SPIN is not a checklist you march through in order. A real conversation loops. You surface a problem, dig into its implications, find a second problem hiding under the first, go back to a situation question to understand it, and so on. Reps who follow S then P then I then N like a flowchart sound like they are reading a form, because they are.
Third, and this is the RevOps failure, none of it gets captured. The rep has a good discovery call, the buyer quantifies their pain at $400K a year, and then that number lives in the rep's head or a scribbled note. It never makes it into the CRM. Three weeks later on the proposal call, nobody remembers the number, the deal reverts to a feature comparison, and it stalls. The best discovery in the world is worthless if the insight evaporates before the next meeting.
How to operationalize SPIN in your revenue engine
This is the piece the other guides skip. They explain the four questions and stop. But whether SPIN works on your team is a systems problem, not a training problem. Training decays in about two weeks. A system holds. Here is how I build one.
Kill situation questions with pre-call enrichment
The fastest win is to remove most situation questions from the call entirely. Everything a rep would ask to understand the account, headcount, tech stack, funding stage, recent hires, current tools, can be pulled before the call. We build this with Clay running waterfall enrichment against each booked meeting, so by the time the rep dials in, they already have the account's shape on one screen. The rep opens with a problem question instead of a fact-finding one, which signals they did their homework and buys instant credibility. This is the same enrichment layer we cover in our waterfall enrichment guide, pointed at discovery prep. If you want the wider setup, that is the AI automation work we do.
Turn implication answers into required CRM fields
This is the change that pays off most. If implication questions are what win deals, then the answers to them are the most important data a rep collects, and they should be structured, not buried in call notes.
Add fields to your deal object that force the rep to capture the output of good discovery: quantified cost of the problem, who feels the pain, what happens if they do nothing, the buyer's stated payoff if they solve it. In HubSpot or Salesforce these become required fields to move a deal past the discovery stage. The rep cannot advance the deal without having actually run implication and need-payoff questions, because the CRM asks for the answers. This is where a real CRM and RevOps build earns its keep: the process is wired into the object, not left to memory.
Feed the captured number into the proposal
Once the buyer's quantified pain lives in a CRM field, it should flow forward automatically. The proposal, the business case, the internal deal review all reference the buyer's own number. When a rep goes into a proposal call and says "you told me this is costing you $400K a year, here is what fixing it looks like," the conversation stays on value instead of collapsing into a price negotiation. We wire this with automation so the discovery insight follows the deal through every stage. This is the connective tissue between good discovery and a strong proposal, and it is the same idea behind multithreading a deal so it does not slip when a champion goes quiet.
Use call recordings to coach the questions, not the pitch
Most sales coaching reviews the pitch and the objection handling. Flip it. Review the discovery. Pull three recorded calls a week and count the ratio of situation questions to implication questions. A rep with ten situation questions and one implication question is the rep losing winnable deals. This is a coachable, measurable habit, and it is far more useful than the vague "be more consultative" feedback most reps get. If you run structured discovery calls already, layer the SPIN question ratio on top as the thing you actually grade.
Where SPIN fits with your other methodologies
People treat sales methodologies like religions, but they solve different problems, and SPIN plays well with the others. SPIN is a discovery and questioning method. It tells you how to run the conversation. It does not tell you how to qualify whether a deal is real or how to map a buying committee.
That is where a qualification framework like MEDDIC comes in. SPIN gets the buyer to quantify their pain. MEDDIC uses that to check whether you have identified the economic buyer, the decision criteria, and a real champion. Run SPIN inside the discovery call, use MEDDIC to decide whether to keep spending time on the deal. And when it is time to make the case, value-based selling picks up the number SPIN surfaced and builds the business case around it. They are layers, not competitors.
Running SPIN as a sticky note instead of a system?
Book a free 30-minute audit and we will show you where your discovery insight is leaking, and the three CRM changes we would make first to hold it.
Book an audit →Frequently asked questions
Is SPIN selling still relevant in 2026?
Yes, and arguably more than before. SPIN came from research on buyer behavior, not seller opinion, so it held up as buyers changed. The one adaptation modern selling requires is cutting situation questions, because informed buyers who did their own research find them annoying. Move that fact-finding to pre-call enrichment and spend the live time on implication and need-payoff questions, which are the parts a buyer cannot do alone from a website.
What is the difference between SPIN selling and MEDDIC?
SPIN is a questioning method for running the discovery conversation. MEDDIC is a qualification framework for deciding whether a deal is worth pursuing. SPIN gets the buyer to name and quantify their problem. MEDDIC checks whether you have the economic buyer, decision criteria, and a champion in place to actually close it. Most strong teams use both: SPIN inside the call, MEDDIC to grade the deal after.
Which SPIN question type matters most?
Implication questions. Rackham's research found they were the biggest single difference between top reps and average ones. They take a problem the buyer mentioned and make its cost concrete, so the buyer prices their own pain before you ever pitch. A deal where the buyer has quantified their problem at a number bigger than your price mostly sells itself.
How many situation questions should a rep ask?
As few as possible. Situation questions gather facts about the buyer's current state, and most of those facts can be pulled from research before the call. If a rep is asking more than two or three, they either did not prepare or are stalling. On a 30-minute discovery call, every situation question is time stolen from the implication questions that actually move the deal.
How do you make SPIN stick across a sales team?
Turn it into a system instead of a training. Kill situation questions with pre-call enrichment, add required CRM fields that capture the answers to implication and need-payoff questions, feed the buyer's quantified pain into the proposal automatically, and coach off call recordings by counting the ratio of situation to implication questions. Training fades in two weeks. A process wired into the CRM holds.
The takeaway
SPIN selling is not a script and it never was. It is a description of what the best reps already do: ask questions that lead the buyer to name and price their own problem, then get out of the way. The framework has survived forty years and a complete change in how people buy because it was built on evidence, not opinion.
The teams that get value from it are the ones that stop treating it as a training slide and start treating it as a system. Move situation questions to enrichment. Capture implication answers as data. Carry the buyer's number all the way to the proposal. Do that and every rep runs discovery at the level your best one does, deal after deal. If you want help wiring that into your CRM and your go-to-market motion, that is the work we do. Talk to us.