SPICED Sales Framework: The 5 Letters, Rep Scripts

What the SPICED sales framework is (the one-paragraph answer)

Start with the problem SPICED solves before you memorize the acronym. A rep finishes a discovery call feeling great — the prospect was engaged, the demo is scheduled, the champion sounds enthusiastic. Three weeks later the deal ghosts. Post-mortem: nobody ever confirmed there was a hard deadline, nobody verified who signs the MSA, and the business pain was described in vague terms that Finance never ratified. SPICED is the framework that stops that pattern.

The plain definition: SPICED is a B2B sales qualification framework. It gives the rep five specific checkpoints to verify on every deal — Situation, Pain, Impact, Critical Event, Decision. Each letter is a condition. Miss one, and the deal is not qualified. Hit all five with honest scores, and the forecast is honest.

The framework was created by Jacco van der Kooij and the Winning by Design team to address a specific gap in existing methodologies: most qualification frameworks were built for the initial sale and assumed a transactional close. SPICED was built for SaaS, where the initial sale is only the beginning — customer success, renewal, and expansion are equally important stages, and a shared qualification language across the whole revenue team produces better outcomes than a framework only the AE team uses.

The framework sits in a specific lane. SPICED is not a selling methodology — it does not teach how to pitch, handle objections, or structure a narrative. It is not a discovery technique — it does not prescribe what questions to ask. SPICED is pure qualification: what has to be true before this deal belongs in the forecast. It is compatible with any selling methodology, which is why teams run it alongside Challenger, Sandler, or SPIN — those methods govern the conversation style; SPICED governs what the rep verifies by the end.

Adoption reflects the design. SPICED has become the dominant qualification framework for B2B SaaS teams, particularly at companies with average contract values between $15K and $200K ACV where the deal is too complex for BANT but not complex enough to justify full MEDDPICC overhead. The five letters match the five questions every SaaS deal forces a rep to answer eventually — SPICED just forces the answers at discovery, not at the final-week slip.

The 5 letters of SPICED: definitions, rep scripts, and watch-outs

Here is the rep-ready breakdown. Each letter gets a plain definition, a rep script that works in a live discovery call, and the failure mode that kills the qualification when the letter is shallow. Read these once, then stop reading SPICED overviews and start running the framework on your next deal.

The five letters are a sequence, not a checklist. Situation provides context that makes Pain credible. Pain anchors the call — everything else amplifies or acts on Pain. Impact converts Pain into a business case. Critical Event gives the business case a deadline. Decision turns the deadline into a mapped path to signature. Break the sequence and you end up with five boxes and zero qualification.

The two letters reps most often rush are Critical Event and Decision. Situation and Pain feel like conversation — they flow naturally. Impact takes a push but most reps have a quantification question. Critical Event and Decision feel like closing pressure, so reps save them for the end of the call and run out of time. Reverse this. Get to Critical Event and Decision by minute 35. The conversation that follows is where the real qualification happens.

One more note on the D letter: Decision is doing double duty. It covers both the decision process (the steps, timeline, and people involved in evaluation) and the decision-maker (the economic buyer who can approve and fund the deal). Some SPICED practitioners split D into two checkpoints in their internal scoring. If the deal is above $75K ACV, that split is worth making explicit in the discovery notes.

SPICED vs MEDDIC vs BANT: which framework fits which deal

Three frameworks, three contexts. Reps switching jobs, getting onboarded, or inheriting a new stack encounter all three — and end up running a confused hybrid that does not qualify anything cleanly. Here is how they actually differ and which one wins for which deal type.

The practical rule: use the framework that matches your deal shape. A $30K SaaS deal with a 45-day cycle, two stakeholders, and a subscription model should run SPICED from discovery to close. A $300K enterprise deal with six buying committee members, a separate security review, and three competing vendors should run MEDDIC or MEDDPICC for pipeline inspection and can layer SPICED for the discovery conversation style. BANT belongs only at the SDR-to-AE handoff — it is a gate, not a qualification framework.

The biggest mistake is treating the frameworks as competing philosophies. SPICED and MEDDIC have significant overlap — both care deeply about pain, impact, and decision-makers. Where they differ: SPICED adds Critical Event as a first-class letter (MEDDIC addresses urgency indirectly through pain), and SPICED is designed for the full customer lifecycle rather than just the initial sale. A team that has SPICED trained into their discovery motion and MEDDIC built into their pipeline inspection stage is running both efficiently.

If the team can only pick one: pick SPICED for a SaaS team under $150K ACV and pick MEDDIC for an enterprise team above $200K ACV. The ACV range between $150K and $200K is where both frameworks work and where the deal complexity usually makes the decision. Deals with buying committees above four stakeholders tend to benefit from MEDDIC's Economic Buyer and Champion specificity; deals with shorter cycles and clearer stakeholder maps run fine on SPICED.

How to run SPICED in a 45-minute discovery call

A SPICED discovery call is not five sequential interrogations. It is a conversation with a framework underneath — the rep is always aware of which letter is being filled, but the prospect experiences a natural dialogue about their business. Here is the minute-by-minute breakdown for a 45-minute first discovery call.

