24 Sept 20265 min read

How to build a sales battlecard your team will use

Put the right evidence within reach when a buyer asks why they should choose you.

The Vyera Team

Product & Research

A sales battlecard is a short reference that helps a salesperson handle a specific competitive conversation. It should explain the buyer context, useful discovery questions, verified differences, relevant objections and a sensible next step. Every material competitive claim needs a source and a review date.

A long competitor profile is difficult to use during a call. The seller needs to know what to ask, which facts matter to this buyer and when the alternative might be a better fit. A strong battlecard makes that judgement easier without turning the conversation into an argument about feature counts.

Build one card for one common comparison first. Improve it with feedback from real conversations before expanding the library.

Start with the deal situation

Define the audience, use case and alternative. A card for a founder comparing software with a manual process will be different from one for a procurement team replacing an established vendor.

Collect the questions buyers actually raise. Ask the sales team which objections recur and where they struggle to find evidence. Record uncertainties so the card does not turn an untested sales assumption into approved messaging.

Write discovery questions before rebuttals

The buyer's priorities determine which differences matter. Start with questions that uncover the work, the constraints and the decision process.

  • Which part of the current workflow takes the most effort?
  • What happens when the team misses an important change?
  • Which sources, integrations or approval steps are essential?
  • How will you judge whether the new approach is working?
  • What would prevent your team from adopting it?

Use the answers to select relevant evidence. Avoid leading questions that manufacture a problem or push buyers to disclose confidential information about another supplier.

Build a compact card with supporting links

Card sectionWhat belongs in it
Deal contextAudience, task and named alternative
DiscoveryThree to five questions about the buyer's priorities
Where we fitSupported advantages relevant to this situation
Where they fitVerified strengths or cases outside our scope
Objection responseAn accurate answer and a question to clarify fit
ProofDocumentation, demonstration or permitted customer evidence
Next stepA test, walkthrough or follow-up tied to the buying decision
MaintenanceOwner, sources and last substantive review date

Keep the working card short enough to scan. Put detailed research behind links. A seller should be able to locate the relevant evidence quickly without reading an entire report during a conversation.

Turn objections into a useful discussion

Use an acknowledge, clarify, evidence and next-step sequence. This is a suggested conversational structure, not a script to recite regardless of the buyer's answer.

Hypothetical objection: "We already track competitors in a spreadsheet."

Example response: "That can work well when the review is manageable. How do you keep the entries current, and who follows up when something changes? Let's compare the steps in your current process with the workflow you are considering, then see whether there is enough benefit to justify changing."

This response does not assume that software is necessary. It creates a way to compare the work and cost. If a demo is appropriate, show only capabilities available in the product and relevant to that buyer's process.

For a pricing objection, compare the same billing period, usage and required features. Include setup work or add-ons where they materially affect the cost. Avoid claiming savings from a list price alone.

The best answer on a sales call is the one you can support and connect to the buyer's priorities.

1

1 deal situation

2

5 discovery questions

3

1 accountable owner

These are suggested limits for the first card.

Give the card an expiry trigger

Assign somebody to maintain the evidence. Review the card when either product changes a relevant capability, price or plan restriction, and schedule a periodic check for stale links and claims.

After calls, capture which questions came up, whether the card helped and what evidence was missing. Measure use and usefulness before attributing changes in win rate to the card. Deal outcomes also depend on fit, budget, timing and the seller's execution.

Keep internal notes separate from public-facing content. The template in this playbook can be public; confidential deal details and unverified competitive notes belong in the internal working version.

A completed battlecard for the manual alternative

This example compares a potential software workflow with a buyer's existing manual review. It is a discussion aid, not a claim that a particular product saves time or improves revenue.

Deal context: A small marketing team checks competitor websites and keeps notes in a spreadsheet. The buyer wants to understand whether changing the process is worthwhile.

Discovery question: "Could you walk me through last week's review, including how a finding became an action?"

Where a manual process can fit: A short watchlist, infrequent relevant changes and a clear owner may make a spreadsheet sufficient. Establish whether the buyer actually experiences a problem.

Difference to demonstrate: For a software option, show how an observed change retains its source, reaches the right person and becomes a reviewed next step. Verify that each demonstrated capability is currently available.

Proof required: Ask the buyer to bring a permitted example from their workflow. Run a small, agreed comparison and record review time, missed relevant changes, false alerts and completed actions. Agree what counts as relevant before testing.

Response to "We can do this ourselves": "You may be able to. Let's identify whether collection, review or follow-up is causing a problem, then test that part of the process."

Next step: Compare the existing and proposed workflows on the same watchlist for an agreed period. Choose the outcome measures in advance. Do not promise a saving before you have measured the work and the full cost.

Disqualifier: If the buyer has no material problem, adequate coverage and a reliable owner, record that outcome. A battlecard should help the team recognise poor fit as well as explain good fit.

How Vyera fits into the workflow

Vyera brings Battle Cards together with competitive research. Use this framework to define the questions, supporting evidence and review process your sales team needs.

Walk into the next conversation prepared

Bring the buyer's priorities and the supporting evidence into the same view. Explore Vyera's approach to competitive context and sales preparation.

Frequently asked questions

A comparison page helps a buyer assess options publicly. A battlecard helps a seller navigate a conversation and can include internal guidance that should not be published.

Start with the comparison that appears most often in current deals. Add another when the team has enough evidence and a clear owner to maintain it.

Leave it out of approved messaging or label it as an open research question. An unsupported claim should not become a talking point simply because it appears in a document.

Ready to
compete smarter?

Your market, watched while you build.

Free to start · No credit card required

teams already joined