SPICED

SPICED is a sales qualification and discovery framework created by Winning by Design for recurring revenue (subscription) businesses. It stands for Situation, Pain, Impact, Critical Event, and Decision, and is used to deeply understand a buyer’s context and desired outcomes so sales, CS, and RevOps can align around measurable business results.

The SPICED Components

• Situation: The buyer’s current state and context (industry, size, team, tools, processes). This is background, not pain.
• Pain: The concrete problems or challenges blocking goals (what’s broken, inefficient, or risky).
• Impact: The quantifiable business effect of the pain (lost revenue, wasted time, missed targets, increased risk).
• Critical Event: The time-bound trigger that makes solving the problem urgent now (budget deadlines, board/exec mandates, contract renewals, competitive threats, launches).
• Decision: How the purchase will be decided (stakeholders, approval steps, criteria, procurement/legal process).

How SPICED Differs from Other Frameworks

• Versus BANT: BANT centers on Budget, Authority, Need, Timeline and is often used to qualify if a deal is worth pursuing. SPICED goes deeper into why the customer needs change and what success looks like, which is better suited to recurring revenue models.
• Versus MEDDPICC: MEDDPICC focuses on complex deal mechanics (Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champion, Competition). SPICED is more customer-outcome-centric, making it easier to carry through from sales into onboarding, adoption, and expansion.

Why SPICED Matters for Recurring Revenue

• It ties discovery directly to business outcomes, not just features.
• It creates a shared definition of success that Sales, CS, and the customer can all reference.
• It supports retention and expansion by documenting the pains and impacts that must be solved to consider the engagement successful.
• It improves handoffs: CS can use the SPICED data captured in discovery to guide onboarding, QBRs, and renewal conversations.

RevOps Use Cases

RevOps can operationalize SPICED by:

• Adding SPICED fields (Situation, Pain, Impact, Critical Event, Decision) to CRM opportunity records.
• Making these fields required at specific stages (e.g., after discovery, before proposal).
• Passing SPICED data into CS tools for handoffs and health scoring (e.g., whether the defined Impact has been achieved).
• Using SPICED data for win/loss analysis to see which pains, impacts, and critical events correlate with higher win rates and better retention.

In practice, SPICED helps teams sell, implement, and support in a way that is tightly anchored to the customer’s real-world business outcomes, not just to closing the initial deal.