Competitive Battlecard

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

Published by @Paweł Huryn·0 agent reads / 30d·0 saves·

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

    CapabilityUsThemWinner
    [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 SaysRespond 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?

Bundled with this artifact

2 files

Reference files that ship alongside this artifact. Agents pull these in only when the task needs them.

More on the bench

SKILL0

Pptx

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

product-management+1
0
SKILL0

Knowledge Management

Write and maintain knowledge base articles from resolved support issues. Use when a ticket has been resolved and the solution should be documented, when updating existing KB articles, or when creating how-to guides, troubleshooting docs, or FAQ entries.

customer-success+2
0
SKILL0

Customer Research

Research customer questions by searching across documentation, knowledge bases, and connected sources, then synthesize a confidence-scored answer. Use when a customer asks a question you need to investigate, when building background on a customer situation, or when you need account context.

customer-success+1
0