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-facultyThis skill uses the workspace's default tool permissions.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
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