Sales Battle Cards: The Evidence-Safe System and Template

A sales battle card is not a page of competitor trivia. It is the delivery layer of a governed evidence system: a rep-facing card, a claim-and-proof register behind it, a named owner, a review trigger, and a feedback route from live deals.

This guide uses official vendor documentation and primary regulatory guidance accessed August 8, 2026. We did not conduct hands-on platform tests or accept affiliate consideration. Vendor pages show documented capabilities, not independent performance. Unsupported win-rate, adoption, retrieval-time, latency, pricing-change, and outcome claims have been removed.

This canonical owns the full battle-card system and reusable template. The sales call battle-card guide focuses narrowly on in-call use. The sales competitive-intelligence guide covers upstream collection and analysis, while competitive discovery covers questions that reveal the buyer’s evaluation.

Treat battle cards as a governed evidence system

Direct answer. Build two connected objects: a short card that a rep can use in a defined moment and an evidence register that stores sources, scope, approvals, limitations, and expiry. The card should never become the only copy of the evidence.

The system boundary matters. A competitor page can change without warning. A rep note can be biased. A customer quote can be real but unapproved for reuse. An AI summary can misstate the underlying source. None becomes approved card language without review.

Build the source, claim, and proof register first

Create one row per material claim. Store a stable claim ID, card IDs using it, exact approved wording, claim type, source URL or record, publisher, source date, capture date, excerpt or evidence location, population and method for metrics, limitations, approver, approval date, expiry, and replacement history.

Use explicit source classes:

• First-party product evidence: your current documentation, contract, security material, release notes, or tested environment.
• Competitor primary evidence: the competitor’s current product, help, pricing, security, legal, or release pages.
• Buyer evidence: approved win/loss interviews, call excerpts, or CRM notes, labeled as perception rather than universal fact.
• Third-party evidence: research or review material with author, sample, method, date, and conflicts visible.
• Unknown: unverified rep report or market rumor kept out of the published card until resolved.

A proof point should support the claim as written. “Customer A reduced review time in a named workflow during a defined period” does not support “all teams save time.” Preserve denominators, exclusions, configuration, and typicality. If the evidence only supports observation, write an observation.

The FTC’s advertising guidance says claims should be truthful, non-deceptive, and evidence-based. Applicable law varies, but this is a useful minimum for battle-card wording. Review comparative, pricing, security, legal, regulated-industry, and customer-result statements with the appropriate owners.

Create a competitor battle card

A competitor card should help a rep diagnose fit and guide a fair comparison—not attack a company. Scope each version by competitor, market segment, persona, use case, product package, and geography. “Us versus Competitor X” is usually too broad.

1. Situation: the buyer context and evaluation stage where this card applies.
2. When they may fit: buyer conditions where the competitor deserves consideration. Credibility starts with honest trade-offs.
3. When we may fit: verified strengths tied to this buyer’s stated requirements.
4. Diagnostic questions: neutral questions about workflow, integration, authority, implementation, service, data, security, and economics.
5. Comparison dimensions: definitions and like-for-like scope before any answer.
6. Approved talk tracks: acknowledge, clarify, answer with scoped evidence, and check.
7. Proof and limitations: claim IDs, short labels, expiry, and known counterexamples.
8. Escalation: named product, security, legal, finance, or sales-engineering owners for unknowns.

Klue’s official material describes deal-specific context, verified proof points, objection plays, and delivery through systems such as CRM, messaging, web, and mobile. Treat the claims on Klue’s automated-battlecard page as its product description, not proof that automation makes a card accurate.

Create scenario and objection cards

Not every battle is a named competitor. Scenario cards are often more reusable because they address a buyer moment: incumbent satisfaction, price comparison, integration risk, security review, build-versus-buy, implementation effort, a missing capability, or “do nothing.”

Use this scenario structure:

Scenario cards support the listen-and-clarify discipline in the sales objection-handling framework. They should not turn objections into keywords that trigger the same canned answer regardless of context.

Set evidence-safe objection boundaries

Define what reps may say, what requires qualification, and what requires escalation. The card is assistance, not authorization to speculate.

