Situation questions
These establish context. How the current process runs, who touches it, what tooling sits underneath it. Keep them short and do the research first. Every minute spent confirming a fact you could have found on the company website is a minute not spent on the parts of the call that change the outcome.
Problem questions
These surface a difficulty the buyer will admit to. What breaks in the current process, where the manual work sits, what the team complains about at quarter end. A problem question has done its job when the buyer states the problem in their own language, because that language is what you will use for the rest of the cycle.
Implication questions do the real work
Implication questions attach a cost to the admitted problem. If the forecast is rebuilt by hand every week, what does that cost in analyst time, and what decisions get made late as a result. If deals push a quarter, what happens to hiring plans and to the board number. These questions are uncomfortable to ask and they are the reason the framework works, because they move a problem from annoying to expensive.
In complex SaaS deals the do-nothing option competes with you for the entire cycle. No decision is what happens when the implication stage was skipped and the buyer never priced the cost of standing still. Weak implication work shows up later as deal slippage, since a deal with no quantified cost of delay has no reason to close this quarter.
Need-payoff questions
These ask the buyer to describe the value of a solution rather than hearing it from the rep. What would it be worth to know the shape of the quarter on day one. Who else benefits if the forecast cycle drops from a week to an hour. Answers to need-payoff questions become the internal pitch your champion delivers when you are not in the room, which is the point.
Teams that grade discovery on implication and need-payoff coverage rather than on call length usually find the difference in win rate first, and in cycle time second, because a buyer who has priced the cost of inaction moves faster through their own process. Track it the same way you track any other input to sales velocity.
Frequently Asked Questions
What are the four types of SPIN questions?
Situation questions establish facts about the buyer's current setup. Problem questions surface a difficulty with that setup. Implication questions expose what the difficulty costs. Need-payoff questions ask the buyer to describe the value of solving it. The order matters, because implication questions land only after a problem has been admitted.
How many situation questions should a rep ask?
As few as possible. Situation questions are the easiest to ask and the least valuable to the buyer, since most of the answers are researchable before the call. A rep who spends fifteen minutes confirming headcount and tech stack has spent the buyer's attention on data that a prep sheet should have covered.
What is the difference between an implication question and a problem question?
A problem question asks whether something is difficult. An implication question asks what that difficulty causes. Asking whether forecast reviews take a long time is a problem question. Asking what a two week forecast cycle means for the ability to correct a bad quarter is an implication question, and it is the one that creates urgency.
Does SPIN still work for B2B SaaS deals?
Yes, with the situation stage compressed. The research SPIN was built on studied large, considered purchases with multiple stakeholders, which describes most enterprise SaaS deals. What has changed is buyer access to information, so the reps who win spend their time on implication and need-payoff rather than on fact gathering.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like spin selling questions into prescriptive action for your team.
Schedule a Demo