SPICED Framework: Situation, Pain, Impact, Critical Event, Decision

By Calvin D. · Updated Oct 12, 2026

SPICED is a sales discovery framework from Winning by Design. It organizes what a rep learns about a prospect into five parts: the Situation, the Pain, the Impact of solving it, the Critical Event that sets a deadline, and the Decision process behind the purchase. Winning by Design describes it as a way to diagnose prospects, like a doctor, before prescribing a solution.

This article covers what each letter means, how SPICED differs from BANT, CHAMP, MEDDIC, NEAT and ANUM, how to run a SPICED call step by step, and a template you can copy into your CRM.

What is the SPICED framework?

The SPICED letters stand for Situation, Pain, Impact, Critical Event, Decision. Yes, that's five ideas behind six letters: the "CE" in the middle is one concept, Critical Event.

Winning by Design's blueprint frames the purpose clearly. The goal is to solve the source of a prospect's pains, not just the symptoms, so the recommendation fits the outcome the buyer wants. That makes SPICED a diagnosis sequence more than a checklist. You're not scoring a lead against fixed gates. You're building a picture of the customer's world and then connecting your product to the parts of it that hurt.

Three things set it apart from older qualification acronyms:

• It starts with the customer's context. BANT opens with budget. SPICED opens with the facts of the prospect's business.
• It treats impact and timing as separate questions. Many frameworks fold urgency into one letter. SPICED asks what the problem costs, then asks what date makes it urgent.
• It's built for handoffs, not just calls. The blueprint says teams can use it to gather information on calls, to pass context between teams (prospecting to sales, sales to customer success), and to summarize deals in internal forecasting meetings.

On origin: Winning by Design lists itself as the publisher of the framework, with a SPICED framework page dated April 2022. The framework is aimed at recurring-revenue selling, and the blueprint's own journey diagram runs from awareness and education through selection, onboarding, use and growth, which is why it extends past the first sale.

The five SPICED elements

S is for Situation

Situation is the facts, circumstances and background of the prospect. The blueprint says it covers the tools, people, industry and landscape of the company, and it helps you judge the size of the opportunity and whether the prospect is a good fit.

Situation questions are mostly closed and factual:

• How many people are on the team, and where are they based?
• What system do you use for this today?
• I saw you're hiring for a group of reps. Did I read that right?

The blueprint's advice on call flow is to keep closed questions to a short run, then move to something richer. Research before the call so you aren't asking things the prospect expects you to know. Treat this as the ground floor: necessary, but a call that stays here feels like an interview.

P is for Pain

Pain is the challenge that brought the prospect to the conversation. The blueprint notes it can be emotional (frustration with a current process) or rational (company-level issues like cash flow, costly mistakes or generating pipeline).

Useful pain questions ask for process, not opinion:

• Walk me through how your team handles this today.
• Where does that break down?
• Who feels it first when it does?

The distinction to hold onto is symptom versus source. "Our reports are late" is a symptom. "Three systems hold the numbers and nobody owns the merge" is closer to the source.

I is for Impact

Impact is what the pain does to the business, and what the buyer gains by fixing it. According to the blueprint, rational impacts typically fall into three groups: increasing revenue, decreasing cost, or improving the customer experience. It also reminds reps not to overlook the emotional impact on the individual.

This is the letter that turns a complaint into a business case. Ask questions like:

• How does that affect your ability to hit the target you own?
• What happened the last time this went wrong?
• If this were solved, what would change for your team?

Get the buyer to supply the numbers. A cost the buyer states and defends is their business case. A cost you calculate on your own is your estimate.

CE is for Critical Event

Critical Event is the deadline by which the impact has to be achieved. The blueprint warns reps against confusing their own critical event (hitting quota this quarter) with what the customer is actually driving toward. It also gives a simple test: when the prospect names an important date, ask what happens if they miss it.

If the answer has teeth (a board meeting, a compliance deadline, a contract ending, a hiring wave), you've found a real critical event. If the answer is "nothing, really," you have a preference, not a deadline.

Questions that help:

• Why is that date important to you?
• What happens if you don't have a solution by then?
• What else is happening around that time?

D is for Decision

Decision covers the process, the committee and the criteria. The blueprint stresses that purchases are usually made by a group of stakeholders rather than one person, and that depending on deal size you may need to map who is involved, who signs off, which approvals come in what order, and how the buyer will evaluate options.

Ask early, and ask in parallel:

• How does your buying process work from here?
• Who else needs to weigh in, and what do they care about?
• Are there reviews we should start now, such as legal, procurement or security?
• Have you brought in a tool like this before?

SPICED does not run in a straight line

The letters read in order, but conversations don't. The blueprint says the Impact and Critical Event parts are not always uncovered in order. A prospect who already knows they have a problem and has studied the options may state their desired outcomes and deadline on the very first qualification call. Others reveal them over several discovery meetings.

So use SPICED as a map of what you need to learn, not a script of what to ask next. Capture whatever surfaces, note which letters are still empty, and steer the next question toward the gap.

The blueprint also sketches a rhythm for the call itself: summarize and ask if you got it right, empathize when a prospect vents (and ask them to prioritize), and avoid jumping to a pitch too early because a solution pitch often results in disengagement.

SPICED vs BANT, CHAMP, MEDDIC, NEAT and ANUM

