SPICED

SPICED is a discovery and qualification framework built around five questions a rep must answer before a deal is real: what is the buyer's Situation, what Pain are they feeling, what is the Impact of that pain in dollars, what Critical event forces a decision by a specific date, and what is the buyer's Decision process. Winning by Design popularized it in 2020 as a successor to BANT for subscription businesses where the goal is not just closing but renewing. The framework's spine is impact-and-event: if a rep cannot quantify the cost of inaction and name a date the buyer must act by, the deal is a wish.

How SPICED Is Structured

Each letter is a gate, not a checkbox. Reps answer all five before forecasting a deal as committed.

Impact and Critical Event are the two letters that separate SPICED from earlier frameworks like BANT. Without a dollar figure on the pain, urgency is theatre.

A Worked Example

A SaaS AE selling a $180k contract to a logistics company. Situation: 47 dispatchers using three tools to route 12,000 daily shipments. Pain: 8% of shipments mis-routed each week. Impact: $4.1M in annual refund credits and a 6.2% churn spike on enterprise shippers. Critical Event: contract with current routing vendor auto-renews on 2026-09-30; if not switched 60 days prior, the company is locked in for another year. Decision: VP Operations signs, CFO approves, IT security reviews — 9-week procurement cycle.

That deal forecasts. A deal where the rep has Situation and Pain but no Impact dollars and no Critical Event is a 2027 deal pretending to be a Q3 deal.

When Sales Teams Use SPICED

VPs of Sales install SPICED in orgs where pipeline is bloated with deals that never close — a problem that shows up as a rising no-decision rate and a pipeline coverage ratio above 5x with attainment still missing. RevOps teams encode SPICED fields into Salesforce stage gates so a deal cannot advance to "Proposal" without an Impact dollar value and a Critical Event date populated. Recruiters at Series B and C SaaS companies — where Winning by Design's playbook is gospel — screen AE candidates on whether they can recite the framework and produce a recent deal where each letter mapped to a real artifact.

Founder-led sales teams reach for SPICED when their first AE hires are closing deals they sourced themselves but missing on outbound — usually because the outbound deals lack a Critical Event the rep didn't know to dig for.

Common SPICED Gaming Patterns

The Impact letter gets fabricated more than any other field. A rep multiplies a buyer's headcount by an industry-average productivity loss pulled from a McKinsey blog post and writes "$3.2M annual impact" with no buyer ever having said that number out loud. The Critical Event gets fabricated next: "end of quarter" is not a critical event for the buyer — it is a critical event for the rep. A real Critical Event is something that happens to the buyer whether they buy or not.

The third gaming pattern is rubber-stamping. Reps fill in all five letters with one-line answers to clear the stage gate, then forecast the deal. SPICED only works when a manager pressure-tests the answers — "show me the email where the CFO confirmed the $4.1M figure" — and rejects deals where the artifacts don't exist. Without that pressure, SPICED becomes another set of required fields that everyone learns to satisfy without doing the work the framework was designed to force.