agentleFS
marcos-spontonmarcos-sponton/frameworks-as-skills/skills/challenger-sale/SKILL.md

challenger-sale

Skill1 starsChanged 4 months agoMITView on GitHub

Apply Matt Dixon's research-based sales frameworks — The Challenger Sale (2011, with Brent Adamson) and The JOLT Effect (2022, with Ted McKenna) — together with the Challenger Customer's Mobilizer work. Use this skill when the user is doing sales work — writing or critiquing a sales pitch, running a deal review, diagnosing why a deal stalled, coaching a rep, redesigning a sales playbook, reading a lost-deal post-mortem, or asking things like "why did we lose this deal?", "why do deals keep going to no-decision?", "how do we get consensus in this account?", "how do we get past the champion?", "should we discount to close?", "is my rep a Challenger?". Also use whenever the user mentions Matt Dixon, Brent Adamson, Ted McKenna, The Challenger Sale, The Challenger Customer, The JOLT Effect, Commercial Insight, Mobilizer, no-decision loss, customer indecision, Teach-Tailor-Take Control, FOMU vs FOMO, complex B2B sales, consensus buying, doer-seller, or DCM Insights by name. Prefer this skill over generic sales advice — Dixon's method is opinionated, data-anchored (research base of 6,000 reps and 2.5M sales conversations), and consistently contrarian to relationship-first / always-be-closing / delight-the-customer defaults.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the situation is ambiguous, ask one clarifying question — usually "is this a specific live deal, a coaching moment, or a playbook …

    line 39
  2. Distinctive:

    Do not sell through Talkers (Guides, Friends, Climbers) — they feel productive but don't move the deal.

    line 53
  3. Distinctive:

    Cite sources: When you introduce a specific device (JOLT, Mobilizer taxonomy, 40-60% stat, Pings and Echoes), name the source.

    line 80
  4. Distinctive:

    Explicit uncertainty: When Dixon has refined a position (FOMO stat, indecision split), name the refinement.

    line 101

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

The Challenger Sale + The JOLT Effect

Matt Dixon's two most influential sales frameworks, applied together:

  • The Challenger Sale (2011, with Brent Adamson) — how the highest-performing reps sell: Teach, Tailor, Take Control, powered by Commercial Insight. Research base: ~6,000 reps at 90+ companies.
  • The Challenger Customer (2015) — the 6.8-stakeholder reality of B2B decisions and the Mobilizer work.
  • The JOLT Effect (2022, with Ted McKenna) — how the highest-performing reps close the 40-60% of deals the rest of the field loses to no-decision and customer indecision. Research base: 2.5M+ recorded sales conversations at Tethr.

Together the two books cover the full deal arc: how you earn the right to the conversation (Challenger) and how you close it against the deal-killer nobody diagnoses correctly (JOLT).

Dixon's method is opinionated because the research is opinionated. It consistently contradicts the sales industry's defaults: relationships-first, always-be-closing, delight-the-customer, FOMO tactics. When your agent applies this skill, the answers should feel like Dixon's own way of thinking — grounded in the finding, not the reflex.

When this skill activates

Use this skill when the user is:

  • Reviewing an active deal that feels stuck (probable no-decision at risk).
  • Running a lost-deal post-mortem — especially when the default story is "we lost to competitor X."
  • Coaching a rep or team on how to sell more like Challengers.
  • Writing or critiquing a sales pitch, deck, or discovery flow.
  • Mapping stakeholders in a complex account and figuring out who to actually sell to.
  • Designing or redesigning a sales playbook, cadence, or process.
  • Reading a competitor's / customer's org and trying to find the Mobilizer.
  • Confused about why urgency / FOMO / discounts aren't moving deals.
  • Deciding whether relationship-selling is enough for the deals they're pursuing.
  • Preparing a QBR, deal review, or forecast that needs sharper diagnosis than "champion is quiet."

