competitive-battlecard
Scannednpx machina-cli add skill Dragoon0x/Product-Skills/competitive-battlecard --openclawCompetitive Battlecard
Create tactical guides for positioning against specific competitors in real conversations.
How to use
/competitive-battlecardApply battlecard constraints to this conversation./competitive-battlecard <competitor>Generate a battlecard against the named competitor.
Constraints
Competitor Snapshot
- MUST describe what they do in one sentence. If you can't, you don't understand them.
- MUST name their ideal customer profile
- MUST state their pricing model and rough range
- MUST state their claimed positioning — what they say they're best at
- SHOULD note funding stage or company size as a behavioral signal
Where We Win
- List 3-5 specific advantages. Not "better UX" — measurable, demonstrable differences.
- Each advantage MUST have: the advantage, a proof point, and the actual words to use in conversation
- NEVER claim advantages you can't demonstrate or prove
Where We Lose
- MUST be honest. Every product loses somewhere.
- Each weakness MUST include: what the competitor does better, which customers care, and how to handle it honestly
- NEVER dodge weaknesses. Acknowledge and redirect.
- SHOULD frame as trade-offs, not failures
Objection Handling
- List top 5 things prospects say about the competitor in deals
- For each: what they say, what they actually mean, and how to respond
- NEVER badmouth the competitor directly. Position against the approach, not the company.
- SHOULD reframe objections as opportunities to highlight your strengths
Competitive Landmines
- Questions to ask early in the sales process that highlight your strengths
- MUST be honest questions, not manipulative tricks
- Examples: "Ask them to demo onboarding end-to-end" or "Ask about pricing at 500 users"
When to Walk Away
- MUST define signals that mean the prospect is a better fit for the competitor
- Walking away gracefully builds long-term reputation
- NEVER fight for a deal where the customer will churn in 6 months
Maintenance
- Battlecards go stale fast. Update when: competitor ships major changes, you lose 3+ deals for the same reason, or quarterly regardless
Source
git clone https://github.com/Dragoon0x/Product-Skills/blob/main/skills/competitive-intelligence/competitive-battlecard/SKILL.mdView on GitHub Overview
Create tactical battlecards to guide conversations against specific competitors in sales, product, and strategy. These cards cover a concise competitor snapshot, win/lose factors, objection handling, and landmines, plus when to walk away. They’re essential for preparing competitive deals, responding to rivals, or entering markets with established players.
How This Skill Works
Technically, you generate a competitor-specific battlecard that includes a concise snapshot (one sentence on what the competitor does, their ideal customer profile, pricing model and range, and claimed positioning) plus 3-5 measurable advantages with proof points and exact phrases. You also document honest weaknesses with rebuttals, common objections with responses, and clearly defined landmines and walk-away signals. Finally, keep the card current by updating it after major changes or losses.
When to Use It
- Preparing for a competitive deal against a named competitor.
- Losing to a specific competitor and needing a counter-strategy.
- Entering a market with established players and a crowded landscape.
- Coaching pre-sales teams with aligned, battlecard-driven messaging.
- Post-deal debriefs to refine positioning and landmines.
Quick Start
- Step 1: /competitive-battlecard <competitor> to generate the battlecard.
- Step 2: Fill the Competitor Snapshot: one sentence of what they do, their ideal customer, pricing, and positioning.
- Step 3: Populate Where We Win, Where We Lose, Objections, Landmines, and Walk Away signals; practice talking points and sample phrases.
Best Practices
- Capture a precise one-sentence competitor description and ideal customer profile.
- Show 3-5 measurable advantages with proof points and exact phrases to use.
- Be honest about weaknesses; frame trade-offs, not failures.
- Base objections and responses on real conversations and data.
- Keep battlecards current by updating after major changes or losses.
Example Use Cases
- Battlecard against Competitor A in mid-market SaaS showing pricing and positioning.
- Counter an incumbent's pricing model in enterprise deals with a true win story.
- Entering a market where Competitor C dominates—map differentiators and landmines.
- Post-loss case: lessons learned from a loss to Competitor D and adjusted messaging.
- Product strategy positioning against Competitor E's feature claims.