Sales Battlecard: A Template for Claims You Can Verify

A sales battlecard is a short internal guide for a specific competitive conversation. It should help a seller understand the buyer's criterion, find a relevant fact and choose the next question. A list of reasons your product is supposedly better is not enough.

This guide includes a practical template, a fictional worked example and a review workflow for AI-assisted research. The central rule is simple: keep what you know about a competitor separate from what you infer about the buyer. A sourced product fact can still be irrelevant to the decision in front of you.

What is a sales battlecard?

A sales battlecard brings together a competitive situation, the facts that matter, a short response and the evidence behind it. A rep can use it before a call or during a discussion when a buyer mentions an alternative. It is usually an internal reference rather than a document to forward unchanged to the customer.

Crayon's battlecard guide distinguishes the underlying competitive comparison from the resource delivered to sellers. That distinction is useful: research can be extensive, but the live conversation needs only the relevant conclusion and a path back to its evidence.

Our sales playbook covers decisions across the selling process. A battlecard is narrower: it supports one recurring competitive situation within that process. A sales pitch explains relevance to a buyer; the battlecard helps when that buyer compares approaches.

What the podcast evidence contributes

In Private Equity FunCast's conversation with Kyle Roemer, the sales and marketing discussion connects customer-call analysis, objections, positioning and battlecards. The hosts discuss using AI to research competitors, and Roemer agrees with the broader point about making detailed research more accessible.

This is a qualitative exchange about practices in middle-market companies. It does not provide a tested battlecard template or establish that AI research is accurate. We use it to identify an input: actual questions and objections from conversations can inform competitive material. The review process below is an editorial proposal, not a protocol attributed to Roemer.

Colin Zima supplies a different caution in A Product Market Fit Show. He describes losing five early Omni deals that had appeared close to signing. The feedback included the company's youth, product readiness and end-user reactions. Those are different problems; a single claim about feature superiority would not answer all of them.

That account supports listening to the reason a buyer hesitates. It does not show that a battlecard caused later wins. Our Omni case study covers the broader founder story; here the task is turning a specific concern into a defensible response.

Choose the situation before collecting facts

Start with a sentence a buyer actually said, using information your team is permitted to process. For example: “We already use another provider and want to avoid a difficult migration.” The important issue is migration effort, not every difference between the two products.

Ask what the alternative really is. It may be a named vendor, an internal spreadsheet, a manual service or leaving the process unchanged. A card comparing two software products will not help if the buyer is deciding whether to change anything at all.

Define the audience and stage. A first-contact card might help a rep ask whether a concern exists. A later evaluation card may need a documented test or a specialist. Do not treat company research as confirmation of an individual buyer's priorities. Our discovery questions help establish those priorities directly.

A sales battlecard template

Keep the front of the card brief. Put supporting material behind links so a colleague can inspect it without searching through the whole research file. These fields are a starting point, not a requirement to fill unknowns with guesses.

• Situation: the buyer's question, relevant use case and alternative being considered.
• Decision criterion: what matters to this buyer, with its status marked as reported, inferred or still unknown.
• Competitor fact: one relevant statement, its source, observation date and scope, including the plan or version when applicable.
• Our evidence: an authorized example, documented capability or test that supports a comparable claim about our offer.
• Honest trade-off: where the alternative may fit better, or where the comparison is not yet established.
• Question and response: a neutral clarification followed by a short answer tied to the confirmed criterion.
• Next verification: the test, document or person needed to resolve uncertainty.
• Owner and review trigger: who maintains the card and what would make the current claim unsafe to reuse.

Avoid mixing a website claim, a customer's experience and an internal opinion into one “verified” statement. A competitor's documentation describes its published offer; it does not prove how every customer uses it. A single buyer's report is evidence of that report, not a universal product limitation.

Example: a migration objection

Consider a fictional buyer evaluating two workflow systems. The buyer says the existing tool already connects to an important data source. A seller is tempted to answer: “Their integration is basic; ours is better.” There is no verified scope behind that comparison, and “better” does not identify the buyer's requirement.

A more useful card records the actual question: can the new workflow preserve the fields, permissions and update frequency the team needs? The competitor entry links to the relevant documentation and marks any missing detail as unknown. The entry for your own product points to a documented capability or a test you can reproduce.

The response could be: “Before comparing the integrations, let's list the fields and permissions your workflow depends on. We can check both approaches against that list and test the unresolved items.” This is an illustrative response, not a quotation from either episode or a claim about a real vendor.

The next step might be a small comparison using permitted sample data, with success criteria accepted by the participants. If the alternative already satisfies the need and changing tools adds no useful value, the card should make that visible. Its purpose is to improve the decision, not manufacture a weakness.

Use AI to organize evidence, then review the claims

AI can help group approved call notes by concern or turn supplied research into a draft. Give it the sources and a limited task. Ask it to keep quotations, published product statements, buyer reports and assumptions in separate categories, and to leave missing details unresolved.

A practical instruction is: “Use only the supplied material. For every competitive claim, identify the supporting passage, observation date and scope. Do not infer missing features, prices or contract terms. Mark contradictions and unknowns. Draft a clarification question and a response for human review.” This instruction is a proposed aid, not a guarantee against error.

Open the cited source yourself. A valid URL does not establish that the page says what the draft claims. Check whether the statement describes the correct product, plan, region and period. Verify the comparison about your own offer with the same care; internal confidence is not a substitute for evidence.

The sales meeting notes guide covers preserving what happened in a conversation. For a battlecard, add another boundary: a buyer's objection identifies a question to investigate, not permission to publish an unsupported assertion about a competitor.

Keep the card usable and current

Assign an owner and a visible last-review date. Trigger a review when a source changes, a rep reports contradictory evidence or your own offer changes. There is no universal update interval that makes every fact safe. A pricing statement and a stable product concept can age differently.

Give reps a simple way to flag a doubtful claim. Record which line is disputed and why, then suspend that line until it is checked. Preserving an old version can explain why an earlier conversation used different information; it should not leave obsolete guidance looking current.

Practice with a real buyer question. Ask a colleague to find the evidence and give the short response without reading a paragraph aloud. If the card produces a long monologue, shorten it. If it encourages attacking the competitor before understanding the criterion, rewrite the question.

Measure usefulness without inventing impact

Begin with a small set of comparable competitive conversations. Record whether the card was used, whether its sources were retrievable, what needed correction and whether the next step resolved the buyer's actual question. Define these measures before reviewing results.

You can compare outcomes over time, but distinguish association from causation. Reps may open battlecards on unusually difficult deals; experienced sellers may use them differently from new hires. A handful of wins or losses cannot isolate the card's effect.

The template, prompt and example are editorial synthesis. The podcasts supply qualitative practices and a founder's reported experience; Crayon supplies a practitioner's definition. None of these sources establishes a universal conversion lift. The useful standard is more concrete: can another seller trace the claim, understand its limit and ask the next relevant question?