I wrote the book on developer marketing. Literally. Picks and Shovels hit #1 on Amazon.

Get your copy
Marketing and demand gen

Battlecard

BAT-ul-kard

A one-page competitive reference for sales reps. Covers a competitor's strengths, weaknesses, and how to win against them.

A battlecard is a concise reference document that arms sales reps to compete against a specific competitor. It fits on one page (or two screens). It is a key competitive positioning tool that answers the questions a rep needs in the middle of a deal: What are their strengths? Where are they weak? When do we win? When do we lose? What should we say? What should we avoid?

The best battlecards are created from real win/loss data, not marketing assumptions. If you lose to Competitor X because of pricing, the battlecard should address pricing head-on with a response the rep can use in the conversation.

Battlecards should be updated quarterly or whenever a competitor makes a significant change (new product, pricing change, acquisition). Stale battlecards are worse than no battlecards because they give reps confidence in outdated information.

Examples

A battlecard structure that works.

One page. Sections: Competitor overview (2 sentences). Their strengths (be honest). Their weaknesses (be specific). When we win (scenarios where we have advantage). Trap questions to ask the prospect. Landmine questions the competitor will plant. Key proof points and customer references. Reps pin it to their monitor.

Battlecard drives win rate improvement.

Win rate against Competitor B: 28%. The team creates a battlecard based on 15 loss interviews. Key insight: prospects choose Competitor B for faster implementation. Battlecard includes a rapid deployment plan and a customer story about a 2-day implementation. Six months later, win rate against Competitor B: 41%.

A battlecard stays unused.

Product marketing creates a 10-page competitive analysis document. Nobody reads it. They condense it to a one-page battlecard with only the information needed during a live sales conversation. Adoption goes from 10% to 75% of the sales team.

In practice

Competitive battlecard framework

BATTLECARD: [Your Product] vs. [Competitor]
Last updated: [DATE] | Owner: [PMM Name]

QUICK POSITIONING
When the prospect mentions [Competitor], say:
"[2-sentence positioning statement that reframes the conversation]"

WHEN WE WIN
- [Scenario 1: e.g., "Customer needs X capability"]
- [Scenario 2]
- [Scenario 3]

WHEN WE LOSE
- [Scenario 1: e.g., "Customer already deployed their ecosystem"]
- [Scenario 2]

KEY DIFFERENTIATORS
| Capability | Us | Them | Proof point |
|------------|----|----- |-------------|
| [Feature]  | [Y/N/Detail] | [Y/N/Detail] | [Customer quote, benchmark, or doc link] |

OBJECTION HANDLING
Objection: "[Competitor] is cheaper."
Response: "[Reframe around value, TCO, or capability gap]"

Objection: "[Competitor] has more integrations."
Response: "[Address with specifics]"

LANDMINES TO SET
Questions to ask the prospect that expose competitor weaknesses:
1. "Have you asked them about [known weakness]?"
2. "How do they handle [capability they lack]?"

PROOF POINTS
- [Customer name]: Switched from [Competitor], saw [result]
- [Benchmark/analyst quote]

Read more on the blog

Frequently asked questions

What should a battlecard include?

Competitor overview, their strengths, their weaknesses, scenarios where you win, trap questions to ask, landmine questions to expect, proof points and references, and common objections with responses. Keep it to one page. If reps cannot scan it in 60 seconds, it is too long.

How often should battlecards be updated?

Quarterly at minimum. Immediately when a competitor makes a major change (new product, pricing change, acquisition, executive hire). Assign a specific person to own each battlecard. Stale battlecards erode trust between marketing and sales.

Related terms

Picks and Shovels: Marketing to Developers During the AI Gold Rush

Want the complete playbook?

Picks and Shovels is the definitive guide to developer marketing. Amazon #1 bestseller with practical strategies from 30 years of marketing to developers.