Ask any VP of Sales why their reps aren't using the battlecards. The answer is almost always one of three things: "they can't find them," "they don't trust them," or "by the time they need them, the call is already happening."
These are not training problems. They're not discipline problems. They're design problems. The battlecard was never built to be usable — it was built to exist, to check the box that says "we have battlecards."
Here's what's usually happening.
The stale PDF problem
Most battlecards live in a shared Google Drive somewhere. Or a Notion page. Or a Confluence doc that nobody has touched since Q2 of last year. The person who created them — usually someone in product marketing — spent real time building them out. Good competitor research, solid objection handling, accurate pricing comparisons.
Then the competitor changed their pricing. Then they launched a new feature. Then they rebranded their enterprise tier. And the battlecard still says what it said nine months ago.
Sales reps know this. After using a battlecard that had wrong pricing once, they stop trusting it. Once they've been in a call where the prospect says "actually, they changed that a few months ago" and the rep is sitting there with outdated information, they stop reaching for it. The battlecard becomes a liability, not an asset.
This is the stale PDF problem, and it's completely avoidable — but it requires a fundamentally different approach to how battlecards get maintained.
The format problem
Even when battlecards are current, many aren't usable in the moment a rep needs them.
A 20-page competitive analysis is not a battlecard. That's a research document. A battlecard is what a rep can pull up mid-call, scan in 15 seconds, and use to handle a specific objection or positioning question. The format matters as much as the content.
Good battlecards have five things, nothing more:
- One-line positioning: What's the core difference? One sentence. If you can't say it in one sentence, you don't have a clear position yet.
- Their three best features: What does the competitor do well? Reps need to be honest about this. "They're strong on X and Y, which is why prospects consider them" builds credibility. "They're weak at everything" trains reps to get blindsided.
- Our three advantages: Specific. Not "better analytics" but "we show headcount changes in real time; they batch it weekly."
- Top 5 objections with responses: The actual words a rep can say. Not bullet points, but sentences. "When they bring up pricing, say this: ..."
- Current pricing: Up to date. If it's more than 30 days old, it shouldn't be on the card.
One page. Scannable. Linked from wherever reps work — their CRM, their Slack, their browser bookmark bar. If a rep has to navigate to it, they won't navigate to it during a call.
The timing problem
Even a current, well-formatted battlecard fails if a rep has to go find it when they're already in a conversation with a prospect.
This is the hardest problem to solve with static documents. The rep finds out they're competing against Klue in the first five minutes of a discovery call. They have two options: interrupt the flow to search for the battlecard, or wing it. Most reps wing it.
The better approach is delivery, not documentation. The rep should have the relevant battlecard in front of them before the call starts, triggered by CRM data. If the opportunity record says "competing against Klue," the Klue battlecard should surface automatically in whatever tool the rep uses to prep.
Some CRMs support this natively now. Outreach and Salesloft have competitive sections. Highspot and Seismic have battlecard features. The technology to solve this exists — but it only works if the battlecard it surfaces is current and formatted for quick consumption.
What living battlecards actually look like
At Prometheus, "living battlecards" means something specific. The content isn't written once and left to decay. It's updated automatically when competitor data changes.
When a competitor changes their pricing page, the pricing section of their battlecard gets flagged for review and updated. When they launch a new feature that appears in their changelog or press release, it appears in their battlecard. When their G2 reviews shift — say, support scores drop significantly — that shows up in the "their weaknesses" section.
A rep looking at a Prometheus battlecard knows it reflects what the competitor is doing right now, not what they were doing last quarter. That reliability changes rep behavior. They start checking battlecards before calls because they trust them.
The win rate data
We analyzed win rates across Prometheus customers who used battlecards actively versus teams that had them but rarely accessed them. The difference was 42 percentage points in competitive win rate for deals where the rep accessed an up-to-date battlecard before the call versus deals where they didn't.
That's not a marginal improvement. It's the difference between winning roughly half of your competitive deals versus winning most of them.
The caveat: the analysis controls for deal size and segment, but it can't fully control for the fact that reps who use battlecards may be more prepared generally. Still, the directional finding is consistent with what our customers report anecdotally — reps who trust their competitive data handle objections better and lose fewer deals to competitors they should beat.
Where to start
If your battlecards are stale PDFs right now, don't try to fix everything at once. Pick your top three competitors by deal frequency and build one-page, format-correct cards for each. Get current pricing directly from their websites today. Find out how to surface these in your CRM or sales tool so reps see them without having to search.
Then figure out how you're going to keep them current. If the answer is "someone updates them manually when they remember," you'll be back in the same spot in six months. Automated monitoring — whether through Prometheus or another approach — is the only way to solve the freshness problem at scale without hiring someone whose entire job is watching competitor websites.
The goal isn't to have battlecards. The goal is to have battlecards that reps actually use. Those are different things, and the gap between them is mostly freshness and format.