Three things the timeline above assumes: the rep did pre-call research on Situation before the meeting started (not live on the call), the prospect knows why they are on the call (the rep sent a brief agenda in the calendar invite), and the rep has a shared document open during the call so both parties can see the notes in real time. Without these three conditions, the 45 minutes compresses and the rep runs out of time before reaching Critical Event and Decision.

The most common failure mode: the rep spends 20 minutes on Situation because the prospect is talkative and context-rich, leaves 10 minutes for Pain and Impact, and never reaches Critical Event or Decision. The call ends with a demo scheduled but zero qualification. The fix is not cutting the prospect off — it is pre-loading Situation from LinkedIn, the company website, and recent news before the call, so the live time can focus on Pain, Impact, Critical Event, and Decision.

Two questions are worth rehearsing until they are automatic. For Critical Event: "Is there a date by which this needs to be solved — and what happens to this initiative if that date slips?" For Decision: "Walk me through how a decision like this gets made — who evaluates it, who approves it, and who would sign?" These are the two questions most reps have not practiced because they feel like closing questions rather than discovery questions. They are both. Run the discovery call framework built for SaaS AEs to see how these questions fit into the broader flow.

The SPICED Prep Method: Gangly's rep-side approach

Every rep who runs SPICED has the same problem: the framework tells you what to capture, but most reps capture it inconsistently, in different formats, at different times after the call — which means the CRM reflects the rep's memory, not the prospect's actual words. Forecast reviews become a negotiation between what the rep thinks happened and what the manager thinks should have happened.

The SPICED Prep Method is Gangly's five-step approach to running SPICED before, during, and after every discovery call — so the framework is not just a qualification checklist but a live workflow wired into the rep's daily motion.

The key difference between the SPICED Prep Method and running SPICED as a post-call exercise: Step 2 (pre-mapping Pain and Impact) turns a 20-minute Situation segment into a 7-minute context confirmation. The rep walks in with a hypothesis — "based on your recent hiring activity and the two-year-old tech stack, I expect the pain is around rep ramp time and manual CRM updates" — and tests it in the first five minutes rather than discovering it in minute fifteen. That hypothesis shortens the S segment, sharpens the P segment, and gets the rep to Critical Event and Decision with time to spare.

Step 4 (scoring each letter 0–5 after the call) produces a deal health score between 0 and 25. A score below 15 means the deal is not qualified — there are gaps that need to be closed in the next interaction before the deal belongs in the forecast. Gangly's call workflow engine surfaces these gaps automatically, so the rep sees which letters are incomplete before pipeline review — not during it.

Metrics that prove SPICED is actually working

A framework without measurable outcomes is a philosophy, not a tool. Here are the four metrics that tell you whether SPICED is working in your pipeline — and what the benchmarks look like for teams that run it with real-time capture versus teams that fill it in post-call.

Forecast accuracy is the headline metric because it is the one the VP Sales and CRO live and die by. A team with ±40% forecast accuracy is essentially guessing — the pipeline call is theater, and the quarter ends with surprises. The Critical Event and Decision letters are the drivers of forecast accuracy: once both are verified with evidence, the deal has a real close date and a real approver, and the only variables left are execution.

Average deal size growth (+17%) is the metric that surprises most teams. The mechanism is Impact quantification: a rep who pushes the buyer to assign a dollar value to the pain surfaces the full scope of the problem — which often includes adjacent teams, second-order effects, and annual cost projections the rep's initial proposal did not address. A quantified Impact statement of $850K annually justifies a $120K contract far more easily than "we spend too much time on manual work." Bigger Impact, bigger budget conversation, bigger deal.

Track the SPICED completion rate per deal alongside these four outcome metrics. A 95% completion rate with flat win rates means reps are filling fields without verifying the underlying criteria — a common pattern when SPICED is installed as a CRM form rather than a live discovery practice. The completion rate is a leading indicator; the win rate is the outcome. Both need to move together for the framework to be working.

For further context on how sales qualification metrics feed pipeline health, see the guide on sales call metrics — particularly the section on deal health scoring and how to structure a pipeline review that surfaces gap letters rather than stage labels.

Seven mistakes reps make when running SPICED

SPICED fails at the implementation layer, not the framework layer. Here are the seven patterns that kill SPICED adoption in the first 90 days — and the fix for each.

The root cause behind most of these mistakes is the same: SPICED was rolled out as a training event rather than wired into the daily workflow. Training changes knowledge; workflow changes behavior. A rep who learns SPICED in a two-hour session and then returns to a CRM that has no SPICED fields, call notes that have no letter structure, and a pipeline review that asks "what stage is this?" instead of "what letters are missing?" will revert to previous habits inside two weeks. The framework only sticks when the infrastructure around the rep reflects the framework — every tool, every review, every coaching conversation.

If the team is currently running a discovery call checklist without a qualification framework underneath it, SPICED is the natural next layer to add — the checklist governs the call structure, SPICED governs what the call needs to produce. Start with the two highest-value letters for the first 30 days: Pain and Critical Event. Once those are captured consistently, add Impact and Decision. Situation usually takes care of itself once the other four are disciplined.