Battlecards: The Template We'd Use Selling Against Ourselves

The fastest way to write a battlecard that a rep will actually use is to stop writing it about your competitor and start writing it as if you were the competitor selling against you. Most battlecards fail because they’re a list of reasons your product is great. A rep on a live call doesn’t need a list of reasons your product is great. They need to know what the other side is about to say, and exactly what to do when it gets said.

So here’s the template we’d build if we were the ones trying to beat Outmano. Same structure works for any B2B SaaS. Steal it, fill it in, ship it to your reps by Friday.

What battlecards are for (and the one rule)

A battlecard is a single-page, glanceable answer to one question: when a deal turns into us-versus-them, what do we say and do in the next 90 seconds? That’s the whole job. Not a competitive teardown, not a feature matrix, not a positioning doc. Those are different artifacts. Sales battlecards are operational: they get opened mid-call, on the second monitor, while the prospect is talking.

The one rule that keeps a battlecard alive: every line has to be something a rep can say out loud or do immediately. If a line can’t survive being read off the screen during a call, it’s research, not a battlecard. Move it somewhere else.

This is also why most competitive battlecards rot. They get built once by product marketing, they’re 2,000 words long, and the first time a rep opens one mid-deal and can’t find the rebuttal in four seconds, they never open it again. Length is the enemy. One screen, or it doesn’t exist.

The battlecard template

Here’s the structure. Eight sections, each with the prompts you fill in. Keep the whole thing to one page per competitor.

1. Snapshot (2-3 lines)

The orientation line a rep reads before dialing.

• Who they are in one sentence: e.g. “Enterprise CI platform, sells to PMM teams at $50M+ ARR companies.”
• Where we win by default: e.g. “Small teams, no analyst, want signal not dashboards.”
• Where they win by default: e.g. “Large PMM org that needs CRM integration and battlecard workflows.”

If you can’t name where they legitimately win, you don’t understand the competitor well enough to sell against them yet.

2. Their pitch, in their words

Write the competitor’s pitch the way their best rep would deliver it. Not a strawman. The strongest, most honest version.

• Their headline claim: what they lead the demo with.
• Their proof points: the two or three things that genuinely land.
• Who they make look good: the buyer persona that should buy them, not you.

You write this section by reading their site, their pricing page, and their G2 reviews, then writing the pitch you’d be scared to hear. If it doesn’t make you a little nervous, rewrite it.

3. Why we lose to them (be honest)

The section that earns the rest of the card. Reps trust a battlecard that admits the truth.

• Deals we shouldn’t fight for: segments where they’re the right call.
• Real gaps we have: the feature or proof we don’t have yet.
• The trap question they ask that makes us look weak: write it down verbatim.

4. Why we win (proof, not adjectives)

• Our wedge: the one thing we do that they structurally can’t, or won’t.
• Proof a skeptic believes: a metric, a customer quote, a teardown, a screenshot, not “we’re easier to use.”
• The reframe: how we change the buying criteria so the deal is judged on our terms.

5. Objection handling (the part reps reread)

Two columns. What they say. What we say. Three to five rows, no more.

They say	We say
“[Competitor] has [feature] and you don’t.”	Acknowledge, then reframe to whether they need it at their size.
“You’re more expensive per seat.”	Shift to total cost including the analyst headcount their tool requires.
“We’ve never heard of you.”	Lead with the specific proof point and a relevant logo, then move on fast.

6. Landmines to plant (use sparingly)

Questions a rep can raise that surface the competitor’s real weaknesses without trash-talking. One or two, used with judgment.

• “Ask them how long onboarding takes and who runs the tool day-to-day.”
• “Ask what happens to your data and dashboards if you drop a competitor from the tracked list.”

A landmine is a question, never an attack. The moment a rep editorializes, it reads as fear.

7. Pricing posture

• Their list price (and what it really costs all-in): seats, implementation, the analyst it implies.
• How we frame our price against it: the unit we want them comparing on.
• Discount discipline: what we will and won’t match.

8. Proof links

Three links, max. The teardown, the customer story, the one-pager. If a rep needs more than three, the card is doing too much.

Selling against ourselves: a worked example

To prove the template isn’t theory, here’s the snapshot and “why we lose” sections filled in for Outmano, written by the version of me trying to beat us.

