JOLT Sales Effect

Buyer Indecision (JOLT Effect)

by LeadMagic · MIT license · ★ 62 on GitHub

Buyer Indecision (JOLT Effect) cover

Overcome buyer indecision with the JOLT Effect — Judge indecision, Offer recommendation, Limit exploration, Take risk off the table. For deals stuck on "need to think about it", FOMU (fear of messing up), and no-decision losses.

---
name: buyer-indecision
description: >-
  Overcome buyer indecision with the JOLT Effect — Judge indecision, Offer
  recommendation, Limit exploration, Take risk off the table. For deals stuck
  on "need to think about it", FOMU (fear of messing up), and no-decision
  losses. Matthew Dixon & Ted McKenna. Use in late-stage enterprise deals,
  deal reviews, and proposal follow-up. Triggers on: "buyer indecision",
  "JOLT", "need to think about it", "no decision", "stuck deal", "FOMU",
  "fear of failure buyer", "close the gap intent to action".
license: MIT
compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
metadata:
  version: "1.1.0"
  author: LeadMagic
  category: sales-revops
  tags: [jolt, buyer-indecision, closing, enterprise, fomu, no-decision, late-stage]
  related_skills: [objection-handling, pipeline-management, meeting-prep, deal-desk, transparency-selling, multi-thread-orchestration, sales-coaching]

Overview

"I need to think about it" is not an objection — it's indecision. Dixon and McKenna's research on 2.5M+ sales conversations: 40–60% of B2B losses are no-decision, and 56% of those are indecision (FOMU — fear of messing up), not preference for status quo. Piling on ROI after intent is established backfires — buyers fear failure more than they crave success.

What you get

  • JOLT deal reviewtemplates/jolt-deal-review.md with indecision score
  • Champion kit1-page recommendation + risk removal for internal sell
  • Call planJ/O/L/T talk track for next meeting
  • Win-loss tagno-decision vs indecision vs lost-to-competitor
Manual install (npx, ZIP)
Claude Codenpx skills add LeadMagic/gtm-skills --skill buyer-indecision -g -a claude-code
Claude Code (degit)npx degit LeadMagic/gtm-skills/skills/sales-revops/buyer-indecision#main ~/.claude/skills/buyer-indecision
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md7.2 KB
Read SKILL.md here
LeadMagic/main1 file shown
SKILL.md
Show the full text173 lines

Buyer Indecision (JOLT Effect)

Overview

"I need to think about it" is not an objection — it's indecision. Dixon and McKenna's research on 2.5M+ sales conversations: 40–60% of B2B losses are no-decision, and 56% of those are indecision (FOMU — fear of messing up), not preference for status quo. Piling on ROI after intent is established backfires — buyers fear failure more than they crave success.

JOLT complements Challenger (teach) and SPICED/MEDDICC (qualify). Use JOLT after solution fit is verbal — when the buyer stalls before signature.

When to Use

  • "Deal stuck in negotiation / proposal"
  • "Champion ghosting after verbal yes"
  • "Need to think about it"
  • "No decision lost deal analysis"
  • "How to close enterprise indecision"
  • "JOLT framework"
  • "Buyer fear of failure"

Do not use JOLT for early discovery — use meeting-prep (SPICED). Do not confuse with price objections — use objection-handling first, then JOLT if stall persists after fit.

Authoritative Foundations

  • The JOLT Effect (Dixon & McKenna, 2022). Four moves for high performers: Judge level of indecision · Offer recommendation · Limit exploration · Take risk off the table. Source: https://www.jolteffect.com/
  • FOMU vs FOMO. Fear of Messing Up > Fear of Missing Out at decision time. Seller role shifts from persuader to buyer agent reducing downside.
  • Challenger Sale (Dixon). JOLT is late-stage; Challenger is early-stage teach.
  • MEDDICC / SPICED. Champion must run JOLT internally on buying committee — equip them with recommendation and risk-removal assets.

JOLT Framework

J — Judge the Level of Indecision

Diagnose before acting. Indecision signals:

Signal Likely Type Not This
"Need to run by [committee]" FOMU — personal risk Don't add more ROI slides
Endless POC extensions Fear of wrong choice Don't widen scope
New stakeholders late Internal saboteurs / passive resistors Don't ignore
Verbal yes, no paper Champion can't sell internally Don't pressure champion

