Help us improve
Share bugs, ideas, or general feedback.
From pm-copilot
Use this skill when the user asks for "competitor battlecards", "battlecard for [competitor]", "how do we beat [competitor]", "how do we handle objections about [competitor]", "competitive win/loss", "sales competitive guide", "how should sales talk about competitors", or needs a structured competitive comparison for sales, customer success, or internal strategy purposes.
npx claudepluginhub productfculty-aipm/pm-copilot-by-product-facultyHow this skill is triggered — by the user, by Claude, or both
Slash command
/pm-copilot:competitor-battlecardsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are creating competitive battlecards — structured one-page guides that help sales, customer success, and the product team understand specific competitors and articulate our differentiators confidently.
Generates sales-ready competitive battlecards in markdown, comparing positioning, features, pricing, objections, and win/loss patterns to specified rivals via web research.
Build competitive battle cards with side-by-side feature comparisons, pricing intel, win/loss patterns, objection responses, and sales talk tracks. Use this skill whenever the user mentions battle cards, competitive positioning, "how do we compare to X", competitor analysis for sales, win themes, competitive differentiation, or needs ammunition against a specific competitor. Also trigger when a rep asks "what do I say when a prospect brings up [competitor]".
Researches competitors and generates interactive HTML battlecards with comparison matrices, product deep-dives, recent releases, sales talk tracks, and positioning.
Share bugs, ideas, or general feedback.
You are creating competitive battlecards — structured one-page guides that help sales, customer success, and the product team understand specific competitors and articulate our differentiators confidently.
Frameworks: April Dunford (Obviously Awesome — positioning against alternatives), Hamilton Helmer (7 Powers), Lenny Rachitsky (competitive differentiation).
Read memory/user-profile.md for product context and current bets. Read context/company/competitors.md if it exists — use as a starting point. If WebSearch is available, research the specified competitor.
For each competitor, gather:
Using WebSearch if available:
For each competitor, produce a one-page battlecard:
[Competitor Name] Battlecard
Who they are: [One sentence description — what they build and who they serve] Best for: [The customer profile they're ideal for — be honest] Price: [If public] Key differentiators: [Their 3 strongest genuine advantages]
Where we win:
| Dimension | Us | [Competitor] | Why We Win |
|---|---|---|---|
| [Dimension 1] | [Our capability] | [Their capability] | [Honest differentiator] |
| [Dimension 2] | [Our capability] | [Their capability] | [Honest differentiator] |
| [Dimension 3] | [Our capability] | [Their capability] | [Honest differentiator] |
Where they win: (Be honest — your team needs to know where competitors are stronger to have credible conversations)
When we lose and why:
Common objections and responses:
"[Competitor] has more integrations"
"[Honest, confident response that acknowledges the point and reframes toward our strength]"
"[Competitor] is cheaper"
"[Response]"
"[Competitor] is more established"
"[Response]"
Trap to avoid: [The one thing to never say when this competitor comes up — often a claim we can't back up or a dismissal that makes us look defensive]
How to qualify: Ask: "[Question that helps determine whether this prospect is better served by us or by [Competitor]"
Add a section of general principles for competitive conversations:
Produce battlecard(s) for each competitor specified. Offer to:
context/company/competitors.mdoutputs/battlecard-[competitor]-[date].md