Sales Battlecard Template: A Free Google Sheet Built From Real Win and Loss Reasons
Publish date: Nov 3, 2026
A sales battlecard template is a one-page sheet per competitor. It tells a rep what to say when that rival comes up, what to ask, and what proves it. The one on this page is a free Google Sheet with five tabs. It arrives filled with Spona's own card against ZoomInfo and the reasons behind 18 closed deals.
Seven in ten teams say at least half of their opportunities are now competitive. 57.5% say more of their deals are competitive than a year ago. The card is how a rep walks into those deals prepared.
Get thousands of leads in 4 minutes.
Stop stitching tools together.
Start with verified sales data, delivered in minutes.
No contracts · No setup · No onboarding
Sales battlecard template: a filled ZoomInfo card
Five Spona reps used this card in 43 deals where ZoomInfo came up, over two months. The second column holds the wording the card proposes to a rep. The third holds the questions reps actually asked.
| Section | What the card says | Question to ask | Proof |
| Quick take | We win on verified coverage and workflow fit. We lose when the team cannot change its process during a migration. | Win loss log | |
| ICP and fit | Agree on the exact geography, industry, role and size cut before evaluating any vendor. | Can we compare 100 identical accounts and count verified contacts your CRM does not already contain? | Spona card |
| Why we win | Buyer wording from the log: "We found the right people in the territory we actually sell to." | Would you test the same accounts and remove duplicates before judging the list? | 18 closed deals |
| Why we lose | Buyer wording from the log: "Our team could not change its process during the migration." | Which part could be tested without changing the current sending workflow? | 18 closed deals |
| Their strengths | "500M+ contacts, 100M+ companies"; "300+ human researchers who verify records" | zoominfo.com | |
| Commercial discovery | Calculate total cost per verified, nonduplicate exported contact using the buyer's actual quote. | What export limits, additional credits and renewal terms are in your written offer? | Calculator on the card |
| Proof and close | Run a small Spona pilot with explicit pass, bounce and usable-record criteria. | Which specific result would justify paying for the pilot rather than extending the evaluation? | Spona card |
| Closing line | Let us price the contacts you can actually use in your exact ICP, with the evidence beside each record. | Can we agree on that acceptance test today? | 43 deals, 5 reps |
Reps recorded a positive next step after the closing prompt in 31 of the 43 deals. A positive next step is not a win, and the card never counts it as one.
The win and loss rows come from a different record: the 18 closed deals in Spona's log that named ZoomInfo. Twelve were won. Three were lost and three ended with no decision. Each deal carries one outcome and one primary reason, coded from the buyer's words.
Verified coverage and workflow fit account for 8 of the 12 wins. The recorded wording for workflow fit: "The file was straightforward to use in the workflow we already had."
Both losses to process change share one line, and it now sits on the card: "Our team could not change its process during the migration." The question beside it asks which part could be tested without touching the sending workflow.
The rival's strengths row quotes ZoomInfo's own page. It claims 500M+ contacts and 100M+ companies. It also lists 300+ human researchers who verify records.
Pricing is quote-only, and each export costs one credit. The contract details sit in our ZoomInfo pricing post, so the card links there instead of repeating them.
Spona's Apollo card ran in 37 deals, and the two cards together cover 69 unique deals. The databases themselves are covered in our comparison of the two.
Battlecard template: tabs, dropdowns and formulas
Open the battlecard template, then choose File and Make a copy. There is no email gate. For Excel, choose File and Download. The formulas use COUNTIFS and INDEX, so Excel and LibreOffice recalculate them too.
| Tab | What it answers | Dropdowns | Formulas |
| Instructions | How do I fill this, who owns it, and how often is it reviewed? | Every dropdown list lives here, one column each | A named cell, ReviewDays, set to 30 |
| Battlecard | What does a rep say and ask when this rival comes up, and what proves it? | Competitor (from the matrix), Status, Evidence type | Closed deals, won, lost and no decision counted from the log; top win and loss reason; days since review; cost per usable contact |
| Competitor matrix | How do rivals compare with us on public facts, and how fresh is each fact? | Source type | Log counts per rival; days since each fact was verified |
| Objection responses | What do buyers push back with, how often, and what do we say? | Category, Rival | Share of calls; rank by call count |
| Win loss log | Why do we win and lose against each rival, in the buyer's words? | Size band, Competitor, Outcome, Reason code, Quote permission | A reasons-by-outcome summary |
The log feeds the card. Pick a rival in cell B2 of the Battlecard tab. COUNTIF then counts every log row whose competitor field contains that name. The match uses a wildcard, so a deal logged as "ZoomInfo + Sales Navigator" counts as a ZoomInfo deal.
Below the card, a ten-row table runs COUNTIFS per reason code and outcome. Two cells above it name the top win reason and the top loss reason, with their counts.
Dropdowns follow Google's data validation from a range. You edit a list once on the Instructions tab, and every dropdown follows. The Competitor field shows a warning rather than rejecting an entry, so a deal that named two vendors still fits. Outcome cells colour themselves: won green, lost red, no decision grey.
The card, the matrix and the objections tab each pair a date column with a days-since formula. Anything older than ReviewDays turns red. Apollo's guide suggests a source URL, a verified date and an approver on every card. The matrix carries the first two, and the Instructions tab names the owner.
The calculator on the card divides the buyer's annual quote by the export units in it, less duplicates. On one call, a buyer said their ZoomInfo quote was $18,000 a year for three seats and 10,000 export units. That is $1.80 an export before a single duplicate is removed. Type your buyer's own numbers; the figure beside them is the one to compare with a per-lead price.
The sheet follows the same pattern as our CRM template: lists in one place, formulas everywhere else. The example rows are there to delete once your own log has data.
What should a sales battlecard include?
The eight rows of the card above, each with a line to say, a question to ask and a proof link. That structure answers the gaps Klue found in more than 150 battlecard audits:
| What Klue's audit measured | Share of cards |
| Include talk tracks a rep can use | 43% |
| Provide supporting evidence or proof points | 19% |
| Include customer-facing proof points | 35% |
Crayon's survey adds the result. Battlecards remain the backbone of compete content, yet the leaders surveyed rate rep readiness at 6.3 out of 10. A card that lists facts without a line to say is a research note, not a battlecard.
Keep each row short. The Product Marketing Alliance keeps the overview to two or three sentences. It lists three or four objections and two or three landmine questions.
The cards in Dock's library of public battlecards run from one page to six. The best of them write objections in the buyer's voice and keep responses short enough to say aloud.
Klue names four card types by audience, from BDR to executive. Build one card per rival for reps first; the other three are views of the same log. Klue's Fact, Impact, Act pattern fits the columns. The fact is the proof link, the impact is the line to say, and the act is the question.
Two rows need outside input. "Their strengths" comes from the rival's own pages, never from a rep's memory. The matrix stores the source link beside it. "ICP and fit" only works when the ICP is written down, and our ideal customer profile template does that in one tab.
Battlecard landmine questions for sales calls
A landmine question is one the buyer carries into the rival's demo. Crayon suggests two or three high-impact questions per card and holds the whole card to an ABC rule: accuracy, brevity, consistency. Gong's template gives them a section beside talk tracks and evidence. It tells you to create a version for each top competitor.
Spona's ZoomInfo card carries three, plus a closing prompt. They are acceptance tests, not traps. Each one asks the buyer to agree on how the data will be judged before anyone argues about database size.
- ICP and fit fixes the sample. A database of any size is only as good as its coverage of your accounts, minus the people you already have: "Can we compare 100 identical accounts and count verified contacts your CRM does not already contain?"
- Commercial discovery moves the limits from the pitch to the contract. The answer feeds the calculator: "What export limits, additional credits and renewal terms are in your written offer?"
- Proof and close gives the pilot a pass mark, so the evaluation cannot drift. Three of the 18 closed deals ended with no decision, the drift this question is meant to stop: "Which specific result would justify paying for the pilot rather than extending the evaluation?"
- The closing prompt is the line reps recorded the most positive next steps against: "Can we agree on that acceptance test today?"
Two rules keep landmines honest. A question the buyer cannot verify in the rival's trial is a jab, not a landmine, so cut it. One question per card row is enough. A rep who asks five in a row sounds like a script.
Objection responses the sales team can reuse
Klue's respondents said 33% of their deals are lost directly to a competitor. They judged nearly half of those winnable. The Objection responses tab holds 12 categories from 371 Spona discovery and evaluation calls. Each carries the buyer's recorded wording and the response.
The five below name a price, an incumbent, a contract or a comparison, so they belong on a competitor card.
| Objection | Buyer wording | Response on the card | Calls, of 371 |
| Price is too high | The price looks high before we know how much we can use. | Judge cost after verification, deduplication and the agreed ICP filter. | 43 |
| Already have a provider | We already have a provider our reps know. | Keep the current workflow and test the missing accounts. | 37 |
| Accuracy concern | How do we know those emails are still valid? | Use a recent verification timestamp and a controlled verified-only send. | 31 |
| Contract timing | The current agreement does not end until next quarter. | Record the renewal date and test incremental coverage before it. | 27 |
| Concern about duplicates | I do not want to pay again for people already in our CRM. | Deduplicate by email, domain and company identifiers before purchase. | 19 |
One call can raise several objections, so the counts overlap. The shares in the sheet do not add up to 100%. The call cohort is also a different population from the closed-deal log. The sheet keeps them on separate tabs for that reason.
Each response ends in a test, not a claim. "Price is too high" gets a cost per usable contact after deduplication, which is the calculator on the card. "Already have a provider" gets the missing-accounts test, which leaves the buyer's workflow untouched.
For the first call, before a rival is named, our cold call scripts carry the openers and objection lines. The card takes over at the evaluation stage.
How often should battlecards be updated?
Monthly for the rival you meet most, quarterly for the rest, and the day a rival changes its public pricing. Apollo's guide sets quarterly as the minimum and monthly for fast-moving rivals. Prospeo asks for a monthly review with one named owner per competitor. Contentcamel flags a card as stale at 60 or more days.
Klue's guide puts it bluntly: "Keeping your content up to date is the most, most, most, MOST important thing to do!"
Crayon's survey shows why the interval matters. About 56% of teams share competitive intelligence weekly, daily or in real time. Those teams report revenue impact far more often than teams on a monthly or slower rhythm.
Spona reviews every closed deal each month, 32 to 40 a month. Each deal gets one outcome and one reason code. The card's counts move on their own, because they read the log. The card's text changes less often: a row is rewritten when the top reason changes or a rival's public page changes.
The sheet enforces the interval. ReviewDays is 30, so a card's days-since-review cell turns red on day 31. Set it to 90 for a rival you rarely meet. Keep the date columns filled; an empty date never turns red, which is the one way to hide a stale card.
Where Spona fits in a data battlecard
The card's first landmine, compare 100 identical accounts, is the test Spona is built for. You describe the ideal customer in a chat. The AI mines 40+ sources, verifies every lead and returns a scored list in about 4 minutes. Every search starts with a free sample of leads, so you see real records before you buy any.
Beyond the sample you pay per lead. A Standard Search lead with an email costs 3 to 7 credits. A credit costs $0.008 to $0.01 by plan. Each new search session also has a one-time cost of 1,000 credits.
The Free plan carries 3,000 one-time credits. Pro costs $99 a month for 10,500 credits. The price per lead shows at checkout, which is the number the card's calculator wants.
On accuracy, quote evidence rather than a slogan. In Spona's own audit, 2,941 of 3,017 records were correct on person, employer and title. Email deliverability is a separate metric. The Accuracy concern response therefore asks the buyer to run a verified-only send and judge that.
Where ZoomInfo is stronger belongs on the card too. Its 300+ researchers and the size of its database matter to a buyer who wants one very large database.
Spona's native CRM integration is HubSpot, on Premium and Expert. Salesforce takes a CSV import, and the API runs on Expert only. Spona does not identify website visitors.
The Existing contract loss in the log is honest as well. That buyer was already committed to the incumbent for the budget period. The recorded response asks when the renewal decision happens and whether a gap can be tested first.
Get thousands of leads in 4 minutes.
Stop stitching tools together.
Start with verified sales data, delivered in minutes.
No contracts · No setup · No onboarding
Sales battlecard template FAQ
What is a sales battlecard?
A sales battlecard is an internal one-page document about one competitor. It gives reps the facts, the lines to say, the questions to ask and the proof for each. It is not a public comparison page; it is written for calls, in the buyer's language. The best ones are rebuilt from win and loss records rather than from the rival's marketing.
How long should a battlecard be?
One screen. Gartner found that B2B buyers in a complex purchase spend 17% of their time meeting suppliers. With three suppliers in a deal, each one gets about 5%. A rep has no time to scroll, so eight rows with one line and one question each fit that window. The longer cards in public libraries are for onboarding, not for calls.
Who should own the battlecard?
One named owner per rival. Crayon's survey puts the compete function in marketing at 42% of companies, followed by strategy or executive teams, then product. Whoever owns the card, sales owns the log. Reps log the outcome, the reason and the buyer's wording after each closed deal; the Instructions tab names the owner and the review period.
Do you need battlecard software?
Not for a handful of rivals. Klue and Crayon bring cards into the CRM and Slack, which matters at dozens of reps. A sheet covers a team with a few rivals and one owner who reviews it monthly. Move to software when reps stop opening the sheet, not before.
What are some free templates for sales?
Spona's template posts come with a Google Sheet, a Make a copy link and no email gate. They include the CRM template, the B2B buyer persona template and the sales territory planning sheet, each with an instructions tab. The lead qualification checklist post offers a free template too.
Share this article
GET FREE LEADS
