Sales Battlecard Template
A competitive battlecard built to be read mid-call, not filed after the kickoff. The full template is below as text you can copy, followed by a worked example and a prompt that fills it in for your own competitor.
No email, no signup. Word opens in Google Docs, the spreadsheet opens in Sheets, and the whole template is on this page as text either way.
The template
1. Header
Who this card is about, and whether it can still be trusted.
Competitor
One competitor per card. A card covering three is a card nobody opens.
—
Where we meet them
Which segment, which deal shape, which persona brings them up.
—
Owner
One named person. Shared ownership means nobody updates it.
—
Last reviewed
A date. If it is more than 90 days old, treat every claim below as a rumour.
—
2. Their pitch, in their words
Write what they say, not what you wish they said. Reps who caricature the competitor lose the room the moment the buyer recognises it.
How they position themselves
One sentence, lifted from their homepage or their pricing page.
—
How the buyer describes them
The sentence you actually hear on calls. It is rarely the same one.
—
3. Head to head
Five dimensions, maximum. The last column is the only one a rep reads while the call is live, so write it as a spoken sentence.
Scroll the table sideways for the remaining columns.
| Dimension | Them | Us | What to say |
|---|---|---|---|
| The core claim | — | — | — |
| Time to first value | — | — | — |
| Depth vs breadth | — | — | — |
| Pricing model | — | — | — |
| Where it breaks | — | — | — |
4. Where we win, and where they win
Both lists, or the card is marketing. The second list is what makes a rep trust the first one, and it is how you stop burning a quarter on a deal that was theirs from the start.
Where we win
Three to five deal conditions, not features. 'The data team owns the budget' beats 'better UX'.
—
Where they win
Say it plainly. Then say what a rep should do about it: qualify out, or change the frame.
—
Walk away when
The one or two conditions where this deal is not worth the quarter.
—
5. Trap questions
Questions you plant with the buyer so their evaluation surfaces the gap without you attacking anyone.
Scroll the table sideways for the remaining columns.
| Question to plant | What it exposes | What a weak answer sounds like |
|---|---|---|
| — | — | — |
| — | — | — |
| — | — | — |
6. Objection responses
Written as the words leaving the rep's mouth. If a line needs to be paraphrased under pressure, it is not finished.
Scroll the table sideways for the remaining columns.
| They say | They mean | You say | Proof |
|---|---|---|---|
| — | — | — | — |
| — | — | — | — |
| — | — | — | — |
7. Proof
Named accounts, dated numbers, or third-party sources. A proof point a rep cannot attribute is a proof point that gets them asked for a source they do not have.
Accounts that switched
Name, quarter, and the one number that moved.
—
Third-party evidence
Analyst note, review site, public benchmark. Link it.
—
8. Do not say
The shortest section and the one that saves the deal. Every claim here has already cost someone a call.
Claims we cannot support
Anything about their roadmap, their churn, or their pricing that you cannot source in one click.
—
Lines that backfire
The disparaging phrasing that makes a buyer defend the incumbent they chose.
—
Filled in: Helio vs Northwind Analytics
Every company, person, and number below is invented. It is here to show the level of specificity the template is asking for.
1. Header
Competitor
Northwind Analytics (Data Health module)
Where we meet them
Mid-market and enterprise data teams that already run Northwind for BI. Almost always raised by the VP Data, never by the analysts.
Owner
Dana Okafor, Product Marketing
Last reviewed
12 August 2026
2. Their pitch, in their words
How they position themselves
“Analytics and data health in one platform, on the stack you already own.”
How the buyer describes them
“We already pay Northwind, and our rep says data quality is included now.”
3. Head to head
Scroll the table sideways for the remaining columns.
| Dimension | Northwind | Helio | What to say |
|---|---|---|---|
| The core claim | Data health checks that run on the dashboards and modelled tables inside Northwind. | Monitoring that runs on the warehouse itself, including raw and staging tables. | Northwind checks the report. We check the table the report is built from. Which one tells you before your CFO opens the dashboard? |
| Time to first value | Coverage starts once a table is modelled in Northwind, so it tracks the BI backlog. | Warehouse connects in a day. First anomalies land inside 72 hours, with no modelling required. | How many tables are modelled in Northwind today, out of everything in the warehouse? That number is your coverage. |
| Depth vs breadth | Freshness and row counts. Broad, shallow, and consistent across everything it sees. | Freshness, volume, schema drift, distribution, and column-level lineage back to the source. | Row counts catch a table that stopped loading. They do not catch a currency column that quietly changed units. |
| Pricing model | Bundled into BI seat count. Invisible until the renewal, then not invisible at all. | Priced per monitored table, so the bill tracks the warehouse rather than headcount. | Ask them what the data health module costs on its own. Most Northwind reps cannot separate it either. |
| Where it breaks | An incident in a table nobody has dashboarded yet is invisible until someone builds the dashboard. | We are not a BI tool. If the team wants one vendor for charts and checks, that is a real trade-off. | You will keep Northwind for reporting. This is about the layer underneath it. |
4. Where we win, and where they win
Where we win
The data platform team owns the budget rather than the analytics team. The warehouse has more than 500 tables. There has been a public incident in the last two quarters and someone has been asked how long it went unnoticed. dbt tests already exist and are already failing silently.
Where they win
A single-vendor mandate from the CIO, which we will not out-argue on a discovery call. Warehouses under about 50 tables, where the extra depth genuinely is not worth a second invoice. Teams where the analytics lead, not the platform lead, controls the evaluation. In the first two, change the frame or qualify out; in the third, multi-thread to the platform lead before the second call.
Walk away when
Procurement has frozen new vendors for the fiscal year and the Northwind renewal is more than two quarters out. There is nothing to sell into until that renewal comes back on the calendar.
5. Trap questions
Scroll the table sideways for the remaining columns.
| Question to plant | What it exposes | What a weak answer sounds like |
|---|---|---|
| When something breaks, is the check watching the table or the dashboard built on it? | That Northwind's coverage is downstream, so detection waits for a dashboard to exist. | “It monitors your Northwind assets.” Assets means modelled tables. |
| How many tables in the warehouse are modelled in Northwind today? | The gap between total tables and covered tables, in the buyer's own number. | A number the buyer has to go and look up. That pause is the point. |
| What did the last data incident cost, and how many hours passed before anyone noticed? | Whether detection time is a metric anyone owns, which is the whole business case. | “We would have to ask the analytics team.” Now there is a second thread to pull. |
6. Objection responses
Scroll the table sideways for the remaining columns.
| They say | They mean | You say | Proof |
|---|---|---|---|
| We already pay for Northwind and data health is included. | I do not want to defend a second invoice to my VP. | Keep it. It is genuinely good at watching what you have already modelled. The question is what is watching the 900 tables that feed those models, because that is where last quarter's incident started. | Wexford Logistics kept Northwind for BI and added Helio underneath it in Q2 2026. |
| Is this not what our dbt tests already do? | I think I have solved this and I do not want to be told otherwise. | dbt tests check the rules you thought to write. Ask your team how many are currently failing and muted. That number is usually the surprise, not the answer. | Public dbt community surveys put muted or failing tests in the majority of mature projects. |
| We will look at this after the warehouse migration. | This is not urgent and I would like to end this call. | That is usually the right call. The one exception is if anything is being decommissioned during the migration, because nobody notices a table that stopped loading while everything is moving anyway. | Two of our last five migrations-first deals came back mid-migration after exactly that. |
7. Proof
Accounts that switched
Wexford Logistics, Q2 2026. Mean detection time on 1,400 warehouse tables went from 9 hours to 11 minutes. Reference call available through Dana.
Third-party evidence
Northwind's own documentation states that Data Health monitors 'assets published to Northwind'. Screenshot in the enablement drive, dated 12 August 2026.
8. Do not say
Claims we cannot support
Nothing about Northwind's roadmap. Nothing about their churn. No pricing figure that is not on their public pricing page, because their enterprise discounting makes any number we quote wrong in the room.
Lines that backfire
Never say Northwind ‘does not do data quality’. It does, at the dashboard layer, and one page of their docs ends your credibility for the rest of the call. Never call it a checkbox feature to the person who bought it.
Fill it in for your competitor
The same eight blocks, researched and drafted for the competitor you actually run into. Give it your website and theirs, then edit the draft rather than starting from a blank card.
Your details
Opens claude.ai or chatgpt.com in a new tab with your prompt ready.
You are a competitive enablement lead at a B2B software company. Build a sales battlecard that an account executive can read mid-call, using the exact structure below. Research both companies before you write. **My company:** ___ **What we sell:** ___ **The competitor:** ___ **Where we meet them:** ___ **Research first.** Read both public websites, pricing pages, documentation, and any recent third-party coverage you can find. Note the date of anything you rely on. If you cannot verify a claim, say so in the card rather than filling the gap. **Produce these eight blocks, in this order:** 1. **Header.** Competitor, where we meet them, and today's date as the review date. 2. **Their pitch, in their words.** One sentence lifted from their own site for how they position themselves, and one sentence for how a buyer is likely to describe them out loud. These are usually different. Do not caricature them. 3. **Head to head.** A five-row table with the columns Dimension, Them, Us, What to say. Use these dimensions: the core claim, time to first value, depth vs breadth, pricing model, and where it breaks. The "What to say" column must be a sentence a rep can say out loud without editing it, and it should be a question or a reframe rather than an attack. 4. **Where we win, and where they win.** Three to five deal conditions in each list, written as conditions rather than features (for example "the platform team owns the budget", not "better UX"). Be honest in the second list, and for each item say what a rep should do about it: qualify out, or change the frame. Add a "walk away when" line. 5. **Trap questions.** Three questions the rep can plant with the buyer so the buyer's own evaluation surfaces the gap. For each one, say what it exposes and what a weak answer from the competitor sounds like. 6. **Objection responses.** Three rows with the columns They say, They mean, You say, Proof. "They say" is verbatim buyer language. "You say" is the exact words the rep uses, and it should start by conceding whatever is true. 7. **Proof.** Any named customers, dated numbers, or third-party sources you could verify. Mark anything you could not verify as unverified. 8. **Do not say.** Claims that cannot be supported, and phrasings that make a buyer defend the incumbent they chose. **Rules:** - Every claim about the competitor must be traceable to something you actually read. Flag anything inferred. - No adjectives in the comparison table. Facts, numbers, and mechanisms only. - Write for someone reading it with a prospect on the line, so short lines and no preamble.
How to use this battlecard template
Most battlecards fail for the same reason: they are written to be comprehensive and then read under pressure. A rep with a prospect on the line has about four seconds of attention to spare. That constraint should decide the format, which is why this template puts a spoken sentence in the last column of every comparison row and keeps the whole card to eight blocks.
Start with block 2, not block 3
Write what the competitor actually says about themselves before you write anything about yourself. Pull the sentence off their homepage. Then write the sentence you hear from buyers, which is usually shorter, less flattering, and much more useful. The gap between those two lines is where most of your positioning lives.
Fill “where they win” honestly
This is the section reps check first, and it is the one that decides whether they trust the rest of the card. A card with no losing conditions reads as marketing and gets ignored. Write the two or three deal shapes you should not chase, and say what to do instead: qualify out, or change the frame. A rep who recognises a losing deal in week one gives you back a quarter.
Write the objection responses as speech
The “You say” column is not a summary of your argument, it is the argument. If a line has to be paraphrased under pressure it will be paraphrased badly. Start every response by conceding whatever is true. “Keep it, it is good at that” buys you the right to say what it is not good at, and it stops the buyer defending the choice they already made.
Date it, own it, and expect it to rot
Put one name and one date in the header. Competitive claims have a half life of about a quarter: pricing pages change, modules ship, and the sentence you lifted off their homepage in March is gone by June. A card older than 90 days should be treated as a set of rumours until someone re-checks it. That is not a process failure, it is what competitive intelligence is.
The card is right the day you write it
A battlecard is a document, and documents go stale between reviews and get read after the call rather than during it. Backdrop takes the same approved content and pushes it into the live call: when a rep hears the competitor's name, the counter-position, the trap question, and the proof point appear on screen, from the version enablement approved this week.
See how Backdrop worksFrequently Asked Questions
What is a sales battlecard?
- A sales battlecard is a one-page reference that tells a rep what to say when a specific competitor comes up in a live deal. It covers how that competitor positions themselves, where you win, where they win, the questions to plant with the buyer, and the exact responses to their most common objections.
What should a sales battlecard include?
- Eight blocks: a dated header, the competitor's own positioning, a head-to-head comparison, honest win and loss conditions, trap questions, objection responses written as speech, verifiable proof points, and a short list of claims your reps must never make. Anything beyond that is documentation, not a battlecard.
How long should a battlecard be?
- One screen per competitor. A rep reading it during a call has seconds, not minutes, so every row needs a sentence they can say out loud without editing it. If a card covers more than one competitor, or runs past a single scroll, it stops being used in the moment it was built for.
How often should sales battlecards be updated?
- Every 90 days at the outside, and immediately after any competitor pricing change, funding round, or major release. Competitive claims decay fast: a pricing page you quoted in March is often wrong by June. Put a named owner and a review date in the header so anyone reading it can judge how much to trust it.
Is this battlecard template really free?
- Yes. The whole template is on this page as readable text, and you can copy it as Markdown or download it without giving us an email address. There is no signup, no gated PDF, and no trial attached. Use it, edit it, and put your own company's name on it.