.webp)
.png)
A sales battlecard is a one-page internal reference that gives a rep what they need to position against a specific competitor while the conversation is happening. It is not a product sheet and not a competitive analysis: its unit of measure is the second, because it gets opened just before a call or during one. This article covers the six blocks that earn their place, what to cut, and the update rhythm without which the card becomes actively harmful.
When did anyone last read the battlecard your team is still using?
The bottom line: a stale battlecard is worse than no battlecard. A rep opens it, cites a claim that is no longer true, the prospect corrects them, and credibility drops for the rest of the meeting. So the question is not what to put in it, but what you can realistically keep current.
What a battlecard is for, and what it is not
The format came out of product marketing, where it solved a specific problem: the people with deep competitive knowledge were not the people in the room when it mattered. The battlecard is the artifact that tried to close that distance.
It is not a full sales argument, not a comparison document for the buyer, and above all not a disparagement sheet. Klue, whose guide on competitive battlecards is the reference piece on the subject, frames them as enablement content that helps reps sell against competitors rather than as a repository of everything known about them. The distinction between helping and documenting is the whole design brief.
The six blocks worth keeping
| Block | Content | Common failure |
|---|---|---|
| Header | Competitor name, last updated date, owner | No date, so nobody knows the card's age |
| When we win | Two or three specific, checkable scenarios | Claiming a better product in general terms |
| When we lose | The cases where they are the right choice | Deleting the block because it is uncomfortable |
| Their real strengths | Three honest points the prospect will raise | Minimising them, which discredits the card |
| Objections and responses | What buyers actually say, with a tested answer | Answers nobody has ever said out loud |
| Reframing questions | Two questions that return to your criteria | Going straight to a head-to-head comparison |
The third block is the one teams cut first and should keep. Knowing where the competitor genuinely fits saves time on unwinnable deals, and it shows in the room: a rep who can say that in this specific case the other solution is the better fit earns credibility that pays across everything else.
What to cut
- Company history, headcount, headquarters. None of it helps during a call.
- The full SWOT, which belongs in an analysis document rather than on a field card.
- Screenshots of their interface, which age faster than anything else on the page.
- Anything you could not defend if the prospect heard it.
That last line is a useful drafting rule: write every entry assuming the competitor will read it one day. It removes disparagement automatically and forces factual precision, which is also what makes a card survive a legal review.
How many, and how often
Four or five cards, covering the competitors you actually meet. Beyond that none gets maintained, and the maintenance question is the real one. A useful split: the battlecard carries what is durable, meaning positioning, recurring objections, proof points, win and loss patterns. This week's movements go somewhere else, in a short competitive digest, and the card only changes when that digest confirms a material shift.
Without that rule the card accumulates every update until it is unreadable, which is the second most common way battlecards die after going stale. Our guide to objection handling covers what belongs in the objections block and what does not.
Why the objections block is always the weakest
The objections and loss-pattern blocks carry most of a card's value and are filled the worst, because they need material nobody collects: what buyers actually said when they pushed back, and what genuinely tipped the deals you lost. In most companies both are written from memory, based on two or three memorable accounts, by someone who was not in those calls.
So the card reflects the deals that made an impression rather than the deals that happened. That is a measurement problem rather than a writing problem, and it is why rewriting the template never fixes it.
Filling battlecards from what buyers actually say
Praiz solves the material problem at its source. Every call is transcribed and analysed by specialized agents: the Competitors Tracker logs each competitor a prospect mentions along with the context of the mention, the Objection Tracker records objections and how often they recur, and lost-deal analysis documents why deals were lost in the customer's own words. You then get what a battlecard should always contain: objections ranked by real frequency, competitors ranked by how often they actually appear in your pipeline, and loss patterns that are documented rather than reconstructed. Everything is filterable by competitor and period, and criteria are configured to your market in the Praiz AI agents library, with onboarding handled alongside you. Praiz customer teams report a +20% win rate on deals where these signals are put to work.
See it in action
Battlecards written from your real deals
Praiz ranks objections by how often they actually come up and documents losses in the buyer's own words.
Frequently asked questions
How long should a sales battlecard be?
One page, two at most. A battlecard is read in the seconds before a call or during it.
Past two pages it becomes a reference document nobody opens at the moment they need it.
How many battlecards should a team maintain?
Four or five, matching the competitors you actually meet in deals.
Producing fifteen guarantees none stays current, and a stale battlecard is worse than no battlecard.
Should a battlecard list the competitor's strengths?
Yes, and it is what makes the card usable. A battlecard claiming the competitor has no strengths gets discarded the first time a prospect names one.
Acknowledging real strengths lets a rep reframe them instead of denying them.