Questions:

  • "What would make this feel safe to move forward?"
  • "What's the downside you're most worried about?"
  • "If you chose nothing, what happens in 90 days?"

Score 1–5 in deal review (templates/jolt-deal-review.md).

O — Offer Your Recommendation

Indecisive buyers want prescription, not more options. High performers give a clear "what I would do in your seat" recommendation.

Script pattern:

"Based on everything we've discussed, my recommendation is [package A / phased start / single use case]. That's what I'd do if I were accountable for [outcome]."

Pair with SPICED Decision criteria — tie to their stated success metrics.

L — Limit the Exploration

More information increases anxiety. Stop adding features, modules, and pricing tiers. Collapse choices to 1–2 vetted paths.

Do Don't
"Here are two paths — A or B" "Here's our full menu"
Fixed timeline for decision Open-ended "whenever"
Pre-built business case (1 page) 40-slide deck

Align with deal-desk — standard packages, not infinite custom.

T — Take Risk Off the Table

De-risk the decision, not just the product:

Tactic Example
Phased rollout Pilot one team / one region
Success criteria Mutual success plan with exit criteria
Executive sponsor Your exec + their EB alignment call
Contract flexibility Shorter initial term, renewal path clear
Implementation safety Named CSM, 30-day checkpoint

Maps to WbD Bowtie — left side onboarding promise reduces FOMU.

Integration with GTM Stack

Stage Skill JOLT Role
Discovery meeting-prep SPICED Build intent
Solution pipeline-management MEDDICC Score ≥14 gate
Proposal deal-desk Standard packages (Limit)
Stall buyer-indecision JOLT Judge → Offer → Limit → Take risk
Price pushback objection-handling Before or parallel to JOLT
Champion weak multi-thread-orchestration EB + JOLT assets for champion

Output Format

  • JOLT deal review — templates/jolt-deal-review.md with indecision score
  • Champion kit — 1-page recommendation + risk removal for internal sell
  • Call plan — J/O/L/T talk track for next meeting
  • Win-loss tag — no-decision vs indecision vs lost-to-competitor

Quality Check

  • Verbal fit established before JOLT (not used as discovery shortcut)
  • Indecision diagnosed (J) — not treated as status quo objection
  • Clear recommendation offered (O) — not "what do you want?"
  • Options limited (L) — max 2 paths
  • Risk removal explicit (T) — phased, success plan, or exec alignment
  • Champion equipped to run JOLT on internal committee

Common Pitfalls

  1. More ROI when they're scared. Increases analysis paralysis. Fix: Limit + Take risk.
  2. Single-threaded champion. Champion can't de-risk alone. Fix: EB meeting + mutual plan.
  3. Unlimited POC. No success criteria = infinite stall. Fix: time-boxed pilot with T.
  4. Confusing objection with indecision. "Too expensive" needs value work; "think about it" after fit needs JOLT.
  5. Skipping Judge. Applying O/L/T blindly. Fix: score indecision type first.

Execution Artifacts

  • references/framework-notes.md — Framework index and authority routing
  • templates/output-template.md — Primary deliverable shell
  • scripts/check-output.py — Validates JOLT deliverables (Judge, Offer, Limit, Take risk)
  • references/jolt-playbook.md — Full J/O/L/T tactics and talk tracks
  • templates/jolt-deal-review.md — Deal review scorecard
  • objection-handling — Taxonomy and AER for pushback
  • pipeline-management — Stage gates, MEDDICC scorecard
  • transparency-selling — Todd Caponi trust-building pre-JOLT
  • deal-desk — Package design for Limit step
  • sales-coaching — Manager deal review with JOLT lens (jolt-coaching reference)
