battlecard — Claude Code command: what it does, how to install
Generates a concise, sales-focused competitive battlecard comparing two products. Useful before prospect calls to align pricing rebuttals and differentiators.
MIT ★ 28,211 updated 2026-10-16
/plugin marketplace add phuryn/pm-skills
/plugin install pm-go-to-market@pm-skillsWhat battlecard does
The command prompts for basic context around the deal stage, target buyer, and competing vendor. It then applies web research via the competitive-battlecard skill to inspect current pricing models, feature releases, and recurring complaints on customer forums.
Claude Code outputs a one-page Markdown battlecard. It contains side-by-side capability matrices, answers to standard objections, and tactical questions designed to reveal rival weaknesses without directly disparaging them.
Real win/loss notes are necessary to ground the advice, because generic competitor claims miss why buyers actually choose alternatives. The documentation also recommends quarterly updates as competitor features change rapidly.
What it helps with
- prepare sales reps for calls against a specific rival
- map counter-positioning angles and pricing objections
- draft trap questions that expose rival product limitations
- structure battle-tested conversation starters for displacement deals
Example prompts for the agent
- /battlecard Our CRM vs Salesforce
- /battlecard ProjectFlow vs Monday.com for mid-market teams
- /battlecard compare our billing platform with Stripe using deal-notes.txt
How to install battlecard
1Plugin marketplace
/plugin marketplace add phuryn/pm-skills/plugin install pm-go-to-market@pm-skills2Manually: put the files in place
.claude/commands/battlecard.mdCall it with /battlecard. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/battlecard.mdCall it with /prompts:battlecard. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/battlecard.prompt.mdManually: put the files in place
.gemini/commands/battlecard.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about battlecard
How do I install battlecard in Claude Code?
First, register the source registry with /plugin marketplace add phuryn/pm-skills. Next, install the module via /plugin install pm-go-to-market@pm-skills. You can also save the file directly to .claude/commands/battlecard.md.
What does the battlecard command do?
It researches the competing product and creates a concise Markdown file with positioning tables, pricing breakdowns, and objection-handling scripts for sales conversations.
What information improves the generated battlecard?
Supplying win/loss data from actual deals and naming the buyer persona produces actionable conversation starters instead of generic marketing comparisons.
Source text
battlecard.md · MIT
--- description: Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies argument-hint: "<your product> vs <competitor>" --- # /battlecard -- Competitive Battlecard Create a concise, sales-ready battlecard that helps your team win deals against a specific competitor. Includes positioning, feature comparison, objection handling, and conversation strategies. ## Invocation ``` /battlecard Our CRM vs Salesforce /battlecard ProjectFlow vs Monday.com for mid-market teams /battlecard [upload competitor materials or win/loss data] ``` ## Workflow ### Step 1: Identify the Matchup Ask: - Your product and the specific competitor - Who is the typical buyer choosing between you? - Do you have win/loss data or sales feedback? - What deal stage does this typically come up? (early evaluation, final decision, displacement) ### Step 2: Research the Competitor Apply the **competitive-battlecard** skill with web research: - Current product capabilities and recent launches - Pricing model and published pricing - Target market and positioning - Known weaknesses (from reviews, forums, customer feedback) - Recent company news (funding, leadership, strategy shifts) ### Step 3: Generate Battlecard ``` ## Competitive Battlecard: [Your Product] vs [Competitor] **Last updated**: [today] **Use when**: [situation where this competitor comes up] ### Quick Summary **We win when**: [buyer profile and situation where you have advantage] **We lose when**: [buyer profile and situation where competitor has advantage] **Key differentiator**: [one sentence] ### Positioning **How they position**: [their messaging] **How we position against them**: [our counter-positioning] ### Feature Comparison | Capability | Us | Them | Verdict | |-----------|-----|------|---------| | [capability] | [status] | [status] | [advantage] | ### Pricing Comparison | Dimension | Us | Them | Notes | |----------|-----|------|-------| ### Objection Handling | Objection | Response | Proof Point | |----------|---------|------------| | "They have [feature]" | [response] | [evidence] | | "They're cheaper" | [response] | [TCO analysis] | | "They're more established" | [response] | [counter] | ### Landmines to Plant [Questions to ask the prospect that expose competitor weaknesses] 1. "Ask them about [topic] — their answer will reveal [weakness]" ### Trap Questions to Expect [Questions the competitor will encourage the prospect to ask you] 1. "[Question]" — How to respond: [response] ### Win/Loss Patterns **We typically win because**: [top 3 reasons] **We typically lose because**: [top 3 reasons] ### Conversation Starters **If they're already using [Competitor]**: - [approach for displacement deals] **If they're evaluating both**: - [approach for competitive evaluations] ### Resources - [Customer story / case study that counters this competitor] - [Third-party comparison or review] - [Demo script optimized for this competitive situation] ``` Save as markdown. ### Step 4: Offer Next Steps - "Want me to **create battlecards for other competitors**?" - "Should I **run a full competitive analysis** of the market?" - "Want me to **draft customer-facing comparison content** based on this?" - "Should I **update the positioning** based on competitive insights?" ## Notes - Battlecards should be updated quarterly — competitors change fast - "Landmines" are the most valuable section for sales — teach reps what questions to ask - Never trash the competitor in front of the prospect — position on your strengths, not their weaknesses - Win/loss data from real deals is worth 10x any analysis — encourage the user to add it - Keep it to one page equivalent — sales reps won't read a 10-page document during a call
© Paweł Huryn · MIT · phuryn/pm-skills