SPICED Qualification Framework: How It Works, When to Use It, and How It Compares to BANT and MEDDIC

SPICED is a sales qualification framework that structures discovery around five questions: what is the prospect's situation, what pain do they feel, what is that pain costing them, what deadline forces action, and how does the decision get made. It qualifies on need and urgency instead of budget, which is why, in our experience, it tracks close rate more closely than older, budget-led frameworks. Where BANT leads with budget and risks disqualifying good deals early, SPICED leads with pain and impact. The two elements most teams skip, a quantified Impact and a confirmed Critical event, are usually the ones that separate a deal that closes from one that slips. If your pipeline is full but stalling, a GTM audit usually traces the leak to weak qualification at the MQL-to-SQL handoff.

What does SPICED stand for?

SPICED is an acronym for the five things a rep needs to confirm before a deal is genuinely qualified. The order is deliberate: you establish the problem and its cost before you ever discuss how a decision gets made. Skip a step and the deal feels qualified but tends to slip later.

• S, Situation: the prospect's environment, such as team size, tools in use, current process, and how things work today. This is the baseline you measure everything else against. Keep it brief. Reps who linger here burn the call on facts that do not move the deal.
• P, Pain: the concrete problem the prospect feels, not a feature they want but a gap they live with. Pain should be named in their words. If you cannot articulate the pain in a sentence the buyer would agree with, you have not found it yet.
• I, Impact: the quantified business consequence of the pain, such as lost revenue, wasted hours, missed targets, or churn. Impact is where most reps go thin. A dollar figure or a clear metric turns a nice-to-have into a budget-worthy problem.
• C, Critical event: the date or trigger that makes solving this urgent, such as a board meeting, a renewal, a launch, a hiring plan, or a contract expiry. No Critical event usually means no real timeline, and deals without a forcing function tend to be the ones that slip quarter after quarter.
• D, Decision: the decision criteria, the process, and the people involved, such as who signs, who influences, and what steps stand between yes and a signed contract. You earn the right to map the decision only after Situation, Pain, Impact, and Critical event are real.

How does SPICED work on a discovery call?

SPICED is a sequence, not a survey. You move through it in order, and each element earns you the right to ask the next. The goal is a conversation where the prospect builds the business case with you, not an interrogation where you tick boxes. Here is how a typical call flows.

1. Open with Situation, but keep it short. Get the lay of the land: current tools, team structure, and how the process works today. Two or three questions, then move on. Reps who park here for ten minutes train the buyer to expect a passive call.
2. Surface Pain in the buyer's words. Ask what is not working and let them name it. Resist the urge to pitch a feature. If you cannot repeat the pain back in one sentence they would agree with, keep digging. You have not found the real problem yet.
3. Quantify the Impact. This is the step that separates strong reps from average ones. Ask what the pain costs, in lost revenue, wasted hours, missed targets, or churn. A number turns interest into a budget-worthy problem. No number, no real deal.
4. Confirm the Critical event. Find the deadline forcing action: a board meeting, renewal, launch, or contract expiry. A real Critical event creates a real timeline. Deals without one tend to drift from this quarter to next, then disappear.
5. Map the Decision. Only now do you map how the choice gets made: criteria, process, and the people who sign or influence. Establishing pain and urgency first means the buyer is motivated to walk you through their process honestly rather than deflect.

When should reps use SPICED?

Run SPICED on every qualified opportunity and revisit it before each stage advance. It earns its keep most in these situations.

• Running discovery calls on consultative B2B SaaS deals.
• The buyer has multiple options and no obvious urgency.
• Deals keep stalling for vague, hard-to-name reasons.
• Reps qualify on interest instead of costed, time-bound pain.
• You need a running checklist to score deal health in reviews.
• Marketing-sourced MQLs reach sales without validated need.

The highest-value moment for SPICED is the deal review. Score every open opportunity on whether each element is confirmed. The deals missing Impact or Critical event are your likely slip risks: they have interest but no forcing function. If qualification gaps show up across the whole team, that is a systemic problem a GTM audit will surface fast.

SPICED vs BANT vs MEDDIC: what's the difference?

All three frameworks qualify deals, but they make different bets about what predicts a close. BANT bets on budget. MEDDIC bets on a complete enterprise picture. SPICED bets on costed, time-bound pain. Here is how they stack up.

These are not mutually exclusive. Many teams run SPICED for discovery and layer MEDDIC detail onto larger enterprise opportunities. SPICED's Impact maps cleanly to MEDDIC's Metrics, and SPICED's Decision covers both decision criteria and process. The choice is less about which is "correct" and more about matching framework weight to deal complexity. For a deeper look at how the Artemis approach compares to the Winning by Design method that produced SPICED, see Artemis vs Winning by Design.

What problems does SPICED solve that BANT and MEDDIC miss?

SPICED forces the two things reps most often skip and the two things that, in our experience, most reliably signal whether a deal will close: quantified Impact and a confirmed Critical event.

The BANT trap

BANT disqualifies on budget, so deals where the pain is severe but the budget is not yet allocated get dropped. The irony: severe, costed pain is exactly what tends to free up budget. SPICED keeps you in the deal long enough to help the buyer build the case for spend.

The MEDDIC weight

MEDDIC captures everything, which makes it powerful for enterprise but heavy for a first call. It can become an internal scorecard the rep fills in after the fact. SPICED keeps qualification inside the live conversation, so the buyer co-authors the business case.

It forces a real number and a real deadline

Impact demands a cost. Without one, you are forecasting on interest. A pain costed in dollars or hours is often the difference between a deal that survives a budget review and one that quietly dies in procurement. The Critical event is, in our experience, one of the strongest signals of whether a deal closes on time. No forcing function means no urgency, and no urgency means the deal tends to slip. SPICED makes the rep confirm one before forecasting.

What's the difference between an MQL and an SQL?

An MQL is a lead marketing thinks is ready; an SQL is a lead sales has confirmed is ready. SPICED is the bridge between them. A marketing qualified lead becomes a sales qualified lead only after a rep validates real, costed pain and a path to a decision, which is exactly what SPICED checks.

The MQL-to-SQL handoff is where most pipeline quietly leaks. Reps accept MQLs as SQLs without validating need, the forecast inflates, and deals stall mid-funnel. Tightening this handoff with a SPICED checkpoint is one of the cheaper pipeline fixes available. For deeper qualification scoring tied to fit, see our pain-first ICP scoring guide, which pairs naturally with SPICED's Pain and Impact steps. To automate the handoff itself, the Qualification Automation System agent builds the MQL-to-SQL routing with you.

Frequently asked questions about SPICED

Sources and references

The guidance here is directional, drawn from our hands-on GTM engagements and widely used qualification methodology, not a controlled study. Outcomes vary by ICP fit, offer, deal size, and sales process.

• Winning by Design: the SPICED framework and its Situation, Pain, Impact, Critical event, Decision structure.
• BANT and MEDDIC qualification methodology: widely documented frameworks for budget-led and enterprise deal qualification, compared here against SPICED.
• Artemis GTM engagements: how qualification gaps at the MQL-to-SQL handoff show up in real pipeline reviews, drawn from our own implementations.