SPIN selling: a good call ends in an advance

Rackham’s book, SPIN Selling, was published by McGraw-Hill in 1988. Huthwaite, the research firm he founded, says its database holds more than 35,000 observed sales calls. Here’s how Huthwaite defines each question type, with two example questions of ours under each, written for a B2B software deal.

• Situation questions “gather background information and understand the context of the sale.” “How does your team track follow-ups after a demo today?” “Who owns that process?”
• Problem questions “explore the customer’s dissatisfactions and concerns.” “Where does that process break when the quarter gets busy?” “What do your reps complain about most?”
• Implication questions “develop apparently isolated problems by examining their ‘knock-on’ effect in other areas of the customer’s business.” “What does a slipped follow-up do to your forecast?” “How much of your managers’ week goes to chasing it?”
• Need-payoff questions invite the buyer to consider the benefits of solving the problem and then “to express an Explicit Need for a solution.” “If every call ended with a dated next step, what would that change for you?” “Why does fixing this matter this quarter?”

Keep Situation questions few and focused, as Huthwaite found successful sellers did. Rackham goes further: the original research found them “slightly negatively correlated with success. You could ask too many of them.” Most of what they dig up is in your CRM or on the buyer’s website before the call starts. Look it up, and spend the call on the other three.

Huthwaite sorts every call into one of four outcomes. An Advance is a step toward a final decision: the buyer takes an action that is new and meaningful. An Order is when “the customer completes the sale.” A Continuation is when “the customer continues the sales process, but things aren’t progressing.” A No Sale is when “the customer halts the sales process altogether.” In Huthwaite’s account of the research, only an Order and an Advance count as a successful call.

Most software deals don’t sign on a call, so the Advance is the outcome your reps are aiming for. For a bigger sale, Huthwaite’s examples are “access to another key decision maker or an agreement to see a demonstration.” A few more of our own: the buyer books a review with their security lead, agrees to a pilot with a start date, or brings their CFO to the next call.

Now the calls that feel good. “Send me some info.” “Let’s talk next quarter.” “Looks great, I’ll share it with the team.” Under Huthwaite’s definition, every one of those is a Continuation. The buyer was friendly, the call ran long, and nothing new is on anyone’s calendar. The deal sits.

The fix: your rep proposes the next step before the call ends. Huthwaite’s research found that top performers “do not even ‘ask for the order’. They propose the highest realistic commitment the customer is able to give.” So before each call, write down the best Advance you could realistically get, and one fallback. If the best is a meeting with the CFO, the fallback might be a working session with the buyer’s ops lead. Then propose it, with a date, while everyone is still on the call.

Proposing a real next step is different from pushing for a yes. On anything bigger than a petty cash item, Huthwaite says “continual use of closing techniques dramatically reduces the chance of success.”

Huthwaite names four stages inside a call: Preliminaries, Investigating, Demonstrating Capability, and Obtaining Commitment. The Advance belongs to the last one.

Huthwaite splits what buyers tell you into two kinds of need. “An implied need is a problem or dissatisfaction. An explicit need is a want or desire.” That split is the heart of the method. Huthwaite’s account of the research puts it bluntly: “In major sales, Implied Needs have no relationship, per se, with success; whereas Explicit Needs are key indicators of a successful outcome.”

So a buyer who complains isn’t yet a buyer who wants to change. As Huthwaite puts it, “people will live with problems.” Implication questions make the cost of the problem bigger than the cost of changing. Need-payoff questions get the buyer to say what fixing it is worth, out loud.

Here’s what that move sounds like on a software deal. Our examples, not quotes from a real call:

Once the buyer has named what they want, answer it in their words before the call moves on. Huthwaite calls this the true Benefit Statement, “the behaviour most closely associated with success.” It “shows how your product satisfies an Explicit Need the customer has expressed.” A feature tour before the buyer has said what they want answers a question nobody asked.

The recap is where an Advance holds or slips. “Thanks for your time, here’s the deck” gives the buyer nothing to agree to. A SPIN recap does two things. It restates the explicit need the way the buyer said it, so they read their own reason to change. Then it names the one commitment from the call, with its date.

If your reps want a head start, our free follow-up email builder takes what the buyer said and the next step, and gives back a short email to send.

Your best rep has a plan in their head for about five deals. The other 15 get improvised. In Arrows, the playbook is a plain-English description of how your team works its best deals. If your team runs SPIN, make the recap a rule in it: “restate the need in the buyer’s words and propose one dated next step.” When a call ends, the Arrows agent reads the playbook and drafts that follow-up, with the next milestone and a date for it, and your rep approves it before it goes out.

SPIN runs the call. It doesn’t tell you whether the deal is qualified: a framework like MEDDPICC tracks what’s proven across the whole deal, call after call.

Yes, on consultative deals, and most B2B software deals are consultative. But it isn’t the four questions that make it work.

In a 2026 Huthwaite interview, asked about the sales lift from the first SPIN training, Rackham said: “it wasn’t the four little questions. It was the whole coaching process, which was also the research process.” A rep who learns SPIN in a one-off workshop gets the vocabulary. A rep whose calls are reviewed against the Advance test every week gets the habit.

He has also stepped back from the book’s big idea, the split between small and large sales. In another 2026 Huthwaite interview, he said he had to put a huge emphasis on that split to get the book published, and that even then he knew it wasn’t the real issue. “I think the big/small divide is a misleading one,” he said. He now talks about “transactional sales versus consultative sales,” and says the internet took the transactional ones. “What was left was the consultative sale.”

The evidence behind all of this is Huthwaite’s own. Rackham says the calls came from productivity projects with Xerox, IBM, and Motorola, where sales managers coded what happened, and he calls it “very noisy data.” It shows what successful calls had in common. Treat it as a strong pattern from the people who built the method, and check it against your own won and lost deals.