How to Use Battle Cards on a Sales Call

You're 18 minutes into a demo. Everything's going well. The prospect is nodding. And then they ask it:

"We're also looking at CompetitorX. How are you different?"

This is the moment that separates founders who close deals from founders who lose to a Google search. The difference? The founder with a battle card wins.

We covered the why of battle cards back in Issue #5. Today we're covering the how — a practical, step-by-step guide to using battle cards on a live sales call. No theory. Just tactics you can use tomorrow.

📋 Before the Call: The 3-Card Rule

Never walk into a sales call without battle cards for your top 3 competitors. Not 10. Not "all of them." Three. Here's why:

1. Competitor #1: The direct rival — the one your prospects mention most. Same ICP, same price range, same category. This is the card you'll use 80% of the time.
2. Competitor #2: The incumbent/budget alternative — the "we could just use Excel/Notion/Google Sheets" or the free tier competitor. Your card should emphasize total cost of ownership and switching cost, not just feature parity.
3. Competitor #3: The wildcard — the adjacent tool that occasionally steals your deals. The "we're considering building this internally" or the enterprise platform that's "good enough."

Generate these three cards here in 10 seconds. Print them, put them in your Notion sales doc, or keep them open in a second tab. You want them accessible in under 2 seconds during the call.

🎯 During the Call: The AAD Framework

When the prospect mentions a competitor, don't panic. Don't trash them. Don't ignore the question. Use this 3-step framework:

Step 1: Acknowledge (10 seconds)

Validate their research. They've done homework. Respect it.

"Great question — CompetitorX is a solid product. A lot of our customers evaluated them before choosing us."

This does three things: it shows confidence, it prevents the prospect from defending their choice to evaluate CompetitorX, and it frames you as the informed option — not the desperate one.

Step 2: Anchor (15 seconds)

Name the dimension where your product is strongest and frame the comparison around it. This is where your battle card earns its keep — you're not guessing, you're citing actual data.

"The key difference is how we handle [your strength]. CompetitorX does [their approach], which works for [their use case]. Our customers typically switch because they need [your unique value]."

Notice the structure: name their approach → acknowledge it works for someone → pivot to what your customers actually need. You're not saying they're bad. You're saying they serve a different customer.

Step 3: Differentiate (30 seconds)

Use specific, verifiable data points from your battle card. Not opinions. Facts.

The golden rule: Never say something you can't back up. If you don't have the data, don't make the claim. That's what battle cards are for — they give you verified facts you can state with confidence.

📤 After the Call: The 30-Minute Follow-Up

Send the battle card within 30 minutes of the call ending. Here's the exact email template:

Hi [Name],

Great conversation earlier. You mentioned you're also evaluating CompetitorX — I put together a quick comparison to help with your decision:

[Link to battle card]

A few things I'd highlight:
• [Your #1 differentiator]
• [Your #2 differentiator]

Happy to walk through any of this in more detail. What's the best way to get a decision by [date]?

Best,
[Your name]

Why this works: (1) It's fast — you're not overthinking it. (2) The battle card link shows professionalism — they can share it internally. (3) Asking for a decision timeline keeps momentum. (4) You've now inserted a Spyglass-branded asset into their company's Slack/email chain. Every internal stakeholder who opens it sees your comparison.

👥 Different Stakeholders Need Different Cards

One battle card does not fit all. The CTO cares about architecture, the CEO cares about ROI, and the end user cares about workflow. Generate a card for each — then use the right one with the right person.

Generate a battle card for each stakeholder profile at spyglassci.com/battle. It takes 10 seconds per pair. Do it once per quarter when competitor data refreshes.

🧪 The "Landmine" Question

Every sales call should end with one question designed to surface competitive risk you can't see:

"Before we wrap up — is there any other tool or approach you're considering that we haven't discussed? Even something like building internally or using a spreadsheet?"

This surfaces the wildcard competitors you didn't prep a card for. If they name one, say "That's a great option for [their use case] — let me send you a quick comparison with us after this call." Then generate the card and send it.

📈 By the Numbers

• 76 detailed comparison pages (SEO-optimized, all cross-linked)
• 133 tools in the competitive intelligence database
• 15 SaaS categories covered
• 13 free competitive intelligence tools (no signup)
• 14 newsletter issues (you're reading #14!)
• 83 blog posts on competitive strategy
• 1 new SaaS Stack Advisor — personalized tool recommendations in 3 clicks

🛠️ What We're Building Next

• Referral program ("Give $10, Get $10") once we hit 5 paying customers
• More SaaS categories and comparison pages
• Public API improvements for the battle card endpoint
• Product Hunt relaunch (v2) after community validation
• Community outreach this Sunday (May 17) — HN Show HN, Reddit, IndieHackers

💭 One Thing Before You Go

We built Spyglass because we watched indie SaaS founders lose deals to competitors they didn't understand. Not because their product was worse — but because they couldn't articulate why it was better. Battle cards fix that. They turn competitive anxiety into competitive confidence.

We're a bootstrapped, solo-built startup with a $100 budget. No VC. No team. Just code, data, and the belief that every indie founder deserves the same competitive intelligence as a funded company.

Next week: the referral program launches. Until then — go close some deals.

— The Spyglass Team

Know Your Competitive Edge · All Issues · Reply