Create a concise battlecard sellers can use in real competitive deals. — Claude Skill
A Claude Skill for Claude Code by Pawel Huryn — run /competitive-battlecard in Claude·Updated Jun 14, 2026·vmain@d384f0c
Turns competitor research, win/loss evidence, and positioning notes into a sales battlecard with comparison, where we win, where they win, objections, landmines, and proof points.
- Condenses competitor research into the few points a seller can remember during a call.
- Shows where your product wins, where the competitor is stronger, and what not to overclaim.
- Writes objection responses and landmine questions that steer discovery toward real differences.
- Connects battlecard language to customer segment, deal type, and evidence strength.
Product marketing writes a long competitor note that sales rarely uses during calls.
Run /competitive-battlecard to produce a compact, call-ready battlecard with proof, risks, and discovery questions.
Who this is for
What it does
Give sellers a practical one-page view when a competitor appears in pipeline.
Update old competitive content after pricing, release, or market changes.
Turn research into talk tracks and objection handling for team sessions.
How it works
Collect competitor overview, buyer segment, deal context, feature differences, pricing notes, and win/loss patterns.
Separate positioning from proof so the battlecard does not become marketing fluff.
Write the quick comparison, our advantages, their advantages, objections, and discovery questions.
Add usage guidance for sales calls and identify claims that need legal, product, or customer-reference review.
Input options
Competitor name, positioning, pricing, product strengths, and public evidence.
Example
Competitor: LearnPro. Our product: AcmeLearn. Target buyer: VP Customer Success at SaaS companies with 200-1000 employees. Known evidence: - LearnPro is strong on templates and quick self-serve setup. - We are stronger on executive reporting and CS workflow governance. - Lost deals: implementation speed and visible pricing. - Won deals: reporting, admin controls, and CSM adoption workflows. Need: battlecard for sales reps, not a long analyst report.
Use AcmeLearn when the buyer needs governed onboarding, executive visibility, and repeatable CS workflows. Expect LearnPro to sound stronger on fast self-serve setup and template variety.
| Buyer concern | AcmeLearn angle | LearnPro angle | Rep guidance | |---|---|---|---| | Fast launch | Guided implementation and admin controls | Strong template story | Ask whether launch speed or durable process matters more | | Reporting | Strong executive reporting proof | Reviews mention gaps | Show CS metrics workflow early | | Pricing | Needs current quote | Public Pro tier | Do not claim price advantage without approved pricing | | Adoption | CSM playbooks and governance | Self-serve templates | Tie to buyer's operating model |
Executive reporting, CS governance, admin controls, and repeatable adoption workflows. Best fit: teams that must report onboarding health to leadership, not just launch a template.
Simple template-first setup and a cleaner public pricing story. Do not attack these strengths. Reframe toward what happens after the first setup is complete.
Objection: LearnPro looks faster. Response: It may be faster to start. The question is whether leadership can see onboarding risk and intervene before customers stall. Objection: Their pricing is easier to understand. Response: We can map pricing to your rollout model once we know seat count, admin needs, and reporting requirements.
How will your VP CS know which teams are stuck after week one? What happens if each CSM configures onboarding differently? Which onboarding metrics need to be visible in QBRs?
Metrics this improves
Works with
Want to use Competitive Battlecard?
Choose how to get started.
Install and run this skill locally on your computer.
Open a terminal on your computer and paste this command:
This downloads the skill with all its files to your computer:
Add -g at the end to make it available in all your projects.
Start Claude Code, then type the command:
Competitive Battlecard
Create a concise, sales-ready battlecard for use against a specific competitor.
Context
You are creating a competitive battlecard for $ARGUMENTS.
Use web search to research the competitor's current product, pricing, positioning, and recent changes. If the user provides files (feature lists, win/loss data, sales call notes), read them first.
Instructions
-
Research the competitor (use web search):
- Current product offerings and features
- Pricing tiers and model
- Target market and positioning
- Recent product launches or changes
- Known strengths and weaknesses
- Customer reviews and sentiment (G2, Capterra, Reddit)
-
Create the battlecard with these sections:
Company Overview
- Founded, HQ, funding/revenue (if public)
- Target market and ICP
- Positioning in one sentence
Quick Comparison
Capability Us Them Winner [Feature area 1] [Our approach] [Their approach] [Us/Them/Tie] [Feature area 2] ... ... ... Pricing ... ... ... Support ... ... ... Where We Win
- [Advantage 1]: [Proof point or customer quote]
- [Advantage 2]: [Specific capability they lack]
- [Advantage 3]: [Better approach with reasoning]
Where They Win
- [Their strength 1]: [Our counter-positioning]
- [Their strength 2]: [How we mitigate this gap]
Common Objections & Responses
Prospect Says Respond With "Competitor X has [feature]" "[Our alternative approach and why it's better for them]" "They're cheaper" "[Value framing: total cost of ownership, ROI, hidden costs]" "They're more established" "[Our advantages: speed, innovation, focus, support]" Landmines to Plant
Questions to ask the prospect that highlight competitor weaknesses:
- "How important is [area where we excel] to your team?"
- "Have you evaluated [specific capability they lack]?"
Win/Loss Patterns
- We tend to win when: [pattern]
- We tend to lose when: [pattern]
- Key differentiator in competitive deals: [what tips the scale]
-
Keep it scannable: Sales reps need to reference this during calls. Use tables, bold text, and short bullets.
Save as markdown. Format for easy printing or sharing in Notion/Confluence.
Further Reading
Reference documents
name: competitive-battlecard description: "Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'"
Competitive Battlecard
Create a concise, sales-ready battlecard for use against a specific competitor.
Context
You are creating a competitive battlecard for $ARGUMENTS.
Use web search to research the competitor's current product, pricing, positioning, and recent changes. If the user provides files (feature lists, win/loss data, sales call notes), read them first.
Instructions
-
Research the competitor (use web search):
- Current product offerings and features
- Pricing tiers and model
- Target market and positioning
- Recent product launches or changes
- Known strengths and weaknesses
- Customer reviews and sentiment (G2, Capterra, Reddit)
-
Create the battlecard with these sections:
Company Overview
- Founded, HQ, funding/revenue (if public)
- Target market and ICP
- Positioning in one sentence
Quick Comparison
Capability Us Them Winner [Feature area 1] [Our approach] [Their approach] [Us/Them/Tie] [Feature area 2] ... ... ... Pricing ... ... ... Support ... ... ... Where We Win
- [Advantage 1]: [Proof point or customer quote]
- [Advantage 2]: [Specific capability they lack]
- [Advantage 3]: [Better approach with reasoning]
Where They Win
- [Their strength 1]: [Our counter-positioning]
- [Their strength 2]: [How we mitigate this gap]
Common Objections & Responses
Prospect Says Respond With "Competitor X has [feature]" "[Our alternative approach and why it's better for them]" "They're cheaper" "[Value framing: total cost of ownership, ROI, hidden costs]" "They're more established" "[Our advantages: speed, innovation, focus, support]" Landmines to Plant
Questions to ask the prospect that highlight competitor weaknesses:
- "How important is [area where we excel] to your team?"
- "Have you evaluated [specific capability they lack]?"
Win/Loss Patterns
- We tend to win when: [pattern]
- We tend to lose when: [pattern]
- Key differentiator in competitive deals: [what tips the scale]
-
Keep it scannable: Sales reps need to reference this during calls. Use tables, bold text, and short bullets.
Save as markdown. Format for easy printing or sharing in Notion/Confluence.