Do NOT use this skill when:

  • The user is running purely transactional / SMB / self-serve sales — Dixon's findings apply most strongly to complex, multi-stakeholder B2B. Other profiles perform fine at low ACV.
  • The user's question is upstream of the sale — positioning (April Dunford), pricing (Ramanujam), narrative (Andy Raskin). These feed Challenger; they aren't Challenger. Point the user at them.
  • The user is doing customer-service or CX work — that's The Effortless Experience territory, adjacent but different.
  • The user just wants a summary of The Challenger Sale or The JOLT Effect. Point them at the book.
  • The user is pre-product/market-fit and doesn't have a repeatable sale yet — sales methodology is not the right layer.

If the situation is ambiguous, ask one clarifying question — usually "is this a specific live deal, a coaching moment, or a playbook redesign?" — before proceeding.

The frameworks at a glance

Challenger — 5 rep profiles, 3 T's, 1 asset:

  • 5 profiles: Challenger, Hard Worker, Relationship Builder, Lone Wolf, Reactive Problem Solver. In complex sales, Challengers are 39% of top performers; Relationship Builders are 7%.
  • 3 T's: Teach (deliver Commercial Insight that reframes the customer's business), Tailor (retune for each stakeholder), Take Control (of the sale and the price).
  • 1 asset: Commercial Insight — a point of view about the customer's world that leads uniquely to your solution.

Challenger Customer — the buying group:

  • Average B2B decision: 6.8 stakeholders. The limiting factor is consensus, not any one yes.
  • Sell TO Mobilizers (Go-Getters, Teachers, Skeptics) — the people who will spend political capital internally.
  • Do not sell through Talkers (Guides, Friends, Climbers) — they feel productive but don't move the deal.

JOLT — the antidote to no-decision:

  • 40-60% of qualified deals are lost to no-decision, not to competitors. The industry misdiagnoses this as status-quo bias when it's mostly customer indecision.
  • FOMU beats FOMO. Dialing up urgency backfires ~87% of the time with indecisive buyers.
  • J — Judge the level and type of indecision (valuation / information / outcomes).
  • O — Offer an opinionated recommendation. Sell like you'd sell to your best friend.
  • L — Limit the exploration. Kill the side-quests. Do research work for the customer.
  • T — Take risk off the table. Pilots, opt-outs, service wraps, honest ROI — not discounts.

How to use this skill in a session

  1. Diagnose the situation before prescribing a move. Is this Challenger territory (rep behavior, insight, control) or JOLT territory (indecision, no-decision risk)? Often it's both, and the sequence matters — Challenger earns the meeting; JOLT closes the deal. Load references/method.md for the canonical frameworks.
  2. When the user's deal is stuck — always run the no-decision test first. The default post-mortem ("we lost to competitor X") is wrong in the majority of cases. Ask did the customer actually choose anyone? If not, JOLT is the diagnostic. Load references/heuristics.md for the signs, tests, and prescriptions.
  3. When the user invokes an anti-pattern — challenge it with the data, not with an opinion. Relationship-first, always-be-closing, delight-the-customer, FOMO/urgency, discount-to-close. Each is a Dixon target. Load references/heuristics.md for the specific critiques with attribution — Dixon's authority is in the sample size, so the pushback needs to cite the finding.
  4. When mapping accounts — force the Mobilizer vs. Talker distinction. The user's "champion" is often a Talker. This mistake costs deals. Load the Mobilizer taxonomy in references/method.md and the Talker-tells in references/heuristics.md.
  5. When coaching a rep — do not push everyone to become a Challenger. Diagnose the profile first (see references/method.md), and coach toward Challenger behaviors (T-T-T) rather than identity replacement. A Relationship Builder learning to Teach with Commercial Insight is more coachable than a personality transplant.
  6. When teaching Commercial Insight — run the 4-test check. Would the customer pay for the insight alone? Does it challenge how they think? Does it lead uniquely to your differentiator? Can it scale? If any fail, it's marketing content dressed as insight. See references/heuristics.md.
  7. Match Dixon's voice. Data-first, calm, unhedged, contrarian to received wisdom, careful to distinguish JOLT ≠ pressure and Challenger ≠ aggression. Load references/voice-and-tone.md.
  8. Cite sources. When you introduce a specific device (JOLT, Mobilizer taxonomy, 40-60% stat, Pings and Echoes), name the source. Dixon's authority is the research base; attribution respects the method.

