ooligo
ENTRY TYPE · framework

Battlecards

Last updated 2026-05-02 RevOps

A battlecard is a one-page reference that prepares a rep for a competitive moment in a deal: how to position against a named competitor, how to handle their strongest objection, and where to push the conversation. A good battlecard is read in under 90 seconds before a call. A bad one is six pages of marketing copy nobody opens. The difference is design discipline.

What goes on a great battlecard

Strict scope. One competitor per card. One page. Five sections.

SectionContentLength
SnapshotTheir positioning, ICP, pricing model, last raise3 lines
Where they winThe 2 deals they take from us, with why3 bullets
Where we winThe 3 deals we take from them, with why3 bullets
Land minesObjections to plant early in the cycle3 questions to ask
Talk trackThe 30-second response when their name comes up4 sentences

Anything beyond this fits in an appendix nobody reads. Resist the urge to add feature comparison tables. Reps do not consult them on a call.

The land mine section is the one that wins deals

Land mines are questions you teach the rep to ask the prospect that, if asked early, expose the competitor’s weakness without the rep having to disparage them. Examples:

  • “How important is multi-region failover for your data residency?” (when the competitor lacks it)
  • “Can you walk me through how their pricing changes when you add a fourth team?” (when their tiers spike)
  • “Have you priced what their professional services cost to get to first value?” (when they hide implementation cost)

A good land mine sounds like genuine discovery and is unfalsifiable in the rep’s mouth.

Keeping them current

A battlecard older than 6 months is presumed wrong. Pricing changes, features ship, competitors reposition. Build a refresh rhythm:

  1. Source signal. Subscribe a Slack channel to mentions of competitor names in Gong calls.
  2. Monthly review. Enablement lead opens the top three cards, validates each line.
  3. Field updates. A “report a change” button on the card. Reps who close-lose to the competitor must annotate why.
  4. Owner per card. A named PMM or enablement person owns each top-three competitor.

Where to host them

The card should be one click from the rep’s daily flow: a CRM panel on the opportunity, a Gong deal card, or a pinned Notion page. PDFs in SharePoint do not survive contact with a calendar full of demos.

Common pitfalls

  • Feature parity tables. Reps lose with feature lists; they win with a sharper question.
  • Marketing tone. “Industry-leading platform” language has zero use in a deal. Use the AE’s language.
  • One mega-card for all competitors. Doesn’t scale and never gets updated. One per competitor, ranked by frequency.
  • No objection rehearsal. A battlecard not role-played is a card not used. Run 30-minute drills monthly on the top three.
  • Ignoring status quo. “Doing nothing” is the most common competitor. Build a card for it.