A useful competitor battlecard helps a seller diagnose fit and tell the truth under pressure. It describes the buyer situation, sourced offer differences, questions that expose tradeoffs, claims the team may make, and claims it must not make. Every volatile field has an observed date, owner, and expiry rule.
What this guide covers
- why conventional battlecards become dangerous;
- a buyer-decision structure instead of a vendor takedown;
- claim, evidence, and expiry controls;
- a copyable living battlecard.
Build around the buyer's decision
Start with the job, segment, constraints, and alternatives. A competitor may be a strong fit for one workload and weak for another. The card should help the seller discover that boundary.
Do not open with “why we win.” Open with:
- the buyer job being compared;
- the environment and risk boundary;
- the commercial workload;
- required integrations and control points;
- decision criteria the buyer has already expressed.
This reduces the temptation to recite generic feature claims.
Separate public fact from field evidence
Official pricing and plan pages such as Cursor pricing and GitHub Copilot plans support current public offer descriptions. A status page such as Cursor status supports the provider's disclosed incident record. None proves why a particular customer chose, succeeded with, or left the product.
Maintain two evidence lanes:
- public product evidence: plan, entitlement, documentation, release, status, and trust facts;
- internal field evidence: dated customer language, evaluated workload, objection, decision, and outcome—with appropriate privacy handling.
Do not turn one lost deal into a market truth or one vendor claim into an independently verified outcome.
Use comparison claims with boundaries
| Claim type | Required support | Expiry |
|---|---|---|
| Current plan or price | official offer page and observation date | 30 days |
| Capability boundary | official documentation and relevant plan | 60 days |
| Reliability statement | scoped incident record and period | event-led |
| Customer outcome | approved case or attributable internal evidence | per evidence owner |
| Our differentiation | shipped capability plus buyer relevance | release-led |
FTC advertising and marketing guidance is written for advertising claims, but its core expectation is directly useful here: claims should be truthful, non-deceptive, and evidence-backed. Sales enablement should not be exempt from that standard.
Prefer discovery questions over attack lines
Strong questions surface the buyer's own decision boundary:
- Which work must remain reviewable before an action runs?
- How variable is monthly usage, and which meter creates overage risk?
- Which administrative policies need organization-wide enforcement?
- What data must remain in a defined environment?
- What happens when an integration or model provider fails?
- How quickly must the team export its history or change providers?
Questions remain useful longer than brittle claims and create better customer evidence.
Copyable living battlecard
# Battlecard — [competitor] — [buyer job]
**Owner:**
**Last evidence review:**
**Next expiry:**
## Best-fit situations
Our likely fit:
Competitor's plausible fit:
Cases where neither is established:
## Decision criteria
| Criterion | Buyer question | Our current evidence | Competitor public evidence | Unknown |
|---|---|---|---|---|
| | | | | |
## Discovery questions
1.
2.
3.
## Approved claims
| Claim | Source | Scope | Observed | Expires |
|---|---|---|---|---|
| | | | | |
## Do-not-say boundaries
- no unsupported outcome claim
- no absolute security/reliability claim
- no stale price or feature claim
- no inference about motive or private roadmap
## Field feedback
| Date | Buyer language | Decision | Outcome | Evidence owner |
|---|---|---|---|---|
| | | | | |Create an update contract
Assign one product-marketing owner. Volatile claim rows expire automatically, even if nobody has reported a change. Product and pricing movements trigger targeted review. Sales submits evidence through a structured field, not by editing the source claims directly.
Retire a card when the competitor no longer appears in the buyer decision. Consolidate cards that repeat the same category truth. Maintain one canonical card per competitor and buyer job; exports and decks are views, not separate sources of truth.
Use the EXVIV company directory and market map for peer context, Evidence Compare for public movements, and the monitoring guide for upkeep. The startup CI system supplies the weekly review loop.
Related EXVIV research
Sources and further reading
Method note
This is an evidence and enablement framework, not legal advice. Customer and internal field evidence must follow applicable privacy, approval, and retention requirements.