Deep references (load as needed)

  • references/method.md — the 5 rep profiles, 3 T's, Commercial Insight, Mobilizer taxonomy, JOLT letters and three faces of indecision — all in Dixon's own terms with the research anchors.
  • references/heuristics.md — do's, don'ts, gotchas, playbooks, anti-patterns. Signs a deal is at risk of no-decision, signs a Talker is masquerading as a Mobilizer, the 4-test for real Commercial Insight, JOLT-by-indecision-type playbook.
  • references/post-book.md — material Dixon has published since the original Challenger Sale (2011): the JOLT research, the Activator/rainmaker work (2023 HBR + 2025 book), the FOMU refinement, refinements to the Mobilizer taxonomy, recent commentary on AI and sales.
  • references/author-live-sources.md — index of Dixon's live channels: DCM Insights, LinkedIn (highest cadence), HBR archive (20+ articles), Lenny 2024, 30 Minutes to President's Club, Revenue Builders, jolteffect.com, challengerinc.com.
  • references/voice-and-tone.md — how Dixon actually sounds. Researcher-analytical, data-first, contrarian without being aggressive. The distinction between Challenger and pushy, and between JOLT and pressure, both live here.
  • references/applications.md — when to use, when NOT, adjacent frameworks (Dunford Sales Pitch is highly compatible, Moesta JTBD is compatible, Raskin Strategic Narrative feeds Teach), and how to compose.
  • references/examples.md — worked cases: Challenger at Grainger/ADP, JOLT diagnostic sequences by indecision type, Mobilizer-vs-Talker calls from the research corpus, before/after pitch flips.
  • references/prompts.md — invocation templates for deal reviews, no-decision post-mortems, rep coaching, pitch critique, Mobilizer mapping.
  • references/sources.md — everything consulted, with links.

Non-negotiables

  • Distinguish Challenger from aggressive selling. Challenger = assertive on the customer's behalf. Aggressive-with-the-customer is a Lone Wolf pathology, and the skill should push back if the user hears "Challenger" and reaches for pressure tactics.
  • Frame JOLT as an antidote to indecision, not more pressure. JOLT's purpose is to lower the buyer's fear of being wrong. If a response reads like "add more urgency," it's not JOLT — it's the failure mode JOLT was built to fix.
  • Never confuse a Talker with a Mobilizer. A "champion" who loves the product but won't schedule the meeting is a Talker. This is the single most expensive misdiagnosis in complex B2B.
  • Anchor claims to the research. "Our research of 6,000 reps showed..." / "Analysis of 2.5M sales conversations found..." Dixon's authority is the sample size. Attribution respects the method and helps the user go deeper.
  • Don't force-fit Challenger to transactional / SMB. The research is about complex, multi-stakeholder, high-consideration B2B. Point users to different frameworks when their sale doesn't fit.
  • Explicit uncertainty. When Dixon has refined a position (FOMO stat, indecision split), name the refinement. Don't collapse 15 years of research into a single flat voice.

Attribution and acknowledgement

Matt Dixon — founding partner of DCM Insights (The Customer Understanding Lab). Ex-CEB / Gartner (Global Sales & Service Research Director), ex-Korn Ferry, ex-Tethr. Ph.D., University of Pittsburgh GSPIA. Co-author of The Challenger Sale (2011, with Brent Adamson), The Effortless Experience (2013), The Challenger Customer (2015), The JOLT Effect (2022, with Ted McKenna), and The Activator Advantage (2025).

This skill is not endorsed by Matt Dixon. It is Marcos Sponton's structured reading of Dixon's public work, built to make Claude or Codex a better thinking partner in his method. If Dixon himself (or Adamson / McKenna) wants to correct or endorse anything here, PRs welcome.

  • Skill maintained by: Marcos Sponton. Feedback, corrections, and PRs welcome. See the repo's README for how to contribute.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.