competitive-battlecard
Competitive Battlecard generates a sales-ready one-page document comparing your product against a named competitor, including positioning, feature comparison, pricing analysis, objection responses, and win/loss patterns. Use this when briefing sales teams before competitive deals, creating marketing collateral, or preparing responses to prospect questions about why your solution beats a specific alternative.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/competitive-battlecard && cp -r /tmp/competitive-battlecard/pm-go-to-market/skills/competitive-battlecard ~/.claude/skills/competitive-battlecardSKILL.md
## 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 1. **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) 2. **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] 3. **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 - [How to Design a Value Proposition Customers Can't Resist?](https://www.productcompass.pm/p/how-to-design-value-proposition-template)
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.