Especially useful for
- B2B SaaS discovery
- Sales and customer success alignment
- Qualification centered on customer impact
Discovery12 min min read
SPICED
Connect the problem to impact and the decision
SPICED structures the customer context around Situation, Pain, Impact, Critical Event, and Decision.
Has the prospect described a significant enough impact, a real deadline, and a decision path that explain why the change can move forward?
What the methodology is really designed to establish
Give discovery, handoffs, and customer follow-up a shared language by starting with the impact the customer wants to achieve.
SPICED is Winning by Design’s framework for aligning revenue teams around the customer’s context, impact, urgency, and decision.
To complete when
- Detailed enterprise contracting
- Primarily emotional or consumer-oriented persuasion
What to listen for during the call
A letter isn’t a box to check. It becomes useful when something the prospect says helps distinguish evidence, hypothesis, and what’s missing.
S
Understand the current context
Situation
The situation covers the environment, constraints, priorities, and triggers that explain why the topic is coming up now.
Evidence sought in the call
The prospect describes how things work, a constraint, and the context for the change.
« What has changed recently to make this a priority for you now? »
Strong signal
A trigger and operational context are clearly stated.
Point to watch
The situation becomes an inventory with no connection to the problem.
P
Identify the friction or risk
Pain
Pain is a concrete, observable problem caused by the current situation.
Evidence sought in the call
A difficulty is described with an example, its frequency, or the people affected.
« Where does this situation create the most friction for the team? »
Strong signal
The prospect describes what actually happens and who has to compensate.
Point to watch
The seller reframes a missing feature as a business pain.
I
Measure what the problem changes
Impact
Impact covers the rational and emotional consequences of solving or not solving the problem.
Evidence sought in the call
The prospect connects the pain to an affected outcome, risk, workload, or level of confidence.
« What outcome becomes harder to achieve as long as this problem continues? »
Strong signal
The impact matters to a priority and can be observed or measured.
Point to watch
The seller calculates an impact without the prospect’s validation.
CE
Establish why timing matters
Critical Event
The Critical Event is a deadline, milestone, or external force that creates real urgency.
Evidence sought in the call
A date has a cause, a consequence, and preceding steps.
« What event means things need to be different by this date? »
Strong signal
The cost or consequence of a delay is understood.
Point to watch
The date is a sales-driven wish with no customer-side event.
D
Understand how the customer will choose
Decision
Decision brings together the stakeholders, criteria, trade-offs, and process needed to move forward.
Evidence sought in the call
The prospect describes who is involved, what will be evaluated, and the next decision.
« Who needs to agree on what for the project to move forward? »
Strong signal
A decision path and criteria are clear.
Point to watch
A next step is scheduled without knowing what decision it is meant to produce.
SPICED example: uncovering real urgency
A scale-up is preparing to bring on twelve sales reps and wants to standardize the quality of its discovery calls.
Call objective
Connect the project to a measurable impact, the onboarding event, and the selection process.
Sales rep
S« How do managers currently coach a discovery call that went poorly? »
The current situation is explored in the context of the problem.
Prospect
P« They ask for the notes and sometimes listen to the call again, but everyone has their own approach. »
Inconsistency and manual rework are the pain.
Sales rep
I« How does this inconsistency affect ramping up new hires? »
The call moves from the problem to its impact.
Prospect
« It takes new hires almost three months to work independently. We want to reduce that time and avoid doubling the amount of time managers spend coaching. »
The impact has a current measure and two desired outcomes.
Sales rep
CE« What deadline makes this improvement necessary? »
Exploring the Critical Event.
Prospect
« The new cohort starts on November 4. The program must be selected and tested six weeks beforehand. »
The event and its preceding milestone are confirmed.
Sales rep
D« How will the program be selected, and who will approve the test? »
The decision is connected to the next step.
Prospect
« The enablement lead is running the process, two managers are evaluating it, and the VP of Sales will approve it if the test shows that coaching gets faster. »
Stakeholders, criteria, and process are clearly stated.
What the example demonstrates
The project is not urgent because the seller wants it to be. It is urgent because a new cohort starts on November 4 and a test must take place six weeks before selection.
The diagnosis at the end of this call
A good call summary doesn’t fill in the blanks. It separates what’s established, what’s still uncertain, and what’s missing.
Confirmed
- Situation: inconsistent coaching and manual call reviews.
- Pain: inconsistent methods and manager workload.
- Impact: close to three months to reach autonomy and the risk of doubling coaching time.
- Critical Event: the cohort arrives on November 4.
- Decision: enablement leads the pilot, managers evaluate it, and the VP of Sales approves it.
Uncertain
- The exact target for reducing ramp time has not been agreed on.
- The program budget has not been discussed.
Missing
- Integration requirements are unknown.
- The consequences if the test fails have not been discussed.
The most useful next question
« What level of reduction in coaching time would allow the VP of Sales to consider the test successful? »
Prepare questions without reciting a script
These questions are a resource to draw on. The salesperson chooses the one that responds to what the prospect has actually just said.
Context and pain
Understand how things work before calculating the impact.
- 1What change prompted the search?
- 2Where does the friction arise?
- 3Who is making up for it today?
Impact and urgency
Connect the problem to a time-sensitive priority.
- 1What outcome is affected?
- 2How is it measured?
- 3What event makes the timing important?
Decision
Turn interest into a decision path.
- 1Who owns each criterion?
- 2What decision should the next step lead to?
- 3What milestone comes before the critical event?
Mistakes that make the method feel artificial
Confusing impact with pain
Pain describes what is not working. Impact explains how that affects results or people.
After identifying the problem, ask what consequence it creates and why that matters.
Inventing a Critical Event
A seller's month-end or quarter-end deadline creates no urgency for the customer.
Look for a real event, its consequences, and the milestones that need to come before it.
Focusing only on the contact
A local impact may not be enough to drive a decision across the organization.
Ask who else is affected and which shared priority is involved.
Using SPICED only at the end of the call
Filling in the framework afterward can hide ambiguities that could have been clarified in real time.
Listen for evidence during the conversation and use gaps to choose the next question.
How the method works in Objeqo
The product connection isn’t a magic score. It’s about keeping the context, the quote, and the next question together.
Before the call
The brief can help prepare hypotheses about Situation and Pain, then questions about Impact, Critical Event, and Decision tailored to the context.
During the call
The transcript helps connect pain to its consequences, a date to its cause, and a next step to the decision it should lead to.
After the call
The report can retain a citation-based SPICED summary that is useful for handoffs and preparing for the next call.
Limitation to keep in mind
A date mentioned is not automatically a Critical Event. Its cause and the consequences of a delay must be explicit.
Frequently asked questions
The distinctions to keep in mind before using SPICED on a real opportunity.
What does SPICED mean?
Situation, Pain, Impact, Critical Event, and Decision.
What is the difference between SPIN and SPICED?
SPIN structures the progression of questions toward an explicit need. SPICED organizes customer information around impact, the critical deadline, and the decision.
What is a Critical Event?
A dated event that creates consequences if a change is not ready in time, such as a launch, a regulatory deadline, or a hiring campaign.
Does SPICED replace MEDDPICC?
No. SPICED is very useful for understanding customer context and impact. MEDDPICC takes a deeper look at the Economic Buyer, Champion, Paper Process, and Competition.
Reference sources
Principles verified on August 9, 2026. The call examples are educational scenarios from Objeqo.
A method becomes useful in the conversation
Test your instincts on a real call.
Prepare the context, listen for evidence, and keep missing information visible.