← Back to list
⚡

competitive-battlecard Checked

Create sales-ready competitive battlecards comparing your product against a specific competitor —…
⚡ Productivity skills By phuryn Version v1.0.0 Added 2026-09-03 Updated 2026-09-03 Source ↗
8.3Overall rating
2Views
5Downloads
26.0kStars

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "competitive-battlecard" skill by following the instructions at https://skill123.me/install/competitive-battlecard.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/competitive-battlecard.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 1 KB
📊 Static rating
8.3/10
Trigger
7.5
Structure
8.0
Workflow
6.8
Content
9.0
Engineering
10.0
Security
10.0

Six-dimension rubric with reviewer rationale.

View scorecard ↓
🛡 Dynamic test
—

Not live-tested yet — this skill is rated on static analysis only.

About this skill

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?'

Documentation

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

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

Score breakdown

Trigger
7.5
Good What/When including indirect why-not-competitor phrasing but no explicit When-Not exclusion
Structure
8.0
Compact single file, no redundancy, but no progressive disclosure layers
Workflow
6.8
Clear research-then-generate flow with rich section template and save step; no error handling or verification
Content
9.0
Concise imperative instructions with concrete table templates and example objection responses
Engineering
10.0
Valid frontmatter; no scripts or file references
Security
10.0
No scripts or sensitive data; external link is credible product blog
Focused single-file generator with research step, detailed battlecard template, and objection-handling tables; lacks verification loop and When-Not boundary.