SPIN Discovery Questions for SaaS Sales Calls

Most reps know discovery matters. Most discovery calls still follow the same tired script: a round of introductions, a dozen questions about team size, tools and budget, a quick slide about the company, and a promise to "send over some information". The rep leaves with a filled-in CRM record. The buyer leaves with nothing they did not already know.

The problem is not the number of questions. It is that the questions serve the seller. "How many people are on your team?" helps you size the deal. It does nothing for the person answering it. When the buyer can feel that they are being qualified rather than helped, they give short answers and keep their real concerns to themselves.

Good discovery flips that. The buyer should finish the call understanding their own situation better than when they started, and wanting to continue the conversation because it was useful to them. That is a high bar, and it is exactly the bar Neil Rackham's research set.

SPIN Selling was published in 1988. It grew out of research by Rackham and his team at Huthwaite, who studied more than 35,000 sales calls. In a 2026 interview published by Huthwaite International, Rackham explained how a sample that large was possible: the team ran productivity projects with companies such as Xerox, IBM and Motorola, trained sales managers to code calls to a research standard, and had them observe their own salespeople before and after coaching.

Several findings from the book are still worth knowing, because they run against habits many reps were taught:

• What works in small, one-call sales does not necessarily work in large, complex ones. Classic closing techniques that help in low-value sales were associated with worse results in larger sales, where buyers are more sensitive to pressure.
• In larger sales, the calls that succeeded were not the ones where the buyer mentioned a problem. They were the ones where the buyer stated an explicit need: a clear statement of something they wanted or intended to do. Rackham called problems and dissatisfactions implied needs, and found that turning them into explicit needs was the core skill.
• Less successful salespeople asked many situation questions about facts and background. Successful ones asked fewer of those and more questions that explored problems, their consequences and the value of solving them.

Rackham is also refreshingly honest about what produced the results. In that interview he says the gains did not come from "four little questions" alone, but from the whole coaching process around them. Keep that in mind: SPIN is a way of thinking about a conversation, practised and reviewed over time, not a script.

SPIN stands for four kinds of questions. They are not a strict sequence, but they tend to flow in this order because each builds on what the previous one uncovered. The examples below assume you sell a customer-support platform to a company that handles support by email and phone today.

Situation questions gather facts about the buyer's current state. You need some, but every one costs the buyer time and gives them nothing back. Do your homework so you only ask the ones you cannot answer yourself. Buyers notice when you have not: in Gartner's 2025 survey, 73% of B2B buyers said they actively avoid suppliers who send irrelevant outreach, and a call full of questions you could have answered from their website sends the same signal.

• "I saw you added a second support location last year. How is work split between the two teams?"
• "When a customer emails you today, where does that message land first?"

Problem questions explore difficulties, dissatisfactions and things that are harder than they should be.

• "Where does that handoff between the two teams slow things down?"
• "How often does a customer have to explain their issue more than once?"
• "What part of the current process do your agents complain about most?"

Implication questions explore the consequences of a problem: what it leads to, what it costs and who else it affects. These are the questions that turn a minor annoyance into a priority.

• "When customers repeat themselves, what does that do to the length of the call?"
• "If a refund request sits in the wrong queue for a day, what happens next?"
• "How does that show up in your renewal conversations with larger accounts?"

Need-payoff questions ask the buyer to describe the value of solving the problem in their own words.

• "If every agent could see the full history before picking up, what would that change for your team?"
• "How would it help your quarterly review if you could show response times by location?"

Most reps can ask situation and problem questions without much thought. Implication questions are where conversations stall, because they require you to understand the buyer's business well enough to know what a problem leads to. Asking them on the fly, with a buyer waiting, is hard.

The fix is preparation. Before an important discovery call, take the three or four problems you most expect to hear about and map their likely consequences. A simple way to do it is to ask, for each problem, what it costs in four areas:

• Time: hours lost, slower cycles, work that has to be done twice.
• Money: direct costs, lost revenue, discounts given to keep upset customers.
• Risk: errors, compliance exposure, single points of failure.
• People: frustration, turnover, managers pulled into firefighting.

Write two or three implication questions for each. You will not use most of them, but having them ready means you can follow the buyer's lead without freezing. Over time, the best of these become a shared library for the team, which is far more useful than a generic discovery script.

One caution: implication questions can feel manipulative if you use them to make a buyer feel bad. Their purpose is to help the buyer see the full picture, including when the problem is genuinely small. If you explore the consequences and they turn out to be minor, that is valuable information. A deal that should not happen is cheaper to lose in the first call than in the sixth.

Need-payoff questions do something subtle. Instead of you telling the buyer why your product is valuable, they tell you why solving the problem is valuable. People believe their own reasons more than yours, and the words they use are the words they will repeat to colleagues.

Rackham also found that need-payoff questions tend to make the conversation feel more positive and helpful, because they focus on solutions rather than problems. In practice, this is where buyers start selling internally on your behalf.

