Battlecard-to-Demo Integration Cheat Sheet
A one-glance method and language library for weaving competitive battlecard points into a live demo without ever naming, mocking, or badmouthing the competitor.
What's inside
- The 3-step method: Confirm, Show, Let Them Conclude
- Do/Don't language table with 5 direct swaps
- 4 ready-to-use language patterns for direct competitor call-outs
- A landmine list of phrases to never use
- Quick-reference table by competitor archetype: incumbent, cheaper alternative, point solution, internal build
The goal is never to win an argument about the competitor. It's to let the prospect reach their own conclusion by watching something, not by being told something. Every pattern below is built around that rule.
The 3-Step Method
1. Confirm, don't assume. Before referencing anything competitive, confirm what they're actually evaluating and why: "You mentioned you're also looking at [Competitor] — what's the main thing you're weighing between the two?" Never demo against a competitor you're guessing about.
2. Show, don't tell. Instead of saying "we're better at X," demo the specific workflow live and let the gap be visible. If the differentiator is speed, show the speed. If it's depth, show the depth. Don't narrate superiority — display it.
3. Let them conclude. After showing it, ask a question instead of delivering a verdict: "How does that compare to what you've seen so far?" Their own answer does more for you than any claim you could make.
Do / Don't Language Table
| Don't say | Say instead |
|---|---|
| "[Competitor] is actually pretty weak at this." | "This is one of the areas we get asked to compare a lot — worth showing you how it works here." |
| "A lot of our customers switched from [Competitor] because it's clunky." | "Some teams evaluating us have used [Competitor] before — the difference usually comes down to [specific, demoable thing]." |
| "Honestly, I wouldn't recommend [Competitor] for a team your size." | "For teams your size, the main thing to weigh is [specific criterion] — let me show you how we handle that." |
| "[Competitor] doesn't even have this feature." | "This is one we built specifically because teams told us it was missing elsewhere — here's how it works." |
| Silence / visibly uncomfortable when competitor is named | "Glad you mentioned that — happy to show you exactly how we approach it." |
Ready-to-Use Language Patterns
When they name a competitor unprompted:
"Good to know you're looking at [Competitor] — that helps me focus. What's the one thing you most want to see us handle well, given that comparison?"
When you need to demo a genuine differentiator:
"This next part is one of the areas teams evaluating multiple options tend to spend the most time comparing — let me just show you rather than describe it."
When asked directly, "how are you different from [Competitor]?":
"The honest answer is it depends on what you're optimizing for. For [their stated priority], the difference tends to show up here —" (demo it) "— for other priorities, it might be a closer call. What matters most to you?"
When a competitor's weakness is genuinely relevant to their stated criteria:
"You mentioned [criterion] matters a lot to you. That's actually one of the more common comparison points — want me to show you how this specific piece works?"
Landmine List — Never Say These
- Anything about a competitor's pricing you haven't independently confirmed is current
- Any claim about a competitor's customers, funding, or company stability
- Jokes or sarcasm about a competitor's brand, name, or founders
- "Everyone knows [Competitor] is struggling" or any unverifiable industry gossip
- Comparisons that require the prospect to already dislike the competitor to land — if it needs pre-existing bias to work, it's badmouthing, not differentiation
Quick Reference by Competitor Archetype
| Archetype | What they're usually weighing | How to demo the contrast |
|---|---|---|
| The Incumbent (they already use a legacy tool) | Switching cost / risk vs. staying put | Show migration/onboarding speed live; address the "why now" directly — incumbents lose to inertia, not features |
| The Cheaper Alternative | Price vs. total cost of ownership | Show the workflow that would require manual work or a workaround on the cheaper tool; let the labor cost speak, don't just say "you get what you pay for" |
| The Point Solution | Best-of-breed vs. integrated platform | Demo the handoff/integration point where a point solution creates a gap; show data flowing through, not just existing |
| The Internal Build | Control/customization vs. maintenance burden | Ask who maintains the internal build today and what happens when that person leaves; then show what ships out-of-the-box vs. what they'd have to build and support themselves |
How to use it
Keep this open in a second tab during live demos; when a competitor comes up, run the 3-step method (Confirm, Show, Let Them Conclude) and pull the matching language pattern or archetype row instead of improvising a comparison in the moment.