Competitor Battlecard Template Directory

Eight battlecard structures, what each is actually good for, and where each one falls apart if it's the only format you use, followed by one complete template to fill in.

1. Head-to-Head Feature Grid

Structure: rows of features, columns of vendors, checkmarks or ratings per cell. Good for: RFP responses and procurement-driven evaluations where a checklist genuinely gets read. Falls apart when: used in live sales conversations: it invites a feature-by-feature argument you can lose on a single row, and it says nothing about outcomes.

2. Landmine / Trap-Setting Battlecard

Structure: a list of discovery questions planted earlier in the sales cycle that make the competitor's weakness surface naturally later, without you ever naming them. Good for: competitive deals where you get to run discovery before the prospect brings the competitor up. Falls apart when: you're brought in after the prospect already has a competitor's proposal in hand, there's no "earlier" left to plant anything in.

3. Objection-Response Battlecard

Structure: a table of the specific things reps hear prospects say about a competitor, paired with a word-for-word response. Good for: onboarding new reps fast and keeping messaging consistent across a team. Falls apart when: the responses read as scripted and defensive rather than confident: reps need to internalize the substance, not just recite the line.

4. Win/Loss Narrative Battlecard

Structure: short real anecdotes: "here's a deal we won against them and why," "here's one we lost and why", instead of static claims. Good for: building rep conviction; stories are more persuasive internally and externally than bullet claims. Falls apart when: it isn't refreshed, a stale win/loss story from 18 months ago on an outdated competitor version does more harm than good.

5. Why-We-Win / Why-We-Lose One-Pager

Structure: two columns: the conditions under which you reliably beat this competitor, and the conditions under which you reliably lose to them. Good for: deal qualification early, deciding whether to compete hard or walk away. Falls apart when: the "why we lose" column is left blank out of ego, an honest battlecard needs both columns to be useful.

6. Persona-Specific Battlecard

Structure: the same competitor, broken into separate one-pagers per buyer persona (economic buyer, technical evaluator, end user) since each cares about different differentiators. Good for: enterprise deals with multiple stakeholders who will each research the competitor separately. Falls apart when: a small team doesn't have the bandwidth to maintain 3-4 versions per competitor, better to have one great generic version than four half-maintained ones.

7. Pricing & Packaging Comparison

Structure: side-by-side breakdown of how pricing models differ (per-seat vs. usage-based, what's bundled vs. add-on, contract terms), not just headline price. Good for: deals where the prospect's real objection is total cost of ownership, not sticker price. Falls apart when: competitor pricing isn't public and gets stale fast, needs a clear "last verified" date or it misleads reps.

8. Migration/Displacement Battlecard

Structure: specifically for deals where the prospect already uses the competitor: covers switching costs, data migration effort, contract-timing tactics, and "what breaks during the switch." Good for: competitive displacement / renewal-timed deals. Falls apart when: used for greenfield deals where the prospect has never touched the competitor, the switching-cost content is irrelevant noise there.

---

The combined template, fill this in per competitor

```markdown

Battlecard: [Your Company] vs. [Competitor Name]

Last verified: [date], pricing and positioning change; recheck quarterly.

30-Second Positioning

[One sentence: when a prospect mentions this competitor, say this.]

Why We Win

• [Condition 1 where we reliably beat them]
• [Condition 2]
• [Condition 3]

Why We Lose (be honest)

• [Condition 1 where they reliably beat us]
• [Condition 2]

Landmine Questions (ask in discovery, before the competitor is named)

• "[Question that surfaces their known weakness naturally]"
• "[Question 2]"

Objection → Response

Pricing & Packaging Notes

[Model type, what's bundled vs. add-on, contract length norms: flagged with last-verified date]

Migration/Displacement Notes (if prospect already uses them)

[Switching cost, data migration effort, contract timing tactic]

Real Win Story

[Short anecdote: deal we won against them, what tipped it]

Real Loss Story

[Short anecdote: deal we lost to them, what tipped it, and what we'd do differently] ```