a builder's codex
codex · operators · Crayon · ins_battlecard-abc-and-distribution

Battlecard adoption fails on distribution, not content quality — embed in the workflow or the card dies

By Crayon · Competitive intelligence software platform · 2026-03-03 · essay · Sales Battlecards 101 — Crayon's complete guide

Tier B · TL;DR
Battlecard adoption fails on distribution, not content quality — embed in the workflow or the card dies

Claim

The hard problem in competitive enablement is not battlecard authoring; it is battlecard adoption. Content quality is necessary but insufficient. The lever is distribution: embed cards in the seller's existing workflow (CRM at the opportunity level, Slack/Teams channels keyed to deal stage, even calendar invites for competitive deals) rather than parking them in a Confluence page nobody opens. The content principle is ABC: Accuracy, Brevity, Consistency. The behavior change is two-pronged: effortless access plus role-modeling from top performers.

Mechanism

Sellers don't read; they search at the moment of need. A battlecard that lives in a Notion page and isn't surfaced inside the CRM record at the moment a competitor enters the opportunity stage is functionally invisible. McKinsey-style behavior change is the underlying frame: make the desired behavior easier than the alternative, and pair it with social proof from peers the seller respects. Crayon's data: 68% of opportunities are competitive, and ~⅔ of CI teams produce battlecards — but the gap between production and adoption is where most CI programs fail.

Conditions

Holds when:

Fails when:

Evidence

"Their two-pronged adoption strategy (effortless access in existing workflows plus role model behavior from top performers) draws on McKinsey's research on behavior change."

"68% of sales opportunities are competitive and nearly two-thirds of CI teams produce battlecards."

— Crayon (synthesized from operator's published work)

Signals

Counter-evidence

Content-only CI orgs argue that the highest-impact card is one that gets talked about (in QBRs, in the all-hands), not one that gets clicked in CRM. Battle-tested adoption frameworks like Klue's argue for win-rate-by-card analytics rather than presence-in-workflow as the primary KPI.

Cross-references

Open the interactive view → View original source → Markdown source →