What SPICED Stands For

SPICED maps a deal across five stages of a buyer’s reality: their current Situation, the Pain driving them to look for a fix, the Impact of that pain (and the upside of solving it), the Critical Event forcing a timeline, and the Decision process that gets a contract signed. Unlike qualification frameworks built around a scorecard, SPICED was designed by Winning by Design as a conversational structure — the questions are meant to sound like curiosity, not a checklist being read off a screen.

Situation: Ground the Conversation in Facts, Not Assumptions

  • “Walk me through how your team handles this today.” — gets the actual workflow, not the org chart version.
  • “What does your current stack look like for this?” — surfaces tools, headcount, and process in one question.
  • “How long has it worked this way?” — tells you whether this is a new problem or a tolerated one.

Pain: Separate the Real Problem From the Polite One

Every buyer has a rehearsed answer to “what’s the problem” — it’s the version that’s safe to say in a first call. SPICED treats Pain as both rational and emotional: the missed number on a dashboard, and the frustration of explaining the same miss to a VP every Monday. Getting past the rehearsed answer takes a follow-up most reps skip: “what has that actually cost you — in time, in deals, in credibility?” A rep who stops at the first answer builds a pitch for a problem the buyer hasn’t fully admitted to yet.

Impact: Quantify What Solving It Is Worth

  • “If this were solved, what changes in 90 days?” — ties the fix to something measurable.
  • “Who else feels this besides you?” — widens the business case beyond one champion’s frustration.
  • “What’s the cost of doing nothing for another two quarters?” — makes inaction a real, comparable option.

Critical Event: Find the Reason “Now” Beats “Eventually”

A critical event is the thing that turns interest into urgency — a leadership change, a renewal date, a board commitment, a competitor move. Without one, “we’re evaluating options” can drift for two quarters with no consequence. The question that surfaces it is rarely subtle: “what happens on your end if this isn’t solved by [date]?” If the honest answer is “not much,” the deal isn’t stalled — it was never as live as the pipeline stage suggested.

Decision: Map Who Actually Says Yes

  • “Besides you, who has to be comfortable with this before it moves forward?”
  • “What does the internal approval process usually look like for a purchase this size?”
  • “Has anything like this stalled before? What happened?” — tests for a hidden approval layer or past false start.
SPICED is designed to feel like a conversation, not a checklist — which is exactly why it’s easy to run half of it and never notice. The empathy that makes the framework work is also what makes it easy to lose track of live.

Why SPICED Breaks Down on a Real Call

The framework’s biggest strength — that it reads like genuine curiosity instead of an interrogation — is also its biggest liability in execution. A rep following a natural conversation is easy to pull off course: the buyer volunteers a tangent about a vendor they hated, or gets defensive about the Critical Event question, and by the time the call wraps, Situation and Pain got real airtime while Decision got a single rushed question at minute 42. Nothing about SPICED enforces coverage — it relies entirely on the rep remembering, mid-conversation, what’s already been covered and what hasn’t.

How Dextego Keeps SPICED Coverage Live, Not Retrospective

Dextego’s AI Sales Coach, Tego, listens to the call as it happens and tracks which SPICED pillars have actually been covered in the conversation — not which ones a rep assumes they hit. If Decision hasn’t come up by the time a call is winding down, Tego surfaces a prompt while there’s still time to ask, instead of a manager flagging the gap in a deal review a week later. It also reads how the specific buyer is engaging, so the Critical Event question lands differently for a buyer who’s already described a board deadline than for one who hasn’t mentioned urgency at all. That’s the difference between a team that can recite SPICED in a training session and a team whose discovery calls actually run it, live, under pressure, every time.

Frequently Asked Questions

What does SPICED stand for in sales?

Situation, Pain, Impact, Critical Event, and Decision — a discovery framework created by Winning by Design to map a buyer’s context, urgency, and decision process in a single, conversational structure.

How is SPICED different from MEDDICC?

MEDDICC is built as a qualification scorecard for deal review; SPICED is built as a conversational discovery flow. Many teams use SPICED to run the call and MEDDICC (or MEDDPICC) to score the deal afterward.

What’s the most commonly skipped SPICED component?

Decision and Critical Event tend to get the least airtime — both require a direct question that can feel presumptuous early in a relationship, so reps often let the conversation stay in Situation and Pain longer than it should.

Is SPICED only for SaaS sales?

It’s most associated with consultative B2B SaaS deals, particularly in the $50K–$250K ACV range, but the underlying structure — context, pain, urgency, and decision process — applies to most complex sales cycles.

Can AI coaching track SPICED in real time?

Yes — real-time AI coaching platforms like Dextego listen to live calls, track which SPICED components have been covered, and prompt reps on what’s missing while the call is still happening, rather than after it ends.

See SPICED Coaching in Action

Book a demo and we’ll show you how Tego tracks SPICED coverage live on the call and prompts reps on what’s missing — not in a deal review next week.

Book a Demo →