SPICED is a sales methodology built around five elements of a customer conversation: Situation, Pain, Impact, Critical Event, and Decision. It was developed by Winning by Design, the revenue consultancy founded by Jacco van der Kooij, for recurring-revenue businesses where a customer has to keep getting value long after the contract is signed. Unlike qualification checklists such as BANT, SPICED is meant to be used by every customer-facing team — sales, onboarding, and customer success — so the diagnosis made in the first call carries through the whole relationship.
Key facts
- Type: Customer-centric diagnostic and qualification framework
- Elements: 5 — Situation, Pain, Impact, Critical Event, Decision
- Created by: Winning by Design (Jacco van der Kooij)
- Best for: SaaS and other recurring-revenue B2B sales with multiple stakeholders
- Used by: SDRs, account executives, and customer success teams — one shared language
What does SPICED stand for?
SPICED stands for Situation, Pain, Impact, Critical Event, and Decision. Each letter is a part of the customer's reality that the seller needs to understand before recommending anything.
- S — Situation. The facts about the customer: company size, team structure, tools in use, market, and how they work today. Most of this should be researched before the call, not asked during it.
- P — Pain. The specific problems that made the customer take the meeting. Pain is what the customer feels and describes in their own words.
- I — Impact. What the pain costs the business, and what solving it would be worth. Impact can be rational (revenue, cost, time) or emotional (stress, reputation, career risk).
- C — Critical Event. A date by which the customer must have a solution, and the consequence of missing it. A critical event is different from a preferred timeline: missing it has a real cost.
- D — Decision. How the decision will be made: who is involved, what criteria they use, and what process they follow.
How does the SPICED sales methodology work in practice?
SPICED works as a conversation structure, not a script: the seller uses the five elements to build a shared picture of the customer's problem, then links any recommendation back to the Impact the customer named. The order is flexible. Good SPICED conversations usually move from Situation to Pain, then spend most of the time on Impact, because Impact is what justifies a decision.
Typical SPICED questions include:
- Situation: "How is the team organized today, and what does the current process look like?"
- Pain: "What made this a priority now?"
- Impact: "If this stays the way it is for another year, what does that cost you?"
- Critical Event: "Is there a date this has to be working by? What happens if it slips?"
- Decision: "When you bought something similar last time, who was involved and how did you decide?"
The output of a SPICED conversation is a short written summary of the five elements that the customer confirms. That summary is then handed to the next team, so onboarding and customer success start from the same diagnosis instead of asking the same questions again.
What is the difference between SPICED, MEDDIC, and BANT?
BANT qualifies whether a buyer can purchase, MEDDIC qualifies whether a complex deal is winnable, and SPICED diagnoses whether the customer will get lasting impact. The three frameworks answer different questions, which is why many teams combine them.
- BANT (Budget, Authority, Need, Timeline) — seller-centric, fast, built for transactional qualification. Weakness: starts with budget before the problem is understood.
- MEDDIC (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion) — built for enterprise deal control and forecasting. Weakness: describes the deal more than the customer's problem.
- SPICED (Situation, Pain, Impact, Critical Event, Decision) — customer-centric, built for recurring revenue and handoffs between teams. Weakness: lighter on stakeholder mapping than MEDDIC.
A practical rule: use SPICED to run the conversation and MEDDIC to inspect the deal afterwards. For a methodology where buyer and seller qualify each other as equals, see our guide to the Sandler sales methodology.
When should you use SPICED?
SPICED fits best when revenue depends on the customer renewing and expanding, not only on the first signature. It is a strong choice if:
- you sell subscriptions, services, or any product where value is delivered over time;
- several teams touch the customer and context is lost at each handoff;
- deals stall because there is no real deadline — the Critical Event element forces that conversation early.
SPICED is less useful for one-off, low-value transactions, where a five-part diagnosis costs more than the deal is worth.
What are the limitations of SPICED?
The main limitation of SPICED is that it assumes the Pain the customer describes is the real problem. In complex B2B decisions, the first pain a buyer names is usually a symptom. A team that records "Pain: reporting takes too long" and moves straight to Impact may build a precise business case for the wrong problem.
Two other limits are worth knowing:
- Agreement is assumed, not built. SPICED does not include a step where buyer and seller explicitly agree on what the conversation is for and what happens next.
- Decision covers process, not confidence. Knowing who signs is different from knowing whether the buyer feels safe deciding.
How does SPICED compare to Diagnostic Sales?
SPICED and Diagnostic Sales™ share the same starting principle — understand before you recommend — but Diagnostic Sales goes one level deeper on cause and on the decision itself. Sales ARC™ moves through four phases: Agreement, Root Cause, Choices, and Soft Landing.
- Agreement vs Situation: Situation collects facts. Agreement makes sure both sides see the same situation and agree on what they are trying to decide.
- Root Cause vs Pain: Pain records what hurts. Root Cause asks why it hurts, so the solution addresses the driver and not the symptom.
- Choices vs Impact: Impact builds the case for acting. Choices presents options that follow from the diagnosis, including the option of not buying.
- Soft Landing vs Decision: Decision maps the process. Soft Landing guides the client to a decision they are confident in — no pressure, no regret.
Teams already using SPICED do not need to replace it. Adding a Root Cause step between Pain and Impact is the single change that improves diagnosis the most. You can read how the phases fit together on the Diagnostic Sales methodology page.
Frequently asked questions
What is the SPICED sales methodology?
SPICED is a sales framework from Winning by Design built on five elements: Situation, Pain, Impact, Critical Event, and Decision. It helps sellers diagnose a customer's problem and the value of solving it before proposing a solution, and it is designed for recurring-revenue businesses.
Who created SPICED?
SPICED was created by Winning by Design, a revenue consultancy founded by Jacco van der Kooij. It is part of the company's wider body of work on recurring-revenue sales.
Is SPICED better than MEDDIC?
Neither is better in general: they solve different problems. SPICED structures the customer conversation around impact, while MEDDIC inspects a complex deal for risk. Many B2B teams use SPICED in discovery and MEDDIC for deal reviews and forecasting.
What is a Critical Event in SPICED?
A Critical Event is a deadline by which the customer must have a solution in place, with a real consequence if it is missed. It differs from a preferred go-live date because missing a Critical Event costs the customer money, compliance, or credibility.
Can SPICED be used outside SaaS?
Yes. SPICED works for any B2B sale where value is delivered over time, including services, manufacturing, and distribution. It is less suited to small one-off transactions, where a full diagnosis is not worth the time.
Conclusion
SPICED is one of the most practical frameworks for making sales conversations about the customer's impact rather than the seller's product — its weak point is that it takes the stated pain at face value. If you want to see whether a deeper diagnostic approach fits your sales environment, take the free 2-minute assessment.
{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is the SPICED sales methodology?","acceptedAnswer":{"@type":"Answer","text":"SPICED is a sales framework from Winning by Design built on five elements: Situation, Pain, Impact, Critical Event, and Decision. It helps sellers diagnose a customer's problem and the value of solving it before proposing a solution, and it is designed for recurring-revenue businesses."}},{"@type":"Question","name":"Who created SPICED?","acceptedAnswer":{"@type":"Answer","text":"SPICED was created by Winning by Design, a revenue consultancy founded by Jacco van der Kooij. It is part of the company's wider body of work on recurring-revenue sales."}},{"@type":"Question","name":"Is SPICED better than MEDDIC?","acceptedAnswer":{"@type":"Answer","text":"Neither is better in general: they solve different problems. SPICED structures the customer conversation around impact, while MEDDIC inspects a complex deal for risk. Many B2B teams use SPICED in discovery and MEDDIC for deal reviews and forecasting."}},{"@type":"Question","name":"What is a Critical Event in SPICED?","acceptedAnswer":{"@type":"Answer","text":"A Critical Event is a deadline by which the customer must have a solution in place, with a real consequence if it is missed. It differs from a preferred go-live date because missing a Critical Event costs the customer money, compliance, or credibility."}},{"@type":"Question","name":"Can SPICED be used outside SaaS?","acceptedAnswer":{"@type":"Answer","text":"Yes. SPICED works for any B2B sale where value is delivered over time, including services, manufacturing, and distribution. It is less suited to small one-off transactions, where a full diagnosis is not worth the time."}}]}