The SPICED framework
Situation. The buyer's current operating reality. How the team works today, what tools are in place, what data is being tracked.
Pain. The specific problem driving the conversation. Discovered through open questions about what's broken.
Impact. The business consequence of the pain. Lost revenue, slow cycles, missed quotas, churn risk.
Critical event. The forcing function or deadline that makes this a now problem, not someday problem. Quarter close, annual planning, executive review.
Decision. The actual decision process. Who's involved, what evaluation criteria, what timeline.
Why SPICED emerged
BANT was built for IBM mainframe sales in the 1950s. MEDDIC was built for PTC's enterprise software sales in the 1990s. Neither was designed for high-velocity B2B SaaS with multi-stakeholder buying committees.
SPICED is built around the insight that critical events are the most predictable closing trigger in modern SaaS. Without a critical event, deals slip indefinitely. With one, they close on time.
How SPICED works in practice
Sample conversation: 'Walk me through how you handle account planning today.' (Situation) 'What's the hardest part of that?' (Pain) 'When QBR prep takes hours, what's the downstream impact on renewal forecasts?' (Impact) 'Is there something coming up that's making this urgent now?' (Critical event) 'If we decided to make a change, walk me through what decision process looks like.' (Decision)
The order matters. Each layer builds on the previous. Skipping to decision without establishing situation and pain produces shallow qualification.
SPICED vs MEDDIC vs MEDDPICC
SPICED is lighter than MEDDPICC. Five dimensions vs seven. Better fit for high-velocity SaaS sales where speed matters.
MEDDPICC includes Paper Process and Competition. SPICED doesn't explicitly cover either, though they often surface inside the Decision dimension.
SPICED emphasizes Critical Event more than any other framework. This is its main differentiator and often its most useful contribution.
Running SPICED inside Salesforce
Add custom fields on the Opportunity: SPICED_Situation, SPICED_Pain, SPICED_Impact, SPICED_Critical_Event, SPICED_Decision_Process.
Critical Event becomes a gating field: deals without a documented critical event can't advance past mid-stage.
Reports surface deals where Critical Event is blank or where the date has passed without a close, flagging the deals most likely to slip.
Frequently asked questions
What does SPICED stand for?
Situation, Pain, Impact, Critical event, Decision. A modern B2B sales discovery framework.
How is SPICED different from MEDDIC?
SPICED is lighter (5 vs 7 dimensions) and emphasizes Critical Event as the leading closing predictor. Better fit for high-velocity SaaS.
Who created SPICED?
Winning by Design, who popularized it in the 2020s as a SaaS-native alternative to BANT and MEDDIC.
CTA
Want to operationalize SPICED in Salesforce with Critical Event tracking that flags slipping deals automatically? See how CRUSH wires it into the Opportunity workflow. [Book a Demo]
