SPICED sales methodology: a script for each step

SPICED is a discovery method from Winning by Design: Situation, Pain, Impact, Critical Event, Decision. A call script with lines for vague answers.

SPICED is a discovery method from Winning by Design with five elements: Situation, Pain, Impact, Critical Event and Decision. The SPICED sales methodology gives a seller a way to learn how a buyer will decide, and when.

The five letters fit in a short block, and the call is where the method gets used. This guide puts them in call order as a script, with the line to say when a buyer answers vaguely and the line to write in the CRM before you move on. Every line is our own wording, written for a made-up company. For where SPICED sits among other methods, see our guide to sales methodologies.

What is the SPICED sales methodology?

SPICED is Winning by Design's framework for understanding how customers make decisions. The company's own page says it created SPICED, and it describes the five elements this way:

  • Situation: the customer's current context, with its business environment, constraints, priorities and the triggers for change.
  • Pain: the specific friction, inefficiency or risk the customer has today, in concrete and observable terms.
  • Impact: what solving or not solving the problem means for the business, including both rational outcomes and emotional stakes.
  • Critical Event: the deadline or milestone, or any outside force, that sets when a decision has to be made.
  • Decision: how the customer will choose, with the people involved, the criteria they use, the tradeoffs and the process to get to a yes.

The same page says sales, RevOps, customer success and revenue leadership teams at B2B companies use the SPICED framework, and that it is framework-agnostic, meaning a team can layer it on the methods, processes and tools it already has. The page adds that SPICED is often introduced through sales and discovery, which is the part this post covers.

It lists the five elements without a required order. Winning by Design's five-page blueprint on the framework, published April 15, 2022, says impact and critical events are not always discovered in sequence and take active listening. The script below runs them in the order we would run them, and that order is ours. Expect to double back: a buyer who names a deadline in the first minute has handed you the Critical Event early.

How does SPICED compare with MEDDIC and BANT?

Winning by Design's FAQ gives its own view of the comparison, so read it as the view of the method's owner. It says SPICED puts customer context and decision dynamics first. It says MEDDIC and derivatives such as MEDDPICC put more weight on deal control, meaning metrics, economic buyers, decision criteria and champion development, and calls them especially valuable in complex enterprise cycles. It describes BANT (Budget, Authority, Need, Timeline) as simpler and a fit for transactional sales, with less depth on impact or decision context. Its conclusion is that SPICED extends these methods and that many teams use it alongside them.

To choose between them for your own deals, how to choose a sales methodology has a decision table. For how to score the letters of MEDDICC on a recording, see MEDDICC call scoring, and for other discovery methods with their own questions, see SPIN selling and the Sandler pain funnel.

A discovery call script, step by step

The company in this script is made up. Mossgate Systems sells appointment-scheduling software to dental clinic groups, and the buyer is the operations director of a regional group with four clinics. Nothing here is a real call. Each step has the same four parts: the question to ask, what counts as an answer, the line to say when the answer is vague, and the line to write in the CRM before the next step.

Step 1, Situation: get today's setup on the table.

  • Ask: "Walk me through what happens between a patient asking for an appointment and the slot being confirmed."
  • Counts as an answer: the buyer describes how the work runs today, with its tools and constraints, and says what made this the moment to look.
  • If the answer is vague ("It works fine"): "Good to hear it works. What made you take this call now?"
  • CRM line: Situation: front desks book by phone and a shared spreadsheet across four clinics. Trigger: two more clinics join the group in February.

Step 2, Pain: find one thing that actually happened.

  • Ask: "Where does that setup break down?"
  • Counts as an answer: a specific, observable episode, with who was involved and what people did about it.
  • If the answer is vague ("Visibility, mostly"): "Take the last time that happened. What did you see, and who found out first?"
  • CRM line: Pain: two patients were booked into the same chair last Thursday. The front desk found out when both arrived.

Step 3, Impact: ask for the business result and the personal one.

  • Ask: "What did that cost you last month?" Then: "Who took the call from the unhappy patient, and what was that like?"
  • Counts as an answer: a measurable result in business terms, plus a personal stake. Winning by Design's page and the library session described below both treat impact as rational and emotional.
  • If the answer is vague ("It costs us a lot"): "A lot compared with what? Take last month and tell me the hours or the empty chairs you can see."
  • If the personal side is vague ("It's annoying"): "Annoying for whom, and what does it do to your week?"
  • CRM line: Impact: about ten front-desk hours a week spent fixing double bookings (made-up figure). The operations director takes the escalated patient complaints personally.

Step 4, Critical Event: find the date and what it costs to miss it.

  • Ask: "Is there a date by which this has to be working?"
  • Counts as an answer: a date or milestone with a real consequence if it passes. The library session on impact and critical events says that without a consequence there is no genuine urgency.
  • If the answer is vague ("Ideally this year"): "What is on the calendar that makes this year matter? And what happens the day after it passes if nothing has changed?"
  • CRM line: Critical event: two more clinics join the group on February 2. Without one booking system, the group plans to hire a scheduling coordinator.

