Winning by Design: the SPICED framework
The founder shared this page on 2026-10-20. Ray's verdict: skim, file. SPICED is a simple way to structure discovery calls. The page itself is a sales page, so take the framing and leave the claims.
Why this is in the vault
SPICED is the "modern Winning by Design canon" at the end of the Commoncog business-to-business (B2B) sales reading path already filed in the vault. It is also the most direct tool yet for the founder's goal of helping phData sales: it gives a technical person five headings for a scoping call that a salesperson will recognize.
The five elements (paraphrased from the page)
The page calls SPICED "the revenue framework built around customer impact." It presents SPICED as a shared language for sales, marketing, customer success, and revenue operations (RevOps), used across the whole customer journey and not only at qualification.
- Situation. The customer's current context: business environment, constraints, priorities, and what triggered the change. It answers "why does this problem exist now?"
- Pain. The friction, inefficiency, or risk the customer has, stated in concrete and observable terms.
- Impact. What happens if the problem is solved or not solved, in terms the business cares about. The page splits this into rational outcomes and emotional stakes.
- Critical Event. A deadline, milestone, or outside force that creates urgency and sets when a decision must happen.
- Decision. How the customer will choose: the stakeholders, success criteria, tradeoffs, and the process needed to move forward.
The page says SPICED works best as an operating model, not a one-time training, and that it can sit on top of other methods.
Bias flag
Winning by Design sells this framework. The same page offers a free 45-minute intro course, a $500 live "Discovery Using SPICED" course with certification, workshops, implementation engagements, and a webinar banner. Its framework comparison is written by the seller, and its four case-study metrics (for example a 3X annual recurring revenue (ARR) increase and 298% more wins) come with no method and are unverified.
SPICED vs. MEDDICC
MEDDICC stands for Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion, Competition. The page itself says MEDDIC and MEDDPICC "place heavier emphasis on rigorous deal control." The differences that matter (Ray's read from general sales practice, not from the page):
- Champion. MEDDICC requires a named internal person who sells for you when you are not in the room. SPICED has no champion slot. "Decision" covers stakeholders but does not ask who is fighting for the deal.
- Paper process. MEDDPICC adds a "P" for the procurement, legal, and security steps needed to sign. SPICED folds this loosely into "Decision," so it is easy to miss.
- Forecasting. MEDDICC is built for sales managers to inspect deals and call the forecast. SPICED is built to understand the customer, so it is better at the first calls and weaker at answering "will this close this quarter?"
Practical read: SPICED for discovery, MEDDICC for deal inspection. The page agrees they can be layered.
Mapping against Ray Data Co
- phData credibility (project_credibility_for_phdata_sales). The founder works in phData's Deal Solutions Architect (DSA) seat, and as Technical Account Lead (TAL) on some accounts, building credibility to help phData sales, measured by pipeline. In Ray's read, technical sellers usually do Situation and Pain well, because those are the technical questions. They tend to skip Impact (what it is worth in money or risk) and Critical Event (why it must happen by a certain date). Those two are what turn a good technical call into a deal a salesperson can forecast.
- A habit to try. Use the five SPICED headings as the template for scoping-call notes. An empty Impact or Critical Event section is a visible prompt to ask one more question before the call ends. It also gives the phData account executive notes in a format they already know. This is Ray's suggestion; the founder has not tested it yet.
- Vasuman cross-check. [[2026-10-19-vasuman-where-to-begin-ai-transformation]] fits SPICED closely. Its step 2, "agree on the value and write it down" (key performance indicators set by the chief executive officer (CEO), chief financial officer, and controller against a $31-per-invoice baseline), is Impact. The CEO's 16-week deadline to show the board results is the Critical Event.
- Discovery artifact. The 7-criterion workflow scorecard in [[2026-06-07-every-executive-guide-implementing-ai]] could fill the Pain and Impact sections for agent use cases.
Related
- [[2026-10-19-vasuman-where-to-begin-ai-transformation]]: value written down = Impact; 16-week board deadline = Critical Event
- [[2026-04-19-commoncog-reading-program-b2b-sales]]: the reading path from Solution Selling through MEDDIC to Winning by Design
- [[2026-06-07-every-executive-guide-implementing-ai]]: workflow scorecard as a ready-made discovery artifact for phData calls
- [[2026-09-29-nov30-credibility-targets]]: the founder's Nov-30 credibility commitments that this habit would support