Pipeline management skill

Design and manage B2B sales processes using Winning by Design's GTM Playbook Kit — stage goals, in-stage actions, exit criteria, SPICED qualification fields, conversion metrics, Bowtie handoffs, forecasting, and deal inspection cadences.

by LeadMagic·MIT license·★ 62 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words
# Pipeline Management

## Overview

Most sales teams have CRM stages that describe rep activity, not buyer progress.
Winning by Design's GTM Playbook Kit fixes this: every stage needs a **Goal**
(what success looks like), **In-Stage Actions** (what the rep does), and **Exit
Criteria** (evidence required to advance). Without all three, pipeline reviews
degenerate into confidence theater.

This skill designs the full sales process — stages, SPICED fields per stage,
conversion metrics, Bowtie handoffs to CS, forecast categories, and inspection
cadences. Load `gtm-system-architecture` first if you have not scored the six
WbD models. Load `sales-enablement` after this to build the playbook assets
reps use at each stage.

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

Files of Pipeline management

LeadMagic/main1 file shown
SKILL.md
Show the full text341 lines

Pipeline Management

Overview

Most sales teams have CRM stages that describe rep activity, not buyer progress. Winning by Design's GTM Playbook Kit fixes this: every stage needs a Goal (what success looks like), In-Stage Actions (what the rep does), and Exit Criteria (evidence required to advance). Without all three, pipeline reviews degenerate into confidence theater.

This skill designs the full sales process — stages, SPICED fields per stage, conversion metrics, Bowtie handoffs to CS, forecast categories, and inspection cadences. Load gtm-system-architecture first if you have not scored the six WbD models. Load sales-enablement after this to build the playbook assets reps use at each stage.

When to Use

  • "Design our sales process" or "build a GTM playbook"
  • "Winning by Design sales process"
  • "Define deal stages with exit criteria"
  • "Set up SPICED in our CRM"
  • "Improve forecast accuracy"
  • "Build a pipeline review cadence"
  • "Design SDR-to-AE handoffs"
  • "Our pipeline is unpredictable — fix it"

Do not use for org design or compensation — use sales-team-building. Do not use for collateral creation — use sales-enablement after the process is defined.

Authoritative Foundations

  • Winning by Design — GTM Playbook Development Kit. The core structure: Goal
    • In-Stage Actions + Exit Criteria per stage. A stage is not "Demo scheduled" — it is "buyer confirms solution maps to quantified pain" with evidence fields.
  • Winning by Design — SPICED. Situation, Pain, Impact, Critical Event, Decision — required qualification dimensions captured progressively through Discovery and Solution stages, not dumped in one call.
  • Keenan — Gap Selling. At Discovery/Solution stages, exit criteria should evidence Current State + Future State + quantified Gap (not rep confidence). Problem Identification Chart aligns product problems to discovery questions. Discovery stage gate: no advance on happy ears — buyer-stated impact required. Playbook → meeting-prep/references/keenan-gap-selling.md.
  • Winning by Design — Bowtie. Revenue continues after Closed Won. Define handoff criteria from Sales → Onboarding (CS) with context package: SPICED summary, stakeholders, success criteria, and expansion signals.
  • Mark Roberge — The Sales Acceleration Formula. Measure conversion rate between every stage. Inspect deals against exit criteria, not rep confidence.
  • Miller Heiman — Strategic Selling. For enterprise deals, map buying influences (Economic Buyer, User Buyer, Technical Buyer, Coach) alongside stage progression.
  • Andy Whyte — MEDDICC (MEDDICC.com). Seven qualification dimensions scored continuously on every deal: Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion, Competition. The MEDDICC scorecard drives go/no-go at stage gates — not rep confidence. "Always Be Qualifying" means re-scoring after every customer interaction.
  • Force Management — MEDDICC Methodology. Original enterprise qualification framework (PTC/Force Management). Andy Whyte's scorecard operationalizes it for deal inspection and CRM fields.
  • John McMahon — Inspection cadence. MEDDICC is the CRO's forecast language: weekly 1:1s inspect 2–3 deals with evidence per letter; slipping commits get role-play coaching (Stage 2 Capital demos). Board forecast uses commit / likely / upside tranches — each backed by MEDDICC proof and named mitigations. Pair Gap Selling at Discovery to block happy ears. Canonical → gtm-leadership/references/cro-enterprise-strategy.md.
  • Joey Gilkey — Disposition Science. Six outcome buckets per completed conversation diagnose top-of-funnel list/message/rep problems before opportunities enter pipeline stages. Map Meeting Scheduled + Activated → qualified handoff; Not Now → nurture tier; Not Me/Referred → list rebuild signal. Requires 50+ completions. → references/joey-gilkey-bucketing.md
  • Ryan Reisert — CRM Activity Buckets. Four contact-level stages (Uncontacted, In Cadence, Priority, Scheduled) for SDR daily workflow — distinct from Gilkey dispositions. Design CRM contact stages and SDR→AE handoff tiers at top of funnel. → references/ryan-reisert-cold-calling.md

