Competitive Battlecard

---
name: competitive-battlecard
description: "Creates a one-page competitive battlecard a seller can use mid-deal: how the competitor positions and prices, where they are honestly strong, where buyers report pain, our differentiators with proof, trap-setting questions, responses to their attacks on us, and win and loss patterns. Use when a named competitor shows up in deals, when win rates against a rival drop, or when a competitor launches or reprices."
license: MIT
metadata:
  title: "Competitive Battlecard"
  category: "sales"
  author: "carolina"
  summary: "Build an honest, evidence-backed battlecard reps can use mid-deal: strengths, weaknesses, differentiators, traps and responses."
  tags: "battlecard, competitive intelligence, sales enablement, win loss, differentiation"
  version: "1.0"
  updated: "2026-10-19"
---
# Competitive Battlecard

Produces a single-page card (plus a longer appendix) that tells a seller how to win against one named competitor: when you usually win, when you usually lose, what to ask early, what to say when the competitor's claims come up, and what proof to show. Credibility comes from being honest about where the competitor is good.

## When to use

- A specific competitor appears in a growing share of your deals.
- Win rate against a rival has dropped, or deals are lost on the same points.
- The competitor has launched a product, changed pricing, or been acquired.
- New reps need to understand the competitive landscape quickly.
- Marketing and sales are describing the competitor differently.

## What you need

Ask for these before building:

1. **Competitor name** and which of their products you meet in deals.
2. **Your product and positioning:** who you serve best and your strongest proof.
3. **Deal evidence:** win and loss notes, call snippets, or rep anecdotes about this competitor.
4. **Public evidence the user can share or you can look up:** their website messaging, pricing page, review site themes, release notes, job postings. Date every piece of evidence.
5. **Segment:** the customer size and industry where you usually meet them.
6. **Constraints:** what your team is not allowed to say (for example, no statements about the competitor's financial health).

If you cannot verify a claim about the competitor, label it unverified or leave it out.

## Process

1. **Summarise how they sell themselves.** One-line positioning in their words, the buyer they target, their pricing model, and the three claims they lead with. Use their language so reps recognise it when buyers repeat it.
2. **Name their real strengths.** Two to four areas where buyers rightly choose them. Reps who pretend a competitor is weak everywhere lose credibility the moment a buyer disagrees.
3. **Collect weaknesses from evidence, not opinion.** Recurring complaints in reviews, gaps visible in documentation, limits that come up in your won deals. Note the source and date for each.
4. **Write differentiators as buyer outcomes.** For each of three to five points: what is different, why it matters to this buyer, and the proof (customer result, demo moment, document). If a differentiator does not matter to buyers, drop it.
5. **Build trap-setting questions.** Neutral discovery questions that lead the buyer to discover the competitor's gap on their own: "How will you handle [scenario where they struggle]?" They must be fair questions a buyer would value even without the comparison.
6. **Prepare defence.** What does this competitor say about you? List their likely attacks and a calm, factual response with proof for each.
7. **Map win and loss patterns.** Under what conditions do you usually win (segment, use case, buyer type) and when do you usually lose? Tell reps when to compete hard and when to qualify out early.
8. **Add pricing guidance.** How their pricing usually compares, the hidden costs buyers often miss (implementation, add-ons, seat minimums), and how to frame total cost rather than list price.
9. **Write the landmines to avoid.** Phrases or claims that backfire, such as disparaging the competitor or claiming a feature gap that they have since closed.
10. **Set maintenance.** An owner, a review date (quarterly is typical, and immediately after major competitor news), and a place for reps to submit new intel.

## Output format

```
# Battlecard: [Us] vs [Competitor]   Updated [date]   Owner [name]

## At a glance
- Who they are: [one line, their words]
- Who they target: [ ]
- Pricing model: [ ]
- Their lead claims: [1] [2] [3]

## When we win / when we lose
| We usually win when | We usually lose when |

## Their real strengths
- [strength] (how to respond: acknowledge, then reframe to [ ])

## Their weaknesses (evidence and date)
- [weakness] Source: [ ] Date: [ ]

## Our differentiators
| Difference | Why it matters to the buyer | Proof |

## Trap-setting questions
1.
2.

## When they say this about us
| Their claim | Our response | Proof |

## Pricing and total cost
[comparison notes, hidden costs to surface]

## Avoid saying
[landmines]

## Appendix
[longer evidence, sources, review quotes summarised, change log]
```

## Quality checklist

- The front page fits on one screen and is scannable mid-call.
- Competitor strengths are stated honestly.
- Every weakness has a source and a date; unverified claims are labelled or removed.
- Differentiators are framed as buyer outcomes with proof.
- Trap questions are fair and useful to the buyer on their own.
- Win and loss conditions tell reps when to qualify out.
- No disparaging language or claims the team cannot substantiate.
- An owner and review date are set.

## Common mistakes

- **A feature checklist instead of a battlecard.** Long comparison grids help nobody on a live call. Lead with when you win and what to ask.
- **Pretending the competitor has no strengths.** Buyers who like the competitor will stop trusting the rep.
- **Stale intel.** A weakness the competitor fixed six months ago is a liability when a rep repeats it.
- **Bashing the competitor.** It makes your team look insecure. Stay factual and steer to buyer outcomes.
- **Differentiators nobody cares about.** Being different is not the same as being better for this buyer.
- **No loss analysis.** If you only study wins, you never learn when to walk away.
- **Building it once and never sharing updates.** A battlecard nobody owns is out of date within a quarter.

## Example prompts

- "Build a battlecard against our main competitor. Here are our win-loss notes from the last two quarters."
- "A competitor just cut its price by 30%. Update our battlecard and pricing talk track."
- "Write trap-setting discovery questions that expose where a rival platform struggles with enterprise security."
- "What does this competitor usually say about us, and how should reps respond?"
- "Turn this long competitive analysis into a one-page card for reps."