Step 5, Decision: map who else has to say yes.

  • Ask: "Walk me through the last purchase of this size. Who was involved, and what did each person need to see?"
  • Counts as an answer: named people, what each needs, the criteria for a yes and the order of the steps. The Winning by Design blueprint says decision processes are driven by a group and have to be mapped explicitly.
  • If the answer is vague ("I'll run it by the team"): "Who is on that team? What would each of them need to see before saying yes?"
  • CRM line: Decision: operations director and finance lead; the clinical lead checks the chair view. Finance wants a cost comparison against the coordinator hire. Signature after a pilot at one clinic.

Step 6, before you hang up: say it back and book the next step.

  • Say: "So two more clinics join on February 2, finance needs a cost comparison against the coordinator hire, and the clinical lead needs to see the chair view. Can we put thirty minutes with finance on the calendar for next Tuesday?"
  • CRM line: Next step: session with finance, booked for next Tuesday.

What does the repair line change on a real call?

Take Step 4 twice. In the first version the seller accepts the vague answer.

  • Seller: "Is there a date by which this has to be working?"
  • Buyer: "Ideally this year."
  • Seller: "Great, let's aim for the fourth quarter."

The seller now has a date with no consequence on it. By the account of the library session on critical events, that is a date without urgency. In the second version the seller uses the repair line.

  • Seller: "Is there a date by which this has to be working?"
  • Buyer: "Ideally this year."
  • Seller: "What is on the calendar that makes this year matter?"
  • Buyer: "We bring two more clinics into the group in February."
  • Seller: "And if the front desks are still on the shared spreadsheet that week?"
  • Buyer: "Then I hire a scheduling coordinator, and finance has already told me no to that."

Now the call holds an event, a date and a consequence, and the Decision step has a name to start from: finance.

What should the CRM say when the call ends?

The CRM lines above are a template: one sentence per element, in the buyer's own terms. Winning by Design's FAQ says SPICED can be embedded in CRM fields, workflows and dashboards, and that teams use it to make CRM data more meaningful.

A simple test is whether a colleague who was not on the call can read the five lines and say why the buyer would act, when, and who has to agree. A line that says "TBD", or repeats a label such as "visibility issues", marks the step to repeat on the next call.

How do you coach SPICED in a weekly 1:1?

The CRM lines from the script give a manager something to hold against the recording. Work on one element at a time:

  1. Open the CRM notes for one recent discovery call and find the line that reads thinnest: empty, "TBD", or a label with no episode behind it.
  2. Play the two minutes of the recording where that element should have come up, and ask the person to say what the buyer actually said.
  3. Ask the person to pick the repair line they would use, then have them say it out loud while you play the buyer.
  4. Agree on the one element to listen for on the next call, and read the CRM line again after it.

Keeping to one element per week is our recommendation and has no measurement behind it. How to run the conversation itself is in our guide to call coaching. To turn the same lines into a scorecard, see sales call scoring, and MEDDICC call scoring shows the idea on another method.

How do you train a sales team on SPICED?

Three steps, in this order.

  1. Give people the definitions. Winning by Design's SPICED page lists a free micro-course, Introduction to SPICED, which it describes as 45 minutes. The same page lists a live course, the Discovery Using SPICED Skills Course, at US$ 500 for a single 2-hour session with a cohort capped at 25 learners. Both are as shown on the page on November 18, 2026.
  2. Hear the two parts that are easiest to skip. The Triple Session library has a 19-minute session, Driving Urgency with Impact and Critical Event in the SPICED Framework. Its public description separates rational impact, a measurable result, from emotional impact, a personal frustration, and calls a critical event a date or milestone with a real consequence if it is missed. A 9-minute session, Deep Discovery Pre-game, says in its description that it uses SPICED to sharpen discovery questions.
  3. Coach from real calls. Use the weekly 1:1 routine above. Our suggestion is that each manager works through a few recorded calls a week for the first month. That cadence is ours and has no measurement behind it.

Where to start

Take your next five discovery calls and write the CRM lines from the script after each one. The line that comes out empty most often tells you which repair line to rehearse in your next 1:1. To see where the script sits in a full sales process, read sales process vs sales methodology. If SPICED is new to your team, what a sales methodology is and sales frameworks give the surrounding vocabulary.

Sources

  • Winning by Design, "SPICED" framework page (definitions of the five elements, FAQ on MEDDIC, MEDDPICC and BANT, CRM, courses and prices), no publication date shown, read November 18, 2026: https://winningbydesign.com/spiced-framework/
  • Winning by Design, "The SPICED Framework" blueprint page (5 pages, 15 to 18 minutes), published April 15, 2022, read November 18, 2026: https://winningbydesign.com/the-spiced-framework/
  • Triple Session, public session page, "Driving Urgency with Impact and Critical Event in the SPICED Framework" (Winning by Design), read November 18, 2026.
  • Triple Session, public session page, "Deep Discovery Pre-game" (Matt Doyon), read November 18, 2026.

See your team's calls scored on your playbook.

Send a few recordings. We score them and show where each person can improve. No cost, no contract.