Sales Battlecard Examples: 5 Competitive Battlecards You Can Copy

By Kavyashree SB, Technical Writer October 27, 2026 10 min read

A practical perspective for connecting this idea to your revenue team’s next move.

Editorial competitive landscape showing five battlecard formats, evidence sources, discovery guidance, proof, and claim review.

Good sales battlecard examples share one structure: when to use the card, a one-line positioning statement, discovery questions that expose the gap, where you win, where the competitor wins, proof, objection responses and an owner with a review date. Below are five complete examples you can copy, for cybersecurity, analytics, HR tech, enterprise software and the “do nothing” option.

Every competitor and company in these examples is fictional. We do not publish battlecards about real vendors: a real card depends on facts you have verified about a specific competitor, and those change often. Use these as structure and tone, then fill in your own sourced facts.

Last updated: 27 October 2026

Disclosure: Revspire publishes this guide and sells software that includes battlecards. The examples work in any tool, including a shared document.

What does a sales battlecard include?

A battlecard is a short, approved guide a seller uses when a specific competitor, or a specific objection, comes up in a deal. These are the fields every example below uses:

Field

What it holds

Length

When to use

The situation that triggers the card

One sentence

Quick positioning

How you describe the difference in one breath

One or two sentences

Discovery questions

Questions that surface needs the competitor handles poorly

Three to five

Where we win

Verifiable strengths, each tied to a buyer outcome

Three bullets

Where they win

Honest strengths of the competitor

Two or three bullets

Objections and responses

What the buyer says and how to answer

Two to four pairs

Proof

Case study, reference or document to share

One to three items

Do not say

Claims that are unverified, outdated or disparaging

One to three bullets

Owner and review date

Who keeps it current, and when it was last checked

One line

Fields used in the five examples. Our sales battlecard template has the same structure, ready to fill in.

Two fields are often missing from real cards: “Where they win” and “Do not say”. Both protect the seller. Buyers check claims; Gartner’s B2B buying journey research (undated, accessed 27 October 2026) says each decision maker arrives with four or five pieces of information gathered independently, and Gartner’s March 2026 buyer survey found 45% of buyers used AI during a recent purchase. A rep who overstates the gap loses credibility fast.

Example 1: Cybersecurity, displacing an incumbent

Context: Tessaly Endpoint (you, fictional) sells endpoint protection. The buyer runs Gravenmoor Shield (fictional), installed five years ago, and is reviewing it at renewal.

When to use: the buyer already runs Gravenmoor Shield and the renewal is within six months.
Quick positioning: “Gravenmoor Shield is a solid antivirus base. Teams usually look at us when they need investigation and response without adding headcount.”
Discovery questions: How long does it take your team to investigate an alert today? Who handles alerts outside office hours? What did your last incident review recommend?
Where we win: automated investigation summaries that cut analyst time per alert; a single console for endpoints and cloud workloads; a managed response option.
Where they win: lower licence cost per endpoint; the buyer’s team already knows it; no migration effort.
Objection: “Switching is too risky.” Response: offer a parallel run on a subset of devices with exit criteria agreed in writing.
Proof: [your case study of a similar-sized migration]; [your migration plan document].
Do not say: “Gravenmoor Shield missed the [named] breach” unless you have a public, citable source.
Owner: product marketing, reviewed monthly.

Example 2: Data analytics, against a low-cost challenger

Context: Quorvale Insights (you, fictional) sells an analytics platform. TallyNimbus (fictional) undercuts on price with a self-serve plan.

When to use: the buyer mentions TallyNimbus’s price or free plan.
Quick positioning: “TallyNimbus is a good choice for a single team getting started. We are built for when finance, operations and sales need the same numbers.”
Discovery questions: How many teams will use the dashboards in a year? Who owns metric definitions today? What happens when two reports disagree?
Where we win: shared, governed metric definitions; row-level permissions; support for the data warehouse the buyer already uses.
Where they win: faster self-serve start; lower entry price; simpler interface for casual users.
Objection: “TallyNimbus is half the price.” Response: compare cost at the buyer’s expected user count in year two, and include the time spent reconciling reports.
Proof: [total cost comparison worksheet]; [reference customer who moved from a self-serve tool].
Do not say: that TallyNimbus “is not secure”. Talk about the permission features you have, not ones they lack, unless their documentation states it.
Owner: competitive intelligence lead, reviewed each quarter and after any TallyNimbus pricing change.

Example 3: HR tech, against a suite’s bundled module

Context: Larkfield Learning (you, fictional) sells employee learning software. Corlane People Suite (fictional) includes a learning module in its HR suite at little extra cost.

When to use: the buyer says “we already get learning in Corlane”.
Quick positioning: “The Corlane module is convenient for compliance training. We are used when learning has to change performance, not just record completion.”
Discovery questions: What does the business ask L&D to prove? How do managers see skill gaps today? How often do you build new content?
Where we win: skills data by role; practice and assessment, not only course completion; faster content authoring.
Where they win: one vendor and one contract; single HR data record; included in the existing price.
Objection: “IT wants fewer vendors.” Response: show the integration with Corlane so the HR record stays the source of truth.
Proof: [integration guide]; [example skills report].
Do not say: “the bundled module is outdated”. Ask the buyer what it does not do for them instead.
Owner: product marketing, reviewed after each Corlane release.