All of these are ways of deciding whether a deal is real and how to advance it. They differ in where they start and how much of the buying process they try to map.

A few practical contrasts:

• SPICED vs BANT. BANT asks whether the buyer has money and authority. SPICED asks what the business looks like, what hurts and what it costs. You'll still learn about budget, but through Impact and Decision rather than as an opening gate.
• SPICED vs MEDDIC. They overlap more than the names suggest. MEDDIC's Metrics and Identify Pain map to Impact and Pain, and its Decision Criteria and Decision Process map to Decision. SPICED adds a Situation step and a Critical Event; MEDDIC adds an explicit Champion and Economic Buyer. Teams often use SPICED for discovery and MEDDIC to run a large deal.
• SPICED vs CHAMP and NEAT. All three are problem-first. SPICED is wider, because it records the setting before the problem and keeps Impact and timing as separate fields.

For a broader comparison, including selling styles like gap selling, see sales methodologies compared. For keeping time-starved buyers engaged once discovery is done, SNAP selling is a useful companion.

How to run a SPICED discovery call, step by step

1. Research first. Read the prospect's site, recent news and job postings. Situation questions should confirm what you know, not collect it from scratch.
2. Confirm the Situation briefly. Ask a handful of factual questions, then summarize back what you heard.
3. Move to Pain. Ask how the work happens today and where it breaks. Listen for both the rational and emotional version.
4. Ask for Impact. Ask what the pain does to a number the buyer owns. Write down the buyer's own words and figures.
5. Test the Critical Event. When a date appears, ask what happens if it's missed. Record the date and the consequence.
6. Map the Decision. Ask about process, committee, criteria and any reviews that should start in parallel.
7. Summarize and check. Read the five parts back and ask whether you got it right. Fix anything the buyer corrects.
8. Propose the next step. Only now tie your product to the pain and impact you recorded. Book the next meeting with a named person.
9. Write it down where the team can see it. The same notes should support a handoff to an implementation team and a deal inspection.

SPICED opportunity notes template

Winning by Design's blueprint includes an opportunity matrix with rows for Situation, Pain (quantifiable and qualitative), Impact, Critical Event, a Compelling Event, Decision (criteria, plus process and committee), Status Quo, Competitors and Next Steps. Here's a simplified version you can paste into a CRM note or deal review doc.

A quick quality check: if any of Pain, Impact or Critical Event is empty, the deal probably belongs in discovery, not in a late-stage forecast category.

SPICED examples by scenario

These are illustrative situations, not case studies.

Inbound lead from a content download. A manager asks for a demo. Situation is clear (team of 12, spreadsheet-based tracking). Pain is vague. A SPICED call spends its time on Pain and Impact: what breaks, who notices and what it costs. If no real pain emerges, the lead goes to nurture.

Renewal with expansion. A customer wants more seats. Situation and Pain are known. The open fields are Critical Event (a budget cycle or a project launch) and Decision (who approves an expansion versus a renewal). SPICED notes also give the account owner a clean handoff to the customer success team.

Enterprise security purchase. The blueprint's own example involves a company with several offices, a board-driven compliance deadline, and a signing authority threshold. Decision is the heavy part: committee, approvals, contract review. A rep would layer MEDDIC-style stakeholder mapping on top of SPICED here.

Services engagement. A consultant learns the client has a regulatory deadline (Critical Event) but no quantified Impact. The next step is a short scoping exercise with the client's finance partner to put a number on the cost of delay.

Outbound to a cold account. The contact replies but can't describe a problem. That's an empty Pain field, and SPICED gives the rep a reason to close the opportunity early rather than carry it as pipeline.

SPICED do's and don'ts

Do:

• Research before the call so Situation questions are quick.
• Ask for numbers and let the buyer say them out loud.
• Test every deadline with "what happens if you miss it?"
• Map the Decision process early, including parallel reviews.
• Use the same fields for call notes, handoffs and forecast reviews.
• Follow a qualified deal with a shared plan such as a mutual action plan.

Don't:

• Treat the letters as a script. Ask in the order the conversation allows.
• Pitch the moment you hear a pain. Finish Impact and Critical Event first.
• Mistake your quota date for the customer's deadline.
• Assume the person on the call makes the decision.
• Accept an Impact figure you built alone as the buyer's business case.
• Leave fields blank and still call the deal qualified.

Where SPICED falls short

SPICED is a discovery and documentation framework. It tells you what to learn and record, but it doesn't give you a scoring rule, stage definitions or a forecasting method. Teams that want pass/fail rules should pair it with explicit opportunity qualification criteria, such as minimum evidence for each letter before a deal advances. It also doesn't name a champion or cover competitive positioning in depth, which is where MEDDIC or the Challenger Sale add structure on larger deals.

Key Facts

• What it is: a five-part sales discovery framework: Situation, Pain, Impact, Critical Event, Decision.
• Publisher: Winning by Design, in its SPICED blueprint.
• Purpose: diagnose the source of a prospect's pain before prescribing a solution.
• Impact categories: increase revenue, decrease cost or improve the customer experience, plus emotional impact on the individual.
• Critical Event test: ask what happens if the prospect misses the date.
• Order: Impact and Critical Event don't always surface in sequence, so treat the letters as a map.
• Best for: consultative and recurring-revenue sales where context and handoffs matter.

For the wider context, see opportunity qualification and the original BANT framework.