SPIN Method: Uncover customer needs with the right questions.

Developed by Huthwaite and associated with Neil Rackham’s work, the method organizes discovery around the customer’s perspective. The four letters provide a framework for building the conversation. It’s not a questionnaire to work through.

On a call, SPIN helps you hold off on presenting a solution while the need is still unclear. A customer who says “our follow-up is complicated” hasn’t yet explained what’s difficult, who it affects, or what outcome they’re looking for.

If the contact isn’t the right person or doesn’t want to talk, SPIN isn’t a reason to prolong the call. Agreeing on the topic comes first.

These questions cover how things work today. They should provide useful information, not make the customer repeat what you could have found out before the call. Too many situation questions can feel like an interrogation.

Hypothetical example: a manager receives quote requests through several channels. Useful question: “How does a request get from the point of receipt to the person who handles it?” This reveals a process.

Then paraphrase: “If I understand correctly, each manager picks up the requests for their area.” The customer can correct you before you build on a misunderstanding.

These questions focus on what isn’t working. Give the customer room to say there’s no problem. There’s no need to impose one.

“When does a request become difficult to track?” lets the customer describe their reality. “You’re probably wasting a lot of time with this tool, right?” already contains your diagnosis.

If the customer mentions handoffs during absences, ask about a recent example without requesting personal information.

These questions distinguish a minor inconvenience from a priority. What does the challenge cause: delays, rework, tradeoffs, or lack of visibility? Let the customer describe the consequences. Don’t assign a dollar amount or frequency they haven’t given you.

“When a request isn’t handed off during someone’s absence, what happens to the team?” The manager may say a colleague has to reconstruct the history. You then know who’s affected.

Don’t overstate the impact. If it happens rarely and is well managed, note that. An honest discovery conversation may conclude that there’s no project. That’s a valid outcome—and it avoids an unnecessary sales cycle.

The customer describes what solving the problem would change. The conversation moves from the current situation to the desired outcome. You’re not asking them to validate your product or price yet.

“If the person stepping in could immediately find all the useful information, what would that change for you?” The answer might be about continuity of service rather than time saved. Your proposal should reflect that priority.

Finally, ask how they would recognize an improvement. Agree on a measurable indicator together; don’t make one up for your pitch.

Choose a situation your offering can genuinely address. Write one question for each category, then role-play the call without requiring yourself to ask them all. The customer may mention a consequence before you ask about the problem.

After the call, sort your questions by intent. Identify duplicates and leading questions. Does your final proposal reflect a benefit the customer expressed? If not, you pitched too soon. A SPIN scorecard is available for scoring your call reports.

SPIN doesn’t replace qualification of the buying process. Once the need is clear, BANT or MEDDIC can complement it. There’s no need to stack methods on a first call.

Working through S, P, I, N in a rigid order. Asking too many situation questions because they’re easy. Dramatizing the implications by exaggerating the cost of inaction.

To improve: review a specific excerpt rather than a general score, replace a leading question with an open-ended one, give the customer time to think, and accept that they may challenge your assumption.