Competitive Battle Card Template

Create one battle card per competitor. Keep it to two pages maximum so reps can reference it quickly during a call. Update every time the competitor makes a significant change.

Competitor Overview

Field	Details
Competitor name
Website
Founded
Funding / Revenue
Target market
Primary positioning
Key customers

Head-to-Head Comparison

Capability	Us	Competitor	Our Advantage
Core feature 1
Core feature 2
Core feature 3
Integrations
Pricing model
Implementation time
Customer support
Data security / compliance

Where We Win

List 3-4 scenarios where we consistently beat this competitor. For each one, describe the customer situation, the specific capability or approach that gives us the edge, and a proof point (a customer name, metric or quote). The first one is filled in with a fictional example for a CRM data-quality tool competing against “Competitor X”.

1. Scenario (example): A sales team of 40+ reps migrating from HubSpot to Salesforce mid-year.

   • Why we win (example): We deduplicate records during the migration instead of after it, so reps never see the duplicates.
   • Proof point (example): “We went live with zero duplicate accounts” — RevOps lead at a fictional customer, Brightline Freight.

2. Scenario:

   • Why we win:
   • Proof point:

3. Scenario:

   • Why we win:
   • Proof point:

Where We Lose (and How to Respond)

Be honest about weaknesses. Reps need to know where they are vulnerable so they can address it proactively.

1. Their strength (example): Competitor X has a lower entry price for teams under 10 seats.

   • Our response (example): Reframe around cost per clean record at the prospect’s real size, and point out the trade-off: their entry plan has no automatic merging, so someone does it by hand.

   Write the response as a way to position around the strength, reframe the conversation, or highlight the trade-off the competitor makes.

2. Their strength:

   • Our response:

Common Objections and Responses

Objection	Response
”Competitor X is cheaper."
"Competitor X has more integrations."
"We already use Competitor X and it works fine."
"Competitor X has a bigger customer base."
"I heard Competitor X just launched a new feature.”

Discovery Questions to Ask

Use these questions to uncover pain points where we have an advantage over this competitor. Each question is shown as a pattern, followed by a filled-in example for the same fictional CRM data-quality tool.

1. Ask how they handle a process where we excel. Example: “How are you currently handling duplicate accounts when two reps create the same company?”
2. Ask what happens in a scenario where the competitor struggles. Example: “What happens when a contact changes jobs and their old email starts bouncing?”
3. Ask how much time goes into a task we automate better. Example: “How much time does your team spend merging records each week?”
4. Ask whether they’ve tested the competitor on a specific use case. Example: “Have you looked at how Competitor X handles merging accounts with open opportunities? What was your experience?”
5. Ask about the outcome we deliver better. Example: “What would it mean for your team if reps never called the same account twice?”

Landmines to Set

Landmines are questions or concerns you plant early in the sales process that become problems for the competitor later.

Fill each one in with an area where the competitor is weak, a workflow where we outperform, or an edge case they don’t support. Examples for the same fictional tool:

1. “When you evaluate solutions, make sure to ask about how merges are undone if the tool gets one wrong.”
2. “One thing I’d encourage you to test is importing a list of 5,000 contacts with duplicates in it. The difference shows up clearly in a side-by-side evaluation.”
3. “Ask them how they handle merging two accounts that both have open opportunities. It may not seem important now, but customers tell us it becomes critical at scale.”

Quick Reference: Elevator Pitch Against This Competitor

When a prospect mentions this competitor, use this 30-second response:

Structure: a fair acknowledgment of the competitor, your two key differentiators, and a specific outcome (with a metric) from customers who switched. Example for the same fictional tool:

“Competitor X is a solid choice for small teams that clean their data once a quarter. Where we differ is that we stop duplicates at the point of entry and we let you undo any merge. Customers who switched from Competitor X tell us their reps stopped double-calling accounts within the first month. Happy to show you the difference in a quick demo.”

Last Updated

Date	Updated By	What Changed