Snapshot. Outmano is an AI-powered competitive intelligence platform for small B2B SaaS teams with no dedicated analyst: pricing, SEO, content, roadmap, and review monitoring with the analysis written for you, delivered through a dashboard, alerts, and a weekly digest. Wins by default when the buyer wants distilled signal without operating a tool. Loses by default when the buyer is an enterprise PMM team that needs CRM-integrated battlecard workflows and a queryable intel library.

Why we lose to us. If I’m Crayon or Klue, I attack on depth and surface area: “Outmano sends you an email; we give your whole revenue org a system of record, battlecard automation, and Salesforce integration.” That’s a fair hit. The honest rebuttal isn’t to pretend we match it. It’s to reframe the buyer: if you have a PMM whose full-time job is operating that system, buy it. If you don’t, you’ll use 8% of it and resent the invoice. The battlecard line a rep says out loud: “Do you have someone who’ll own a platform full-time? If not, the depth is a cost, not a feature.”

That reframe only works because the “why we lose” section was written honestly first. A battlecard that pretends you have no weaknesses teaches your reps to get ambushed.

How to keep the card from rotting

A battlecard is a living doc or it’s a dead one. Three habits keep it alive:

• Own it per competitor, not per team. One person is accountable for each card. Diffused ownership means nobody updates anything.
• Update on signal, not on schedule. When the competitor changes pricing, ships a tier, or rewrites their homepage hero, the card changes that week. This is exactly where competitor monitoring feeds the GTM motion: the signal that moves the card is the same signal worth watching. Our lightweight competitive intelligence operating system covers the cadence for catching those changes weekly instead of quarterly.
• Feed it from real deals. The best objection-handling rows come from win/loss analysis, not from a brainstorm. After every competitive loss, ask what they said that you didn’t have an answer for, and add the row.

The one move worth making this week

Pick your single most-encountered competitor. Open a blank page and fill in only two sections from the template above: “Why we lose to them” and the objection-handling table with three rows. Skip everything else for now.

Then send it to your two best reps and ask one question: “Is this what actually happens on calls?” Their edits are your real battlecard. Build the rest of the page around what survives that conversation.

---

Outmano watches the signals that force a battlecard update (competitor pricing changes, new tiers, repositioned messaging, roadmap and review shifts) with AI analysis on every change, delivered via dashboard, alerts, or weekly digest, so your cards stay current without a dedicated analyst. See how it works →

Frequently Asked Questions

What’s the difference between battlecards and a competitive analysis?

A competitive analysis is a research document (market shape, feature depth, strategy) read once by leadership. Battlecards are a call-time tool: one page per competitor, opened mid-conversation, telling the rep what’s about to be said and what to say back. The most common failure is publishing an analysis and calling it a battlecard; reps open it once, can’t find the rebuttal in four seconds, and never come back.

Who should own battlecards: product marketing or sales?

Product marketing (or a founder, pre-PMM) should own the writing, because it requires reading competitor sites, reviews, and win/loss data that reps don’t have time for. Sales owns the truth test: if reps say a line doesn’t match what happens on calls, the line changes that week. The wrong owner is a committee: cards with shared ownership get updated by nobody.

How do I get reps to actually use battlecards?

Make the card faster than winging it. Put it one click away in the tool where calls happen, keep it to one screen, and lead with the objection table, because that’s the part reps reread under pressure. Then close the loop publicly: when a rep wins a deal with a line from the card, share the story. Adoption follows evidence, not mandates.

What tool should I build battlecards in?

Whatever your reps already have open. Notion, Google Docs, or a pinned Slack canvas all work fine below roughly 15 reps. Dedicated battlecard platforms like Klue or Crayon earn their price when you need usage analytics, CRM embedding, and dozens of cards kept current across a large team. Buying the platform before the habit exists just gets you expensive stale cards.

Are battlecards worth it before you have a sales team?

Yes, in a stripped-down form, because founder-led sales hits the same objections with worse notes. Keep a single page covering the two or three competitors prospects actually name, the honest “why we lose” list, and the rebuttals that worked on real calls. That page becomes the training doc for your first sales hire. Skip the full eight-section version until there’s someone to hand it to.