SPICED

What is SPICED?

SPICED is a five-letter discovery and qualification framework developed by Winning by Design in the late 2010s for modern B2B SaaS. Situation, Pain, Impact, Critical Event, Decision. It was designed specifically for mid-market SaaS motion where BANT is too shallow but MEDDPICC is too heavy. Deals in the $10–100K ACV range with 2–4 stakeholders and 30–90 day sales cycles.

The framework was introduced by Jacco van der Kooij and became popular in the 2020–2024 period as SaaS sales orgs looked for a middle-weight qualification approach. SPICED's distinctive move is the Critical Event field — a dated business reason that forces a decision by a specific deadline. Without a Critical Event, the deal doesn't commit. This is the single most predictive field in the framework for whether a mid-market SaaS deal actually closes on time.

For an AE running mid-market SaaS, SPICED is the typical qualification framework. It pairs well with SPIN-style discovery (the Situation-Pain-Impact sequence maps naturally to SPIN's Situation-Problem-Implication questions) and with Challenger or Sandler approaches. It's the framework most B2B SaaS training programs teach as the default in 2026.

The five SPICED letters

Each letter has a specific role. The sequence matters — Situation establishes context, Pain surfaces the problem, Impact quantifies cost, Critical Event creates deadline pressure, Decision maps the process.

• Situation — context. What the prospect's current state looks like — team size, tech stack, process today. Short. Similar to SPIN's Situation questions.
• Pain — the specific problem. Not 'we want better reporting' but 'our forecast was 23% off last quarter.' Pain needs to be concrete and recent.
• Impact — what the pain costs. Dollars, hours, strategic risk. Quantified. 'The forecast miss cost us $2M in missed expansion targets and the CRO is on a PIP.' No quantification, no qualified deal.
• Critical Event — the dated business reason forcing a decision. Board meeting, quarter end, launch date, contract expiration, compliance deadline. If there's no Critical Event, the prospect will happily stay with the status quo indefinitely.
• Decision — the decision process. Who signs, who reviews, what procurement looks like, timeline per step. Lighter than MEDDPICC's Decision Process + Paper Process split, but still captured.

Why SPICED works for mid-market SaaS

Three reasons SPICED fits the mid-market SaaS motion better than BANT or MEDDPICC. First, the Critical Event field. BANT asks 'timeline'; SPICED asks 'what forces a decision by that timeline.' In mid-market SaaS, the answer is almost always a specific dated event (quarter-end close, board review, tech migration deadline). Capturing it explicitly gates the rep against forecasting deals with no real urgency.

Second, Impact quantification. BANT's 'need' is qualitative. MEDDPICC's 'Metrics' is quantitative but heavy. SPICED's Impact is mid-weight: quantified but not requiring a board-level metric. An AE can capture Impact in one or two sentences — 'costs us 15 hours/week per rep, roughly $4K/week in lost selling time' — without the formal rigor MEDDPICC expects.

Third, pace. SPICED's five letters can be covered in a single discovery call. MEDDPICC's eight letters usually take two. For mid-market deals that close in 30–90 days, spending two calls on qualification is too slow. SPICED compresses to one good discovery call.

How to run a SPICED discovery call

1. Open with a brief Situation recap based on pre-call research. 'I saw you're a 150-person fintech using Salesforce, running 12 AEs. Is that right?' Confirm, don't learn.

2. Transition to Pain questions. 'Where does your current sales motion break down?' Listen. Follow threads. Don't rush.

3. Drill Impact on every real Pain. 'What does that cost you?' 'When does it hurt most?' 'Who feels it?' Quantify everything.

4. Ask the Critical Event question directly. 'What's forcing a decision by the date you mentioned?' If the prospect can't name a specific event, the timeline isn't real — the rep pleasantly disqualifies and moves on.

5. Map Decision briefly. 'Walk me through how a decision like this happens here.' Capture names and steps. If procurement will be involved, note it.

6. Close with a specific next step tied to a date. Not 'I'll follow up' but 'let's get your VP Engineering on Thursday so we can map security.'

Common mistakes reps make with SPICED

1. Accepting a vague Critical Event. 'We need to move by Q3' isn't a Critical Event. 'Our compliance audit is October 15 and we need this deployed by then' is. Push for specifics.

2. Skipping Impact quantification. Qualitative Pain without quantified Impact doesn't commit to forecast. Always quantify.

3. Treating SPICED like a checklist and rushing through. SPICED works when the rep genuinely listens between the fields, not when they race to fill them. Don't interview — converse.

4. Using SPICED on enterprise deals where MEDDPICC is needed. Above $100K ACV with committee buying, SPICED misses Paper Process and Competition. Upgrade the framework.

How Gangly captures SPICED automatically

Gangly's Live Call Coach watches discovery calls in real time for SPICED signals. When the prospect mentions a quantifiable impact, it tags it as candidate Impact. When they reference a dated business event, it tags it as Critical Event. When they name internal approvers, it populates Decision. The rep sees the flags mid-call and confirms.

After the call, CRM Auto-Population pushes structured SPICED fields into Salesforce or HubSpot. Teams using Gangly report SPICED completeness rising from the typical 50–60% to 80%+ within the first month, with no change to rep behavior beyond confirming auto-captured fields.

See how Live Call Coach works →

Frequently asked questions