battlecard-creator

name	battlecard-creator
description	Build a competitive battlecard — when to land-grab vs. when to walk away, key wedges, objection handling, landmines to set. Use on "build a battlecard against <competitor>", "how do we beat <X>", or "compete review".
allowed-tools	["Read","Write","WebSearch","AskUserQuestion"]

Battlecard Creator

A battlecard is a rep's survival kit in a competitive deal, not a marketing brochure.

Workflow

1. Name the competitor. Ask which one and ask for: (a) 3 deals you've won against them, (b) 3 you've lost, (c) what reps keep getting stuck on.
2. Research their latest public pricing, product positioning, recent announcements (web search). Do not fabricate.
3. Write the battlecard to ./battlecards/<competitor>.md.

Battlecard structure

# vs. <Competitor>  (last updated <date>)

## One-line positioning
We win when <specific scenario>. They win when <specific scenario>.

## Fight or flight (lead with this)
**Fight** when the prospect has: <3 qualifiers that favor us>.
**Flight** when: <2-3 deal-killer conditions> — redirect to partner / walk.

## Our wedge (3 max — not 10)
1. <Wedge>: <evidence/metric> · Prospect question to surface: "<q>"
2. …
3. …

## Their strengths (name them honestly)
- <Strength> — why this matters to <persona>
- <Strength>

## Landmines to set (questions a prospect should ask them)
1. "Can you show me <specific capability> without custom code?"
2. "What does <edge-case workflow> look like in your product?"
3. "Can I see a customer at my scale in production?"

## Objection handling
- **"<Competitor> has <feature> and you don't"**
  Acknowledge → reframe to what matters → evidence. Verbatim example.
- **"<Competitor> is cheaper"**
  …
- **"We're already evaluating them"**
  …

## Trap the reference
If they're going to <competitor>'s reference call, tell the champion to ask:
- "<specific uncomfortable question>"
- "<another>"

## Proof we win
- <Customer X> switched from <competitor> — outcome: <metric>
- <Customer Y> evaluated both — quote: "<verbatim>"

Guardrails

• Don't publish anything you couldn't say in front of the competitor.
• No feature-matrix checkboxes without context — always explain why a difference matters to the buyer.
• Rebuild every quarter. Stale battlecards lose deals.
• If you can't find 3 wedges you honestly believe in, the product/positioning gap is the real issue — flag it.