Sales battlecard template with a filled example
A buyer asks why they should choose you over the tool they already own. A useful sales battlecard gives the rep a question to ask, a claim they can support and a next step that tests the buyer’s choice.
Use this editable template to build that reference for your team. The guide includes a blank card, a fictional filled example and a practice exercise for checking how a rep uses it.
Copy the sales battlecard template
Download the editable Word template or Markdown template. Both include the blank card, evidence fields and practice notes.
A sales battlecard is a short reference a rep uses to handle a particular buyer decision. It should help the rep ask a useful question, make a supported claim and agree on the next step. Keep the detailed research in a separate evidence sheet.
Copy this table into your team's document, then fill it for one buyer type and one decision. The editable download includes the card and an evidence-and-practice worksheet.
Field | What to write |
|---|---|
Buyer and decision | Who is choosing, what they need to do, and the alternatives they are considering. |
When to use this card | The call stage or question that makes the card relevant. |
First question | A question that checks the buyer's requirement before you make a comparison. |
Supported position | What you can say, the condition under which it is true, and the evidence reference. |
When the alternative fits | A buyer situation in which the other option may be the sensible choice. |
Proof to offer | The document, demonstration or other approved material that supports your position. |
Unknown or unsafe claim | What has not been checked and what the rep must not claim. |
Next step | The test, meeting or follow-up that would resolve the buyer's decision. |
Owner and review | Who approves the card, when it was checked, and what would trigger another review. |
Use short sentences on the card. Link to the source instead of pasting its entire feature list into the response. A rep should be able to find the relevant question while preparing for the call.
Fill the card with buyer questions and usable proof
Start with the requirement that could change the buyer's choice. “Why are we better?” is too broad to guide a useful card. “Can a location manager change a reminder without asking the central team?” gives you a condition to check.
Choose the situation. Write the buyer's role, the job they need to complete and the alternatives they are considering. The alternative might be a competing product, a tool they already own or their current manual process. Avoid adding a competitor just because sales wants a card for its name.
Check the criterion before giving an answer. A buyer who asks about customization might mean branding, permissions, workflow changes or integration work. Ask which change they need to make and who needs to make it. The objection-handling roleplay guide gives practice scenarios for clarifying the concern behind a buyer's first objection.
Write a claim with a boundary. Replace “we are easier to use” with something a rep can show under stated conditions. Record the source, the relevant version or plan, who checked it and when. A product page may show that a feature is advertised; it does not prove that the feature meets the buyer's particular permissions or workflow requirement.
Give the alternative a fair fit. If the buyer already has a tool that does the required job, the card should allow for that answer. HubSpot's battlecard guidance includes organizing advantages and disadvantages. Treat a competitor's strength as a buying consideration, not a cue to invent a weakness.
Pair the response with proof and a next step. The rep needs to know which approved material to show and what to ask the buyer to do next. Gong's template guidance puts evidence alongside talk tracks and differentiators. Keep that connection visible on your card: claim, supporting material, useful next action.
If you cannot verify a claim, put it in the unknown field. “We have not checked that permission in your setup” is a usable answer. Missing information on a competitor's website is not proof that a capability is absent.
A filled battlecard for a fictional buyer decision
The following example is fictional. Option A, Option B, the buyer and the evidence packet are invented to show how to fill the template. They do not describe Quotain, a customer or any real competitor.
A regional service business is choosing how its location managers will edit appointment reminders. Option A is a separate appointment tool. Option B is the business suite the company already uses.
For this exercise, the source packet contains three facts:
- R1, buyer requirement: location managers need to edit reminder text without asking a central administrator.
- A1, observed exercise: a location-manager account changed reminder text in Option A's test environment. This says nothing about price, other permissions or production deployment.
- B1, open check: the same task has not been tested with the company's current Option B permissions.
Here is the completed card.
Field | Fictional example |
|---|---|
Buyer and decision | Regional operations lead deciding whether to add Option A or keep reminder editing in Option B. |
When to use this card | The buyer asks why another appointment tool is needed. |
First question | “Who needs to change the reminder, and what happens today when they try?” |
Supported position | “In our test, a location-manager account edited reminder text in Option A.” Reference A1. |
When the alternative fits | Keep Option B if its current setup meets the requirement and the buyer prefers to avoid administering another tool. |
Proof to offer | Show the edit using the intended role in a test environment. Ask the buyer to confirm the result against R1. |
Unknown or unsafe claim | Option B's permissions are untested. Do not say it cannot perform the task. |
Next step | Ask the suite administrator to run the same edit in Option B, then compare the results. |
Owner and review | The assigned product specialist checks both results and updates the card before the recommendation. |
The claim stays narrow even when the buyer invites a broader answer:
Buyer: “So the suite we already have can't do this?”
Rep: “We haven't checked the permissions in your setup. We can show the edit in Option A and ask your suite administrator to try the same task. If the suite already does what your managers need, that changes the decision.”
The rep has answered the question, preserved the unknown and proposed a way to resolve it. The card has not turned an untested feature into a competitive claim.
Rehearse the conversation the card is meant to support
Use the finished card in a short practice exchange before relying on it with buyers. One person plays the buyer and another responds using the card. The buyer should ask a question that tests a boundary in the evidence.
For the fictional example, start with: “We already pay for the business suite. Why would we add another tool?” If the rep jumps straight to Option A, ask: “What have you checked about our current permissions?”
The observer records what the rep actually said:
- Did the rep ask who needs to edit the reminder and what happens today?
- Did the rep keep the Option A claim within the observed test?
- Did the rep acknowledge that Option B's permissions were still unknown?
- Did the rep propose the same task as a fair test for both options?
These are suggested practice checks, not a validated certification standard. Record the missed question or unsupported statement, give one piece of feedback and repeat the exchange. For a wider coaching rubric, use the sales call scorecard.
If you want an AI buyer for the exercise, Quotain's sales simulations support tailored personas, situations, objections and scorecards. Keep the battlecard's research and claim approval with its owner. Use practice to inspect the rep's response; it does not verify the underlying competitor facts.
Keep evidence notes behind the card
Give every card an owner and a review trigger. Klue's battlecard guide recommends collecting internal and external sources, getting rep feedback and keeping the information current. A visible checked date helps the rep know when the source was reviewed; the date alone does not show that it is accurate.
Use the second sheet in the download for the research detail:
Evidence field | What belongs here |
|---|---|
Claim reference | A short label that connects the card's response to this entry. |
Source and scope | A link or document reference, relevant version or plan, and conditions of any test. |
What it supports | The exact fact the source supports. |
What it does not support | Assumptions, missing checks or broader conclusions the rep must avoid. |
Review owner and date | The person who checked it and the date of that check. |
Sharing status | Whether the material is approved to share with buyers or restricted to internal use. |
Review trigger | A product change, changed buyer requirement, contradictory evidence or scheduled check. |
Keep the detailed notes available to the rep without crowding the card. When a source changes or a buyer exposes a gap, flag the affected statement and ask the owner to check it before it is reused. Update the response and its supporting material together.
Put one card into use
Choose a buyer decision already on your team's calendar. Fill the card, check the claims and rehearse the question most likely to expose a gap. Use the first attempt to decide what needs fixing before the real conversation.
Bring an approved battlecard to a Quotain demo to discuss the buyer scenario and the response you want reps to practice.