Example 4: Enterprise software, late-stage pricing against the market leader

Context: Wrenfield Workflow (you, fictional) is in the final round against Dravonix (fictional), the best-known vendor in the category. Procurement asks for a discount to match Dravonix.

When to use: final round, procurement involved, Dravonix named as the alternative.
Quick positioning: “Dravonix is the safe choice by brand. We are chosen when time to value and admin effort matter more than brand.”
Discovery questions: What did your team estimate for implementation with each vendor? Who will administer the system day to day? What would a six-month delay cost?
Where we win: shorter implementation plan; admin without specialist consultants; pricing that does not rise with every new user.
Where they win: brand recognition with the board; broader partner ecosystem; more third-party integrations.
Objection: “Dravonix offered 30% off.” Response: ask what scope and term that price covers, compare three-year cost including services, and trade any discount for term or scope, not for nothing.
Proof: [three-year cost model]; [implementation plan with dates].
Do not say: anything about Dravonix’s financial health or roadmap you heard second-hand.
Owner: deal desk with product marketing, reviewed each quarter.

Example 5: The do-nothing option

Context: the most common competitor is no decision. Ambery Ops (you, fictional) sells operations software; the buyer is considering keeping spreadsheets.

When to use: the buyer agrees there is a problem but has not set a date or budget.
Quick positioning: “Spreadsheets work until the process depends on one person. Most teams act when that person is about to leave or the volume doubles.”
Discovery questions: What happens if the person who owns the spreadsheet is away for a month? How many hours a week go into it? What decision is waiting on better data?
Where we win: fewer manual hours; an audit trail; one version of the data.
Where they win (the status quo): no cost, no change, no training.
Objection: “Now is not the right time.” Response: agree a small, dated first step, such as a two-week pilot on one process.
Proof: [simple cost-of-delay worksheet]; [customer story about the trigger event].
Do not say: invented productivity statistics.
Owner: sales enablement, reviewed twice a year.

Five examples side by side

Example

Competitor type

Main tactic

Review cadence

Cybersecurity

Incumbent

Parallel run with exit criteria

Monthly

Data analytics

Low-cost challenger

Year-two cost at real user count

Quarterly and on price change

HR tech

Bundled suite module

Integrate, do not replace, the suite

On each competitor release

Enterprise software

Category leader

Three-year cost and time to value

Quarterly

Do nothing

Status quo

Small, dated first step

Twice a year

All companies fictional.

How to keep battlecards accurate and fair

Source every competitor claim. Link the competitor’s pricing page, documentation or a public review. If you cannot source it, put it under “Do not say”.
Stay truthful when comparing. The US Federal Trade Commission’s Statement of Policy Regarding Comparative Advertising (August 1979) encourages naming competitors, but says comparisons must be clear and not deceptive, and that disparaging claims are acceptable only when truthful. Sellers repeat what cards say, so hold cards to the same standard as marketing copy.
Date every card. Put the review date at the top. A card older than its review cadence should show a warning.
Feed in win/loss. Crayon’s 2026 State of Competitive Intelligence (ninth edition, accessed 27 October 2026) says “battlecards still rule, but win/loss and win stories are rising”. Use win/loss analysis to update “Where they win” honestly.
Practise before using. Reps who rehearse the objection responses use them better in calls. See objection handling practice with AI.

For benchmark data on how teams use cards, see our battlecard usage benchmark, and for tools, our battlecard software guide. Revspire’s AI Playbook Engine drafts battlecards from approved revenue knowledge and routes them for approval, and its training module lets reps practise deal-specific objections with battle cards.

Frequently asked questions

What is a battlecard example?

A one-page guide for a specific competitor, such as a low-cost challenger, with when to use it, a positioning line, discovery questions, where you win and where they win, objection responses, proof and a review date. Example 2 above is a typical version.

What should be on a competitive battlecard?

Positioning, discovery questions, verifiable strengths, the competitor’s real strengths, objection handling, proof points, claims to avoid and an owner with a review date. Keep it to what a seller can use during a live conversation.

How long should a battlecard be?

One screen or one page for the seller-facing view. Put supporting detail and sources behind links, so the card stays readable during a call.

How often should battlecards be updated?

On a fixed cadence, monthly to quarterly depending on how fast the competitor changes, and immediately after a competitor’s pricing or product change. Every card should show when it was last reviewed.

Sources

The B2B Buying Journey, Gartner, undated, accessed 27 October 2026
Gartner Sales Survey Finds 67% of B2B Buyers Prefer a Rep-Free Experience, Gartner, 9 March 2026, accessed 27 October 2026
Statement of Policy Regarding Comparative Advertising, US Federal Trade Commission, 13 August 1979, accessed 27 October 2026
2026 State of Competitive Intelligence, Crayon, 2026, accessed 27 October 2026