Fill in the card header, then sections 1 to 5
Source every claim
Write it to be said out loud
Set a review date and file the row
Card header
Concept review: Card header
Concept review: Card header
1. Competitor overview
Company name, and any product names a buyer would say out loud: E.g. Cruller Systems. Buyers usually say “Cruller” and sometimes name the module, “Cruller Flow”. How do they position themselves? Their claim, in their words, not ours: E.g. “The enterprise platform for regulated operations.” They lead on governance, audit trails, and configurability, and pitch to a buyer who has been told to consolidate tools. Who do they primarily sell to? Company type, team, and the role that signs: E.g. Companies over 1,000 people in financial services and healthcare. They sell to a VP of Operations, and the signature comes from IT or procurement after a security review. Where do we overlap, and where do we not compete at all? E.g. We overlap on process operations teams at 200 to 1,000 people. Below 200 people we rarely see them. In regulated enterprise above 5,000 we are not in the deal.Concept review: Competitor overview
Concept review: Competitor overview
2. Why they win
Where do they genuinely beat us? One row per reason, with the deal situation it shows up in.Concept review: Why they win
Concept review: Why they win
3. Why we win against them
Where do we beat them? One row per reason, with the evidence behind it.Concept review: Why we win
Concept review: Why we win
4. Common objections and how to handle them
The objections that come up when this competitor is in the deal. Three to five, in the order you hear them.Concept review: Objections
Concept review: Objections
5. Landmine questions
Questions to ask the buyer that surface this competitor’s limits, in their words rather than ours. Three to five.Concept review: Landmine questions
Concept review: Landmine questions
6. Pricing and packaging comparison
How their pricing is structured, and where ours differs:Concept review: Pricing and packaging
Concept review: Pricing and packaging
7. Key takeaways and sales strategy
The strategy against this competitor, in two or three sentences: E.g. Compete on time to value and on who controls change after launch. Avoid a feature-count comparison, which we lose. Get the process owner into a working setup before IT builds a formal scorecard, because a running workflow reframes the evaluation. Soundbites a rep can say as written. Two or three.- E.g. “They’re built for a team that has a consultant on retainer. We’re built for the person who owns the process.”
- E.g. “Same problem, different bet. They bet on configurability, we bet on you never needing a ticket to change something.”
- E.g. “Most teams we talk to were paying for depth they used twice a year.”
Concept review: Key takeaways and sales strategy
Concept review: Key takeaways and sales strategy
Before you publish the card
Check every claim has a source
Check the absolutes
Confirm the proof points are cleared
Read it out loud
File the row
Related resources
- Battle card concepts What a card is for, and why it is structured this way.
- Battle card library Every card in circulation, with tier, owner, and review date.
- Positioning The competitive frame this card operates inside.
- Messaging The approved words and the claims that have been cleared.
- Legal review process What comparative claims need before they leave a sales conversation.
MCP wiring
MCP wiring
Domains: strategy, brand
Provides:
battle-cardUses:
approved-claims, concept:battle-card, glossary, legal-triggers, library:battle-card, messaging, positioningTriggers: “Make a battle card for a competitor” · “How do we beat Competitor X?” · “Help sales handle objections about a rival” · “Compare us to a competitor”Asks, in order:- Which competitor, and is there already a card for them? Options:
library:battle-card. - How do they describe themselves, in their own words? Options: your answer. Skip when: URL given.
- Where do they genuinely beat you, and in which deals? Options: your answer.
- What evidence do you have for where you win, and which customer stories are cleared? Options:
approved-claims. - Which objections come up when they’re in the deal? Options: messaging#objection-responses.
- Do you have real pricing to compare? Options: yes or no.