What This Template Is For
Sales reps lose deals they should win because they cannot articulate why the product is better than Competitor X when the prospect asks. The rep fumbles, improvises, or says "let me get back to you." By the time they follow up, the prospect has moved on.
A competitive battlecard gives the sales team ready-to-use responses for every competitive scenario they encounter. It covers what each competitor does well, where they fall short, the specific objection patterns that come up in deals, and the talking points that win. The best battlecards are living documents that update with every deal won and lost.
This template works for direct competitors (same category, same buyer) and indirect competitors (different approach, same problem). For the broader product strategy that informs competitive positioning, see the strategy handbook. If you need to structure the full messaging framework around your competitive position, use the product messaging template.
How to Use This Template
- Create one battlecard per competitor. Do not combine multiple competitors into a single document. Each card should stand alone so reps can pull the relevant one before a call.
- Source from real deals, not marketing pages. The best competitive intelligence comes from win/loss interviews, customer calls, and sales call recordings. Competitor websites show aspiration, not reality.
- Write for a 2-minute read. Reps read battlecards between meetings. If it takes longer than 2 minutes to scan, it will not get used.
- Update monthly. Assign a PMM or competitive analyst to review each battlecard monthly. Competitors ship features, change pricing, and pivot positioning. Stale battlecards cause more damage than no battlecard.
- Test with the sales team. After drafting, role-play three competitive scenarios with a senior rep. Their feedback tells you whether the card is practical or theoretical.
Competitive Battlecard Template
Competitor Overview
| Field | Details |
|---|---|
| Competitor name | [Name] |
| Website | [URL] |
| Category | [Same category / Adjacent category / Indirect competitor] |
| Founded | [Year] |
| Funding / Revenue | [Last known funding round or estimated ARR] |
| Target market | [Who they sell to: company size, vertical, role] |
| Pricing model | [Freemium / Per seat / Usage-based / Enterprise custom] |
| Key differentiator | [One sentence: what they claim makes them unique] |
Quick Comparison
| Dimension | Us | [Competitor] |
|---|---|---|
| Primary audience | [Our target] | [Their target] |
| Core strength | [What we do best] | [What they do best] |
| Pricing | [Our model + starting price] | [Their model + starting price] |
| Integration depth | [Key integrations] | [Key integrations] |
| Deployment | [Cloud / On-prem / Hybrid] | [Cloud / On-prem / Hybrid] |
| Support model | [Our support] | [Their support] |
Where We Win
List the scenarios, segments, and use cases where we consistently beat this competitor. Support each with data from closed-won deals.
- ☐ Win scenario 1 documented with deal reference
- ☐ Win scenario 2 documented with deal reference
- ☐ Win scenario 3 documented with deal reference
| Scenario | Why We Win | Evidence |
|---|---|---|
| [e.g., Mid-market SaaS with 50-200 employees] | [e.g., Faster implementation, no professional services needed] | [Won 8 of last 10 competitive deals in this segment] |
| [e.g., Teams using Slack-first workflows] | [e.g., Native Slack integration vs. their webhook-only approach] | [Customer quote: "The Slack integration sealed it for us"] |
| [e.g., Companies with compliance requirements] | [e.g., SOC 2 Type II certified, they are Type I only] | [Won 3 enterprise deals citing compliance gap] |
Where They Win
Be honest. Knowing where you lose is more valuable than pretending you always win. This section helps reps qualify out early and focus on winnable deals.
| Scenario | Why They Win | Our Response |
|---|---|---|
| [e.g., Enterprise 5,000+ seats] | [e.g., Deeper admin controls and SCIM provisioning] | [Acknowledge the gap. Position our Q3 roadmap for enterprise admin features.] |
| [e.g., Teams deeply embedded in their ecosystem] | [e.g., Switching cost is high, they have 3+ integrations in place] | [Focus on the integration pain points. Offer migration support.] |
Objection Handling
The top 5-7 objections reps hear when competing against this vendor. Each objection gets a response framework: acknowledge, reframe, proof point.
| Objection | Acknowledge | Reframe | Proof Point |
|---|---|---|---|
| "[Competitor] has more features" | "They have been in market longer and have built a lot." | "The question is which features your team will actually use. Our customers deploy in days, not months, because we focus on the 20% of features that drive 80% of value." | [Customer X deployed in 3 days vs. 6-week Competitor implementation] |
| "[Competitor] is cheaper" | "Their entry price is lower, that's true." | "Look at total cost including implementation, training, and the integrations you will need. Our all-in cost is typically 30% lower over 12 months." | [TCO comparison spreadsheet from 5 recent deals] |
| "We already use [Competitor]" | "A lot of our customers switched from them." | "The switching cost is lower than you think. We offer free migration and your team will be productive in the first week." | [Migration case study: Acme switched in 5 business days] |
| "[Competitor] is the industry standard" | "They are well-known in this space." | "Market share and product fit are different things. We built specifically for [your segment], which is why our NPS with teams your size is 72 vs. their published 38." | [NPS data by segment, G2 reviews from similar companies] |
Landmine Questions
Questions the rep can ask in discovery that expose the competitor's weaknesses without naming them.
- ☐ "How important is [area where we are strong] to your evaluation?"
- ☐ "What has your experience been with [process where competitor is weak]?"
- ☐ "How are you handling [use case that competitor does not support]?"
- ☐ "What does your team's workflow look like for [task where our UX is better]?"
- ☐ "Have you looked at the total cost including [hidden cost in their model]?"
Win/Loss Tracker
| Deal | Outcome | Segment | Key Factor | Date | Rep Notes |
|---|---|---|---|---|---|
| [Acme Corp] | Won | Mid-market SaaS | Integration speed | [Date] | [Notes] |
| [Beta Inc] | Lost | Enterprise | Admin controls gap | [Date] | [Notes] |
| [Gamma Co] | Won | Startup | Price + time to value | [Date] | [Notes] |
- ☐ Win/loss data reviewed and updated this month
- ☐ New patterns identified and added to "Where We Win/Lose" sections
- ☐ Objection handling updated based on recent deal feedback
Filled Example: Battlecard vs. LegacyPM Tool
Competitor Overview
| Field | Details |
|---|---|
| Competitor name | LegacyPM |
| Category | Direct competitor |
| Founded | 2015 |
| Target market | Enterprise product teams (1,000+ employees) |
| Pricing model | Per seat, $45/user/month, annual contract required |
| Key differentiator | "End-to-end product management platform" with roadmapping, analytics, and feedback in one tool |
Where We Win
| Scenario | Why We Win | Evidence |
|---|---|---|
| Mid-market teams (50-500 employees) | They need 3 months of professional services to deploy. We deploy in 3 days with self-serve onboarding. | Won 12 of 15 mid-market competitive deals in Q4. |
| Teams prioritizing speed to value | Their UI requires training. Ours is intuitive enough that teams self-adopt. | Average time-to-value: 4 days (us) vs. 47 days (them). |
Top Objection
"LegacyPM has a built-in analytics module."
Acknowledge: "They do bundle analytics." Reframe: "Their analytics module has a 23% adoption rate according to their own case studies. Most teams still export to Amplitude or Mixpanel. We integrate natively with both, so your team keeps the analytics tool they already know." Proof: Three customer quotes confirming the integration advantage.
For frameworks that help structure competitive analysis decisions, review the RICE framework for scoring competitive feature gaps. The glossary entry on competitive analysis covers the foundational concepts. To map competitive positioning into your go-to-market strategy, ensure each battlecard feeds into your launch messaging.