Battle card

What is a battle card?

A battle card is a concise, rep-facing document that equips a sales rep to compete against a specific named competitor in a live deal. A good battle card covers: what the competitor is strong at (so the rep isn't caught off guard), where the competitor falls short and why (the exploitable weaknesses), the specific proof points that outperform them (customer quotes, benchmark data), and the exact objection responses to use when the prospect raises the competitor by name.

The term comes from military intelligence briefings — mission-specific cards that gave pilots and soldiers the critical information they needed in a format they could consume quickly under pressure. The sales version follows the same logic: clear, short, immediately actionable. A battle card that requires five minutes to read in the middle of a call is useless.

For an AE in a competitive market where the prospect is evaluating 3–5 vendors simultaneously, battle cards are the difference between winging the competitive conversation and owning it. Reps without battle cards revert to 'we're better because...' which sounds defensive. Reps with battle cards pivot to specific facts: 'A lot of our customers came from [Competitor] specifically because [concrete reason with a number].'

What a good battle card contains

Battle cards fail when they're too long, too generic, or too positive about your own product. A working battle card is ruthlessly specific.

• Competitor strengths — what the competitor is genuinely good at. If your reps don't know this, they'll be blindsided when the prospect mentions it. Acknowledging strengths builds rep credibility.
• Competitor weaknesses — specific, documented, verifiable gaps. Not 'their support is bad' but 'their average implementation time is 90 days vs. our 14 days — here are two customer quotes verifying both numbers.'
• Winning proof points — 3–5 specific facts that demonstrate why customers choose you over this competitor. Ideally from customers who switched from the competitor. Numbers, not adjectives.
• Common objections when this competitor is in the deal — and the specific rep-tested response to each. Not generic — tuned to this competitor.
• Landmines to set — questions the rep can ask that expose the competitor's weaknesses organically. 'Have you asked them how long implementation typically takes?' instead of 'we implement faster.'
• When not to bring up this competitor — some competitor mentions backfire. If the prospect hasn't named them, introducing the competitor can create evaluation noise.

How to build a battle card that actually works

1. Start with win/loss data. Interview AEs who've won and lost against this competitor in the last quarter. What did the prospect say was the deciding factor? What objections came up? What would have changed the outcome?

2. Get intelligence from the field. Reps who competed against this vendor last week have more current intelligence than any analyst report. Build a channel (Slack, Salesforce field, monthly debrief) for reps to submit competitive intel.

3. Get a customer who switched from the competitor to be a reference. A quote from a customer who came from [Competitor] is 10x more powerful than anything the marketing team writes.

4. Keep it to one page (or two max). If the rep can't scan it in 90 seconds, they won't use it in a live call. Use bullets, not paragraphs.

5. Test it. Role play the competitive scenario with two or three reps before launching the card. The objection responses that sound good in a doc often fall flat in a live call. Iterate before publishing.

6. Review it quarterly. Competitors change pricing, features, and positioning faster than most battle cards are updated. A stale battle card with wrong information actively hurts the rep.

Common battle card mistakes

1. Too long. One page. Two if the competitive set is complex. Anything more doesn't get used in the moment it's needed.

2. No competitor weaknesses. Battle cards written by marketing often only list product advantages. Without knowing the competitor's real weaknesses — and how to expose them — the card is just a features comparison.

3. No named proof points. 'Customers prefer us' is not a proof point. 'Acme Inc. switched from [Competitor] and reduced implementation time from 90 days to 14 — here's the quote' is.

4. Not tested in role play. Objection responses that sound good in writing often feel awkward in live calls. Test every response before publishing.

How Gangly uses battle cards in live calls

Gangly's Live Call Coach watches the live transcript for competitor name mentions. When a prospect says '[Competitor]' or 'how do you compare to [Competitor],' the overlay surfaces the relevant battle card content in the rep's peripheral view — the weaknesses to probe, the proof points to lead with, and the specific objection response for the most common competitive challenge the prospect raises.

The rep doesn't have to find the battle card mid-call. It fires automatically when it's needed. Reps using Gangly in competitive deals report 35–45% faster competitive response times and less post-call research.

See how Live Call Coach works →

Frequently asked questions