Battle Card

Origin & evolution

The artefact predates the software industry that now obsesses over it. The "battle card" borrows its name and shape from military aide-mémoire, the laminated reference a soldier carries for fast recall under pressure, and sales organisations adapted the idea decades ago as printed cheat sheets for reps working against a known rival. What changed in the last fifteen years is ownership and cadence.

As product marketing matured into a discipline, the battle card moved under it. Product marketers already held the adjacent work: competitor positioning🎪PositioningGo-To-MarketProduct positioning statementView reference →, pricing watch, analyst commentary, and win-loss analysis. The Product Marketing Alliance treats battle cards as a core product-marketing deliverable rather than a sales hand-me-down, because the person who synthesises competitive intelligence is the person who should distil it into something a rep can use in ninety seconds.

The competitive-intelligence software wave (Klue, Crayon, Kompyte and others) reframed the card again, this time around the freshness problem. Klue's own data puts battle-card adoption at 86 per cent of competitive-intelligence leaders in software, and these tools exist largely because the static card was failing in a predictable way: a rival ships a feature⭐FeatureProduct SpecificationA product capability or featureView reference → or cuts a price, the card still claims the old reality, and a rep gets caught quoting a fact the prospect knows is stale. The modern card is a living document fed by alerts, win-loss interviews, and field submissions, scored on how often reps actually open it.

How it works in practice

A Series B analytics company keeps losing competitive deals to a cheaper incumbent. Win-loss interviews surface the pattern: the incumbent's reps tell prospects "they charge per seat, so it gets expensive fast," and the analytics company's reps fumble the reply.

Product marketing builds a card for that one competitor. The objection-handling section scripts the exact response: per-seat pricing includes unlimited queries, the incumbent meters API calls and bills overages, so a 40-seat team running heavy reporting pays less on the named plan once volume crosses roughly 2 million events a month. The "traps to set" section gives the rep a question to ask early: "How does their pricing change as your query volume grows?" Six weeks later, competitive win rate against that incumbent moves from 31 per cent to 44 per cent, and the field-submission box on the card fills with three new objections reps heard in live calls, which feeds the next revision.

Competitive battle card vs. its neighbours

• Competitive analysis📊Competitive AnalysisMarket IntelligenceA structured analysis of the competitive landscapeView reference → is the upstream study: a thorough teardown of a rival's product, pricing, and positioning, written for an internal strategy audience. A battle card is the field-ready extract of that analysis, compressed for recall in a live conversation. One is the research; the other is the weapon you hand the rep.
• Objection is a single unit the card responds to. A prospect says "your competitor integrates with Salesforce natively and you don't," and the card carries the rehearsed answer to that one line. A card is the container; an objection is one entry inside it, and a card with no objection handling is just a feature comparison.
• Sales playbook📒PlaybookCustomer SuccessA standard operating procedure for CSView reference → covers how to run the whole deal: discovery questions, the demo arc, the close. A battle card is narrower and adversarial, scoped to a named competitor and triggered only when that rival enters the conversation.

In the graph

In the Unified Product Graph, a competitive battle card sits in the go-to-market region. The defining edges trace its supply chain: gtm_strategy_arms_with_competitive_battle_cardGTM Strategyarms withCompetitive Battle Cardhierarchy ties it to the strategy it serves, competitive_battle_card_references_competitorCompetitive Battle CardreferencesCompetitorcross-domain anchors it to the named rival it was built against, and competitive_battle_card_addresses_objectionCompetitive Battle CardaddressesObjectionhierarchy connects it to each objection it scripts a response for. That structure makes the freshness problem queryable. A card whose referenced competitor has shipped a tracked competitor feature🔬Competitor FeatureMarket IntelligenceA feature offered by a competitorView reference → since the card was last touched is a card that has gone stale, and the graph can surface it before a rep quotes it in a losing deal.