Write down their exact phrases. If the head of support says, "I would finally be able to show the board that the new location is pulling its weight," that sentence belongs in your follow-up email, your demo opening and the business case your champion takes to finance. For more on that last step, see equipping your champion.

SPIN was developed when buyers depended on salespeople for much of their information. Today many arrive with a problem already defined and a solution already in mind. That does not make discovery less important, but it changes its job.

Matthew Dixon and Brent Adamson argue in The Challenger Sale that the strongest reps do not simply ask buyers what they need; they bring a perspective that changes how the buyer sees the problem. Daniel Pink makes a related point in To Sell Is Human: when buyers can find information on their own, the seller's value shifts from solving the problem the buyer describes to helping them find the problem they have not yet named.

In practice, combine the two. Use problem and implication questions to test the buyer's own diagnosis, and be ready to share what you have seen at similar companies when their diagnosis looks incomplete. "Most teams we talk to think the issue is response time, but when we look at their data, the bigger cost is usually repeat contacts. Could we check whether that is true for you?" That is still discovery. It just starts from a point of view instead of a blank page. The Challenger article covers how to build that point of view.

A common reaction to SPIN is to ask more questions. Call data suggests that is a mistake. In Gong's 2025 analysis of 326,000 recorded sales calls of at least ten minutes, sellers who won deals asked 15 to 16 questions per call on average, while sellers who lost deals asked about 20. Gong's interpretation is that struggling sellers fire off questions without building a real dialogue, which feels like an interrogation to the buyer.

The same analysis found an average talk ratio of 60% talking to 40% listening. Reps talked 57% of the time in deals they won and 62% in deals they lost. The gap was larger for low performers, whose talk time swung from 54% in won deals to 64% in lost ones, and lost deals often featured long seller monologues. Gong's original 2016 analysis had suggested a "golden ratio" of 43% talking to 57% listening.

Treat these numbers as a direction, not a target. A few habits that help:

• Follow up on answers before moving on. "Tell me more about that" is often a better next question than the next one on your list.
• Summarize what you heard and ask whether you got it right. It slows you down and catches misunderstandings early.
• Pause for a couple of seconds after the buyer finishes. The most useful information often comes in the second half of an answer.
• Keep your own explanations short until the buyer asks for more.

Discovery on a video call has one big advantage over a meeting room: you can both look at the same thing. Use it.

• Ask the buyer to show you their current process. "Could you share your screen and walk me through what happens when a refund request comes in?" You will spot problems they have stopped noticing, and your implication questions will be about real things rather than guesses.
• Take notes in a document they can see. When they see their own words appear, they correct you, add details and trust the summary later.
• Sketch the process as they describe it. A rough flow with five boxes is enough. Problems often become obvious when the handoffs are drawn out.
• End with the explicit needs written on screen. "Here is what I heard you need. Is anything missing or wrong?" That list becomes the agenda for your demo.

If the buyer cannot share their screen in your meeting tool, do not push. Ask them to describe it, or offer to look at a screenshot later. Discovery should be easy for the buyer, not a technical hurdle. For more on running calls this way, see why SaaS is now sold on a shared screen.

Rackham described four possible outcomes of a sales call: an order, an advance, a continuation and a no-sale. An advance is an event, in the call or after it, that moves the sale forward. A continuation is a call that ends pleasantly with no specific agreement to act: "Great talking, send me some information." In complex sales, continuations feel like progress but usually are not.

In SaaS, real advances look like this:

• The buyer agrees to bring the person who owns the budget to the next call.
• They will send a sample of real data so your demo can use it.
• Their IT lead will join a 30-minute technical review next week.
• They will share the decision criteria the team is using.

Before the call, decide what advance you will ask for. During the call, earn it. At the end, ask for it directly and put it on the calendar before you hang up. If the buyer is not willing to commit to anything, that tells you something about the deal that no amount of questioning would.

1. Two minutes: agree the agenda on screen and ask what they would like to get out of the call.
2. Five minutes: check what you learned in your research. "I read that you are moving to a single support team. Is that still the plan?"
3. Fifteen minutes: problems and their implications, ideally while the buyer shows their current process on screen.
4. Ten minutes: need-payoff. Ask what solving the main problems would mean for them, their team and their boss. Capture their words.
5. Five minutes: summarize the explicit needs on screen and ask what is missing.
6. Five minutes: if it fits, a very short look at one thing that answers their top need. Only if it fits.
7. Three minutes: agree a specific advance and book it.

Afterwards, send a short summary that leads with their needs in their words, not with your product. The demo that follows should open by confirming that summary.

If you record your calls, listen to a few with these in mind:

• Asking situation questions you could have answered from their website or LinkedIn.
• Jumping to a solution the moment the buyer mentions a problem, before you understand what it costs them.
• Asking implication questions in a leading, dramatic way that makes the buyer defensive.
• Telling the buyer what the value is instead of asking them.
• Ending without a specific next step that the buyer has committed to.

Discovery is a skill you improve by reviewing real calls, ideally with a manager or a peer. That was true in Rackham's research, and it is still true now.