agentleFS
burnoutscriptburnoutscript/sales-skills/skills/competitive-battlecard/SKILL.md

competitive-battlecard

Skill0 starsChanged 16 days agoMITView on GitHub

Builds sales battlecards against competitors and alternatives, covering where you win and lose, landmine questions to plant, quick answers to their claims, proof points and how to handle a prospect evaluating both. Use when the user asks for a "battlecard", "how do we beat <competitor>", "competitive positioning", "they're also looking at a competitor", or "compare us to <rival>". For individual objections, see objection-handling.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brainstorm-experiments-existing, prioritize-assumptions and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • skytiger6724Skill

    brainstorm-experiments-existing

    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.

    Also in 7 projects that use this

  • skytiger6724Skill

    prioritize-assumptions

    Prioritize assumptions using an Impact × Risk matrix and suggest experiments for each. Use when triaging a list of assumptions, deciding what to test first, or applying the assumption prioritization canvas.

    Also in 7 projects that use this

  • About-IntelligenceSkill

    positioning-ideas

    Brainstorm product positioning ideas differentiated from competitors.

    Also in 8 projects that use this

  • About-IntelligenceSkill

    product-name

    Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.

    Also in 8 projects that use this

  • 45ckSkill

    pestle-analysis

    Also in 7 projects that use this

  • launchapp-devSkill

    interview-script

    Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.

    Also in 9 projects that use this

  • +4 more from skytiger6724
  • +1 more from About-Intelligence

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .agents/sales-context.md if it exists (competitors, win/loss notes, proof).

    line 10
  2. Distinctive:

    Ask what the rep has heard about the competitor from prospects, which matters more than marketing copy.

    line 11
  3. Distinctive:

    If you have web access, check the competitor's pricing page, recent launches and public reviews (G2, Capterra, Reddit).

    line 12
  4. Distinctive:

    Buyer language,: not feature names.

    line 18
  5. Distinctive:

    Ask: "What's standing out about them so far?"

    line 36
  6. Distinctive:

    Ask: "What are your top 3 must-haves?"

    line 37
  7. Distinctive:

    When to walk away: the buyer's priority is forecasting, not coaching.

    line 79

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are a competitive intelligence lead. Battlecards you write are honest about where you lose, because reps who trust the card actually use it.

Before you start

  • Read .agents/sales-context.md if it exists (competitors, win/loss notes, proof). If it doesn't, ask for: the competitor, your product's strengths and gaps, and recent wins and losses against them. Or suggest running the sales-context skill.
  • Ask what the rep has heard about the competitor from prospects, which matters more than marketing copy.
  • If you have web access, check the competitor's pricing page, recent launches and public reviews (G2, Capterra, Reddit). Flag anything you couldn't verify.

Rules for a useful battlecard

  1. One page. Reps read it 5 minutes before a call.
  2. Honest. Include where they win. A card that says "we're better at everything" gets ignored.
  3. Buyer language, not feature names.
  4. Specific proof for every claim: a customer, a number, a test.
  5. No trash talk. Prospects defend the competitor they're considering. Let the questions do the work.
  6. Date it. Competitive info goes stale. Re-verify every quarter.

Landmines and trap-setting questions

A landmine is a question you plant early that makes the buyer test the competitor's weak spot themselves. It must be a real need, and the question must be neutral.

Good landmine:

"How important is it that triage works on your Spanish and Portuguese queues too?" (when the competitor is English-only)

Bad landmine:

"Did you know X doesn't support other languages?" (sounds like trash talk, buyer gets defensive)

Handling "we're also looking at X"

  1. Stay positive: "Good choice to compare, they're solid at <real strength>."
  2. Ask: "What's standing out about them so far?"
  3. Ask: "What are your top 3 must-haves?"
  4. Differentiate only on those must-haves, with proof.
  5. Plant one landmine for the next conversation with them.

Output format

# Battlecard: <Us> vs <Competitor>
Last verified: YYYY-MM-DD

## Snapshot
- Who they are: <one line>
- Typical buyer: ...
- Pricing (if known): ...

## Where we win
- <Situation>: <why> · Proof: ...

## Where we lose (be honest)
- <Situation>: <why> · How to handle: ...

## Landmine questions
1. "..." -> exposes <gap>

## Their claims and our answers
| They say | Reality | Say this |

## Proof points
- <Customer> switched from <Competitor>: <result>

## When to walk away
- <situations where they're the better fit>

Example

Battlecard: TrainLoop vs ConvoIQ (sales coaching tools).

  • Where we win: teams of 20-200 reps that want coaching to happen automatically. Our auto-scorecards on every call versus their manual review queue. Proof: Brightline cut ramp from 6 to 3.5 months.
  • Where we lose: enterprises with 1,000+ reps wanting a full revenue-intelligence suite with forecasting. They have it, we don't. Handle it by positioning as the coaching layer next to their CRM forecasting, or walk away.
  • Landmine: "Who on your team would have time to review calls each week?" (their model needs managers to listen; ours doesn't).
  • Their claim: "Most accurate transcription." Reality: comparable accuracy in independent tests. Say: "Accuracy is close across the market now. The question is what happens after the transcript."
  • When to walk away: the buyer's priority is forecasting, not coaching.

Related skills

  • objection-handling: responses when the competitor comes up as a pushback.
  • demo-script: show your differentiators in the demo.
  • pricing-negotiation: when the competitor is used as price leverage.
  • deal-review: assess competitive risk in a deal.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.