SPICED in the Real World: A Practical Guide for B2B Sales Discovery

There are methodologies that help structure conversations.

And there are methodologies that help protect deals.

Understanding the difference explains how I view the SPICED framework, one of the most popular discovery models used in modern B2B SaaS sales.

SPICED stands for:

• Situation

• Problem

• Impact

• Critical (or Compelling) Event

• Decision

It was popularized by Winning by Design and is now widely used in SaaS organizations to guide sales discovery conversations and align discovery with the stages of the sales process.

On the surface, SPICED feels practical. It mirrors how buyers move through a problem, and compared to frameworks like SPIN, it replaces the abstract “Need Payoff” with something more commercially real: a critical event that creates urgency.

But over time I’ve come to see SPICED differently.

I use it frequently in conversations.

I do not rely on it to qualify large deals.

And that distinction matters.

Sales Methodology vs Qualification Methodology

In many sales teams these two concepts get mixed up.

They shouldn’t.

A sales methodology helps structure conversations with a buyer. It guides how discovery unfolds across meetings, how a rep asks sales discovery questions, and how the conversation moves from context to problem to impact.

A qualification methodology, however, is different.

It helps assess risk across the entire deal lifecycle. It answers questions like:

• Where could this deal fall apart?

• What information is still missing?

• What risks must be mitigated before we proceed?

This is where frameworks like MEDDIC shine. They separate different risks clearly—decision criteria, economic buyer, champion, decision process.

SPICED compresses most of those risks into one letter: D for Decision.

For smaller deals that simplification works.

For complex deals, it becomes dangerous.

Because when a deal stalls, the reason usually isn’t “decision” in general. It’s something specific:

• A weak champion

• No access to the economic buyer

• Decision criteria favoring a competitor

• A misunderstood procurement process

If those risks aren’t separated, they remain blurry.

That’s why I think of SPICED as a conversation framework, not a full qualification framework.

The Buying Journey Changes How SPICED Works

Another reason SPICED needs nuance is that buyers enter conversations at different stages.

Some are problem unaware.
Some are problem aware.
Some are already solution aware.

Outbound and inbound conversations therefore look very different.

In outbound sales

Many prospects don’t even perceive a problem yet.

Take something like manual call note-taking.

For years sales teams joined calls, wrote notes, and transferred them into a CRM afterwards. It was simply “how things worked.”

Only when automated call recording and note tools appeared did many teams suddenly realize something:

“This friction we accepted for years can actually disappear.”

That’s the shift from problem-unaware to solution-aware.

Understanding that transition matters because it changes how discovery works.

The Open-Question Myth in Sales Discovery

Sales advice often says: always ask open questions.

In reality, that’s an oversimplification.

Some open questions are powerful.
Others are simply lazy.

For example:

“What are your challenges?”

This question creates cognitive load. It signals that the rep hasn’t done homework. And it forces the buyer to decide which problem is relevant to mention.

Closed questions, when framed well, can be stronger.

For instance:

“Typically companies your size struggle with either A, B, or C. Which one resonates most with your reality?”

Technically it’s closed. But it provides context and shows expertise.

Good sales discovery questions reduce mental effort for the buyer while still creating insight.

The key variable isn’t open vs closed.

It’s relevance and trust.

S — Situation: Why I Rarely Start There

Both SPICED and SPIN begin with Situation.

In theory that makes sense.
In practice it often leads discovery in the wrong direction.

Imagine a typical outbound scenario.

An SDR books the meeting.
An AE runs the first call.

The AE begins with situational questions:

• How many reps do you have?

• How many calls per week?

• Do you record calls today?

• How do reps enter CRM data?

These questions are factual.

They are also egocentric.

They help the seller understand the setup but offer little value to the buyer. Early in the call—when trust is limited—these questions feel extractive.

I think of this as spending trust credits.

Every question asks the buyer to give something. If those questions don’t return value, engagement drops quickly.

That’s why I rarely start with Situation.

Problem Is Usually the Real Starting Point

In most outbound conversations, the real entry point is Problem.

If an SDR passed along context, I start there:

“One thing my colleague mentioned was your interest in automating CRM data entry.
Can I ask—why is that interesting for you?”

That question invites explanation. It surfaces motivation and emotion.

If there was no clear trigger for the meeting, I ask something simpler:

“You spoke with my colleague earlier. What made you decide to spend time on this call today?”

That single question often reveals more than ten situational ones.

It tells me:

• whether there is real pain

• whether the buyer is exploring casually

• where they are in the buying journey

Once the problem is clear, discovery becomes natural.

Because from there we can move directly to impact.

I — Impact: Where Discovery Becomes Commercial

Impact is where a conversation stops being interesting and starts being commercially meaningful.

