A product marketing manager updates the battle card for the main competitor on Monday. On Wednesday an account executive loses a deal to a feature that was never on the card. This is not a story about a careless PMM. It is the normal life cycle of a battle card built the usual way: researched episodically, written once, and left to age.
Reps know this, which is why they stop reading them. Surveys of sales enablement content consistently find that the majority of what marketing produces is never used in a deal. Battle cards are among the most requested and least trusted of those assets, and for the same reason: the rep hears the competitor's current pitch every week, and the card describes last quarter's.
This guide covers the structure of a battle card that reps trust and the maintenance loop that keeps it that way.
Why battle cards go stale
Three forces work against every card.
The competitor changes faster than the review cycle. Competitors ship features, change pricing, and adjust messaging continuously. A quarterly review, which is generous for most teams, means the card is out of date for most of its life.
The inputs are episodic. The PMM's sources are a handful of call recordings sampled from hundreds, a Slack thread where two reps gave conflicting answers, the competitor's website, and G2 reviews. The sample is small and biased toward whichever deal someone was thinking about when asked.
There is no feedback loop. The card ships, and nothing reports back on whether the positioning worked. If the "why we win" section is wrong, the PMM finds out at the next loss review, if at all.
The underlying issue is that the intelligence the card needs already exists in the sales team's conversations. Every discovery call where a competitor is named is a data point about their current pitch, their pricing, and the objections they generate. Almost none of it reaches the card.
Common approaches and why they fall short
| Approach | Why teams do it | Where it breaks | |----------|-----------------|-----------------| | Feature comparison matrix | Feels rigorous; easy to build from websites | Reps do not sell from feature lists. Prospects rarely decide on them. Goes stale the moment either vendor ships. | | Annual competitive deck | One big research push | Out of date within weeks; no rep opens a 40-slide deck mid-deal | | Vendor-copied positioning | Fast | Describes the competitor as they describe themselves, not as prospects experience them | | "Ask the reps" Slack thread | Real field input | Anecdotal, contradictory, unrecorded. The knowledge dies in the thread. | | Competitive intelligence tools (external signals only) | Tracks the competitor's public moves | Knows what the competitor announced, not what prospects say about it or which deals it appears in |
Each captures part of the picture. None connects external signal to internal evidence, and none updates as a byproduct of selling. For a view of tools in this space and what each actually monitors, see the competitive intelligence tools directory category.
The structure of a card that gets used
A battle card has one job: help a rep handle the next 90 seconds after a prospect says the competitor's name. Everything on it should serve that moment. The structure below is what works, in the order a rep needs it.
1. What they do (two sentences)
How the competitor positions itself, in their words, and the buyer they are built for. This sets the frame. If a rep does not understand what the competitor is genuinely good at, every other section reads as spin.
2. Their real strengths
Three or four honest points. Reps will encounter these strengths in the deal; a card that pretends they do not exist loses credibility on first use. "Their call recording quality is excellent" is more useful than a card that implies otherwise, because it tells the rep not to fight on that ground.
3. Their weaknesses, from the buyer's side
Not what you wish were wrong with them. What prospects and churned customers actually say. Each weakness should be traceable to evidence: a call, a review, a loss interview. The weaknesses that win deals are the ones the prospect has already felt.
4. Where we win and where we lose
Two short lists of deal conditions. "We win when the buyer needs insights to reach marketing, not just sales" is a condition a rep can recognize in discovery. "We lose when the buyer is 500+ reps and needs enterprise support infrastructure" tells the rep when to stop spending time. The losing list is the most honest and the most useful section on the card, and it is the one most teams omit.
5. Objection handling
The two or three things a prospect says when they are leaning toward the competitor, each with a response that has worked. The response should be short enough to say aloud and should redirect toward a strength rather than attack the competitor.
6. The one-line differentiator
A sentence the rep can say from memory. If the rest of the card disappeared, this is what survives.
7. Sources and last verified
The date the card was last checked against evidence, and the calls, reviews, or interviews it drew on. A card without this is an opinion.
The competitive battle card template has this structure as a fill-in document.
Worked example: a card built from calls
Here is what the process looks like for a hypothetical competitor, call them Competitor A, a well-funded call-recording platform.
Step 1: Pull the evidence. Searching the last 90 days of call transcripts for "Competitor A" returns 34 calls. Extracting the relevant passages produces:
- 21 calls where a prospect mentions Competitor A as an incumbent or an alternative
- 9 distinct objections, of which three account for 70% of mentions: "we already have it," "our reps are used to it," and "the API integration was painful but it's done"
- 6 calls where a prospect volunteered a frustration: insights "stay in the sales org," and pricing "went up at renewal"
- Outcomes: 8 won, 7 lost, 6 open
Step 2: Find the pattern. Of the 8 won deals, 6 had a stated need for call insights to reach marketing or product. Of the 7 lost, 5 were enterprise accounts with a multi-year contract in place. That is the "where we win / where we lose" section, written by the data.
Step 3: Draft the card.
What they do. Competitor A is the category leader in conversation intelligence: recording, transcription, and call analytics, expanding into forecasting.
Strengths. Transcription and speaker identification are excellent. Deep enterprise adoption and CRM integrations. Name recognition: "Competitor A" is nearly synonymous with call recording.
Weaknesses (from prospects). Insights stay in the sales org; marketing never sees them (6 calls). Export requires heavy custom engineering (4 calls). Renewal pricing increases (3 calls).
We win when the buyer wants call insights to reach marketing and product; the team is mid-market and priced out of the enterprise tier; the buyer describes the "data in, nothing out" problem unprompted.
We lose when the account is enterprise with a multi-year contract; the buyer only needs recording and basic analytics; sales ops is the sole buyer with no cross-functional mandate.
Objection: "We already use Competitor A." "It is excellent at recording and analyzing calls. The question is what happens after the analysis. Does it update your battle cards? Feed your content team? Most Competitor A customers tell us their call data is a gold mine they never fully mine."
Differentiator. "Competitor A records your calls. We turn them into knowledge your whole GTM team uses."
Sources. 34 calls, 2026-06-01 to 2026-08-31. Last verified 2026-09-05.
Every claim on that card points at a call. When a rep doubts a weakness, they can listen to the prospect say it.
Step-by-step implementation
- Pick the three competitors that appear most in your pipeline. Not the ones that worry leadership most. Check the CRM competitor field, or search transcripts for names, and rank by frequency.
- Define the evidence window. The last 90 days of calls is enough for most teams. Older evidence describes a competitor that no longer exists.
- Extract, do not sample. Run every call in the window through a step that pulls out competitor mentions, the objection raised, the prospect's verbatim frustration if any, and the deal outcome. A person with a template can do this for 30 calls; past that, use a call intelligence tool or an extraction pipeline.
- Write the card from the evidence, in the seven-section structure. Every weakness and every win condition should cite at least one call.
- Ship it where the rep will see it. Pinned in the CRM competitor field, linked in the deal record, surfaced in call prep. A card in a Confluence space is a card nobody reads.
- Set a refresh trigger, not a refresh date. The card is re-verified whenever the competitor appears in ten new calls, or when a loss review names a claim on the card as wrong. Quarterly review is the fallback, not the plan.
- Close the loop at loss reviews. Every competitive loss answers one question: was the card right? If the prospect raised an objection the card did not cover, it goes on the card that week.
Maintenance cadence
| Trigger | Action | Owner | |---------|--------|-------| | Competitor named in 10 new calls since last verification | Re-run extraction; update weaknesses and objections | PMM | | Competitive loss | Loss review checks every claim on the card; add missing objection | AE + PMM | | Competitor pricing or packaging change | Update strengths, objection handling; note date | PMM | | New rep onboarding | Rep reviews card, then flags anything that did not match their first 10 calls | Rep | | 90 days with no trigger | Full re-verification | PMM |
The point of trigger-based maintenance is that the card's freshness tracks the market's rate of change, not the calendar. A competitor who appears in three deals a week gets refreshed weekly. One who appears twice a quarter does not consume the PMM's time.
Where this leads
A battle card built this way is a view over a body of evidence, not a document. That is a different thing to maintain. When the evidence updates continuously (every call is extracted, every loss review is captured), the card can be regenerated rather than rewritten, and the PMM's job shifts from research to editorial judgment.
This is how battle cards work in TurnkeyGTM. Call transcripts and documents are extracted into competitive mentions, objections, and pain points with confidence scores; a battle card is generated from that evidence with numbered citations back to the calls, and it can be regenerated as new calls land. The PMM reviews and edits rather than rebuilding from a Slack thread. If you want to see what your last quarter of calls says about your top competitor, join the waitlist.
Related
- Template: Competitive battle card
- Guide: How to reduce sales rep ramp time
- Directory: Competitive intelligence tools · Call intelligence tools
- Glossary: Competitive battlecard · Win-loss analysis