• Competitor capability: use current public evidence and a capture date; avoid “cannot” unless the scope is demonstrably complete.
• Pricing and packaging: label currency, unit, edition, term, region, taxes, usage, effective date, and whether the information is public or buyer-reported. Prefer directing the buyer to current official terms.
• Security and privacy: use approved documentation. Never infer compliance from a logo or answer architecture questions from memory.
• Customer proof: confirm permission, context, population, period, and whether the result is representative. Do not turn a quotation into a performance guarantee.
• Roadmap: label unavailable capability and use only approved commitment language.
• Unknown: state the gap, name the evidence owner, and give a dated follow-up rather than improvising.

Replace “landmines” with diagnostic questions. “How does your current system handle failed CRM writes?” invites comparison. “Competitor X loses your data” is an accusation requiring strong evidence. Evidence-safe language is usually more persuasive because the buyer can verify it.

Assign owners, versions, and review triggers

Every card needs a business owner and evidence owners. Product marketing may own the card; product owns capability; finance owns pricing; security/privacy/legal own their approved language; customer marketing owns reference permissions; enablement owns training and delivery; sales operations owns CRM taxonomy.

Version the card and the claims separately. A card version should record status—draft, approved, deprecated, archived—effective date, prior version, approvers, changed claim IDs, affected segments, and publication channels. A corrected proof point must invalidate cached copies and linked cards.

Choose a maximum review interval by risk, then add event triggers: product release, pricing or packaging change, competitor update, legal/security change, expired customer permission, repeated “not useful” feedback, new loss theme, or material source deletion. Do not publish a universal 30-day rule. Stable definitions and volatile pricing need different cadences.

The review meeting should answer: Which claims expired? Which sources changed? Which cards were eligible but unavailable? Which questions remained unanswered? Which buyer wording recurred? Which feedback reflects one deal versus a pattern? Record the decision and owner.

Deliver cards through CRM and enablement workflows

Publish one approved source of truth, then deliver views into the rep’s workflow. A CRM opportunity can expose competitor, stage, persona, use case, and card version. An enablement system can support search, training, acknowledgement, and analytics. A messaging channel can announce changes. An in-call surface can show a concise scenario card. None should become an unmanaged copy.

Klue’s battlecard product page documents delivery across email, Slack, web, mobile, and Salesforce plus consumption measurement. Highspot’s current battlecard guide describes concise guidance built from product marketing research, win/loss data, and revenue-leader input. These sources establish approaches; test permissions, version propagation, search, offline behavior, analytics, export, and deletion in your own stack.

Define delivery rules: eligible account/persona/stage, card priority, why it appeared, version, expiry, acknowledgement, and fallback when context is missing. Test false triggers and false omissions. A card surfaced on every mention becomes noise; a card hidden behind exact naming may miss the buyer’s shorthand.

Gangly disclosure. Gangly’s repository says Live Call Coach supports Zoom and Google Meet and can surface competitor comparison data when a competitor is named. The rep drives the conversation. Call Prep can include likely objections and recommended talk tracks. Post-call outputs are rep-reviewed drafts. The repository does not establish automatic card governance, self-updating proof, sub-second latency, or outcome improvements, so this guide does not claim them.

Measure usage and capture field feedback

Measure the system as a funnel: eligible competitive situations, correct card available, card exposed, opened or expanded, response used or adapted, buyer reaction captured, question resolved, follow-up completed, and feedback reviewed. Keep denominators and segment by card, competitor, scenario, persona, region, stage, tenure, and delivery channel.

Add one-click feedback with structured reasons: useful, irrelevant, stale, unsupported, wrong context, too long, missing branch, unsafe language, or technical delivery failure. Require a note and evidence link for proposed factual changes. Feedback creates a review ticket; it should not directly rewrite approved content.

Win rate is an outcome with selection effects: hard deals may use cards more often, competitive tagging may be incomplete, and many factors affect results. Pair outcome analysis with quality evidence such as correct availability, proof defects, stale-claim incidents, manager observation, resolution of unanswered questions, and time to approved correction.

The sales enablement metrics guide can help separate content exposure, behavior, and business outcomes. Use the competitive analysis workflow to turn recurring field evidence into upstream research.

Print the battle-card template and checklist

A battle card is ready when a rep can use the concise view, a reviewer can reconstruct every material claim, and an owner can correct or retire every distributed copy. Anything less is sales copy with no reliable control plane.