1---
2name: buyer-indecision
3description: >-
4 Overcome buyer indecision with the JOLT Effect — Judge indecision, Offer
5 recommendation, Limit exploration, Take risk off the table. For deals stuck
6 on "need to think about it", FOMU (fear of messing up), and no-decision
7 losses. Matthew Dixon & Ted McKenna. Use in late-stage enterprise deals,
8 deal reviews, and proposal follow-up. Triggers on: "buyer indecision",
9 "JOLT", "need to think about it", "no decision", "stuck deal", "FOMU",
10 "fear of failure buyer", "close the gap intent to action".
11license: MIT
12compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
13metadata:
14 version: "1.1.0"
15 author: LeadMagic
16 category: sales-revops
17 tags: [jolt, buyer-indecision, closing, enterprise, fomu, no-decision, late-stage]
18 related_skills: [objection-handling, pipeline-management, meeting-prep, deal-desk, transparency-selling, multi-thread-orchestration, sales-coaching]
19 frameworks:
20 - "Matthew Dixon & Ted McKenna — The JOLT Effect (2022)"
21 - "Matthew Dixon — The Challenger Sale (teaching, reframe)"
22 - "Winning by Design — SPICED Decision criteria"
23 - "Andy Whyte — MEDDICC (EB access, scorecard gates)"
24---
25 
26# Buyer Indecision (JOLT Effect)
27 
28## Overview
29 
30"I need to think about it" is not an objection — it's **indecision**. Dixon
31and McKenna's research on 2.5M+ sales conversations: **40–60% of B2B losses
32are no-decision**, and **56% of those** are indecision (FOMU — fear of messing
33up), not preference for status quo. Piling on ROI after intent is established
34**backfires** — buyers fear failure more than they crave success.
35 
36JOLT complements Challenger (teach) and SPICED/MEDDICC (qualify). Use JOLT
37**after** solution fit is verbal — when the buyer stalls before signature.
38 
39## When to Use
40 
41- "Deal stuck in negotiation / proposal"
42- "Champion ghosting after verbal yes"
43- "Need to think about it"
44- "No decision lost deal analysis"
45- "How to close enterprise indecision"
46- "JOLT framework"
47- "Buyer fear of failure"
48 
49Do not use JOLT for early discovery — use `meeting-prep` (SPICED). Do not
50confuse with price objections — use `objection-handling` first, then JOLT if
51stall persists after fit.
52 
53## Authoritative Foundations
54 
55- **The JOLT Effect** (Dixon & McKenna, 2022). Four moves for high performers:
56 **J**udge level of indecision · **O**ffer recommendation · **L**imit exploration
57 · **T**ake risk off the table. Source: https://www.jolteffect.com/
58- **FOMU vs FOMO.** Fear of Messing Up > Fear of Missing Out at decision time.
59 Seller role shifts from persuader to **buyer agent** reducing downside.
60- **Challenger Sale** (Dixon). JOLT is late-stage; Challenger is early-stage teach.
61- **MEDDICC / SPICED.** Champion must run JOLT internally on buying committee —
62 equip them with recommendation and risk-removal assets.
63 
64## JOLT Framework
65 
66### J — Judge the Level of Indecision
67 
68Diagnose before acting. Indecision signals:
69 
70| Signal | Likely Type | Not This |
71|---|---|---|
72| "Need to run by [committee]" | FOMU — personal risk | Don't add more ROI slides |
73| Endless POC extensions | Fear of wrong choice | Don't widen scope |
74| New stakeholders late | Internal saboteurs / passive resistors | Don't ignore |
75| Verbal yes, no paper | Champion can't sell internally | Don't pressure champion |
76 
77**Questions:**
78- "What would make this feel safe to move forward?"
79- "What's the downside you're most worried about?"
80- "If you chose nothing, what happens in 90 days?"
81 
82Score 1–5 in deal review (`templates/jolt-deal-review.md`).
83 
84### O — Offer Your Recommendation
85 
86Indecisive buyers want **prescription**, not more options. High performers give
87a clear "what I would do in your seat" recommendation.
88 
89**Script pattern:**
90> "Based on everything we've discussed, my recommendation is [package A / phased
91> start / single use case]. That's what I'd do if I were accountable for [outcome]."
92 
93Pair with SPICED Decision criteria — tie to their stated success metrics.
94 
95### L — Limit the Exploration
96 
97More information increases anxiety. Stop adding features, modules, and pricing
98tiers. **Collapse choices** to 1–2 vetted paths.
99 
100| Do | Don't |
101|---|---|
102| "Here are two paths — A or B" | "Here's our full menu" |
103| Fixed timeline for decision | Open-ended "whenever" |
104| Pre-built business case (1 page) | 40-slide deck |
105 
106Align with `deal-desk` — standard packages, not infinite custom.
107 
108### T — Take Risk Off the Table
109 
110De-risk the **decision**, not just the product:
111 
112| Tactic | Example |
113|---|---|
114| Phased rollout | Pilot one team / one region |
115| Success criteria | Mutual success plan with exit criteria |
116| Executive sponsor | Your exec + their EB alignment call |
117| Contract flexibility | Shorter initial term, renewal path clear |
118| Implementation safety | Named CSM, 30-day checkpoint |
119 
120Maps to WbD Bowtie — left side onboarding promise reduces FOMU.
121 
122## Integration with GTM Stack
123 
124| Stage | Skill | JOLT Role |
125|---|---|---|
126| Discovery | `meeting-prep` SPICED | Build intent |
127| Solution | `pipeline-management` MEDDICC | Score ≥14 gate |
128| Proposal | `deal-desk` | Standard packages (Limit) |
129| Stall | **buyer-indecision** JOLT | Judge → Offer → Limit → Take risk |
130| Price pushback | `objection-handling` | Before or parallel to JOLT |
131| Champion weak | `multi-thread-orchestration` | EB + JOLT assets for champion |
132 
133## Output Format
134 
135- **JOLT deal review** — `templates/jolt-deal-review.md` with indecision score
136- **Champion kit** — 1-page recommendation + risk removal for internal sell
137- **Call plan** — J/O/L/T talk track for next meeting
138- **Win-loss tag** — no-decision vs indecision vs lost-to-competitor
139 
140## Quality Check
141 
142- [ ] Verbal fit established before JOLT (not used as discovery shortcut)
143- [ ] Indecision diagnosed (J) — not treated as status quo objection
144- [ ] Clear recommendation offered (O) — not "what do you want?"
145- [ ] Options limited (L) — max 2 paths
146- [ ] Risk removal explicit (T) — phased, success plan, or exec alignment
147- [ ] Champion equipped to run JOLT on internal committee
148 
149## Common Pitfalls
150 
1511. **More ROI when they're scared.** Increases analysis paralysis. Fix: Limit + Take risk.
1522. **Single-threaded champion.** Champion can't de-risk alone. Fix: EB meeting + mutual plan.
1533. **Unlimited POC.** No success criteria = infinite stall. Fix: time-boxed pilot with T.
1544. **Confusing objection with indecision.** "Too expensive" needs value work; "think about it"
155 after fit needs JOLT.
1565. **Skipping Judge.** Applying O/L/T blindly. Fix: score indecision type first.
157 
158## Execution Artifacts
159 
160- `references/framework-notes.md` — Framework index and authority routing
161- `templates/output-template.md` — Primary deliverable shell
162- `scripts/check-output.py` — Validates JOLT deliverables (Judge, Offer, Limit, Take risk)
163- `references/jolt-playbook.md` — Full J/O/L/T tactics and talk tracks
164- `templates/jolt-deal-review.md` — Deal review scorecard
165 
166## Related Skills
167 
168- `objection-handling` — Taxonomy and AER for pushback
169- `pipeline-management` — Stage gates, MEDDICC scorecard
170- `transparency-selling` — Todd Caponi trust-building pre-JOLT
171- `deal-desk` — Package design for Limit step
172- `sales-coaching` — Manager deal review with JOLT lens (jolt-coaching reference)
173 
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 62
Checked
Source
LeadMagic/gtm-skills ↗
Creator
LeadMagic · 129 listings
View creator

