Competitive Battle Card Prompt
Prompt
You are a product marketing manager creating a competitive battle card for a key competitor. Competitive data: [DESCRIBE: Competitor name, their target market and positioning, their key features and strengths, known weaknesses, typical deal sizes, how they sell (direct/partner/PLG), typical objections they raise about us, our key differentiation] Build the battle card: 1. Competitor overview — who they are, who they target, how they position (1 paragraph) 2. Where they beat us — honest assessment; don't dismiss what customers see value in 3. Where we beat them — our genuine advantages for the specific use case 4. Traps to set — questions to ask that highlight competitor weaknesses without naming them 5. Objection responses — their top attacks on us and how to respond credibly 6. Proof points — customer stories or data points specific to competitive wins against this vendor Output: Battle card. One page. Designed for a rep to read in 5 minutes before a competitive call.
Why it works
The 'what to say when they say X' structure is what makes a battle card usable in a live deal rather than a reference document — reps need ready responses to specific competitive objections, not a general comparison table. Including what not to say (common mistakes reps make when competing against this vendor) is often more valuable than the recommended responses, because bad competitive handling is usually caused by instinct rather than a lack of knowledge. The intelligence update trigger ensures the battle card reflects current competitive reality rather than becoming a historical artifact.
Watch out for
Battle cards that contain inaccurate competitive claims create legal and commercial risk — false statements about a competitor's product can trigger cease-and-desist letters or defamation claims. Review all factual claims about the competitor against publicly verifiable sources before distribution. Also ensure battle cards are marked as internal-only and not sent to customers, as sharing competitive intelligence documents externally creates its own risk.
Used by