SPICED + MEDDICC — complementary, not competing:

Layer Framework When Purpose
Discovery conversation SPICED (WbD) Connect → Discovery Uncover Situation, Pain, Impact, Critical Event
Deal qualification MEDDICC (Whyte) Solution → Negotiation Score EB, Champion, Metrics, Competition with evidence
Both map to CRM Shared fields All stages Impact → Metrics; Critical Event → Pain urgency; Decision → EB + Process

Use SPICED in early calls. Use MEDDICC scorecard from Solution stage onward and for any deal ≥$50K ACV. Never advance to Proposal without Champion named and Economic Buyer engaged (Whyte's rule).

Prerequisites

  • CRM configured (HubSpot, Salesforce, or Attio)
  • Average ACV and sales cycle length known
  • ICP defined (icp-scoring or gtm-context)
  • Motion selected: transactional, consultative, or strategic (icp-targeting-tiers)

Step-by-Step Process

Phase 1: Motion Selection (WbD by ACV)
ACV Range Motion Typical Stages Cycle
<$5K Transactional 4–5 stages, self-serve assist Days–2 weeks
$5K–$50K Consultative 5–7 stages, SDR optional 2–8 weeks
$50K+ Strategic 7–9 stages, multi-thread required 2–6 months

Pick one motion per segment. Do not run enterprise stages on SMB deals.

Phase 2: Stage Design (GTM Playbook Kit)

For each stage, document all three components:

Component Definition Bad Example Good Example
Goal What buyer + seller achieve at this stage "Have a call" "Pain quantified with business impact"
In-Stage Actions Rep activities that advance the buyer "Send follow-up" "Run SPICED discovery, document Impact $"
Exit Criteria Evidence required to advance (CRM fields) "Rep feels good" "Impact field populated, EB identified"

Consultative motion — reference stage map:

Stage Goal Key Exit Criteria (Evidence)
1. Target Account fits ICP ICP score ≥ threshold, verified contacts
2. Connect Interest established Reply received, Situation documented
3. Discovery Pain + Impact quantified SPICED: Pain, Impact, Critical Event captured
4. Solution Solution validated Demo complete, requirements confirmed, Champion named
5. Proposal Commercial terms presented Proposal sent, Decision Process mapped
6. Negotiation Terms + procurement engaged Redlines resolved, EB engaged, MEDDICC complete
7. Closed Won Contract executed Signed agreement, handoff package to CS
8. Closed Lost Learning captured Loss reason, competitor, stage-of-death

Strategic/enterprise additions: add Technical Validation and Security Review stages between Solution and Proposal. Require multi-thread map (multi-thread-orchestration).

Phase 3: SPICED Field Mapping

Map SPICED dimensions to stages — capture progressively, not all at once:

SPICED Captured By Stage CRM Field Examples
Situation Connect → Discovery current_tools, team_size, process_today
Pain Discovery primary_pain, pain_owner
Impact Discovery impact_annual_cost, impact_metric
Critical Event Discovery → Solution why_now, deadline_date
Decision Solution → Proposal economic_buyer, decision_process, criteria

Disqualification rule: No Critical Event by end of Discovery → downgrade to nurture or Closed Lost. No deal urgency = no deal timeline.

Phase 4: MEDDICC Scorecard (Andy Whyte)

Score each dimension 0 (unknown), 1 (suspected), or 2 (confirmed with evidence). Re-score after every meeting. Load meeting-prep for discovery questions and sales-coaching for manager-led deal reviews.

Letter Dimension Confirmed (Score 2) Requires CRM Field
M Metrics Buyer-defined KPIs with baseline and target success_metrics, metric_baseline
E Economic Buyer Named person with budget authority; met directly economic_buyer_name, eb_engaged_date
D Decision Criteria Documented evaluation criteria (incl. yours) decision_criteria
D Decision Process Mapped steps, dates, approvers decision_process_steps
I Identify Pain Quantified pain + cost of inaction identified_pain, cost_of_inaction
C Champion Power + influence + personal win + sells internally champion_name, champion_test_passed
C Competition Named competitors, status quo, build-vs-buy assessed competition_landscape

Andy Whyte — Champion test (all four required):

  1. Has power to influence the decision (not just enthusiasm)
  2. Has a personal win if the deal closes
  3. Can articulate the problem without your help
  4. Has committed to sell internally when you are not in the room

Stage gate minimums (consultative $5K–$50K):

Advance To Minimum MEDDICC Score Hard Requirements
Solution (from Discovery) 6/14 Pain=2, Metrics≥1
Proposal 10/14 Champion=2, EB≥1, Decision Process≥1
Negotiation 12/14 EB=2, Decision Criteria=2
Commit forecast 13/14 All dimensions ≥1, no zeros on E/I/C

Enterprise ($50K+): add Paper Process (legal_review_steps, procurement_contact) and require multi-thread map before Proposal (multi-thread-orchestration).

Go/No-Go: Score <6 at Solution stage → nurture. Score <10 at Proposal → do not send proposal. Score drops week-over-week → manager deal review within 48 hours.

Phase 5: Conversion Metrics (Roberge + WbD)

Define target conversion rates between stages. Measure monthly:

Conversion Formula Healthy Range (Consultative)
Target → Connect Connects / Targets worked 15–25%
Connect → Discovery Meetings held / Connects 40–60%
Discovery → Solution Demos / Discoveries 50–70%
Solution → Proposal Proposals / Demos 40–60%
Proposal → Closed Won Wins / Proposals 25–40%

When a conversion drops >10 points below baseline, inspect exit criteria — reps are advancing deals without evidence, or the stage Goal is wrong.

Time-in-stage limits: Discovery >21 days without Critical Event = stalled. Alert + manager review. Proposal >30 days without EB engagement = at risk.

Phase 6: Bowtie Handoffs

Sales process does not end at Closed Won. Define handoff packages:

Handoff From → To Package Contents SLA
MQL → SDR/AE Marketing → Sales Source, campaign, SPICED Situation 24 hours
SDR → AE SDR → AE SPICED summary, meeting notes, next steps Same day
AE → CS Sales → Onboarding Full SPICED, stakeholders, success criteria, contract scope Before kickoff
CS → AE (expansion) CS → Sales Usage signals, expansion trigger, champion status On signal

Load gtm-system-architecture for the full Bowtie (Onboarding → Adoption → Expansion → Renewal) and CS stage design.

Phase 7: Forecast Categories
Stage Group Forecast Category Confidence
Target, Connect Pipeline 10–20%
Discovery, Solution Upside 30–50%
Proposal, Negotiation Commit 70–85%
Closed Won Won 100%

Commit deals require all Exit Criteria for Proposal stage met — not rep optimism.

Phase 8: Deal Inspection Cadence

Weekly pipeline review (60 min):

  1. New deals entered — exit criteria met for current stage?
  2. Stalled >14 days — which SPICED/MEDDICC dimension is missing?
  3. Commit at risk — what changed since last week?
  4. Missing next steps — action assigned with date
  5. Close date pushed — pattern or one-off?

Deal review questions (never "how do you feel?"):

  • "Walk me through each SPICED field — what's the evidence?"
  • "Who is the Economic Buyer and when did you last speak to them?"
  • "What is the Critical Event date and what happens if they miss it?"
  • "What would cause this deal to die?"

Load sales-coaching for REKS-based manager coaching on process adherence.

Output Format

GTM sales process document containing: motion selection rationale, full stage table (Goal + Actions + Exit Criteria), SPICED/MEDDICC CRM field map, conversion metric targets, time-in-stage rules, Bowtie handoff specs, forecast categories, and weekly inspection agenda.

Use templates/output-template.md for the deliverable structure. Run scripts/check-output.py on the finished document before delivery.

Quality Check

Before delivering, verify:

  • Every stage has Goal, In-Stage Actions, AND Exit Criteria — not just a label
  • Exit criteria are evidence fields in CRM, not subjective judgments
  • SPICED dimensions mapped to specific stages with disqualification rules
  • MEDDICC scorecard defined with 0/1/2 scoring and stage gate minimums
  • Champion test (Whyte) documented with four criteria
  • SPICED + MEDDICC field mapping shows no duplicate/conflicting CRM fields
  • Conversion rate targets defined between each stage pair
  • Time-in-stage limits set with alert thresholds
  • AE → CS handoff package defined (Bowtie continuity)
  • Forecast categories tied to exit criteria, not rep confidence
  • Weekly inspection agenda uses SPICED/MEDDICC questions

Common Pitfalls

  1. Stages named after rep activity. "Demo scheduled" is an action, not a stage goal. Fix: name stages after buyer outcomes; actions live inside the stage.

  2. SPICED collected once, never updated. SPICED fields go stale. Fix: require re-validation at Proposal stage; Critical Event dates must be current.

  3. No conversion metrics. You cannot diagnose a broken process without stage-to-stage rates. Fix: baseline conversions, review monthly.

  4. Handoff to CS is an email. CS starts blind, churn risk spikes. Fix: structured handoff package with SPICED summary and success criteria.

  5. Too many stages. More than 9 stages creates CRM friction without accuracy gains. Fix: consolidate admin-heavy stages; keep 5–7 for consultative.

  6. Process without enablement. Reps know the stages but lack talk tracks. Fix: load sales-enablement to build playbook assets per stage.

Execution Artifacts

  • references/framework-notes.md — WbD Playbook Kit, SPICED, Bowtie, MEDDICC, Gap Selling anchors
  • templates/output-template.md — copy-paste sales process deliverable
  • scripts/check-output.py — validates required sections in finished output
  • references/cro-enterprise-strategy.md — McMahon QBR inspection checklist, three-view forecast (Pattern 31)
  • references/cold-calling-experts-index.md — Phone bucketing router (Gilkey vs Reisert)
  • references/joey-gilkey-bucketing.md — Disposition Science → pipeline tiers
  • references/ryan-reisert-cold-calling.md — CRM Activity Buckets
  • gtm-system-architecture — Six-model audit and Bowtie architecture
  • sales-enablement — Playbook, battlecards, talk tracks per stage
  • sales-coaching — REKS (Jacco van der Kooij), MEDDICC deal reviews, JOLT coaching, 1:1/call rubrics
  • meeting-prep — SPICED/MEDDIC discovery question banks
  • multi-thread-orchestration — Enterprise buying committee mapping
  • crm-integration — CRM field and stage configuration
  • gtm-metrics — Pipeline dashboards and conversion reporting
  • buyer-indecision — JOLT for Proposal+ stalls ("think about it", FOMU)
1---
2name: pipeline-management
3description: >-
4 Design and manage B2B sales processes using Winning by Design's GTM Playbook Kit
5 — stage goals, in-stage actions, exit criteria, SPICED qualification fields,
6 conversion metrics, Bowtie handoffs, forecasting, and deal inspection cadences.
7 Use when designing sales process stages, building a GTM playbook, improving
8 forecast accuracy, or setting up pipeline reviews. Triggers on: "sales process
9 design", "GTM playbook", "pipeline management", "deal stages", "Winning by Design
10 process", "SPICED stages", "forecasting", "deal inspection", "CRM hygiene".
11license: MIT
12compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
13metadata:
14 version: "1.2.0"
15 author: LeadMagic
16 category: sales-revops
17 tags: [pipeline, sales-process, spiced, forecasting, crm, deal-management, wbd]
18 related_skills: [gtm-system-architecture, sales-enablement, sales-coaching, buyer-indecision, founder-sales, sales-team-building, meeting-prep, gtm-metrics, crm-integration, revenue-forecasting]
19 frameworks:
20 - "Winning by Design — GTM Playbook Development Kit"
21 - "Winning by Design — SPICED Qualification"
22 - "Keenan — Gap Selling"
23 - "Winning by Design — Bowtie Handoff Design"
24 - "Mark Roberge — The Sales Acceleration Formula"
25 - "Miller Heiman — Strategic Selling (buying influence)"
26 - "Andy Whyte — MEDDICC Qualification & Scorecard"
27 - "Force Management — MEDDICC Methodology"
28 - "Joey Gilkey — Disposition Science (top-of-funnel diagnostics)"
29 - "Ryan Reisert — CRM Activity Buckets (contact prioritization)"
30 - "John McMahon — MEDDICC inspection cadence, three-view forecast, anti–happy ears"
31---
32 
33# Pipeline Management
34 
35## Overview
36 
37Most sales teams have CRM stages that describe rep activity, not buyer progress.
38Winning by Design's GTM Playbook Kit fixes this: every stage needs a **Goal**
39(what success looks like), **In-Stage Actions** (what the rep does), and **Exit
40Criteria** (evidence required to advance). Without all three, pipeline reviews
41degenerate into confidence theater.
42 
43This skill designs the full sales process — stages, SPICED fields per stage,
44conversion metrics, Bowtie handoffs to CS, forecast categories, and inspection
45cadences. Load `gtm-system-architecture` first if you have not scored the six
46WbD models. Load `sales-enablement` after this to build the playbook assets
47reps use at each stage.
48 
49## When to Use
50 
51- "Design our sales process" or "build a GTM playbook"
52- "Winning by Design sales process"
53- "Define deal stages with exit criteria"
54- "Set up SPICED in our CRM"
55- "Improve forecast accuracy"
56- "Build a pipeline review cadence"
57- "Design SDR-to-AE handoffs"
58- "Our pipeline is unpredictable — fix it"
59 
60Do not use for org design or compensation — use `sales-team-building`. Do not
61use for collateral creation — use `sales-enablement` after the process is defined.
62 
63## Authoritative Foundations
64 
65- **Winning by Design — GTM Playbook Development Kit.** The core structure: Goal
66 + In-Stage Actions + Exit Criteria per stage. A stage is not "Demo scheduled" —
67 it is "buyer confirms solution maps to quantified pain" with evidence fields.
68- **Winning by Design — SPICED.** Situation, Pain, Impact, Critical Event,
69 Decision — required qualification dimensions captured progressively through
70 Discovery and Solution stages, not dumped in one call.
71- **Keenan — Gap Selling.** At Discovery/Solution stages, exit criteria should
72 evidence Current State + Future State + quantified Gap (not rep confidence).
73 Problem Identification Chart aligns product problems to discovery questions.
74 Discovery stage gate: no advance on happy ears — buyer-stated impact required.
75 Playbook → `meeting-prep/references/keenan-gap-selling.md`.
76- **Winning by Design — Bowtie.** Revenue continues after Closed Won. Define
77 handoff criteria from Sales → Onboarding (CS) with context package: SPICED
78 summary, stakeholders, success criteria, and expansion signals.
79- **Mark Roberge — The Sales Acceleration Formula.** Measure conversion rate
80 between every stage. Inspect deals against exit criteria, not rep confidence.
81- **Miller Heiman — Strategic Selling.** For enterprise deals, map buying
82 influences (Economic Buyer, User Buyer, Technical Buyer, Coach) alongside
83 stage progression.
84- **Andy Whyte — MEDDICC (MEDDICC.com).** Seven qualification dimensions scored
85 continuously on every deal: Metrics, Economic Buyer, Decision Criteria, Decision
86 Process, Identify Pain, Champion, Competition. The MEDDICC scorecard drives
87 go/no-go at stage gates — not rep confidence. "Always Be Qualifying" means
88 re-scoring after every customer interaction.
89- **Force Management — MEDDICC Methodology.** Original enterprise qualification
90 framework (PTC/Force Management). Andy Whyte's scorecard operationalizes it for
91 deal inspection and CRM fields.
92- **John McMahon — Inspection cadence.** MEDDICC is the CRO's **forecast language**:
93 weekly 1:1s inspect 2–3 deals with evidence per letter; slipping commits get
94 role-play coaching (Stage 2 Capital demos). Board forecast uses **commit / likely /
95 upside** tranches — each backed by MEDDICC proof and named mitigations. Pair Gap
96 Selling at Discovery to block happy ears. Canonical → `gtm-leadership/references/cro-enterprise-strategy.md`.
97- **Joey Gilkey — Disposition Science.** Six **outcome** buckets per completed
98 conversation diagnose top-of-funnel list/message/rep problems before opportunities
99 enter pipeline stages. Map Meeting Scheduled + Activated → qualified handoff;
100 Not Now → nurture tier; Not Me/Referred → list rebuild signal. Requires 50+
101 completions. → `references/joey-gilkey-bucketing.md`
102- **Ryan Reisert — CRM Activity Buckets.** Four **contact-level** stages
103 (Uncontacted, In Cadence, Priority, Scheduled) for SDR daily workflow — distinct
104 from Gilkey dispositions. Design CRM contact stages and SDR→AE handoff tiers at
105 top of funnel. → `references/ryan-reisert-cold-calling.md`
106 
107**SPICED + MEDDICC — complementary, not competing:**
108 
109| Layer | Framework | When | Purpose |
110|---|---|---|---|
111| Discovery conversation | SPICED (WbD) | Connect → Discovery | Uncover Situation, Pain, Impact, Critical Event |
112| Deal qualification | MEDDICC (Whyte) | Solution → Negotiation | Score EB, Champion, Metrics, Competition with evidence |
113| Both map to CRM | Shared fields | All stages | Impact → Metrics; Critical Event → Pain urgency; Decision → EB + Process |
114 
115Use SPICED in early calls. Use MEDDICC scorecard from Solution stage onward
116and for any deal ≥$50K ACV. Never advance to Proposal without Champion named
117and Economic Buyer engaged (Whyte's rule).
118 
119## Prerequisites
120 
121- CRM configured (HubSpot, Salesforce, or Attio)
122- Average ACV and sales cycle length known
123- ICP defined (`icp-scoring` or `gtm-context`)
124- Motion selected: transactional, consultative, or strategic (`icp-targeting-tiers`)
125 
126## Step-by-Step Process
127 
128### Phase 1: Motion Selection (WbD by ACV)
129 
130| ACV Range | Motion | Typical Stages | Cycle |
131|---|---|---|---|
132| <$5K | Transactional | 4–5 stages, self-serve assist | Days–2 weeks |
133| $5K–$50K | Consultative | 5–7 stages, SDR optional | 2–8 weeks |
134| $50K+ | Strategic | 7–9 stages, multi-thread required | 2–6 months |
135 
136Pick one motion per segment. Do not run enterprise stages on SMB deals.
137 
138### Phase 2: Stage Design (GTM Playbook Kit)
139 
140For each stage, document all three components:
141 
142| Component | Definition | Bad Example | Good Example |
143|---|---|---|---|
144| **Goal** | What buyer + seller achieve at this stage | "Have a call" | "Pain quantified with business impact" |
145| **In-Stage Actions** | Rep activities that advance the buyer | "Send follow-up" | "Run SPICED discovery, document Impact $" |
146| **Exit Criteria** | Evidence required to advance (CRM fields) | "Rep feels good" | "Impact field populated, EB identified" |
147 
148**Consultative motion — reference stage map:**
149 
150| Stage | Goal | Key Exit Criteria (Evidence) |
151|---|---|---|
152| 1. Target | Account fits ICP | ICP score ≥ threshold, verified contacts |
153| 2. Connect | Interest established | Reply received, Situation documented |
154| 3. Discovery | Pain + Impact quantified | SPICED: Pain, Impact, Critical Event captured |
155| 4. Solution | Solution validated | Demo complete, requirements confirmed, Champion named |
156| 5. Proposal | Commercial terms presented | Proposal sent, Decision Process mapped |
157| 6. Negotiation | Terms + procurement engaged | Redlines resolved, EB engaged, MEDDICC complete |
158| 7. Closed Won | Contract executed | Signed agreement, handoff package to CS |
159| 8. Closed Lost | Learning captured | Loss reason, competitor, stage-of-death |
160 
161**Strategic/enterprise additions:** add Technical Validation and Security Review
162stages between Solution and Proposal. Require multi-thread map (`multi-thread-orchestration`).
163 
164### Phase 3: SPICED Field Mapping
165 
166Map SPICED dimensions to stages — capture progressively, not all at once:
167 
168| SPICED | Captured By Stage | CRM Field Examples |
169|---|---|---|
170| **S**ituation | Connect → Discovery | `current_tools`, `team_size`, `process_today` |
171| **P**ain | Discovery | `primary_pain`, `pain_owner` |
172| **I**mpact | Discovery | `impact_annual_cost`, `impact_metric` |
173| **C**ritical Event | Discovery → Solution | `why_now`, `deadline_date` |
174| **D**ecision | Solution → Proposal | `economic_buyer`, `decision_process`, `criteria` |
175 
176**Disqualification rule:** No Critical Event by end of Discovery → downgrade to
177nurture or Closed Lost. No deal urgency = no deal timeline.
178 
179### Phase 4: MEDDICC Scorecard (Andy Whyte)
180 
181Score each dimension 0 (unknown), 1 (suspected), or 2 (confirmed with evidence).
182Re-score after every meeting. Load `meeting-prep` for discovery questions and
183`sales-coaching` for manager-led deal reviews.
184 
185| Letter | Dimension | Confirmed (Score 2) Requires | CRM Field |
186|---|---|---|---|
187| **M** | Metrics | Buyer-defined KPIs with baseline and target | `success_metrics`, `metric_baseline` |
188| **E** | Economic Buyer | Named person with budget authority; met directly | `economic_buyer_name`, `eb_engaged_date` |
189| **D** | Decision Criteria | Documented evaluation criteria (incl. yours) | `decision_criteria` |
190| **D** | Decision Process | Mapped steps, dates, approvers | `decision_process_steps` |
191| **I** | Identify Pain | Quantified pain + cost of inaction | `identified_pain`, `cost_of_inaction` |
192| **C** | Champion | Power + influence + personal win + sells internally | `champion_name`, `champion_test_passed` |
193| **C** | Competition | Named competitors, status quo, build-vs-buy assessed | `competition_landscape` |
194 
195**Andy Whyte — Champion test (all four required):**
1961. Has power to influence the decision (not just enthusiasm)
1972. Has a personal win if the deal closes
1983. Can articulate the problem without your help
1994. Has committed to sell internally when you are not in the room
200 
201**Stage gate minimums (consultative $5K–$50K):**
202 
203| Advance To | Minimum MEDDICC Score | Hard Requirements |
204|---|---|---|
205| Solution (from Discovery) | 6/14 | Pain=2, Metrics≥1 |
206| Proposal | 10/14 | Champion=2, EB≥1, Decision Process≥1 |
207| Negotiation | 12/14 | EB=2, Decision Criteria=2 |
208| Commit forecast | 13/14 | All dimensions ≥1, no zeros on E/I/C |
209 
210**Enterprise ($50K+):** add Paper Process (`legal_review_steps`, `procurement_contact`)
211and require multi-thread map before Proposal (`multi-thread-orchestration`).
212 
213**Go/No-Go:** Score <6 at Solution stage → nurture. Score <10 at Proposal → do not
214send proposal. Score drops week-over-week → manager deal review within 48 hours.
215 
216### Phase 5: Conversion Metrics (Roberge + WbD)
217 
218Define target conversion rates between stages. Measure monthly:
219 
220| Conversion | Formula | Healthy Range (Consultative) |
221|---|---|---|
222| Target → Connect | Connects / Targets worked | 15–25% |
223| Connect → Discovery | Meetings held / Connects | 40–60% |
224| Discovery → Solution | Demos / Discoveries | 50–70% |
225| Solution → Proposal | Proposals / Demos | 40–60% |
226| Proposal → Closed Won | Wins / Proposals | 25–40% |
227 
228When a conversion drops >10 points below baseline, inspect exit criteria —
229reps are advancing deals without evidence, or the stage Goal is wrong.
230 
231**Time-in-stage limits:** Discovery >21 days without Critical Event = stalled.
232Alert + manager review. Proposal >30 days without EB engagement = at risk.
233 
234### Phase 6: Bowtie Handoffs
235 
236Sales process does not end at Closed Won. Define handoff packages:
237 
238| Handoff | From → To | Package Contents | SLA |
239|---|---|---|---|
240| MQL → SDR/AE | Marketing → Sales | Source, campaign, SPICED Situation | 24 hours |
241| SDR → AE | SDR → AE | SPICED summary, meeting notes, next steps | Same day |
242| AE → CS | Sales → Onboarding | Full SPICED, stakeholders, success criteria, contract scope | Before kickoff |
243| CS → AE (expansion) | CS → Sales | Usage signals, expansion trigger, champion status | On signal |
244 
245Load `gtm-system-architecture` for the full Bowtie (Onboarding → Adoption →
246Expansion → Renewal) and CS stage design.
247 
248### Phase 7: Forecast Categories
249 
250| Stage Group | Forecast Category | Confidence |
251|---|---|---|
252| Target, Connect | Pipeline | 10–20% |
253| Discovery, Solution | Upside | 30–50% |
254| Proposal, Negotiation | Commit | 70–85% |
255| Closed Won | Won | 100% |
256 
257Commit deals require all Exit Criteria for Proposal stage met — not rep optimism.
258 
259### Phase 8: Deal Inspection Cadence
260 
261**Weekly pipeline review (60 min):**
2621. New deals entered — exit criteria met for current stage?
2632. Stalled >14 days — which SPICED/MEDDICC dimension is missing?
2643. Commit at risk — what changed since last week?
2654. Missing next steps — action assigned with date
2665. Close date pushed — pattern or one-off?
267 
268**Deal review questions (never "how do you feel?"):**
269- "Walk me through each SPICED field — what's the evidence?"
270- "Who is the Economic Buyer and when did you last speak to them?"
271- "What is the Critical Event date and what happens if they miss it?"
272- "What would cause this deal to die?"
273 
274Load `sales-coaching` for REKS-based manager coaching on process adherence.
275 
276## Output Format
277 
278GTM sales process document containing: motion selection rationale, full stage
279table (Goal + Actions + Exit Criteria), SPICED/MEDDICC CRM field map, conversion
280metric targets, time-in-stage rules, Bowtie handoff specs, forecast categories,
281and weekly inspection agenda.
282 
283Use `templates/output-template.md` for the deliverable structure. Run
284`scripts/check-output.py` on the finished document before delivery.
285 
286## Quality Check
287 
288Before delivering, verify:
289- [ ] Every stage has Goal, In-Stage Actions, AND Exit Criteria — not just a label
290- [ ] Exit criteria are evidence fields in CRM, not subjective judgments
291- [ ] SPICED dimensions mapped to specific stages with disqualification rules
292- [ ] MEDDICC scorecard defined with 0/1/2 scoring and stage gate minimums
293- [ ] Champion test (Whyte) documented with four criteria
294- [ ] SPICED + MEDDICC field mapping shows no duplicate/conflicting CRM fields
295- [ ] Conversion rate targets defined between each stage pair
296- [ ] Time-in-stage limits set with alert thresholds
297- [ ] AE → CS handoff package defined (Bowtie continuity)
298- [ ] Forecast categories tied to exit criteria, not rep confidence
299- [ ] Weekly inspection agenda uses SPICED/MEDDICC questions
300 
301## Common Pitfalls
302 
3031. **Stages named after rep activity.** "Demo scheduled" is an action, not a
304 stage goal. Fix: name stages after buyer outcomes; actions live inside the stage.
305 
3062. **SPICED collected once, never updated.** SPICED fields go stale. Fix:
307 require re-validation at Proposal stage; Critical Event dates must be current.
308 
3093. **No conversion metrics.** You cannot diagnose a broken process without
310 stage-to-stage rates. Fix: baseline conversions, review monthly.
311 
3124. **Handoff to CS is an email.** CS starts blind, churn risk spikes. Fix:
313 structured handoff package with SPICED summary and success criteria.
314 
3155. **Too many stages.** More than 9 stages creates CRM friction without accuracy
316 gains. Fix: consolidate admin-heavy stages; keep 5–7 for consultative.
317 
3186. **Process without enablement.** Reps know the stages but lack talk tracks.
319 Fix: load `sales-enablement` to build playbook assets per stage.
320 
321## Execution Artifacts
322 
323- `references/framework-notes.md` — WbD Playbook Kit, SPICED, Bowtie, MEDDICC, Gap Selling anchors
324- `templates/output-template.md` — copy-paste sales process deliverable
325- `scripts/check-output.py` — validates required sections in finished output
326- `references/cro-enterprise-strategy.md` — McMahon QBR inspection checklist, three-view forecast (Pattern 31)
327- `references/cold-calling-experts-index.md` — Phone bucketing router (Gilkey vs Reisert)
328- `references/joey-gilkey-bucketing.md` — Disposition Science → pipeline tiers
329- `references/ryan-reisert-cold-calling.md` — CRM Activity Buckets
330 
331## Related Skills
332 
333- `gtm-system-architecture` — Six-model audit and Bowtie architecture
334- `sales-enablement` — Playbook, battlecards, talk tracks per stage
335- `sales-coaching` — REKS (Jacco van der Kooij), MEDDICC deal reviews, JOLT coaching, 1:1/call rubrics
336- `meeting-prep` — SPICED/MEDDIC discovery question banks
337- `multi-thread-orchestration` — Enterprise buying committee mapping
338- `crm-integration` — CRM field and stage configuration
339- `gtm-metrics` — Pipeline dashboards and conversion reporting
340- `buyer-indecision` — JOLT for Proposal+ stalls ("think about it", FOMU)
341 

Discussion

Alternatives

⚡ NEXUS Quick-Start Guide> Get from zero to orchestrated multi-agent pipeline in 5 minutes.Business & ops · MITclean-cut — the step-1 cut pipelineStep 1 of the AI Video Editor pipeline — turn raw talking-head footage into a clean master cut. Use when the user wants to "clean cut", "cut the raw footage", "remove filler / dead air / bad takes", "tighten the pacing", produce cuts.json, run the cut editor, or render a cleaned preview/master for a video-N project in this repo. Covers audio extraction, AssemblyAI transcription, authoring cuts.json (keeps/cuts/fluff categorized), the cut policy (content-aggressive, pause-natural ~0.5s), QA + review docs, the local cut-editor UI, tight/natural previews, the final 4K60 render, and producing edited-transcript.json as the handoff to /make-tsx. Not for building TSX overlays (that is /make-tsx) or the raw TSX authoring rules (that is vidtsx-2d-generator).Sales & ecommerce · MITVocaloid-style MV pipeline (手書き / 文字PV)Make an original animated music video (MV / PV) for a song from its audio file plus lyrics, in the Vocaloid / J-pop lyric-video tradition: 手書き/tegaki (V家手书, 手描きMV, ボカロPV), 文字PV and kinetic typography (リリックモーション, リリックビデオ, 歌詞動画, 歌词视频, 动态歌词), anime-illustration MVs with an original character — for any mood, from dark ballads to bright upbeat summer pop. Renders to MP4 with a deterministic Canvas2D/WebGL2 engine in a headless browser: JIZURA lyric motion, AI-generated art, optional Blender toon 3D, beat-locked editing, 9:16 vertical/Shorts version. Use it whenever the user wants a music video, MV, PV, lyric video or beat-synced animation for a song, e.g. make an MV for my song", "turn this track into a lyric video", "给这首歌做个MV/PV", "做个V家手书", "この曲のMVを作って", ボカロPV作って", "縦型ショートも" — even if they only give a .wav/.mp3 and say "make a cool video for it". Not for editing existing footage or clip compilations.Sales & ecommerce · MITConstruction Agent — Email → Project Management PipelineConstruction company AI agent — orchestrates email (Google Workspace), project management (JobTread Pave API), and file routing for a construction business. Handles email triage, attachment routing to JobTread, project status, task management, and daily briefings via Telegram. Reference implementation for a construction/trades business with an existing email→Drive→PM pipeline.Sales & ecommerce · MIT