Similar skills

See all →
SkillPlan Weakness AnalyzerJeffallan/claude-skills · by https://github.com/JeffallanPaste the plan or decision you're about to make and get back its strongest weaknesses, blind spots, and hidden assumptions — plus a tougher version of the plan.★ 11.6k GitHub starsSkillHTML Explainer BuilderQingYunA/answer-me-with-html · by QingYunATurns an answer into a one-page visual HTML explainer: the model writes a short Markdown draft and the bundled CLI builds one page. Use it proactively and liberally, without being asked, whenever a page would help the reader more than plain text, even if plain text would also work: any explanation of how something works or how parts relate (flow, request path, architecture, code or folder structure, state machine, lifecycle, history); any comparison, trade-off or decision with pros and cons; any diagnosis, review or investigation, especially with several causes or findings to rank; any answer with a table, a numbered or ranked list, steps, branches or several sections; or when the user says "I don't get it / draw it / explain visually / 讲讲原理 / 没看懂 / 画个图". When in doubt, use it: a page is quick and cheap to make. Also for explainer videos ("make a video", "做个视频") and for changing its settings. Skip only for small talk, a trivial one-line answer, or when the user asks for plain text.★ 3.7k GitHub starsSkillClinical Decision SupportK-Dense-AI/scientific-agent-skills · by K-Dense-AIPrepare and validate research-only clinical decision-support evaluation, evidence-profile, cohort, survival, biomarker/model, privacy, and governance artifacts. Use for aggregate or synthetic research documentation and traceability—not patient care or live clinical operation.★ 46k GitHub starsSkillDecision Analysis AdvisorK-Dense-AI/scientific-agent-skills · by K-Dense-AIHand in a decision you're stuck on. Get back a clear breakdown of every angle — the trade-offs, the risks, the blind spot, and a recommended path.★ 46k GitHub starsSkillADR Documentation Writerwshobson/agents · by wshobsonWrite and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.★ 39.9k GitHub starsSkillLaunch Risk Pre-Mortemphuryn/pm-skills · by phurynRun a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.★ 26.6k GitHub stars

