What is SPICED selling? (and how to use it without overthinking)

What is SPICED selling?

Short answer: SPICED is a five-letter qualification framework — Situation, Pain, Impact, Critical Event, Decision — popularised by Winning by Design as a modern, lighter alternative to MEDDPICC. It captures the essentials of B2B qualification for mid-market deals without the procurement-and-paper overhead of MEDDPICC.

For B2B service firms with mid-market deal sizes (£20–100K) and 60–120 day cycles, SPICED is usually the sweet-spot framework. Heavier than BANT, lighter than MEDDPICC.

TL;DR — the five letters

A deal where you can answer all five is forecastable. Below 3 of 5, the deal is in your pipeline as a hopes folder, not a real deal.

Going through each letter

S — Situation

The current state of the buyer's world, in their own words and with enough specificity that you understand the context.

Bad version:

They're a mid-sized B2B company.

Good version:

65-person IT services firm, founded 2012, growing 30% YoY, recently hired a Head of Sales after the founder stepped back from day-to-day. Currently 4 AEs, 1 SDR, HubSpot CRM, Apollo for prospecting. Mostly inbound; want to add outbound discipline.

Situational specificity is the foundation. Without it, the rest of the framework floats on assumptions.

P — Pain

The specific problem the buyer is solving. Not a polite version — the actual operational pain.

Bad version:

They want to grow.

Good version:

Win rate dropped from 35% to 22% over the last 12 months. The new Head of Sales says the team has stopped qualifying — too many discovery calls with prospects who never had budget. Reps are burning out. The founder is back in the seat closing deals he should have moved on from.

The discovery question: "What happens if you do nothing about this?" produces a more honest pain articulation than "what is your pain?"

I — Impact

The cost of the pain, ideally quantified.

Bad version:

The pain is significant.

Good version:

The 13-point win rate drop on £25K average deal size translates to roughly £450K of lost ARR annualised. The founder's time back in the seat costs the company another £200K-equivalent of his product work. Internal estimate: £650K/year of cost from the broken process.

If the buyer cannot articulate Impact, they cannot defend the spend internally — which means the deal will stall at procurement no matter how strong the discovery feels.

C — Critical Event

The forcing function. The reason this decision is happening this quarter, not next.

Bad version:

They are thinking about this for next year.

Good version:

The new Head of Sales has a 90-day plan to show progress, deadline end of next quarter. Either she demonstrates pipeline improvement by then or she becomes the one being moved on from. This is the only reason the discovery call happened — there is genuine urgency, not exploratory shopping.

Critical Event is the single most-skipped letter in SPICED practice. Reps love the deal and assume the urgency. Surfacing the actual critical event reveals which deals will close this quarter versus which deals will drift to "let's revisit in 6 months."

D — Decision

How and when the buyer will decide, with named stakeholders.

Bad version:

They will decide in a few weeks.

Good version:

Discovery this week (head of sales). Demo next week (head of sales + CEO). Reference call third week (head of sales calls one of our customers). Final decision fourth week, formal sign-off from CEO. Signed by end of month, work starts the following Monday. CEO is the Economic Buyer; Head of Sales is the Champion.

A clear Decision is the foundation of a forecastable date. Without it, "next month" is wishful.

SPICED versus MEDDPICC versus BANT

For most B2B service firms running 4–10-person sales teams against mid-market buyers, SPICED is the right choice. It is fast enough to use on every deal and substantive enough to drive forecasting.

Embedding SPICED in the CRM

A typical CRM implementation:

The SPICED score becomes the gate for forecast category eligibility:

Common SPICED mistakes

Mistake 1: Asking the questions in order. Reps work down the five letters mechanically. The buyer feels interrogated. Real SPICED discovery moves around — Pain often comes first, Situation often emerges in pieces.

Mistake 2: Treating Impact as optional. Without Impact, the deal cannot survive procurement. Reps who let Impact stay vague produce a pipeline that looks healthy but breaks at the commercial stage.

Mistake 3: Inventing Critical Event. A rep is desperate to forecast and writes "fiscal year end" as the critical event when there is no real urgency. The deal slips. Every time.

Mistake 4: Decision Process documented without dates. "They will decide soon" is not Decision. Specific stakeholders, specific dates, specific signature pathway.

For UAE & KSA teams

Regional adjustments to SPICED application.

• Situation needs to include relationship context. "Who introduced us, who has the existing vendor relationship, who has approval authority above the buyer's title" — all part of Situation in GCC contexts.
• Critical Event is often softer. GCC deals are less likely to have a sharp "must decide by date X" event than Western equivalents. Acceptable substitutes: budget cycle timing, fiscal year boundary, an upcoming senior leadership review.
• Impact in regional terms. Use AED/SAR for Impact quantification, not GBP/USD — the magnitude resonates more with regional buyers in local currency.
• Decision Process is longer. Three to five named stakeholders is normal for GCC mid-market. Add explicit Paper Process notes (often missing from pure SPICED) when procurement is involved.
• Champion strength matters more. A GCC deal with no champion is structurally weaker than the same deal in the UK or US. SPICED should be supplemented with a "Champion strength 1–5" field in GCC deployments.

What MAVEN does about it

SPICED installation is part of the Sales Process Program for mid-market clients. We configure CRM fields, train the team on the question banks, and run the first 4–6 pipeline reviews using SPICED to bed in the discipline.

The Sales OS Blueprint covers SPICED in the broader architecture context.

Frequently asked

SPICED or MEDDPICC for my team?

SPICED for £20–100K deal sizes with 60–120 day cycles. MEDDPICC for £200K+ with 6+ month cycles and formal procurement.

Can I run SPICED on long-cycle deals?

You can, but add Paper Process and Competition as supplementary fields. At that point, you have re-invented MEDDPICC.

Is SPICED the same as the Winning by Design "GTM" framework?

SPICED is part of Winning by Design's broader methodology, yes. The framework itself is now widely adopted independently.

How long does SPICED adoption take?

4–8 weeks for a team to move from no framework to SPICED-default discovery. Faster than MEDDPICC because the framework is lighter.

Should every deal have a SPICED score?

Every deal past Discovery, yes. Pipeline-stage deals do not need full SPICED yet.

---

Post 25 of our outbound + sales OS series.

Related reading

• What is a sales operating system?
• What is MEDDPICC?
• How to forecast B2B sales accurately
• How to build a B2B sales pipeline from scratch
• Healthy pipeline coverage ratio
• Sales discovery questions that work