A rep is on a call and the buyer mentions a rival by name. The rep cannot pause the conversation to dig through old research notes, and guessing at an answer in the moment is how deals slip. A competitive battlecard fixes this: one page a rep can glance at before or during the call that tells them what to ask, what to say, and what to show. This guide is a sales battlecard template you can fill in with your own research, and by the end you will have a usable competitor battlecard for sales team conversations, built around one competitor and one deal situation.
This guide assumes the competitive research is already done. If you still need to figure out who your true competitors are and what actually sets you apart, that is a separate step and a separate piece of work. Here, we turn research you already have into something a rep can use live.
Fix the card to one competitor and one deal situation
Before you write a single line, decide exactly what this card is for. Name the rival. Name the buyer or segment the rep is usually talking to. Name the moment in the sales process where the rep needs help: early discovery when the rival's name comes up, a late evaluation objection, or pricing pressure right before close. Name who owns the card, because a document nobody owns quietly goes stale.
Resist the urge to build one giant card that covers every competitor and every situation at once. A generic card mixes objections that do not belong together and buries the one thing a rep actually needs under background nobody reads mid-call. Start narrow. Pick the competitor that comes up most in your deals right now and the moment where reps struggle most, and build that card first.
As a founder or marketing lead, you can build this first card yourself, using the competitive research and deal notes your team already has, and then hand it to a rep to check before it goes live. You know when this card is done because a rep can tell, just from the heading, when to open it, whose conversation it serves, and which competitor it addresses.
Where it goes wrong: trying to cover every rival on one page, or shipping a card with no named owner. Both lead to the same outcome: reps stop trusting it and go back to guessing.
Choose the buyer-relevant win theme and acknowledge the trade-off
Look at what you already know about this competitor and pick the one difference that matters most to this specific buyer's stated priority. Not your favorite feature. Not the thing your product team is proudest of. The thing this buyer actually said they care about.
Write it as a chain: the verified difference, why it matters to this buyer, and what the rep should do about it. That last part is what turns a fact into something usable. A line like "we support more integrations" tells a rep nothing to do with it. A line like "if their team is moving data between five systems by hand today, ask how much time that costs them each week, then show the workflow that removes it" gives the rep an actual play.
Put an honest limitation right next to the win theme. If the rival is genuinely a strong fit for a certain kind of buyer, or your product has a real gap, say so on the card. A rep who tells a buyer "we are better across the board" loses credibility the moment the buyer notices otherwise, and buyers usually notice.
If your team uses Deep IQ to store your own positioning, differentiators, and the claims you are and are not allowed to make, that is a reasonable place to check your wording before it goes on the card. It tells you what your own team has approved to say about your own product. It does not verify anything about the competitor, and it is not a substitute for the research you already did on the rival.
Done when: the card has one buyer-specific win theme, stated as fact for your own product and framed as an approved claim for anything about the rival, plus one honest trade-off a rep could say out loud without sounding defensive.
Turn each important difference into a discovery question
A rep who leads with a feature pitch before learning whether the buyer cares about that feature is guessing. Write two or three short, neutral questions that find out whether the difference you picked in the last step actually matters to this buyer.
A useful discovery question sounds like something a curious person would ask, not an interrogation. "How much time does your team spend moving data between these systems today?" is neutral. It does not assume an answer, and it does not smuggle in a claim about the rival that you have not verified. If the buyer says integration friction is a real cost, the rep now has an opening to talk about a workflow you can actually back up.
For each question, write down what answer to listen for and which approved talking point it leads to. That is what makes the card usable in real time: the rep is not deciding what to say next, they are following a path you already mapped out.
Avoid "gotcha" questions built to trap the buyer into admitting the rival is bad. Buyers can tell when a question is loaded, and it reads as manipulative rather than helpful.
Where it goes wrong: leading with the pitch before asking anything, or writing questions that only work if the buyer gives the answer you want.
Write speakable responses to the objections reps actually hear
This is the part of the card reps will use most, so write it the way a person actually talks. Take the real objections your reps hear, word for word if you can get them, and write a short response to each: acknowledge what the buyer said, clarify or reframe the concern, back it up with something real, then ask a question that moves the conversation forward.
Price comes up in almost every competitive deal, so give it a real response. Something like: "I understand the lower quote is attractive. Which implementation and support costs are included in that number? We can walk through the full scope together." That is a script a rep can read without sounding scripted, and it turns a defensive moment into a real conversation about what is actually being compared.
You also need a response for the case where the buyer genuinely prefers the rival. Pretending that never happens does not help your reps. Give them a line that acknowledges the buyer's reasoning, explains the trade-off honestly, and proposes a reasonable next step, like a side-by-side trial or a specific reference call, instead of arguing the point into the ground.
Pro tip: read every response on the card out loud before you publish it. If it sounds like marketing copy instead of something a person would actually say in a conversation, rewrite it. A rep will not memorize a paragraph, but they will remember a sentence.
Where it goes wrong: writing long marketing copy instead of a short spoken line, promising a feature that does not exist yet, or writing a response that does not actually address what the buyer is worried about.
Attach proof and remove unsafe claims
Every claim on the card needs something behind it, and that something needs to be current. For a claim about your own product, point to the actual documentation or a demonstrated capability. For a customer result, use only an approved case study or quote, not an anecdote someone mentioned in a hallway. For anything about the rival's public claims, use a dated, specific source rather than something you half-remember from a sales call two years ago.
Note whether each piece of proof is approved to share outside your company. An internal case study your customer success team uses in QBRs is not automatically something a rep can forward to a prospect. Mark it either way so a rep does not have to guess.
If you do not have solid proof for a claim, take it off the card. A vague "we're faster" with nothing behind it gives a rep nothing to point to when a buyer pushes back, and it puts the rep in a bad spot if the buyer asks for specifics. "Not verified yet" is a better state for a line to be in than a claim you cannot back up.
Common mistake: treating a vendor's own marketing page as independent proof of anything. It tells you what the vendor says about itself, not what is actually true. Look for a dated, specific source instead, and if you cannot find one, leave the claim off the card rather than repeating unverified marketing copy as fact.
Lay out the one-page card for a live call
Everything up to this point has been about deciding what goes on the card. This step is about arranging it so a rep can actually use it while they are on a call.
Put the deal situation and the primary action at the very top. Then the discovery questions and talk tracks, then proof, then the honest limitation, then the next step. Use short labels and bullets a rep can scan in a few seconds, not paragraphs they have to read start to finish. Keep detailed source records and deep competitor specifications in a separate internal file; the live-call view only needs what the rep will actually say or ask.
A structure that works well as a sales battlecard template, one you can reuse for the next competitor:
| Section | What goes here |
|---|---|
| Header | Competitor, buyer or segment, deal moment, owner, last verified, next review |
| Top line | One-sentence win theme plus one honest limitation |
| Ask | Two or three discovery questions and the buyer signal to listen for |
| Know | The two or three differences that matter, each with its buyer consequence |
| Say | Objection in the buyer's words, then the response |
| Show | The approved proof, where to find it, and whether it can be shared externally |
| Avoid | The unverified claim or known weak spot reps should not repeat |
| Next move | The specific next step to propose |
Keep this card internal. It is a decision aid for the rep, not something to hand a prospect. Anything meant for the buyer's eyes, like an approved case study or comparison sheet, is a separate asset that this card can point to.
Done when: someone who has never seen the card before can find the question, the response, the proof, and the caution without reading through a paragraph of context first.
Test it with a rep, then publish the approved version
Do not publish the card straight from your own draft. Hand it to a rep and walk them through a realistic scenario: an unfamiliar version of the objection, asked the way a real buyer would ask it. Watch whether they can find the right question, state the one supported difference, point to the proof, and name the honest limitation without hunting through the page.
Whatever they stumble on, fix it. If a rep cannot find the response fast enough, the layout is wrong. If a rep does not believe the proof, get a better source or take the claim off. This is the cheapest round of feedback you will get, and it is far better to catch a weak spot here than in a live deal.
Once it passes that test, put the current version somewhere reps already work, whether that is the CRM, your sales enablement workspace, or wherever your team actually looks for this kind of thing. Retire old copies so nobody is working from a stale version by accident. A short walkthrough or a quick role-play with the wider team when you launch it goes a long way toward actual adoption, not just a document that exists somewhere.
Where it goes wrong: publishing without rep input, or mistaking the card's existence in a shared folder for reps actually using it.
Assign review triggers and inspect use
A battlecard is only accurate for as long as someone keeps it accurate. Put an owner, a last-verified date, and a next review date right on the card, and give reps a simple way to flag something that looks wrong or out of date.
Review the card at least quarterly, and sooner if something material changes: a pricing update on either side, a new feature the rival ships, an acquisition, or a pattern of the same objection showing up in lost deals. If your own product or packaging changes, update the card at the same time, not on the next scheduled review.
Track whether reps are actually opening and using the card, and whether they report inaccuracies. If a card sits unused, that is worth investigating on its own, separately from whether your win rate against that competitor is moving. Win rate is affected by a lot of things beyond one document, so treat any change in it as a signal to look closer, not as proof the card caused it.
Where it goes wrong: updating only on the calendar even after something material has changed, or claiming a revenue result from a card with no real way to measure it.
What to do next
Start with the one competitor your reps run into most and the one deal moment where they struggle hardest. Build that single competitor battlecard for your sales team using the steps above, test it with a real rep, and put it where your team will actually find it. Once it is working, use the same sales battlecard template for your next competitor or your next deal moment. A battlecard that reps trust and actually open beats a folder full of cards nobody reads.
If keeping your own product positioning, personas, and approved claims consistent across every piece of content is part of what is slowing this down, DeepSmith stores that context once and uses it across the content your team produces, so your own facts stay consistent without a re-brief every time. Start a free 7-day trial to see how it fits your workflow.