More from LeadMagic

SkillFirst-Party Analytics SetupLeadMagic/gtm-skills · by LeadMagicSet up first-party tracking and analytics — website pixels, conversion tracking, UTM architecture, cookie consent, server-side tagging vs client-side, 1P vs 3P data strategy, and identity resolution. Use when setting up tracking, implementing pixels, building attribution, or preparing for privacy-first measurement. Triggers on: "pixel", "tracking", "conversion tracking", "first-party data", server-side tagging", "UTM", "cookie consent", "1P vs 3P", "identity resolution", or any tracking implementation request.★ 62 GitHub starsSkillStrategic Account MarketingLeadMagic/gtm-skills · by LeadMagicRuns strategic 1-to-1 ABM for 5-15 high-value accounts: account plans, custom microsites, executive engagement, direct mail, and board-level connections. Use when a named enterprise account justifies bespoke content and executive time, or when the user needs a strategic account plan. Triggers on: "1-to-1 ABM", "strategic ABM", "custom ABM", "key account marketing", "named account".★ 62 GitHub starsSkillCluster Account MarketingLeadMagic/gtm-skills · by LeadMagicRuns ABM at scale (1-to-few) for 15-50 clustered accounts: industry or persona clusters, semi-custom campaigns, and cluster-level content. Use when named-account ABM needs to reach more accounts without bespoke work per account. Triggers on: "1-to-few ABM", "ABM scale", "cluster ABM", "industry ABM".★ 62 GitHub starsSkillProgrammatic Account TargetingLeadMagic/gtm-skills · by LeadMagicRuns programmatic 1-to-many ABM for 50-200+ accounts: automated personalization, scaled outbound, intent-based targeting, and lookalike expansion. Use when ABM coverage must grow without adding headcount or when the user wants automated account-based outreach. Triggers on: "1-to-many ABM", programmatic ABM", "scaled ABM", "automated ABM".★ 62 GitHub starsSkillAccount Strategy DesignerLeadMagic/gtm-skills · by LeadMagicDesigns an account-based marketing program: tier selection, account scoring, channel orchestration, BDR alignment (account-based sales development), and a measurement framework. Use when the user is launching or redesigning ABM, choosing between 1-to-1, 1-to-few, and 1-to-many, or building a target account program. Triggers on: "ABM strategy", "account based marketing", "ABM playbook", "design ABM", "target accounts", "ABSD", "account based sales development", "Lars Nilsson".★ 62 GitHub starsSkillTarget Account SelectorLeadMagic/gtm-skills · by LeadMagicBuilds and tiers a target account list: fit and intent scoring models, tier assignment, and TAM segmentation. Use when the user needs to decide which accounts to target, score or tier an account list, or prioritize a TAM for ABM or outbound. Triggers on: "account selection", "target account list", "tier accounts", "prioritize accounts", "TAM segmentation".★ 62 GitHub stars