SPICED and the Buying Center

The deal had been in commit for two quarters. The rep loved the champion, the demo had gone great, and every forecast call ended with the same confident nod. Then it slipped a quarter. Then another. Then the champion changed jobs and the deal went dark. When I finally pulled the call notes apart in a deal review, the hole was obvious: we knew the prospect had a problem and we knew our product solved it, but we never learned what the problem was costing them, or what deadline would force them to fix it this year instead of next. The deal was real. The urgency was something we had invented on our own side of the table.

That hole is exactly what SPICED is built to close, and it is where the operating model stops being a diagram and starts changing how deals run. In the last chapter (The Operating Model) we landed on the operating model as three parts: one data model (the Bowtie), one common language (Impact), and one interface that every tool and methodology in the stack plugs into. That interface is SPICED. This chapter is the interface itself: how to run a single customer-centric methodology across acquisition, retention, and expansion, and how to map whatever framework your team already argues about onto it instead of crowning a winner.

SPICED is a diagnosis, not a script

SPICED comes from Revenue Architecture, and it is a way of understanding a customer, not a set of questions to read off a sheet. Five elements, in order.

Four traits make it more than a checklist. It is customer-centric, organized around the buyer’s reality rather than your pipeline stages. It is sequential: Situation grounds Pain, Pain justifies Impact, and you cannot credibly reach one without the one before it. It is causal, which is the sharp edge; skip Pain and your Impact number is a correlation you are hoping holds, not a claim the customer will defend to their CFO. And it treats Decision as the outcome, which is why the same five letters qualify a renewal or an expansion, not only a new logo. A renewal has a Situation that has changed, a Pain if impact stalled, and its own Decision. Run the whole lifecycle on one language and the story stops being re-litigated at every handoff.

Rational impact wins the company, emotional impact wins the person

Impact is the element deals cut corners on, and it has two halves that operators keep collapsing into one. Get both wrong and the deal reads as “they liked us” with no reason to buy.

Three principles hold this together. Emotional impact benefits a person first while rational impact benefits the company first. Emotional impact varies by individual, so you map it per role instead of writing one story for the account. And people decide emotionally, then defend the choice with the rational numbers. A business case with no personal stake behind it stalls in committee because nobody in the room is fighting for it. A champion full of passion but light on ROI gets overruled the moment finance asks for the math. You need both, aimed at the right people.

Priority is impact over time

Priority is not a fixed attribute of a deal. It is Impact viewed as a function of time.

That reframe gives you four priority levels, and it is worth memorizing that the lowest number is the highest priority. Level 4 is business-as-usual: real interest, no reason to change now. Level 3 is a compelling event: a genuine upside with no clock on it, good to have. Level 2 is a critical event: a dated consequence for doing nothing. Level 1 is mandatory: a regulatory or contractual must-do, the top of the stack. Deals at Level 1 or 2 reliably close in the quarter you forecast them. Deals at Level 3 slip, no matter how warm the champion is.

The Critical Event Timeline

Once a critical event has a real date, you plan backward from it. The Critical Event Timeline, credited to Daniel J. Adams in Revenue Architecture, anchors on the date the customer needs first impact, then works right to left, assigning a required-by date to every milestone that has to clear before it.

The timeline converts “we hope to close in Q4” into a chain the customer owns: for a February go-live, the contract has to be signed by mid-December, which means procurement starts in November, which means the business case is approved in October. Now the plan belongs to the buyer, every date has a name against it, and a missed milestone shows up as a problem in October rather than a surprise in December. This is the honest version of a mutual action plan.

You are selling to a buying center, not a champion

Gartner finds 6 to 10 decision makers in a typical complex B2B purchase, and Revenue Architecture counts up to about 20 people in a large buying center, organized into nine roles. The roles are defined by what a person does in the decision, not by their title, which is why an org chart is a poor map and the buying center is a good one.

The distinction that decides more forecasts than any other is Champion versus Decider. A Champion advocates for you inside the account but holds neither the budget authority nor the power to set a delivery date. A Decider controls the resources and owns the critical event. Mistaking one for the other is how a deal with a passionate champion sits in commit for two quarters and then evaporates. Your qualification is not finished until you have reached the Decider and confirmed the critical event with the person who actually controls it.

Every framework plugs into the same interface

Because SPICED is customer-centric, the methodologies your team already runs are not rivals to it; they are different entry points into the same five elements. That is the interoperability the operating model promised, made concrete.

The four sales methodologies differ mainly in where the seller engages, and that is driven by deal size, not preference. All four run the same SPICED sequence.

A $2K self-serve motion and a $500K Challenger motion need completely different playbooks, and that is fine. The point is not which methodology wins. It is that both describe the same customer reality in the same five terms, so a lead can pass from marketing to an SDR to an AE to a CSM without the story being rebuilt at every handoff.

What this gives the operator

You do not carry a bag, but you own the definitions that make SPICED real in the system: the fields that capture Impact and the critical event, the stage-gates that will not let a deal advance without a Decider named, the deal-review question that separates a critical event from a compelling one. Wire those into the CRM and the forecast and qualification stops being a matter of rep opinion. It becomes something the operating model enforces, deal after deal, the same way every time.

SPICED tells you how one deal and one customer move through the factory. The next question is how the whole business moves: how a company grows from its first million to its first hundred, which engine carries it at each stage, and why the growth rate falls even when everything is working. That is The Growth Model, and it is where we go next.