# Sales Battlecard Template A competitive battlecard built to be read mid-call, not filed after the kickoff. One competitor per card. Keep the whole thing to one screen. Free from Backdrop: https://www.getbackdrop.ai/tools/sales-battlecard-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. | 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. - **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. | 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. | They say | They mean | You say | Proof | | --- | --- | --- | --- | | | | | | | | | | | | | | | | ## 7. Proof - **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 - **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._ --- # Worked example: 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 | 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. ## 5. Trap questions | 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 | 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. - **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. - **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. --- Free sales templates and AI prompts: https://www.getbackdrop.ai/tools