# Competitive Battle Card

> Create a concise, sales-ready competitive battle card that captures positioning differences, win/loss talking points, objection handling, and landmine questions for competitive deals.

- Skill: `nandanosql/competitive-battle-card` (Agent Skill)
- Install (CLI): `npx skillmds@latest add nandanosql/competitive-battle-card`
- Raw SKILL.md: https://api.skillmd.com/api/skills/nandanosql/competitive-battle-card/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: nandanosql (https://skillmd.com/u/nandanosql)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/nandanosql/competitive-battle-card

---


## Purpose

Create a concise, actionable competitive battle card for sales teams and PMs. Captures **how to position against a specific competitor**, including win themes, loss themes, objection handling, and landmine questions to plant during deals.

---

## Key Concepts

### Battle Card Structure

| Section | Purpose |
|---------|---------|
| **Overview** | Who they are in 2 sentences |
| **Positioning** | How we're different (not "better") |
| **Win Themes** | Why customers choose us over them |
| **Loss Themes** | Why we lose (be honest) |
| **Objection Handling** | Top 3 objections and responses |
| **Landmine Questions** | Questions the prospect should ask the competitor |
| **When to Compete** | Deals we should fight for |
| **When to Walk** | Deals that favor them |

### Anti-Patterns

- **Not a feature matrix:** Features change monthly. Battle cards capture *positioning* strategy.
- **Not trash-talking:** If your card sounds dismissive, it will backfire when the prospect talks to both vendors.
- **Not static:** Update quarterly or after significant competitive shifts.

---

## Application

### Step 1: Competitor Overview

```markdown
# Battle Card: [Your Product] vs. [Competitor]
**Last Updated:** [Date]

## Competitor Overview
**Who they are:** [2-sentence summary]
**Target market:** [Primary segment]
**Pricing:** [Key price points]
**Market perception:** [How the market sees them]
```

### Step 2: Positioning Differentiators

```markdown
## Our Positioning Against [Competitor]

| Dimension | Us | Them |
|-----------|----|----|
| **Primary strength** | [Our strength] | [Their strength] |
| **Target user** | [Our ICP] | [Their ICP] |
| **Approach** | [Our philosophy] | [Their philosophy] |
| **Best for** | [Scenarios where we win] | [Scenarios where they win] |

**Our one-liner:** "[Concise positioning statement against this competitor]"
```

### Step 3: Win & Loss Themes

```markdown
## Why We Win
1. **[Theme]:** [Explanation + evidence]
2. **[Theme]:** [Explanation + evidence]
3. **[Theme]:** [Explanation + evidence]

## Why We Lose (Honest Assessment)
1. **[Theme]:** [What to watch for + mitigation]
2. **[Theme]:** [What to watch for + mitigation]
```

### Step 4: Objection Handling

```markdown
## Objection Handling

**"[Competitor] has [feature/advantage we lack]"**
→ Response: "[Reframe + our alternative approach + why it's better for their situation]"

**"[Competitor] is cheaper"**
→ Response: "[TCO argument / value framing / different buyer equation]"

**"My team already knows [Competitor]"**
→ Response: "[Switching cost vs. opportunity cost framing]"
```

### Step 5: Landmine Questions

```markdown
## Questions to Ask the Prospect (About the Competitor)
1. "Have you asked [Competitor] about [their known weakness]?"
2. "What happens when you need [capability they lack]?"
3. "How does [Competitor] handle [edge case we handle well]?"
```

### Step 6: Fight or Flight

```markdown
## When to Compete (Fight)
- [Scenario 1 — we have strong advantage]
- [Scenario 2 — prospect profile favors us]

## When to Walk Away
- [Scenario 1 — prospect needs what they excel at]
- [Scenario 2 — deal mechanics favor them]
```

---

## Examples

### ✅ Good Win Theme

```markdown
**Why We Win: Purpose-built for PM workflows**
Notion is a general-purpose workspace. We're purpose-built for product managers.
When prospects compare, they see that our PRD templates, roadmap views, and
prioritization tools are native — not recreated from blank pages.
Evidence: 7 of last 10 competitive wins cited "ready-to-use PM workflows" as deciding factor.
```

### ❌ Bad Win Theme

```markdown
**Why We Win: We're better**
Our product is just better than Notion for PMs. Trust us.
```

---

## Quality Rubric

| Dimension | 0 (Missing) | 1 (Partial) | 2 (Excellent) |
|-----------|-------------|-------------|----------------|
| **Balance** | Only strengths listed | Strengths + vague weaknesses | Honest win + loss themes |
| **Actionability** | General observations | Some talking points | Specific objection responses |
| **Evidence** | No data | Anecdotal | Win/loss data cited |
| **Landmines** | None | Generic | Specific to competitor's real weaknesses |
| **Recency** | Undated | Dated | Current + update cadence |

---

## Common Pitfalls

### Pitfall 1: Feature-by-Feature Comparison

**Fix:** Features change monthly. Position on *approach, philosophy, and outcomes* — those are durable.

### Pitfall 2: Ignoring Your Losses

**Fix:** If sales can't articulate *why you lose*, they can't avoid bad-fit deals. Be honest about loss themes.

---

## References

### Related Skills
- `skills/discovery/company-research/SKILL.md` — Deep-dive research feeds the battle card
- `skills/discovery/win-loss-analysis/SKILL.md` — Systematic win/loss data
- `skills/strategy/positioning-statement/SKILL.md` — Positioning framework

---

**Skill type:** Component
**Domain:** Discovery & Research