SPICED — Situation, Pain, Impact, Critical Event, Decision

What is SPICED?

SPICED (Situation, Pain, Impact, Critical Event, Decision) is Winning by Design's revenue-architecture framework, designed to be used by the whole customer-facing organisation rather than only by new-business reps. Its distinguishing features are Impact and Critical Event. Impact forces the pain to be quantified rather than described, which is what makes an internal business case possible. Critical Event is the date-bound reason this has to be resolved by a specific moment — a contract expiry, a funding milestone, a compliance deadline, a launch. It is the single best predictor of whether a deal closes in the quarter it is forecast in, because without one, everything slips and nobody is at fault. The other design goal is continuity: because SPICED is used in onboarding and renewal too, the customer is not asked to re-explain their situation to each new person who appears.

When to use SPICED

• SaaS and recurring-revenue businesses
• Teams wanting one framework shared across sales, success and support
• Forecasting, where critical events separate real close dates from hopeful ones

Real examples

• Situation: 'Five SDRs, two team leads, onboarding runs six months.'
• Pain: 'Reps ramp too slowly and a third leave before producing.'
• Impact: 'Roughly $600K of unrealised quota a year.'
• Critical event: 'Eight new hires start in January.'
• Decision: 'VP of Sales signs; finance approves anything above $25K.'

Common mistakes

• Recording pain without impact, leaving nothing for the buyer to justify spend against.
• Inventing a critical event to make a forecast look better.
• Treating decision as a single name when an approval chain exists.
• Using it only in new business, which loses the continuity that is the framework's main advantage.

Want to practice SPICED live? Run a roleplay with an AI buyer.