Sales battlecard examples: seven templates reps will use

A sales battlecard is a one-page internal reference that tells a rep what to know, ask, and say in one recurring situation: a named competitor, a familiar objection, a buyer persona, or a pricing conversation. The examples below are fictional templates with placeholders, so you can copy the structure and fill it with your own verified facts.

Most teams start with a competitor card and stop there. The cards that change deal outcomes cover the situations reps meet every week, and they stay honest about where the alternative is strong.

What a sales battlecard does in a live deal

Sales battle cards exist for the moment a rep has seconds to respond. A buyer mentions a rival’s lower quote, asks whether you integrate with their CRM, or says the finance team needs to sign off. The rep needs the facts, the right follow-up question, and a credible answer without opening five documents.

That defines what a battlecard is for. It is a retrieval tool, read in under a minute, and built for a single situation. It sits inside a broader sales playbook, which explains when each play applies, and it draws on the research described in our guide to competitive intelligence for proposals.

A battlecard is also internal. It can hold candid notes that would read badly in front of a buyer, which is why the buyer-facing version of the same answer needs its own format (covered at the end of this guide).

What every battlecard needs before a rep will trust it

Reps abandon cards that feel like marketing. Before writing any example below, agree on the fields every card shares:

The “where they are strong” row matters most. A card that only lists weaknesses trains reps to disparage, and buyers notice. Neutral framing also keeps every claim defensible: anything the card says about another company should be something you could show the buyer a public source for.

Sales battlecard examples by type

Each template below uses placeholders in square brackets. Replace them with facts your team has verified, and delete any row you cannot support.

1. Competitor battlecard

Use it when a named alternative appears in a deal.

• Situation: Buyer is also evaluating [Competitor A].
• Where they are strong: [Competitor A] is well known in [segment] and offers [capability buyers praise in reviews].
• Where we fit better: Teams that need [outcome] across [team or region], or that must [requirement such as access control or analytics].
• Discovery questions: “What would make the rollout a success six months from now?” “Who outside your team will review the content?”
• Response to a common claim: “[Competitor A] covers that well. The question for your team is [buyer-specific criterion], and here is how we handle it.”
• Proof: [Customer story in the same industry], [demo moment that shows the difference].
• Owner / last verified: [Product marketing owner], [date].

2. Objection battlecard

Use it for the objections that repeat across deals: price, timing, incumbent, and authority. Our sales objection handling framework explains how to diagnose each one; the card stores the team’s agreed wording.

• Objection: “[It costs more than we planned].”
• Likely cause: Comparison to [another quote / internal estimate / cost of doing nothing].
• Clarifying question: “What is that number being compared against?”
• Response: Reframe around [cost of inaction or outcome], with [proof point].
• When to stop pushing: [Signals that the fit is wrong, such as company size or budget cycle].

3. Product or feature battlecard

Use it when a release, add-on, or capability keeps generating questions.

• What it does: One sentence in the buyer’s language.
• Who it is for: [Persona] trying to [job to be done].
• Questions buyers ask: [Integration], [security], [pricing tier].
• What it does not do yet: Stated plainly, with a workaround if one exists.
• Demo path: [Three clicks that show the value].

The “does not do yet” line saves more deals than it loses, because reps stop overpromising.

4. Persona battlecard

Use it when a new stakeholder joins the deal, such as a CFO, an IT reviewer, or a procurement lead.

• What this person is measured on: [Budget accuracy / risk / time to value].
• What they worry about: [Security review / switching cost / adoption].
• Questions to ask them: “What would make you comfortable approving this?”
• Material that helps: [Security overview], [ROI model], [reference call].
• Words to avoid: Jargon that belongs to a different team.

5. Pricing and packaging battlecard

Use it when buyers compare plans, request discounts, or ask what is included.

• Packaging summary: [Plans and what separates them].
• Common confusion: [Feature buyers assume is included].
• Discount guardrails: [Approval levels and what to trade in return].
• Response to a lower quote: Compare scope line by line before discussing price.

6. Incumbent or displacement battlecard

Use it when the buyer already runs a process or tool that works well enough.

• What they have today: [Current tool or manual process].
• Switching cost they will raise: [Migration / retraining / contract timing].
• Gap to find: “What specifically is not working with the current setup?”
• Transition plan: [Onboarding steps and support offered].
• Timing signal: [Renewal date or project that opens a window].

7. Industry or use-case battlecard

Use it when the same vertical or use case produces the same questions in every deal.

• Context: How [industry] buys, who signs, and which regulations apply.
• Typical use case: [Proposal, onboarding, or account-based campaign].
• Questions that qualify: [Two or three industry-specific questions].
• Proof: [Customer story from the same industry].
• Pitfalls: [Terms or claims that do not land in this sector].

Why battle cards go stale, and how to keep them current

A battlecard decays from the day it is published. Competitors change pricing, your product ships releases, and the objection that dominated last quarter fades. A rep who quotes an outdated fact in front of a buyer loses more credibility than a rep with no card at all.

Four habits keep cards current:

1. Name an owner per card. Product marketing usually owns competitor and product cards; sales leadership or enablement owns objection and persona cards.
2. Review on a schedule. A quarterly review fits most teams. Anything not reviewed in that window is flagged, not silently kept.
3. List update triggers. A competitor pricing change, a relevant release, or a new pattern in win and loss interviews triggers an immediate edit.
4. Collect feedback from the field. Add one line at the bottom of every card: “Something wrong or missing? Tell [owner].” Reps see changes in buyer language first.

Retire cards too. A card nobody has opened in two quarters is either covering a situation that no longer happens or is too hard to find.

Where reps use battle cards in the sales cycle

Cards earn their place at specific moments:

• Call preparation. Before a discovery or demo call, the rep reads the competitor and persona cards that match the account.
• During the call. A short card open on a second screen gives the exact wording for a pricing question or a rival’s claim.
• Proposal writing. The “where we fit better” and “proof” fields shape which case studies and sections go into the proposal.
• Deal reviews. Managers use the discovery questions to test whether the rep actually qualified the situation.
• Onboarding. New reps learn the market faster from ten good cards than from a long competitor deck.

Battle cards are one type of internal enablement asset. For the buyer-facing materials they support, see our guide to sales collateral, and for the technical documents buyers request during evaluation, our product datasheet examples.

From internal card to a buyer-facing answer

The card stays inside your team. What reaches the buyer is the result: a fair comparison, a case study from their industry, or a written answer to the question their CFO raised. That answer has to reach every stakeholder, including the ones who were never on the call.

Sending it as an email attachment leaves you guessing. A trackable microsite or digital sales room puts the comparison, proof, and follow-up answers in one place. With microsite analytics, the rep sees who visited, when, for how long, and which sections they read or skipped, and can subscribe to notifications when visitors are on the site. If the committee keeps returning to the pricing section, the pricing card is the next one to open.

That feedback also improves the cards. Sections buyers read closely show which arguments matter; sections they skip show which ones to cut.

Ready to see which answers your buyers actually read? Request a demo.