Battle cards written for commercial competitors fall apart against an open source project. The buyer isn't comparing two vendors — they're comparing your contract to a free download their staff engineer already cloned last weekend. "Open source" here means the competitor offers a self-hostable, source-available version of the product at zero license cost; the threat isn't the project itself but the perception that paying you is optional.
The four objections that don't appear in your normal card:
Fill it for one project at a time
Don't build a generic open-source card. Build one per project — the engineering culture around Postgres is not the engineering culture around Elasticsearch. Use the worksheet below.
Open Source Battle Card
Eight fields. Fill it for one OSS competitor at a time. State persists in your browser.
Before you ship the card
QA before it goes to sales
Hand it to one AE. Run three calls. Rewrite the field that broke.
Keep reading
Battle Card Template for Startup vs. Incumbent
A six-field battle card built for the startup-versus-incumbent fight, with the moves that actually work when the buyer already trusts the bigger logo
Battle Card Template for Low-Price Competitors
A fillable battle card for selling against cheaper competitors without racing to the bottom or pretending price doesn't matter to the buyer
Battle Card Template for High-Price Competitors
A fillable battle card template for selling against pricier competitors, built around value justification rather than discount-first reflexes
Battle Cards
Give your reps the exact rebuttal for every competitor — updated automatically.
Battle Cards generates per-competitor rebuttal kits grounded in your own positioning — not generic 'we're better because' copy. When Competitor Signals detects a material move, the relevant card updates automatically.
- ✓Per-competitor cards built from your own positioning
- ✓Auto-updates when competitors change their story
- ✓Built for live deals, not slide decks that rot in Drive