How to Build Competitive Battle Cards Without a Research Team

When a prospect says "we're also looking at [Competitor X]," your sales team needs a fast, reliable answer. Not a 20-minute deep-dive, not a shrug — a crisp, confident response that moves the deal forward.

That's what competitive battle cards are for. This guide walks through how to build them, what to include, and how to keep them current — without a dedicated research team.

What Is a Competitive Battle Card?

A battle card is a one-page reference document for your sales team. It covers one competitor and answers the questions a rep needs in a competitive deal: what the competitor does well, where they fall short, how to position against them, and how to handle the objections they create.

Good battle cards are concise, opinionated, and kept up to date. A battle card that's 6 months out of date is worse than no battle card — it gives your reps false confidence.

What to Include in a Battle Card

A battle card should fit on one page and be skimmable in under two minutes. Here's the structure that works:

Overview (2–3 sentences) — Who they are, what they do, who they target. This orients the rep fast. Not a Wikipedia entry — a selling context.

Pricing — Current pricing tiers, entry price, notable billing options. Keep this updated — it changes more than anything else.

Their strengths (honest) — Where are they genuinely better? Your reps will be more credible if they can acknowledge competitor strengths before pivoting. Don't spin this — be accurate.

Their weaknesses — Where do customers complain? What do they not support? What do their negative reviews say? This is where you win deals.

Your differentiators vs. them — Specific, concrete advantages you have over this competitor. Not generic "we're better" language — specific feature or experience advantages.

Common objections and responses — "They're cheaper." "They have a feature you don't." "We already use their other product." These come up every time — have the answers pre-loaded.

When to compete and when to walk away — Honest guidance on deal types where you win vs. lose. Some deals are just not winnable against certain competitors — it's better to know that upfront.

How to Build the First Version

Step 1: Start with their pricing page and homepage

These two pages tell you most of what you need to know. The homepage tells you who they think they are and who they're targeting. The pricing page tells you what the deal looks like. Read both carefully and take notes.

Step 2: Read their recent reviews on G2 or Capterra

Filter for 1–3 star reviews. Read the most recent 20. You'll see patterns fast — the same complaints surface repeatedly. These are your talking points. Also read 4–5 star reviews to understand what customers genuinely love about them.

Step 3: Mine your own lost deals

Pull the last 10 deals where you lost to this competitor. What reasons did the prospect give? What objections came up repeatedly? Your own CRM is the best research source you have — use it.

Step 4: Talk to your sales team

Ask your reps: "When this competitor comes up, what questions do you struggle to answer?" The goal of the battle card is to solve the gaps they actually have, not the gaps you imagine they have.

Step 5: Write a first draft — fast

Don't spend more than 2 hours on the first version. A rough battle card you can iterate is better than a perfect one you never finish. Share it with your reps, get feedback, and improve it over time.

Keeping Battle Cards Current

This is where most battle card programs fail. The initial version gets built, filed somewhere, and never updated. Six months later, the pricing is wrong and the competitor has launched the feature that was your main differentiator.

Two things make battle cards stay current:

A trigger-based update process — Update the battle card whenever you detect a significant competitor change — new pricing, new features, new messaging. Don't wait for a quarterly review cycle.

Automated change detection — If you're manually checking competitor pages for updates, it will fall off your to-do list. Automated monitoring tools notify you when something changes, so you can update the card immediately.

Common Battle Card Mistakes

Making it too long

If it's longer than one page, reps won't use it in a real deal. Ruthlessly cut. Every section should earn its place.

Being dishonest about competitor strengths

If your reps say "they're not actually good at anything," buyers see through it immediately. Acknowledge real strengths — it makes your weaknesses section more credible.

Building it once and forgetting it

Set a recurring reminder to review each battle card quarterly at minimum. Update immediately when you detect a major change.

Not including objection responses

The objection handling section is the most-used part of the battle card. If it's not there, you haven't built a battle card — you've built a fact sheet.

Storing it somewhere nobody looks

Battle cards only work if reps access them. Put them where your sales team lives — Notion, your CRM, a shared Google Drive folder they already use.

Automating the Intelligence Gathering

The hardest part of maintaining battle cards isn't writing — it's detecting when information changes. Pricing updates, messaging shifts, new feature announcements — these happen without warning.

OSA Radar monitors your competitors' key pages automatically and delivers a weekly summary of changes. When something shifts, you get notified — so you can update your battle cards before your reps walk into a deal with outdated information.

Know when your competitors change — automatically.

Free during beta. Paid plans from $99/month.

Start monitoring competitors →

Summary

Build one battle card per major competitor. Keep it to one page. Include pricing, honest strengths and weaknesses, your specific differentiators, and objection responses. Build the first version fast using their pricing page, homepage, and review site data. Update it whenever something significant changes. Store it where your reps actually work.