How many battlecards should we have?

The competitors reps actually see, ranked by deal frequency. Typically 4-8 for a Series A/B B2B company. Above 10, you're building content for competitors who rarely show up in deals, at the cost of maintenance on the ones that matter.

Should we share battlecards with customers or partners?

No. Battlecards are internal-only. Customer-facing competitive materials (independent comparison sheets, third-party analyst reports) are different assets, produced with different tone and standards.

Can we generate battlecards with AI?

Partially. AI is useful for first drafts of the summary, competitor news aggregation, and pulling quotes from public sources. It can't do the win-loss synthesis, the landmine questions, or the customer-specific proof that makes battlecards actually useful. Treat AI as a research assistant, not the author.

Sales Battlecards: Structure, Distribution, and Maintenance

A battlecard is the sales rep's fastest path to answering a competitive question in the middle of a deal.

Sales Battlecards: The 2-Page Asset That Lifts Competitive Win Rates by 10-25 Points

A battlecard is a concise, sales-facing document about one competitor — how they position, where they win, where they lose, how to sell against them. It exists to close the time gap between a rep hearing a competitor's name on a call and having the right answer in the follow-up email. Battlecards that live only in a portal nobody visits produce nothing; battlecards embedded in the reps' daily workflow lift competitive win rates measurably.

One battlecard per competitor, two pages maximum

Above two pages, reps don't read it in the middle of a deal. Structure: (1) 30-second summary at the top — who they are, primary positioning, ideal customer, stage. (2) Where they beat us — honest, specific, so reps aren't blindsided. (3) Where we beat them — with specific facts and customer proof. (4) Landmines — questions to ask early that expose their weaknesses. (5) Top 5 objections and how to respond. (6) Recent news bar (last 60 days). Longer than this and reps use the browser instead.

Distribute where reps already work

The failure mode: battlecards in Google Drive, Notion, or a competitive-intel portal reps have to remember to open. What works: linked in your CRM under each opportunity's competitor field, surfaced via Slack bot when a competitor is mentioned, embedded in sales enablement tools (Highspot, Seismic, Gong), and included in the deal-desk workflow for any deal above a size threshold. Adoption depends more on placement than on quality.

Freshness beats depth

A slightly-imperfect battlecard updated monthly beats a comprehensive one that's 8 months old. Assign an owner per battlecard (product marketing usually), quarterly review meeting where each owner presents changes, kill or archive battlecards for competitors reps no longer see in deals. Stale battlecards are worse than absent ones — reps use them, get blindsided when the competitor has changed, and lose trust in the asset.

The response scripts that actually work

For each top objection, write the exact language a rep should use — not principles. 'They said X is cheaper' → response: '<specific 2-sentence reframe using outcome instead of price>, and here's a customer who switched and here's why: <one-line quote>'. Reps under deal pressure don't extemporize; they use language you gave them. Test the language by listening to Gong recordings and refining the phrases that worked.

Measure use, not existence

Track: battlecard opens per rep per week, competitive deal win rate before and after a battlecard update, deals where the battlecard was referenced in the notes, rep-reported usefulness (2 questions in monthly enablement survey). A battlecard that isn't opened is a signal to either kill it or redistribute it — not to make it better.

Frequently asked questions

How many battlecards should we have?: The competitors reps actually see, ranked by deal frequency. Typically 4-8 for a Series A/B B2B company. Above 10, you're building content for competitors who rarely show up in deals, at the cost of maintenance on the ones that matter.
Should we share battlecards with customers or partners?: No. Battlecards are internal-only. Customer-facing competitive materials (independent comparison sheets, third-party analyst reports) are different assets, produced with different tone and standards.
Can we generate battlecards with AI?: Partially. AI is useful for first drafts of the summary, competitor news aggregation, and pulling quotes from public sources. It can't do the win-loss synthesis, the landmine questions, or the customer-specific proof that makes battlecards actually useful. Treat AI as a research assistant, not the author.