SPICED: situation, pain, impact, critical event and decision, with questions for each
SPICED is a customer-centric discovery and qualification framework from Winning by Design. It covers five things a rep needs to understand: the buyer's Situation, their Pain, the Impact of solving it, the Critical event that makes it urgent and how the Decision gets made. It was built for recurring-revenue businesses, so the same notes are meant to carry from the first call through onboarding and renewal.
SPICED was developed by Winning by Design, the revenue consulting and training firm founded by Jacco van der Kooij, and is taught mostly to SaaS and other subscription businesses. Winning by Design presents it as a shared language for every customer-facing team rather than a sales-only checklist: the impact a customer expects when they sign is what customer success checks against at renewal.
Best for
- SaaS and subscription businesses where renewal and expansion matter as much as the first deal
- Teams that want one discovery language shared by SDRs, account executives and customer success
- Mid-market deals that need more than BANT but less than full MEDDPICC
- Reps whose deals slip because nothing makes the buyer's date real
- Handoffs where the post-sale team needs to know why the customer bought
Practice SPICED in Vonvo by building a custom scenario around it (Starter plan and up). Calls are scored on the NEPQ-based scorecard.
The SPICED stages
In order, with what each stage is for and questions you can adapt.
Situation
Collect the facts about the buyer's business and setup that give the rest of the call context. Keep it short; most of it should come from research.
- "How is the team set up today, and who owns this process?"
- "What are you using now, and how long have you had it?"
- "I saw you opened a second warehouse this spring. How has that changed things?"
- "What does a normal week look like for the people doing this work?"
Pain
Find the problem the buyer actually wants solved, why it exists and what they have already tried.
- "What's getting in the way right now?"
- "Why do you think that keeps happening?"
- "What have you already tried, and what happened?"
- "Who on the team feels it most?"
Impact
Establish what solving the pain is worth: the measurable business result, and what it means for the buyer personally.
- "If this were fixed, what would change in the numbers you report on?"
- "Roughly what is it costing today, in hours, revenue or churn?"
- "What would it mean for you and your team to have this off your plate?"
- "Which matters more to your leadership here, the saving or the growth it unlocks?"
Critical event
Find the date that matters to the buyer and what happens if they miss it. A deadline with no consequence attached is not a critical event.
- "Is there a date this needs to be solved by?"
- "What happens on that date if nothing has changed?"
- "What's driving that timing: a launch, a renewal, a board meeting, a regulation?"
- "Working back from that date, when would you need to decide?"
Decision
Understand how the decision gets made: the criteria, the people, the steps and the paperwork.
- "How will you choose between the options you're looking at?"
- "Who else needs to be comfortable with this, and what will each of them care about?"
- "Walk me through what happens between choosing a vendor and signing."
- "Have you bought something like this before? How did that go?"
What SPICED sounds like on a call
An illustrative excerpt. Notice where the rep asks instead of pitches.
- Rep
I read that you moved support in-house last year. How is the team set up now?
- Buyer
Twelve agents and one lead, all on email and chat through our help desk.
- Rep
What's getting in the way?
- Buyer
Volume. Half the tickets are 'where's my order', and the team spends all day copying tracking numbers.
- Rep
Why do you think those tickets come in at all?
- Buyer
Our shipping emails are vague, and customers can't track anything themselves.
- Rep
If those tickets went away, what would that change?
- Buyer
We'd hit our response-time target without hiring. And I'd stop getting pulled into escalations every evening.
- Rep
Is there a date this needs to be fixed by?
- Buyer
Peak season starts November 1. Last year we hired eight temps and our satisfaction score still dropped.
- Rep
So if nothing changes by November, you're looking at temps again. Who besides you would sign off on a change?
- Buyer
Our COO approves anything outside the budget, and IT has to review the integration.
- Rep
Then working back from November, would it make sense to start IT's review this month?
A SPICED call scorecard
What a reviewer should listen for.
| Criterion | What good looks like |
|---|---|
| Situation, kept brief | The rep uses research and asks only the situation questions needed to understand the pain. |
| Pain and its cause | The buyer describes a specific problem and why it happens, not just a symptom. |
| Rational impact | The buyer puts a number or measurable result on solving the pain, in their own terms. |
| Emotional impact | The rep learns what the change means for the buyer and their team, beyond the numbers. |
| Critical event | The rep identifies a date and the consequence of missing it, and confirms both with the buyer. |
| Decision | The rep learns the criteria, people, steps and paperwork between now and signature. |
| Shared summary | Before the call ends, the rep plays back the SPICED summary and the buyer confirms or corrects it. |
Common mistakes
- Spending most of the call on situation questions that a few minutes of research would have answered.
- Calling any date a critical event. 'We'd like it by Q3' is a preference; a contract expiry or a launch with consequences attached is a critical event.
- Recording impact in the rep's numbers instead of the buyer's, so nobody in the buying group repeats it.
- Capturing only the rational impact and missing what the change means to the buyer personally, which is often what creates urgency.
- Treating the letters as a strict sequence. Pain and impact usually come up together, and decision questions can start on the first call.
- Keeping SPICED notes in the rep's head instead of the CRM, so customer success inherits the account without knowing why the customer bought.
How to practice SPICED
- Build a custom Vonvo scenario with a support or operations leader persona and run a 10-minute discovery call. End only when you can play the pain, the impact and the critical event back to the AI buyer in a few sentences.
- Drill the critical event: have the AI buyer give a vague timeline like 'sometime this year', and practice finding the event and the consequence behind it without suggesting one yourself.
- Run the impact stage twice in the same scenario, once asking only about numbers and once also asking what the change means to the buyer personally, then compare the scored feedback.
- Practice the decision letter against a persona who says they're the only decision maker, and use questions about past purchases to surface the other people and the paperwork.
- After each roleplay, write a five-line SPICED summary using only what the AI buyer actually said. Any letter you have to guess is the one to work on next. Calls are scored on Vonvo's NEPQ-based scorecard, so use the scorecard on this page for the SPICED review.
SPICED questions, answered
What does SPICED stand for?
Situation, Pain, Impact, Critical event and Decision. Situation is the context, pain is the problem the buyer wants solved, impact is what solving it is worth, the critical event is the date that makes it urgent, and decision covers how the buying decision gets made.
What is a critical event in SPICED?
A specific date the buyer has to hit, with a real consequence if they miss it, such as a contract expiring, a product launch, a regulatory deadline or a peak season. It's stronger than a target date the buyer picked, because something actually goes wrong when the date passes. Deals without one are more likely to slip.
SPICED vs MEDDPICC: which should I use?
SPICED is lighter and more customer-centric, and it's designed to carry past the sale into onboarding and renewal. MEDDPICC goes deeper on enterprise deal mechanics such as the economic buyer, the champion, the paper process and competition. Mid-market subscription teams often find SPICED enough; teams with long, multi-stakeholder enterprise deals tend to use MEDDPICC, sometimes with SPICED for discovery.
How is SPICED different from BANT?
BANT checks whether a lead is worth pursuing: budget, authority, need and timeline. SPICED is centered on the buyer: what's going on, what hurts, what fixing it is worth and why now. Impact takes the place of budget as the question that matters most, on the view that budget usually follows a clearly understood impact.
Is SPICED only for SaaS?
It was designed with subscription businesses in mind, which is why it links the first sale to renewal, but the five letters work for most considered B2B purchases. The impact and critical event questions carry over especially well to services, agencies and other repeat-purchase businesses.
Does Vonvo score SPICED calls?
Not with a SPICED rubric of its own. Vonvo scores practice calls on an NEPQ-based scorecard, and SPIN, MEDDIC and BANT are available as frameworks for practice and live-coaching guidance. For SPICED, build a custom scenario with the buyer persona and critical event you want to practice, then review the call against the scorecard on this page.
Related methodologies
SPICED is a trademark of Winning by Design. Vonvo is not affiliated with Winning by Design.
Make SPICED a habit
Reps get better at methods by saying the questions out loud, often. Start with 250 free credits and get every practice call scored.