The SPICED sales methodology: questions, a worked example and when to use it

This page is for SDRs and account executives running discovery, and for revenue leaders who want one shared way to record deals from first call through renewal. It covers what each letter means, questions for each, a worked example built around a real regulatory deadline, and how SPICED compares with BANT and MEDDPICC.

What SPICED is and where it came from

SPICED comes from Winning by Design, a sales and revenue consultancy, which calls it its "industry-standard framework for aligning revenue teams around a repeatable, scalable approach to growth." Winning by Design says the framework is built from its work with thousands of B2B organizations and that more than 25,000 professionals have been trained on it. Its own pages don't give a creation date, so we don't guess one.

Two things set SPICED apart from older qualification acronyms. It's built for diagnosis: Winning by Design describes it as replacing "surface-level qualification." And it's meant to run past the signature, with a shared way of "capturing and transferring customer context across Sales, CS, and Account Management." That makes it a natural fit for subscription businesses, where the second and third years of a contract are worth more than the first.

The five letters

Situation is the letter you can mostly fill before the call. Company size, locations, systems, recent hires and news are usually public, and account research covers where to look. At volume, Bebop does that research for each account in a list, so call time goes on pain, impact and the critical event.

Questions for each letter

SITUATION
I read that you [fact from research]. How has that changed things for your team?
Walk me through how [the process] works today. Who's involved?
What's changed in the last year that made you look at this?

PAIN
Where does that process break down?
When did it last cause a real problem? What happened?
Who notices first when it goes wrong?

RATIONAL
What does that cost when it happens: hours, money, customers?
How often does it happen? What does a year of it add up to?
If it were fixed, what would you do with that time or money?

EMOTIONAL
How is this landing with [your manager / the owner / the board]?
What does it mean for you if it's still like this next year?

CRITICAL EVENT
Is there a date this has to be solved by? What happens if it slips?
Is that date set by you, or by someone outside (a customer, a regulator, a contract)?
What has to be true by then, and what has to happen first?

DECISION
Who else will be involved in choosing, and what does each care about?
How will you judge which option is best?
What steps happen between now and a signature, and how long do they usually take?
Who could stop it, even if everyone else agrees?

Is it really a critical event?

Most deals that slip had a "critical event" that was really a hope. Test the date before you forecast on it.

Worked example: working back from a regulatory deadline

Illustrative example. The companies, people and figures are invented. The CMMC dates and rules are real and sourced below; this is not compliance advice.

The seller: Keystone Secure (keystonesecure.example), a cybersecurity managed service provider. The buyer: Tri-County Precision (tricountyprecision.example), a 65-person CNC machine shop that makes parts for defense primes and handles controlled unclassified information (CUI) such as drawings. The call: April 2026, with the owner and the quality manager.

Situation. Under the Department of Defense's CMMC Program rule (32 CFR part 170), CMMC requirements are phased into contracts. Phase 1 began when the complementary acquisition rule took effect on 10 November 2025. Phase 2 begins one calendar year later, 10 November 2026, when DoD intends to require Level 2 (C3PAO) status, meaning a third-party certification assessment, as a condition of award for applicable contracts. Level 2's security requirements are identical to NIST SP 800-171 Revision 2. Tri-County's largest prime has told suppliers it expects certified Level 2 status for a program solicitation due 1 December 2026.

Pain. Tri-County submitted a self-assessment in 2025 but knows it has gaps: shared logins on shop-floor PCs, no multifactor authentication on email, and no written system security plan. The quality manager owns compliance on top of her day job.

Impact.

The margin at risk is about 6.3 times the year-one cost ($924,000 ÷ $146,800). The emotional stakes: the owner founded the shop, and 18 machinist jobs depend on the defense work.

Critical event, worked backward. The quality manager and Keystone built the plan from the bid date using her estimates of each step:

So the real decision date was 9 June 2026, almost six months before the bid and only weeks after the first call. That changed the conversation from "sometime this year" to "this month."

Decision. The owner signs; the quality manager recommends; the prime's supplier quality team will review the plan. Criteria: experience with NIST SP 800-171 work, a fixed remediation price, and support during the assessment.

What made this work: the critical event was external, written down and tied to a named loss. Working backward turned a deadline almost eight months away into a decision date within weeks.

Recording SPICED and handing it over

SITUATION: [context and why now, with sources]
PAIN: [problem in their words] (example: [date, what happened])
IMPACT, RATIONAL: [amount per year] = [arithmetic]
IMPACT, EMOTIONAL: [who cares, and why]
CRITICAL EVENT: [date] because [who set it]; if missed: [consequence]
DECIDE BY: [date, worked back from the critical event]
DECISION: signer [name]; recommends [name]; can block [name]
CRITERIA: [1] [2] [3]
NEXT STEP: [what, who, date]

At the handoff to customer success, the impact line becomes the success measure and the critical event becomes the first milestone. In the example, success is "certified before 1 December," not "onboarded."

Scoring and decision rules

Score each letter 0 (unknown), 1 (seller's belief) or 2 (confirmed by the buyer), for a maximum of 10. These rules are our guidance, not Winning by Design's.

• 8 to 10: forecast it, with the decision date worked back from the critical event.
• 5 to 7: keep discovering; the lowest letter is the next call's agenda.
• 0 to 4: early stage; don't forecast it.
• Critical event at 0 or 1: don't put it in this quarter's forecast, however strong the other letters.
• Impact smaller than your price: you've missed something, or it isn't a fit.

When SPICED fits and when it doesn't

SPICED compared with other frameworks

Common mistakes

• Filling the letters from your own assumptions. If the buyer didn't say it, mark it unconfirmed.
• A soft critical event. "End of quarter" is your deadline, not theirs.
• Impact without arithmetic. "Big problem" isn't impact. Write the sum.
• Stopping at the signature. The point of SPICED's shared language is the handoff. Use it.
• Using it as a script. Run the conversation naturally and fill the letters afterward.

Next step: prepare your next discovery call with the free sales call planning template.