A competitive battlecard that actually helps reps can be built in about twenty minutes with AI: gather public raw material, run it through a structured extraction, and edit the output against what you have heard in real deals. The two chronic battlecard problems — never built, or built once and instantly stale — both disappear when the build cost drops this low.
What a good battlecard actually contains
Most battlecards list features. The useful ones script behavior: what to say when the competitor comes up, what to ask that exposes their weakness, what to avoid claiming because it will not survive contact. A working structure has six blocks — how they position against you, where they genuinely win, where you genuinely win, landmine questions to plant early, objection responses in conversational language, and pricing/packaging intelligence with its source and date. If a block cannot change what a rep says on a live call, it does not belong on the card.
Minutes 1–8: gather the raw material
Collect what is public and what is tribal. Public: the competitor's homepage and pricing page copy, two or three recent review-site entries (the negative reviews are the gold — they are your differentiation, written by their customers), any comparison content they publish. Tribal: your own team's notes from deals where this competitor appeared, especially losses. Paste quality beats search breadth here; five specific inputs outperform twenty generic ones.
Minutes 8–15: run the structured extraction
Prompt: "You are a competitive intelligence analyst for [YOUR COMPANY], which sells [YOUR SOLUTION]. Build a battlecard for [COMPETITOR] from this material: [PASTE EVERYTHING]. Return six sections: (1) their likely pitch against us in their own framing, (2) two areas they genuinely win with honest reasoning, (3) three areas we win with the evidence, (4) four landmine questions a rep can ask early that expose their weaknesses without naming them, (5) conversational responses to the two objections they most likely plant about us, (6) pricing and packaging intelligence with confidence level per claim."
The honesty instructions in sections two and three are load-bearing. A battlecard that claims you win everywhere gets ignored by reps after its first contact with a real deal — credibility on where you lose is what makes the rest of the card trusted.
Minutes 15–20: edit against deal reality
The model's draft knows the public record; you know the last six deals. Correct anything that contradicts live experience, add the objection you actually heard last month, and cut any landmine question your buyers would find transparent. Date-stamp the card and note the confidence level on pricing claims — competitor pricing changes quietly, and an undated card teaches reps stale numbers with full confidence.
The 5-minute quarterly refresh
Staleness, not absence, is how battlecards die. Calendar a quarterly pass per major competitor: re-pull their pricing page and latest reviews, paste alongside the current card, and ask for a diff.
Prompt: "Compare this existing battlecard: [PASTE CARD] against this fresh material: [PASTE NEW COPY AND REVIEWS]. List what changed — positioning, pricing, packaging, new weaknesses in recent reviews — and rewrite only the sections that need updating, marking each change."
Five minutes per competitor per quarter keeps the whole set live. A team covering five competitors spends twenty-five minutes a quarter on intelligence most teams never maintain at all.
Closing the loop with deal outcomes
The card gets sharper if wins and losses feed back into it. After every competitive deal closes either way, add two lines to the card's material: what the competitor actually said, and what worked or failed in response. Next quarter's refresh then runs against real engagement data, not just public copy — and within three cycles the card stops being research and starts being institutional memory. This is the difference between a document and an asset: assets appreciate.
Distribution beats perfection
A battlecard in a folder is a battlecard nobody uses. Put the card where deals happen — pinned in the team channel, linked from the CRM's competitor field — and attach a one-line trigger: when this competitor appears in a deal, open the card before the next call. The build is twenty minutes; the value is entirely in the moment of use.
Frequently Asked Questions
What if I don't have any internal deal notes about a competitor?
Build from public material alone — reviews carry most of the signal — and mark the card as unvalidated. Then update it after the next two live encounters; the second draft is always sharper.
Should reps see where the competitor genuinely wins?
Yes. Reps trust and use cards that match what they hear in deals, and a buyer's objection about a real competitor strength is only handleable if the card prepared the rep for it honestly.
How many competitors deserve a full battlecard?
The three to five that appear in real deals. Coverage of hypothetical competitors costs maintenance without changing any live conversation — add a card the first time a new name shows up twice.
Put It to Work
The battlecard build and refresh prompts here sit in the competitive strategy collection of the Promptifi library. Browse the library and build your first card before your next competitive deal.