Verified against ChatGPT · 2026-08-12
Build a competitor battlecard reps will pull up mid-call, not skim once and forget
Produces a scannable, mid-call-usable battlecard for a specific named competitor, organized around the moments a rep actually needs it, rather than a generic feature-comparison document nobody opens twice.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Build a battlecard for Northbeam Analytics that a rep can actually pull up mid-call and use in under ten seconds — not a static feature comparison document that gets read once in onboarding and never opened again. OUR PRODUCT AND POSITIONING We're positioned on faster time-to-value — live in under a week — versus a heavier implementation. WHAT WE KNOW ABOUT Northbeam Analytics They raised prices 15% last quarter and require a 6-week onboarding with a dedicated implementation team. WHERE WE ACTUALLY LOSE TO THEM Their reporting module is genuinely more customizable than ours for enterprise finance teams. DEAL SITUATIONS WHERE THIS COMES UP MOST Usually surfaces when the prospect is a former customer of theirs, or when finance stakeholders get looped in mid-cycle. STRUCTURE THE BATTLECARD AROUND MOMENTS, NOT FEATURES Organize by the specific moment a rep encounters this competitor — 'prospect mentions them unprompted,' 'prospect is actively comparing pricing,' 'prospect says a colleague recommended them' — with a one-line response for each, not a features table down one side and theirs down the other. For each moment, give the rep something to say, not just something to know; a fact without a sentence to deliver it in still leaves the rep improvising live. Include the honest loss reasons explicitly and tell the rep how to acknowledge a real weakness rather than deny it — a rep who denies a known weakness the prospect has already researched loses credibility on everything else they say afterward. Flag anything in the competitor intel that's more than two quarters old as potentially stale, since competitor products and pricing change and a battlecard confidently repeating outdated information is worse than one admitting a gap. OUTPUT FORMAT - A 'when this comes up' section: 4-6 real moments, each with a one-sentence thing to say. - A 'where we honestly lose' section: 2-3 items, each with how to acknowledge it without conceding the whole deal. - A 'landmine questions to ask' section: 2-3 questions that surface the competitor's actual weak point through the prospect's own answer, rather than the rep stating it directly. - A staleness flag on any intel older than two quarters.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Organizing around moments instead of features directly targets why most battlecards go unused: a side-by-side feature table requires the rep to do the translation work live, mapping a static document to whatever the prospect just said, under time pressure on a call — moment-based structure does that mapping in advance, so the rep is pattern-matching a trigger phrase to a ready response instead of improvising from a reference sheet, which is a fundamentally easier cognitive task mid-call. Requiring an honest acknowledgment of real weaknesses rather than a denial or deflection reflects a specific finding in competitive sales conversations: a prospect who has already done their own research and hears a rep flatly deny a known gap discounts everything else that rep says afterward, so the battlecard's value comes from giving the rep language that concedes the specific point while redirecting to what still matters, not from pretending the weakness doesn't exist. The landmine-questions section exists because a rep stating a competitor's weakness directly reads as biased sales talk, while the same weakness surfacing through the prospect's own answer to a well-placed question is self-persuasion, which is far more durable than being told something by the person trying to win their business. The staleness flag matters mechanically because competitor intel embedded in a prompt has no way to self-verify against current reality — GPT-5.1 will confidently repeat whatever intel it's given as current fact unless explicitly instructed to flag its age, and stale pricing or feature claims stated with false confidence is a more damaging failure than an acknowledged gap in the battlecard's freshness.
What you get back
When this comes up: prospect says 'we're also looking at Northbeam' -> 'A lot of teams compare us on implementation speed specifically — we're typically live in under a week versus their six-week onboarding.' Where we honestly lose: their reporting customization is genuinely deeper for complex finance use cases -> acknowledge it, then pivot to how fast the team can start using what we do have. Landmine question: 'How long did their team say implementation would take before you'd see full reporting live?'
Verified against
ChatGPT GPT-5.1 · 2026-08-12
Changelog
- 2026-08-12 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
