SPIN Selling

There's an old limit on how a seller can explain value: the same sentence lands differently depending on who says it.

"You're probably losing about forty hours a month to documents people can't find." Said first by a rep, the prospect hears exaggeration. It's arithmetic from someone trying to sell, so discounting it is the reasonable response. What they do next isn't verify the number, it's argue it down. The reply is that they're not nearly that bad.

The same number calculated by the customer changes character. Ask how often it happens in a week, how long it takes each time, and how many people it happens to, and the customer does the multiplication themselves. That figure isn't a claim you brought; it's a fact they just produced. People don't argue with facts they made, and they repeat them later to their own colleagues.

SPIN selling is the question order that makes the customer do that arithmetic. Because the seller talks less and asks more, it changes the character of a first call from a presentation into a conversation.

Four kinds of question, used in order. Keeping the order is the whole method.

1. Situation questions — what they do today and how. Where documents live, how many people edit them, how they find last year's material. These are questions of fact, so they're easy to answer. But don't ask here what you could have looked up: asking for headcount signals you came unprepared.
2. Problem questions — what's inconvenient about that setup. Whether they've ever failed to find something, whether anyone has rebuilt a file a departed colleague had already made. This is where the first complaint comes out.
3. Implication questions — what follows if the inconvenience stays. This step is the core of the method. Ask how many hours the rebuild took, how often that happens in a month, and how many people it happens to, and the prospect calculates forty hours a month themselves. The seller states no numbers, only questions.
4. Need questions — what improves if it's solved. If those forty hours halved, what would they do with the time? The sentence they answer with is the sentence they'll use when they push the approval internally.

Proportion matters. A beginner asks ten situation questions and no implication questions. A prepared call runs roughly three situation, three problem, four implication, and two need. Situation questions are easy to answer, so the conversation flows pleasantly — and a call that leaves only the pleasantness behind has confirmed nothing.

The setting for this conversation is a discovery call, where you learn the customer's situation and problems. The benchmark is that the seller talks for less than a third of it.

It fits when the customer doesn't yet see their situation as a problem. Explain a solution however well to someone who has never said out loud that their current way is inconvenient and it won't reach them. The problem has to exist first for the solution to have anywhere to sit, which is why this method belongs at the front of a deal rather than in the middle of one.

Three situations are a poor fit.

1. Requirements the customer has already fixed. Open with situation questions in a room where they wrote up what they need and invited vendors in, and the only impression left is wasted time. Answering against their list directly works better.
2. Small, fast deals. A contract that closes in one call has no room for four kinds of question.
3. Fifteen minutes on the calendar. You can't walk the whole order, so pick problem and implication and run only those.

The limits are clear. Turn the questions into a list and read down it and the prospect becomes a person filling in answers, and the call starts to sound like an interrogation. Sentences that play back what you just heard have to sit between the questions for it to be a conversation.

Pushing implication questions too hard is the other frequent failure. Keep enlarging the inconvenience and the prospect feels their own work is being attacked — the person who chose the current setup is often the person in the room.

And this is not a checklist. Whether budget, authority, and timing are confirmed is not something this conversation tells you. That side gets checked separately against a framework like BANT or MEDDIC. Teams that ask well and never qualify end up with deals sitting in the same pipeline slot for a year, all of them with a genuine problem behind them and no path to a signature.

"Three situation questions on this one and then straight to implication. We only have fifteen minutes."

Adjusting the proportions to fit the time available.

"We talked for twenty minutes on that call. Next one we ask more."

A critique measured by talk ratio.

"The customer worked out forty hours a month themselves. That sentence goes into the proposal as is."

Using the buyer's own number as the evidence.

At Pagedeck, Sofia writes down twelve questions before a first call. Only three of them are situation questions, and anything she could have looked up — company size, current tools — is left out. After the call she copies down the numbers the prospect said, exactly as they said them. Not rewording them is the rule, because a rounded-up number stops being the customer's and becomes hers.

Grace listens to a few recordings of these calls each quarter, against one criterion: whether a number the prospect calculated themselves appears in the call. The ones where it did moved quickly through later stages; the ones where it didn't tended to reach the demo and stop.

A common belief is that SPIN selling is a question list. The four kinds have names, so it looks like reading prepared sentences in order. But what the method actually does is choose the next question from the last answer. If a problem question returns no inconvenience, you don't advance to implication — you go back to situation questions in a different area. Read the list straight through and you end up asking implication questions about a problem that isn't there, and the prospect feels pushed.

The other misreading is that more questions means a better call. Less talking feels like using the method. But the goal of the conversation is an output, not a count: one number the prospect said out loud, and one sentence about what they'd do if it were fixed. Ask twenty questions without producing those two and there's no basis for advancing the deal.