Battle Card Intel: How to Win Every "How Are You Different from X?" Question

The Head-to-Head Positioning Statement

This is the 30-second answer to "How are you different from X?" It goes at the top of the card in bold. You should be able to deliver it without looking.

Formula: "[Your SaaS] is built for [specific audience with specific need], while [Competitor] is [their audience/lens]. The biggest difference: [one thing you do that they can't or don't.]"

Example: "Spyglass is built for indie SaaS founders who need actionable competitive intelligence without enterprise overhead. Crayon is built for Fortune 500 CI teams with dedicated analysts. The biggest difference: we deliver a complete competitive report in 48 hours for $29 — they require a 1-year contract starting at $1,000/month.

Your Strengths Mapped to Their Weaknesses

This is the most important section on the card. It's not a generic list of your features. It's a direct mapping of each of your top 3 strengths to a specific, documented weakness of the competitor.

Don't guess their weaknesses. Research them: check their G2/Capterra reviews (sort by 1-3 stars), read their subreddit, scan their support forums. Find real pain points their users complain about.

Format:

• They struggle with: [specific weakness sourced from reviews/support threads]
• We deliver: [your specific strength that addresses this]
• Say this: [exact quote for the sales call]

Their Strengths — and How to Reframe Them

Every competitor has strengths. Pretending they don't makes you look uninformed. Instead, acknowledge what they do well — and immediately reframe it as a weakness for your prospect's specific situation.

Pattern: "X is great at [strength], which is perfect if you [context where this strength matters]. But if you [your prospect's actual situation], that same [strength] becomes [liability]. Here's why…"

This technique is called "kill with kindness" in enterprise sales. You're not attacking the competitor. You're helping the prospect realize the competitor wasn't built for them.

Pricing Comparison With Context

Don't just list prices side by side. That's a commodity comparison and you'll lose if you're more expensive. Instead, compare total cost of ownership or value per dollar.

If you're cheaper: Show what they get and what they save. Use hard numbers.

If you're more expensive: Show what they get that the competitor doesn't offer. Frame it as "the difference between buying a tool and buying a solution."

If prices are similar: Shift the conversation to speed, support quality, or specialization. "Same price, but we're built specifically for [their use case] — they're a general-purpose tool."

Landmine Questions for the Competitor

These are questions you can suggest the prospect ask when evaluating the competitor. They're designed to surface the competitor's weaknesses without you having to point them out.

Rules for landmine questions:

• They must be fair — genuinely useful questions, not traps
• They should surface information that helps the prospect make a better decision
• Each question should point to a known weakness in the competitor's offering

Example: "Ask them what their average time-to-value is for a team your size. We've heard from mutual customers it can be 4-6 weeks — for us it's under 48 hours."

Win Story / Loss Analysis

One short paragraph about a deal you won against this competitor (or lost and learned from). Real examples are best. If you don't have one yet, use a hypothetical based on your competitive positioning research.

Format: "We recently [won/lost] a deal with [type of company] who was evaluating [Competitor]. The deciding factor was [specific reason]. Here's what we learned…"

Prospects trust stories more than feature lists. A single well-told win story is worth 10 feature comparison rows.

Wait for them to bring up the competitor

Never introduce a competitor comparison unless the prospect asks. Bringing it up unprompted signals insecurity. When they ask, you're ready — and that confidence is visible.

Validate their question before answering

Start with: "That's a great question — a lot of people compare us to [Competitor] and I understand why." This shows you're not threatened by the comparison and you've heard it before (which means you're established).

Deliver the positioning statement, then ask a question back

Give your 30-second positioning statement (section 1 of the card), then immediately ask: "Is there a specific feature or capability you're hoping [Competitor] would provide that you're not seeing in what I've shown so far?" This turns a comparison into a discovery conversation.

Use one weakness-to-strength mapping, not all three

Don't dump the whole card on them. Based on their answer, pick the ONE weakness-strength pairing that's most relevant and deploy it. Save the other two for follow-up emails. One precision strike beats a shotgun blast.

Close with a landmine question

End the competitive discussion with: "One thing I'd recommend — when you're evaluating [Competitor], ask them about [landmine topic]. We've found it's the thing their users wish they'd known before signing up." This plants a seed that outlasts the call.

Build one battle card for your top competitor

Pick the one competitor whose name comes up most on sales calls. Research their weaknesses and build a complete 6-section battle card. This will take 2-3 hours of research. Put it somewhere accessible — a pinned Notion doc, a physical printout near your desk, or a tab you keep open during calls.

Practice your positioning statement out loud

Deliver your head-to-head positioning statement to a mirror, a friend, or a voice memo app. Do it 5 times. The goal is to sound like it just occurred to you, not like you're reading from a script. Record yourself and listen back — you'll catch things that sound unnatural.

Update your CRM to track competitor mentions

Add a "Competitors Mentioned" field to your deal records in whatever CRM you use (even if it's a spreadsheet). After 10 deals, you'll know exactly which competitors you need battle cards for — and which ones rarely come up and aren't worth the research time.