Battlecard Examples Directory

Most competitive battlecards fail for the same reason: they're a feature checklist dressed up as strategy. The best ones — the patterns you'll recognize across strong SaaS, industrial, and services teams — follow one of a small number of structural archetypes, matched to the actual shape of the competitive matchup. This directory annotates ten of them so you can borrow the structure without copying anyone's specific claims.

---

SaaS

1. Category Leader vs. Fast-Growing Challenger

(the dynamic commonly visible between an established, broad-suite incumbent and a newer, more focused entrant)

• Structure: Leads with "where the leader is vulnerable" — usually price complexity, implementation time, or feature bloat — instead of a feature-for-feature grid.
• Borrow: The "3 questions that expose the gap" technique — three pointed questions a buyer can ask any vendor that quietly favor you, rather than a comparison table.
• Avoid: Don't fight the leader on brand trust or longevity — you'll lose that argument. Fight on speed, cost, or fit instead.

2. Point Solution vs. Suite/Platform

(common where a single-purpose tool competes against an all-in-one bundle)

• Structure: Depth-vs-breadth framing — "we do one thing better than their bundled version does it."
• Borrow: A "what breaks when it's bundled" side-by-side, showing specific functionality that degrades inside a suite.
• Avoid: Don't imply the suite is bad everywhere — concede where it genuinely wins (single-vendor procurement, one invoice) and win narrowly on the specific use case.

3. Open-Source/Self-Hosted vs. Managed SaaS

• Structure: Total-cost-of-ownership framing (including internal engineering time), not sticker price.
• Borrow: A simple TCO calculator embedded directly in the battlecard — hours-to-maintain × loaded engineer cost, made visible.
• Avoid: Don't dismiss the open-source option's credibility with technical buyers — respect the audience and argue economics, not merit.

4. Low-Cost Disruptor vs. Premium Incumbent

• Structure: "Why cheap costs more later" — support quality, security/compliance gaps, hidden implementation cost.
• Borrow: One powerful, specific proof point (a real migration story) beats ten generic claims.
• Avoid: Never call the competitor "cheap" as an insult to a price-sensitive buyer — reframe as a different risk profile, not a lesser product.

---

Industrial

5. Regional Distributor vs. National Account

• Structure: Leads with responsiveness and relationship depth vs. scale claims.
• Borrow: Local service-level proof points — actual lead times, on-site support response windows.
• Avoid: Don't compete on catalog breadth against a national player — you'll lose on paper every time.

6. Legacy Manufacturer vs. Modern/Connected Entrant

• Structure: Total lifecycle cost (uptime, parts availability, service network), not just the spec sheet.
• Borrow: Reliability/uptime data as the anchor proof point, not innovation language.
• Avoid: Don't over-index on "innovative" messaging with buyers who are optimizing for risk reduction, not novelty.

7. Single-Source Supplier vs. Multi-Vendor Integrator

• Structure: Accountability framing — "one throat to choke" vs. finger-pointing risk across vendors.
• Borrow: A real incident-response comparison — who the buyer actually calls at 2am, and what happens next.
• Avoid: Don't overpromise integration simplicity you can't back with a live reference.

---

Services

8. Boutique Specialist vs. Big-4/Global Consultancy

• Structure: Senior attention and speed-to-value vs. the brand-safety appeal of the global name.
• Borrow: "Who actually does the work" — partner-led delivery vs. junior-staffed pyramids, made concrete.
• Avoid: Don't lead on price alone — clients hiring boutiques are usually buying attention, not a discount.

9. Full-Service Agency vs. Fractional/Specialist Provider

• Structure: Focus and speed ("we do the one thing you need, well, fast") vs. one-stop-shop convenience.
• Borrow: Time-to-first-deliverable as the anchor proof point.
• Avoid: Don't disparage the generalist's breadth — reframe it as lack of focus, not deficiency.

10. Incumbent Agency of Record vs. Challenger Displacement Pitch

• Structure: Leads with a specific, evidence-based gap the incumbent has left unaddressed — documented via a discovery audit, not assumed.
• Borrow: The "audit as the pitch" technique — show the gap, don't just assert it.
• Avoid: Never win a displacement purely by bad-mouthing the incumbent's relationship; win by demonstrating a real blind spot.