How to Build a One-Page Battlecard for Each Competitor

Reps need to scan it while a buyer waits, so every block should answer a live question:

• When they show up: the buyer types and situations where this competitor gets shortlisted.
• How buyers describe them: what the competitor does well, in the buyer's words.
• Where we win: the two or three situations where your approach fits better, with the reason.
• Where we lose: the situations where the competitor is the better choice. Saying so builds trust and tells reps when to walk away.
• Questions to ask: discovery questions that surface the criteria you're strongest on, without attacking anyone.
• Objections and answers: the three most common, with a short truthful reply.
• Proof: one or two customer outcomes you're permitted to share.
• Last updated: date and owner.

Leave out pricing tables and feature grids you can't verify. They go stale and invite arguments.

Start with your own deals, then add public material:

1. Review recent losses and wins that involved the competitor, and note why the buyer chose as they did. Gathering intelligence from lost deals covers how to ask.
2. Ask two or three customers who evaluated both what tipped the decision, with their permission.
3. Read the competitor's public website, documentation, pricing pages and customer stories, and note what they emphasize.
4. Check review sites and forums, treating individual comments as leads to verify, not facts.
5. Ask your services, support and onboarding teams what customers say about switching.

Keep the source of each claim in your notes. If you can't say where a point comes from, leave it off the card.

Buyers often know the competitor better than your rep does. Write claims that hold up:

• State what's true and checkable, and describe differences as fit, not superiority. "Better for teams that need X" beats "the best."
• Don't make claims about a competitor's product, security, pricing or customers unless you can support them from public information. Untrue or misleading statements about a rival can create legal trouble, so have your counsel check any comparison you publish.
• Acknowledge real strengths first. It makes your points about differences more credible.
• Tie every difference to a buyer outcome, such as time to launch or ease of change, not to a feature name.

A test: could a rep say every line on the card to the competitor's own customer without embarrassment? If not, rewrite it.

Trap questions steer the evaluation toward criteria where you're strong. They work when they're honest and useful to the buyer, so avoid anything that feels like a trick.

For example, if your strength is quick setup for a small team, ask "how many people will need to be involved in rollout, and what's your timeline?" A buyer with a small team and a short timeline will notice the tradeoff on their own.

For objections, use a three-part reply: acknowledge the concern, give a specific answer, and confirm it with the buyer. Say a buyer tells you the competitor is cheaper. Instead of matching on price, respond with what the buyer would give up, ask what they've budgeted for the outcome, and offer to compare total effort, not only license cost. Rehearse these in role-play, not just on a page.

A stale card is worse than none. Give each card an owner and a review date, and set triggers that force an update: a competitor's product launch, a pricing change, or three deals in a row with the same new objection.

Put cards where reps already work, such as beside the deal in the CRM or in the sales content library. A content platform like Highspot or Seismic helps once you have many cards and need to see which ones reps open. The enablement comparison explains how those tools differ, and live battlecards with AI covers newer approaches.

Also tie cards to your sales playbook, so competitor guidance matches the process reps follow, and review win-loss results monthly to see whether the cards change outcomes.