salescompetitive intelligence

Competitive Sales Battlecard

Builds a one-page competitive battlecard with positioning, win/loss themes, objection handlers, and trap-setting questions.

Prompt
You are a competitive intelligence analyst. Create a one-page sales battlecard for [your product] vs [competitor product]. Structure: (1) At a Glance: a side-by-side comparison table with 8-10 key criteria (features, pricing, deployment, support, integrations, security, scalability, ease of use), using checkmarks and X marks, (2) Our Strengths (Why We Win): 3 differentiators with a supporting proof point for each (customer quote, benchmark, or analyst recognition), (3) Their Weaknesses (Where They Fall Short): 3 specific weaknesses with evidence (G2 reviews, known limitations, customer complaints), (4) Trap-Setting Questions: 5 questions for the rep to ask the prospect that expose the competitor's weaknesses naturally (e.g. 'How important is [thing competitor can't do] to your workflow?'), (5) When We Lose: 2-3 scenarios where the competitor wins and how to mitigate, (6) Objection Handlers: responses to 'Why should I pick you over [competitor]?' and '[Competitor] is cheaper', (7) Customer Win Story: 50-word story of a customer who switched from the competitor with the result achieved. Keep everything scannable. A rep should find any answer within 10 seconds.

Why this prompt works

The context score is 30 because battlecards are by design context-light: a rep needs to find any answer in 10 seconds, which means dense layouts and tight wording, not contextual prose. What the prompt produces well is the structure (at-a-glance comparison, our strengths with proof points, their weaknesses with evidence, trap-setting questions, when-we-lose scenarios, objection handlers, customer win story), each sized for scanability. The trap-setting questions section is the most underrated; they convert competitive disadvantages into prospect realisations rather than rep claims. The 50-word win story is short on purpose; reps don't read longer stories during calls.

When to reach for it

  • You're rolling out a new sales motion against a specific competitor and need a single-page reference card the team can use immediately.
  • You're updating an existing battlecard after a competitor's product launch or pricing change.
  • You're a competitive intelligence analyst building a battlecard library across your top three competitors.
  • You're a new AE inheriting a deal where the prospect mentioned a specific competitor and you need to ramp on positioning fast.

How to customise it

Pick a real competitor your team actually loses to, not a competitor you'd like to compare favourably against. Battlecards built against soft targets are useless. The criteria in the comparison table should reflect what your prospects actually evaluate; ask sales which 5 to 8 criteria come up most often in calls. The trap-setting questions are the section most worth iterating on with real reps after the first version; ask 'which of these questions has actually surfaced their weakness in a call?' and prioritise those.

What good output looks like

A scannable one-pager with seven sections: comparison table with checkmarks/X-marks, three differentiators with proof points, three competitor weaknesses with evidence, five trap-setting questions, two or three loss scenarios with mitigation, two objection handlers, and a 50-word customer win story. The whole thing fits on a single printed page or one Notion card. Total length 600 to 1,000 words.

Watch out for

The model can make confident claims about a competitor's weaknesses that turn out to be outdated or exaggerated. Verify each weakness against current G2 reviews, recent product changes, or prospect-call notes before publishing. The customer win story tends to be generic; replace it with a real, named-and-attributed story (with the customer's permission) to make it credible. Battlecards should be reviewed quarterly; the competitive landscape moves faster than most teams update their cards.

battlecardcompetitive intelligencesales enablementwin/lossChatGPT / Claude

Build a prompt like this for your task

Use the free guided prompt builder on the homepage: pick what you need, answer three quick questions, and get a high-scoring prompt of your own.

Open the prompt builder →
87
out of 100
Role definition100
Task clarity100
Specificity100
Context30
Output format100
Constraints70
Examples100