How do I build competitive battlecards for my sales team?
Build competitive battlecards reps actually use: the fields to include, where the content comes from, a worked example, and how to keep them accurate.
Nicolas Heath
RevOS™ Director, Swivel
A competitive battlecard works when it's built from how deals against that competitor are actually won and lost — real rep interviews, real call and CRM notes, real objections — not from a marketing team's guess at what the competitor probably says. Done properly it is a competitive intelligence asset with a single job: give a rep the right sentence in the ten seconds after a competitor's name comes up.
Why most battlecards don't get used
A battlecard nobody opens mid-call isn't a battlecard, it's a document. The usual failure mode: marketing writes it from the competitor's website and a few analyst blurbs, ships it as a PDF, and reps stop opening it after the second deal where it didn't match what the prospect actually said. Two things fix that:
Source it from the field, not the internet. The reps who've actually gone head-to-head with a competitor know which objections show up, which claims the competitor's AEs actually make on calls, and where the deal really gets won or lost. That's the raw material — not the competitor's homepage.
Format it for the middle of a call, not a read-through. Scannable sections, short lines, the exact language a rep can repeat back. Nobody is reading paragraphs while a prospect is talking.
The pattern is consistent: the card is built once, reviewed by nobody who sells, and stored where reps don't work. It is too long to read mid-call and too generic to help. Length is the tell — if a rep has to scroll, the card has already failed.
What to include
A battlecard that reps actually use in the room covers:
Who they win against, and why — the two or three situations where that competitor is genuinely the better choice. Reps who can say this out loud get believed on everything else.
Where we win — the specific capability or outcome, not an adjective.
Their strongest objection to us, with the exact response a rep should use.
Our strongest objection to them, with the proof point attached.
Trap-setting questions — two or three questions that surface the competitor's real weakness without naming it.
Pricing and packaging shape — how they charge, not what they charge; the model is stable, the number is not.
Landmines — claims not to make, because they are unverifiable or untrue.
Last verified date and owner — a named person, not a team.
Eight fields is close to the ceiling. Past that, reps stop opening it.
A worked example
Here is what those eight fields look like filled in. The competitor is deliberately generic — a named example dates the moment their pricing page changes, and the method is the part worth copying.
Competitor A — a mid-market platform vendor
Who they win against, and why: Single-department buyers with a hard 30-day deadline. Their self-serve onboarding is genuinely faster, and with no cross-team requirement they are the better choice. Say so.
Where we win: Multi-team rollouts where the numbers have to reconcile across departments. Their reporting is scoped per workspace, so the second team becomes a second source of truth.
Their strongest objection to us: "They take three months to implement." Rep response: "Four weeks to a working report, twelve to full rollout. Three months is the complete multi-team build — ask them what their timeline looks like when the second team joins."
Our strongest objection to them: Reporting does not join across workspaces, so consolidation is a migration rather than a setting. Proof: your strongest consolidation reference, named, with the before-and-after number.
Trap-setting questions: "How many teams will touch this in the next twelve months?" / "Who owns the number when two teams report different figures?" / "What does your per-seat cost look like at fifty users?"
Pricing and packaging shape: Per-seat, billed annually, onboarding sold separately. Tiers gate reporting rather than usage, so the figure a buyer quotes you is rarely the figure they end up paying.
Landmines: Don't say they have no API — they do. Don't suggest they fail security review — they're certified. Both are checkable in a minute, and both cost you the room.
Last verified: 10 Oct 2026 — Nicolas Heath
One card, eight lines, readable in the ten seconds a rep actually has.
Where the content actually comes from
This is the part that determines whether the card gets used. Two sources, in order:
Interview the reps who've been in the room. Not a survey — a real conversation with whoever most recently won and most recently lost against that competitor. Ask what the prospect actually said, not what you assume they said.
Pull it from the data you already have. If your calls are recorded and your CRM notes are real (not "no update"), that's a second, more objective source — what actually got said on the call, and what the deal notes say killed or saved the deal. This is also why a competitive battlecard is a good forcing function to check whether your calling and CRM data are actually usable for this kind of thing — if they're not, that's worth fixing on its own.
Whichever source you use, verify every specific claim about a competitor before it goes on the card. A battlecard with an inaccurate claim about a competitor is worse than no battlecard — the first time a prospect catches it, the rep loses credibility on everything else the card says.
Getting reps to actually use it
Three things move adoption, in this order.
Put it where the deal is, not where the documents are. A card that lives in the CRM on the opportunity record gets opened; a card in a shared drive does not. If your reps work in HubSpot, the card belongs on the deal.
Let the reps write the objection responses. The person who has said the sentence on a live call writes a better sentence than the person who imagined the call. Marketing's job is structure and verification, not wording.
Review it on a cadence tied to deals, not to the calendar. Every lost deal against that competitor is a review trigger. Quarterly reviews drift; loss-triggered reviews stay current. Treating this as part of how you measure the whole revenue motion rather than a one-off enablement project is what keeps it alive.
Keeping it accurate
Competitor positioning shifts — pricing changes, new features ship, messaging gets refreshed. A battlecard is not a one-time document:
Set a review cadence (quarterly is reasonable for most B2B categories) and put someone's name on it
After any deal you win or lose against that competitor, log what was different from the card — that's your update queue
Re-verify named claims periodically rather than assuming they're still true
How this differs from a sales playbook
A sales battlecard is competitor-specific and built for the moment a deal turns into a head-to-head comparison. A sales playbook is broader — it covers the whole first-meeting-to-close motion regardless of which competitor is in the deal. Most teams need both; they're not interchangeable, and a battlecard trying to also be a playbook usually ends up too long for anyone to use live on a call.
A playbook is how you run the deal. A battlecard is what you say when one specific competitor shows up inside it. If you are still settling the definition, start with what a sales battlecard is and come back here for the build.
Want to know whether your sales enablement layer is actually the gap?
A 20-point growth audit scores your revenue engine across four pillars — Foundation, Demand Gen, Human-Centric BD and Sales Performance — and forecasts the pipeline your gaps are costing you.
FAQ
What should a competitive battlecard include?
Eight fields: who the competitor wins against and why, where you win, their strongest objection to you with the response a rep should use, your strongest objection to them with the proof attached, two or three trap-setting questions, their pricing and packaging shape, the landmines your reps must not step on, and a last-verified date with a named owner. Eight is close to the ceiling — past that, reps stop opening it.
Who should build the battlecard — sales or marketing?
Both, with a clear split. Sales supplies the raw material and writes the objection responses, because the person who has said the sentence on a live call writes a better sentence than the person who imagined the call. Marketing owns the structure, the verification and the last-verified date. A card written entirely by marketing reads like marketing; one written entirely by sales tends to be inaccurate about the competitor.
How is a battlecard different from a sales playbook?
A playbook is how you run the deal — stages, discovery questions, qualification, next steps. A battlecard is what you say when one specific competitor shows up inside that deal. The playbook is competitor-agnostic and covers the whole process; the battlecard is competitor-specific and gets opened for ten seconds mid-call. Most teams need both, and conflating them is why battlecards end up too long to use.
How often should battlecards be updated?
Tie reviews to deals, not to the calendar. Every deal lost to that competitor is a review trigger, and so is every win where the competitor's pitch had visibly changed. Quarterly reviews drift because nothing forces them; loss-triggered reviews stay current because the trigger is real. On top of that, re-verify the factual fields — pricing shape, certifications, integrations — at least twice a year, because those are the ones that go stale quietly.
Do reps actually use battlecards, or do they end up ignored?
They get used when three things are true: the card lives on the deal record in the CRM rather than in a shared drive, the objection responses were written by reps rather than for them, and it is short enough to read without scrolling. Cards that fail usually fail on placement first — a rep mid-call will not leave the CRM to go looking.
Do you have a competitive battlecard example or template?
The eight fields above are the template: who they win against and why, where you win, their strongest objection to you and your response, your strongest objection to them with proof, two or three trap-setting questions, their pricing and packaging shape, the landmines to avoid, and a last-verified date with a named owner. The worked example above shows what each field looks like filled in. Build it in whatever tool your reps already open — the format matters far less than whether it lives on the deal record.
