Battlecards: what to put on one, with a template and examples
Battlecards are one-page guides that tell a seller how to talk about a competitor: where you win, where you lose, what to say to common objections and what to avoid. Below are a battlecard template you can copy and two filled, fictional examples.
What are sales battlecards?
Sales battlecards are short reference documents that help sellers win deals against a named competitor. A rep opens one before a call or during it, finds the line they need and moves on. They sit in the CRM, a wiki or a shared drive, and they are for internal use only.
A good card answers four questions fast. Who are we up against? Why would a buyer pick us? What will the buyer worry about? What should I never say? A bad card is a long essay that nobody opens after the first week.
What goes on a battlecard?
Six sections cover most needs. Keep each one to a few lines.
- Positioning. One sentence on how you describe yourself against this competitor, and one on who this competitor is best for.
- Strengths. Where the competitor is genuinely good. Reps who deny this lose credibility, so be honest.
- Weaknesses. Where you do better, with the fact behind each claim.
- Objections. The three to five things buyers say when this competitor is in the deal, each with a short reply.
- Landmines. Questions you can ask that expose a gap, and traps to avoid, such as topics where you are weaker.
- Proof. Customer stories, numbers and links the rep can use. Only real ones, with permission.
Add a header with the competitor name, a "last checked" date and an owner. These three things make the card trustworthy and keep it from going stale.
Battlecard template to copy and adapt
Paste this battlecard template into your wiki or CRM and fill each field. Delete any field you cannot back up.
Competitor: [name] Last checked: [date] Owner: [name]
Quick take (one line): [Who they are and who they suit best.]
Our positioning against them: [One or two sentences. Start with the buyer's need, not our feature list.]
Where they are strong:
- [Strength 1, with source]
- [Strength 2, with source]
Where we win:
- [Our advantage 1] Proof: [link or customer]
- [Our advantage 2] Proof: [link or customer]
Common objections and replies:
- "[Objection]" Reply: [two sentences max]. Ask: [one question to move on]
- "[Objection]" Reply: [two sentences max]. Ask: [one question]
- "[Objection]" Reply: [two sentences max]. Ask: [one question]
Questions that expose gaps (landmines to set):
- [Question about a need they handle poorly]
- [Question about a need we handle well]
Traps to avoid:
- [Topic where we are weak. What to say if asked.]
- [Claim not to make, and why]
Proof points: [Case study links, verified numbers, review sites]
Pricing notes: [Public prices only, with date checked]
Write replies the way people talk. If a rep cannot say it out loud without sounding like a brochure, rewrite it. For more reply patterns, see sales objection handling examples.
Competitive battlecard examples
These two competitive battlecard examples are fictional. "Northbeam" is a made-up project-planning tool, and the competitors "Gridly" and "Quillboard" do not exist. All prices, features and numbers are invented to show the shape of a card. Use real, checked facts on your own.
Example 1: Northbeam vs Gridly (fictional)
Competitor: Gridly Last checked: [date] Owner: [name]
Quick take: Gridly is a spreadsheet-style planner. It suits small teams who like a familiar grid and plan simple projects.
Our positioning: Northbeam is for teams that coordinate across several groups and need dependencies and timelines to update on their own.
Where they are strong:
- Very quick to start. A new user can build a plan in minutes.
- Lower price for teams under ten.
Where we win:
- Dependencies update the timeline automatically. Gridly needs manual edits. Proof: [demo link]
- Portfolio view across projects. Proof: [customer story]
Objections and replies:
- "Gridly looks simpler." Reply: It is simpler at the start. The question is what happens at the point your plan has more than a few dozen tasks and three teams. Ask: How many teams touch a typical project?
- "Gridly costs less." Reply: For a small team that is true. Let's compare the total cost once you count the time spent keeping the dependencies right by hand. Ask: Who owns plan updates today?
- "We already know spreadsheets." Reply: We can import your sheets, so you keep the layout and add the timeline view. Ask: Can I show you an import of one of your files?
Landmines to set:
- "What happens to your timeline when one task slips?"
- "How do you report across projects today?"
Traps to avoid:
- Do not claim we are faster to learn. We are not.
- Do not quote Gridly prices from memory. Check their pricing page.
Example 2: Northbeam vs Quillboard (fictional)
Competitor: Quillboard Last checked: [date] Owner: [name]
Quick take: Quillboard is a large suite with many modules. It suits big companies that want one vendor for everything.
Our positioning: Northbeam does planning well and connects to the tools you already own. You do not need to replace your stack.
Where they are strong:
- Broad feature set and a large partner network.
- Procurement teams already know the vendor.
Where we win:
- Faster setup. Customers go live in weeks. Proof: [real customer, with permission]
- Open connections to common tools. Proof: [integration list link]
Objections and replies:
- "Quillboard does more." Reply: It does, and many teams use a fraction of it. Which three features would you use every week? Ask: Let's check those three against our product.
- "IT prefers one vendor." Reply: Understood. We pass the same security review steps and connect through standard sign-in. Ask: Can I send our security summary to your IT contact?
- "Switching is a big project." Reply: We plan a phased start with one team first. Ask: Which team would be the best pilot?
Landmines to set:
- "How long did your last rollout of a large suite take?"
- "Who in your team can change a workflow without a consultant?"
Traps to avoid:
- Do not say we have the same depth of features. We do not.
- Do not criticize the buyer's current vendor. They chose it.
How do you keep battlecards current?
Stale cards do more harm than no cards, because a rep who repeats an old price loses trust on the spot. A simple routine helps.
- Put a date and an owner on every card. Unowned cards rot.
- Review on a calendar. Quarterly works for most teams. Tier your competitors, and review the top few more often.
- Watch for triggers. A new price, a launch, a funding round or a rebrand each justifies a review within days.
- Use public sources. The competitor's pricing page, docs, release notes and customer reviews. Note the date you checked.
- Collect field notes. After each deal, ask reps what the buyer said about the competitor. A shared form or a CRM field is enough.
- Cut dead cards. If nobody has opened a card in a quarter, archive it.
- Check with legal. Claims about competitors can create risk. Keep to facts you can support.
How do you use battlecards on live calls?
Reading a battlecard top to bottom on a call does not work. Use it in three moments.
- Before the call. Skim the quick take, the landmine questions and the traps. Pick two questions to ask.
- During the call. Keep the objections section one click away. When the buyer names the competitor, find the matching line, answer in your own words, then ask the follow-up question from the card.
- After the call. Note what the buyer said and whether the card helped. Send the note to the owner.
Do not read replies word for word. Buyers hear it. Learn the idea behind each reply and say it your way. Listen first, because the buyer's actual concern is often different from the one on the card.
If you want live help on a call
Preparing and practicing beats any tool. Still, on a live call it can be hard to find the right line while also listening. Hintly is a desktop app for Mac and Windows that listens to a call and shows a suggested answer in a small overlay, built from your own notes such as battlecards and deal docs. The overlay is left out of screen shares. It is pre-launch, so you can join the waitlist. Check your company's rules on tools in customer calls first. More on the AI sales call assistant page.
Questions
What is a sales battlecard?
A sales battlecard is a short internal document, usually one page, that helps a seller handle a deal where a specific competitor is involved. It covers how to position against them, their strengths and weaknesses, likely objections with replies, and traps to avoid.
How long should a battlecard be?
One page, or one screen. If a seller cannot find the answer in about ten seconds during a call, it is too long. Put the deeper research in a separate document and link to it.
Who should write battlecards?
Product marketing or sales enablement usually owns them, but the best input comes from sellers who have been in the deals. Ask reps what customers actually said, and check claims with product and legal before they go out.
How often should battlecards be updated?
Review each card on a set schedule, such as every quarter, and also whenever a competitor changes pricing, ships a major feature or changes positioning. Put a last-checked date on every card and retire cards nobody uses.
Can I share battlecards with customers?
No. Battlecards are internal and often include frank notes on your own weak spots. Build a separate, polished comparison page for customers and make sure every claim on it is accurate and sourced.
Should battlecards name competitor weaknesses?
Yes, but only facts you can back up from the competitor's public pages, reviews or your own deal notes. Do not repeat rumors. If a point is a rumor, leave it off or label it as unverified.