If someone says:

“Our reps spend too much time entering data into the CRM.”

The next step is obvious.

What does that actually change?

Many reps try to calculate ROI through interrogation:

• How many reps?

• How many calls?

• How long does data entry take?

Eventually they build a business case.

But the buyer often feels manipulated.

A better approach is transparency.

I usually ask something like:

“Have you ever calculated the ROI of improving this process?”

If the answer is no, I suggest:

“Want to sanity-check it together with rough numbers?”

Now situational questions make sense.

Not because they suddenly became valuable—but because the buyer understands why we’re asking them.

That changes the dynamic completely.

Instead of extracting data, we’re building insight together.

Impact Isn’t Always What You Expect

Another reason impact should follow the problem closely: the real impact is often different from what the seller assumes.

Take the CRM example again.

At first glance, the problem is time loss.

But when buyers elaborate, the real issue might be:

• reps avoiding CRM updates

• poor data quality

• unreliable forecasting

• inability to evaluate performance

In other words, the real impact might be decision quality, not time.

If a rep jumps too quickly to ROI math, they might miss that completely.

Good discovery lets impact emerge from the buyer’s perspective.

C/E — Critical or Compelling Event

The next element in SPICED is the critical or compelling event.

This is where urgency comes from.

But here’s the uncomfortable truth:

In outbound sales, critical events are often missing.

A buyer might acknowledge a problem but still have no timeline. They simply became aware of something interesting.

That doesn’t mean they’re ready to act.

This is why many reps struggle with creating urgency in sales. They try to manufacture deadlines that don’t exist.

Instead, I focus on understanding the level of pain.

I think of it in three layers.

Personal pain (red)

Someone finds a workflow annoying.

Example:
“Manual reporting wastes an hour every day.”

Real, but rarely enough to justify a large purchase.

Organizational problem (yellow)

Now the issue affects company-level metrics:

• revenue

• efficiency

• profitability

But the organization still might not act.

Business initiative (green)

This is where urgency truly appears.

The company launches an initiative to address a problem.

For example:

• the company is behind on growth targets

• leadership launches a pipeline generation initiative

• marketing is now under pressure to improve performance

If my solution aligns with that initiative, urgency becomes real.

Not because I forced it.

Because the organization already decided to act.

D — Decision: Where SPICED Gets Blurry

The last element of SPICED is Decision.

This is also where the framework becomes weakest in complex deals.

The “D” typically includes questions like:

• Who is involved in the decision?

• What criteria will they use?

• What steps lead to signature?

These questions are useful.

But they combine multiple risks into one bucket.

In larger deals the failure usually isn’t “decision confusion.” It’s something specific:

• the champion lacks influence

• the economic buyer isn’t involved

• the decision criteria favor a competitor

• procurement changes the rules

SPICED doesn’t force reps to isolate those risks.

That’s why many enterprise teams complement SPICED with deeper qualification frameworks.

The Champion Problem

One of the biggest blind spots in SPICED is the champion.

A deal can look perfect:

• clear problem

• strong impact

• a timeline

• defined decision process

And still fail.

Why?

Because the internal contact was never truly supporting you.

They might simply be collecting options to satisfy procurement—or even quietly supporting a competitor.

The real test of a champion is simple:

Do they give you access to the process and the people involved?

If a contact consistently blocks access to other stakeholders, that’s a major warning sign.

The Three Most Important Decision Questions

Even if you use SPICED, three questions provide strong structure at the end of discovery:

1. What steps are required to reach a final decision?

2. Which people are involved in each step?

3. Based on what criteria will the decision be made?

These questions reveal how the decision actually works.

But in complex deals, they are just the starting point.

Because the moment competitors enter the process, decision criteria become critical.

If your differentiation isn’t part of those criteria, you’re already at a disadvantage.

When SPICED Works Best

Despite its limitations, SPICED is extremely useful.

Especially for structuring discovery conversations.

But its usefulness depends on deal size.

For example:

• Small deals: SPICED is often enough

• Mid-size deals: SPICED works with some additional qualification

• Enterprise deals: deeper frameworks are needed to manage risk

In other words:

SPICED is excellent at guiding conversations.

It is less effective at managing complex deal risk.

Final Thoughts

SPICED remains one of the most practical frameworks for structuring B2B sales discovery.

But the letters shouldn’t be treated as a rigid order.

In practice:

• Situation rarely needs to come first.

• Problem is usually the real entry point.

• Impact turns discovery into a business conversation.

• Critical events reveal whether urgency actually exists.

• Decision must be unpacked further in complex deals.

Used this way, SPICED becomes what it should be:

A framework that helps salespeople have better conversations—not a rigid checklist that pretends to qualify every deal.