Most battlecards fail in one of two ways. Either they are a 15-page competitive analysis no rep will open during a call, or they were written once at launch and now describe a competitor that has changed its pricing, product and pitch. A useful battlecard is short, specific to one competitor, written from evidence and updated on a schedule. This article gives you the structure, a fill-in template with blanks in square brackets, where the inputs should come from and the light process I use to keep cards current. It is about competitive selling. The agreement on how leads move between marketing and sales is a different document, which I cover in my sales and marketing SLA template.
What a battlecard is for, and what it is not
A battlecard has one job: help a rep handle a competitor in a live deal. That means it is used at three moments. Before discovery, to plan which questions to ask. During a call, when the prospect says they are also looking at a named competitor. And before a proposal, to frame the comparison on criteria where you win. It is not a market analysis, a product roadmap or a list of every feature the competitor lacks. Feature lists age quickly and invite a feature war you may lose. It is also not a script for criticising the competitor. Buyers discount that, and anything you claim about a competitor needs to be accurate and current, because a prospect who catches one wrong claim stops trusting the rest. I keep each card to one screen or one printed page. If a rep cannot find the answer to an objection in under ten seconds, the card is too long. Write one card per competitor you meet regularly, plus one for the most common alternative of all: doing nothing or staying on spreadsheets.
The battlecard template
Template text. Competitor: [name]. Last updated: [date] by [owner]. Who they sell to: [their core segment in one line]. Their likely pitch: [the two or three claims they lead with]. Where we win: [segments, use cases or situations where our win rate against them is strongest, with the evidence]. Where we lose: [honest list of situations where they win, and whether we should walk away]. Landmine questions: [three to five discovery questions that surface our strengths and their gaps without naming them, e.g. 'How will you handle X when your team doubles?']. Objection handling: [their claim] / [our response] / [proof], for the top three to five objections. Proof points: [customer stories, reviews or published case studies that switched from them, with links]. Pricing and packaging notes: [only what is public or confirmed by a prospect, with the date]. Traps to avoid: [claims we should not make, topics where they are genuinely stronger]. Recent changes: [releases, pricing moves, leadership or funding news in the last 90 days]. The 'where we lose' line is the one teams resist and reps value most.
Where the content should come from
A battlecard written from the product team's opinion of a competitor is usually wrong in the places that matter. I fill it from four sources. First, closed deals. Add a Primary competitor field and a structured loss reason to your opportunities, then pull win rate, deal size and cycle length by competitor. That tells you where you win and lose with numbers rather than anecdotes. Second, call recordings and rep notes from deals where the competitor came up. Search for the competitor's name and collect what prospects said about them in their own words. Those quotes feed the 'likely pitch' and 'objection' lines. Third, win and loss interviews, ideally run by someone other than the rep who owned the deal. Fourth, public material: the competitor's website, pricing page, release notes, review sites and job posts, which often signal where they are investing. Date every claim. If a pricing note came from a prospect, say so and record when. Unsourced, undated claims are how battlecards become liabilities.
Making it usable inside the CRM
A card in a shared drive gets used in the first month and forgotten after. Put it where the rep already works. In HubSpot, Sales Hub Professional and Enterprise include Playbooks, which can be opened from the right-hand panel of a contact, company, deal or ticket record. A playbook can hold the battlecard content, include questions the rep answers during the call and log the answers back to the record. HubSpot's knowledge base also notes you can set rules so a playbook is recommended based on record properties, which means you can surface the right card when the competitor field on a deal is set. In Salesforce, the equivalent is usually a Knowledge article or a linked document surfaced on the opportunity page when the competitor field is filled. In Zoho CRM, a linked document or a custom related list on the deal works. Whatever the tool, the trigger should be the same: the rep records the competitor on the deal, and the card appears. That also gives you the data to report win rate by competitor.
Keeping the card current
Staleness is the main way battlecards fail, so the process matters more than the first draft. I use a simple cadence. Every card has one named owner, usually in product marketing or, at smaller companies, the marketing lead. Once a month, the owner spends 30 minutes per active competitor checking release notes, pricing pages and the last month of call mentions, then updates the 'recent changes' line and the date. Once a quarter, the owner pulls win rate and loss reasons by competitor and rewrites the 'where we win' and 'where we lose' sections if the numbers have moved. Between those reviews, reps need a fast way to report something new: a dedicated Slack channel or a simple form works. Any rep who hears a new competitor claim posts it with the deal name. Retire claims you cannot verify. And when a competitor stops appearing in deals for two quarters, archive their card rather than maintaining it. Fewer accurate cards beat a library of stale ones.
Testing whether the battlecards help
You can measure battlecard impact without a dedicated tool if the competitor field is filled consistently. Track three things by competitor, quarter over quarter. Win rate in deals where that competitor was present. The share of those deals where the playbook or card was opened, if your CRM logs it. And the most common loss reasons. If win rate against a competitor is flat while card usage is high, the content is not answering the objections that actually lose deals; go back to the loss interviews. If usage is low, the problem is access or trust, so ask reps directly what they skip and why. I also run a short role-play in the monthly sales meeting: one rep plays the prospect using the competitor's pitch, another responds using only the card. Gaps show up within minutes. Treat the card as a sales asset that is tested and revised like ad creative, not a document that is published once.
Sources
HubSpot Knowledge Base, Use playbooks: https://knowledge.hubspot.com/playbooks/use-playbooks
FAQ
The competitor's core segment and likely pitch, where you win and lose against them, landmine discovery questions, responses to the top objections, proof points, dated pricing notes, traps to avoid and recent changes. Keep it to one page per competitor so a rep can use it mid-call.
Check recent changes monthly and rewrite the win and loss sections quarterly using deal data. Give each card one named owner and a visible last-updated date, and give reps a quick channel to report new competitor claims between reviews.
Usually product marketing, or the marketing lead at a smaller company. Sales should contribute evidence and review drafts, but a single owner is what keeps cards current. Shared ownership tends to mean nobody updates them.