The honest truth about most battlecards is that they're built once, hosted in a sales-enablement wiki, and forgotten. The product team asked for one. Someone built a 12-page deck per competitor. It went into a folder. The reps occasionally remember it exists when a prospect says a competitor's name on a discovery call. They click through, can't find what they need in the moment, and answer from memory anyway.
This guide is about building battlecards that actually get used. Not a wiki page nobody opens — a working set of pages in your vault that the agent can read, update, and surface in seconds when a competitor's name comes up.
Why traditional battlecards go stale fast
The shape is wrong. A 12-page deck per competitor tries to be both reference material and in-the-moment ammo, and it's bad at both. Too long to read mid-call. Too rigid to update when something shifts. Too separated from the actual conversations where the competitor's name gets said.
There's also a maintenance problem. The product marketer who built the original deck moved teams six months ago. Nobody owns updating the pricing section when the competitor changed their packaging. The objection-handling section still references a feature gap that closed three releases back. Reps stop trusting the card because half of what's in it might be wrong.
The fix is to build battlecards as living markdown pages instead of decks, in the same vault as your call transcripts and account plans, with an agent that helps keep them current. The broader sales-day workflow this fits inside is in How to Use AI in Sales (Without Falling for the Hype), and the related-account-plan shape that pairs with this is in How to Build Account Plans in Your Notes App (Without a Separate Tool).
The 6-section battlecard that fits one screen
A battlecard that gets used has six sections. Six is enough.
- TL;DR — three sentences. What this competitor is, who they target, the one thing to remember.
- Where they win — the genuine strengths. Be honest. A card that pretends a real competitor has no strengths gets ignored.
- Where we win — our genuine differentiators against this specific competitor. Specific, not generic.
- Common objections (and our answers) — the four or five objection patterns reps actually hear, with handling notes.
- Recent moves — what's changed in the last 90 days. New product, pricing change, executive shuffle, raise, layoffs.
- Field intelligence — quotes pulled from our own call transcripts where prospects mentioned this competitor.
Each section is plain markdown. The TL;DR is the part you read in the thirty seconds between when the prospect says the competitor's name and when you have to respond. The other sections are there for prep before the call.
Recent moves, kept current by the agent
The Recent moves section is what battlecards usually get wrong. They get built and then frozen. The fix is making the maintenance lightweight enough to actually do.
A simple shape works: subscribe to a Google Alert or RSS feed for the competitor, save anything notable as a PDF or markdown snippet to the competitor's page in your vault. Press releases, product updates, executive announcements, funding news. The PDFs auto-convert to markdown via docstrange so they become searchable text the agent can read.
Once a quarter, ask the agent: "Read the source documents on the Acme Competitor page from the last 90 days. Update the Recent moves section to reflect what's actually shifted." A draft comes back; you sharpen it; the section is current. Twenty minutes of upkeep instead of a full redo.
For the broader competitive-research shape — the one that pairs with prospect research before cold outreach — see How to Use AI Notes for Prospect Research Before Cold Outreach.
Field intelligence, pulled from your own calls
This is the section that makes a battlecard genuinely useful and that wikis can never produce. Real prospect quotes about the competitor — the words they actually used, the concerns they raised, the wins they cited.
The mechanic is simple. Your call transcripts already live in the vault, with speaker labels. Once a month, ask the agent: "Read every call transcript from the last 30 days. Find every mention of Acme Competitor — what the prospect said, the context, and the speaker. Add the relevant quotes to the Field intelligence section of the Acme Competitor page."
A draft list comes back. You curate — keep the genuinely insightful ones, drop the noise — and the section grows over time into a corpus of real prospect language that beats any product-marketing pitch about the competitor. The capture habit that makes the call transcripts available in the first place is detailed in AI Notes for Discovery Calls: Capture, Recall, Close.
After six months of this, the Field intelligence section is the most-read part of every battlecard. It's the only place a rep can hear actual prospects' actual words about the competitor, in plain text, attributable.
Where they win — the section that earns trust
The hardest section to write honestly is "Where they win." Most battlecards either skip it or fill it with weak compliments that nobody believes. Reps stop trusting the card.
The honest version names the genuine strengths. If the competitor has a real advantage — an integration we don't have, a vertical they own, a pricing model that fits a particular segment better than ours does — write it down. The point isn't to demoralize the team. The point is to give reps a card they can actually use, including knowing when to walk away from a deal that the competitor is genuinely better suited for.
Ask the agent to help: "Read the call transcripts from the last 60 days where prospects ultimately picked Acme Competitor over us. Pull the reasons they cited. Suggest additions to the 'Where they win' section." The agent reads the losses (which you should be tracking anyway) and surfaces patterns. You confirm.
When reps feel the card is honest, they open it. When they feel it's marketing-team chest-thumping, they don't. The shape that this descends from for the broader account-plan view is in How to Build Account Plans in Your Notes App (Without a Separate Tool).
In-the-moment use during a live call
The in-the-moment use case is the test for whether the card is built right. The prospect says "we're also evaluating Acme." You have ten seconds before they expect a substantive response.
The card needs to be openable in two clicks and readable in ten seconds. The TL;DR section earns its keep here. Three sentences telling you what this competitor is, who they target, and the one thing to remember. You glance at it; you have a coherent opening response.
The follow-up — the part where you actually need to handle the objection or differentiate — happens in the next thirty seconds while the prospect is still talking. You glance at "Where we win" and "Common objections." Specific differentiators, not generic talking points.
If the conversation goes deep into the comparison, you take a breath, ask a clarifying question to buy time, and read the Field intelligence section while the prospect answers. Real prospect quotes about the competitor often unlock the right next question — "I've heard that from other folks evaluating both of us; what's driving the comparison for your team?" — and the conversation gets easier.
Common objections, answered specifically
The Common objections section is the part reps reach for most often. Done badly, it's a generic "if they say X, say Y" script. Done well, it's specific patterns drawn from real calls.
For each objection, three pieces — the objection in the prospect's words, the underlying concern (what they're really worried about), and the handling notes (the questions you ask, the differentiators you lean on, the proof points you reach for).
Ask the agent: "Read the call transcripts from the last 90 days. Find every objection that was framed in terms of Acme Competitor. Group them by pattern. Add the most common patterns to the Common objections section." The agent finds patterns you wouldn't have noticed; you write the handling notes from your own playbook.
The shape that pairs with this for handling enterprise-deal objections specifically is in How Enterprise Sales Teams Use AI Notes for Deal Management.
Maintenance — and a calmer way to carry competitive context
The reason most battlecards die is that nobody owns maintenance. The fix isn't to assign an owner — that doesn't survive reorgs — it's to make maintenance so cheap that anyone can do it in a few minutes.
Once a month, ask the agent: "Across all competitor pages, what hasn't been updated in 60 days? Which Field intelligence sections have new quotes worth pulling from recent calls?" A short list comes back. Twenty minutes of shared maintenance keeps the cards current.
When a competitor does something significant — a major release, a leadership change, a funding round — anyone on the team can drop the source PDF onto the competitor page, ask the agent to update the Recent moves section, and the card is current within minutes. The maintenance is distributed and low-friction.
Worth being clear about limits. This isn't a competitive intelligence platform — Klue and Crayon still have their place if your team is at that scale. It isn't shared in real time across a team in the way a wiki is — the vault is single-user, scoped to the rep who owns it.
What it is: a working set of battlecards each rep can keep current, in the same vault as their call transcripts and account plans, with an agent that surfaces the right card at the right moment. Cards that get used.
Competitive deals are going to be a lot of context whether your tools are good or not. But the part that makes battlecards useless — the staleness, the wrong-format problem, the disconnect from real call data — is fixable.
Try Docapybara free. Pick the one competitor you lose deals to most often, build the six-section card, and let the agent pull real prospect quotes from your call transcripts.