RC-401g · Module 2
Battle Card Creation
3 min read
A battle card is not a product comparison sheet. It is a decision-support tool for the rep who is sitting across the table from a prospect who just mentioned a competitor's name. In that moment, the rep has approximately 15 seconds to respond with something that reframes the conversation. The battle card must deliver the right response in those 15 seconds — not after reading three pages of competitive analysis, not after consulting a 40-slide competitive deck, but immediately. This means the battle card is an exercise in compression and prioritization, not comprehensiveness.
- Structure for Speed, Not Depth Every battle card has five sections, each under 50 words. Quick take: one sentence positioning against this competitor. Their pitch: what the competitor says about themselves (so you can acknowledge it before redirecting). Their weakness: the one structural limitation that matters most to the buyer (not a feature gap — a structural constraint that cannot be solved by their next release). Your counter: the specific capability or approach that exploits their weakness. Proof point: one measurable result or client reference that validates your counter. Five sections. Two minutes to read. Fifteen seconds to deploy the right piece.
- Ground in Intelligence, Not Opinion Battle cards built from sales anecdotes decay within weeks. Battle cards built from intelligence remain accurate for months. VANGUARD provides the ecosystem context: where is the competitor positioned in the broader market trajectory? Are they swimming upstream or downstream? PATCH provides the competitive evidence: actual product capabilities, actual pricing, actual customer feedback, actual hiring patterns that reveal future direction. Every claim on the battle card is traceable to a specific intelligence signal. If you cannot cite the source, remove the claim.
- Build the Update Cadence A battle card that is 90 days old is a liability. Competitors ship updates, change pricing, pivot messaging, and acquire companies. PATCH monitors each competitor's public signals weekly and flags changes that invalidate any battle card claim. When a flag fires, the battle card enters revision within 48 hours. HUNTER provides field feedback: which battle card responses are landing with prospects and which are falling flat? Combine PATCH's external monitoring with HUNTER's field data, and the battle card evolves with the competitive reality instead of falling behind it.
Do This
- Limit each battle card section to 50 words — the rep needs a 15-second response, not a research paper
- Ground every claim in a traceable intelligence signal — "we believe" is not a competitive response
- Update battle cards within 48 hours of a material competitor change — stale cards are worse than no cards
Avoid This
- Build 10-page competitive analysis documents and call them battle cards — nobody reads them mid-conversation
- Include feature-by-feature comparison grids — feature wars are unwinnable because the competitor can always ship the missing feature
- Write battle cards once per quarter and assume they remain accurate — competitive reality moves faster than your content calendar