Battlecard

Competitors come up mid-meeting, without warning. A prospect says they're also looking at another tool, and the rest of the call turns into a comparison. Without preparation the answer is "let me check on that and get back to you," and the decision slides a week.

Inconsistency was the other half of the problem. Three reps hearing the same comparison question gave three answers: one said the other product was slow, one said it was expensive, one said they weren't sure. All three knew the product; each just reached for whatever evidence came to mind. If the buyer happened to speak with all three, the vendor looked like a company that can't agree with itself.

Writing the reasoning down somewhere internal didn't fix it either. The moment of need sits in the middle of a call, and nobody opens a twenty-page competitive analysis there. So the format came first: one competitor per page, thirty seconds to scan, sentences a rep can say out loud unchanged. The name comes from that constraint rather than from any particular content.

One card covers one competitor. Bundling several into a single document makes it slower to find the right part mid-call, which means it stops getting opened. Six items usually make up the page.

1. A one-line description of their product. Who uses it and for what, in a single sentence. A new hire hearing the name for the first time should be able to follow the conversation from this line alone.
2. What they're genuinely good at. The instinct is to lead with weaknesses, but the order runs the other way. The buyer has already seen the competitor's strengths, so an answer that refuses to acknowledge them makes everything that follows sound like advertising.
3. Where you're better, with the evidence. Not adjectives like "faster" but checkable facts: no cap on document count, a named contact through the first week of rollout. Where a messaging document already fixes the core phrases for the product, the wording comes straight from there.
4. The comparison questions that actually get asked, with answers. Write the question in the buyer's own words and put a finished sentence underneath, not a summary — a summary is useless when someone needs to speak in three seconds. This is the part that handles a competitor objection.
5. When to walk away. Spell out the situations where the other product is the right choice, such as a certification you don't hold yet. Having this line written down cuts weeks spent on deals that were never winnable.
6. The date it was last checked and the name of whoever checked it. A battlecard becomes wrong the day a competitor changes prices, so the vintage matters as much as the content.

If pricing goes on the card, convert it rather than copying their published table. What twenty seats cost per month, calculated the same way on both sides, is the only version that compares.

The writer and the reader being different people is what shapes this document. A product marketing person usually writes it and a salesperson reads it. The writer has the time to gather competitor material and internal detail and turn it into sentences; the reader is in the room where those sentences are needed and has no time to research.

So the reader reviews it. The test is whether a rep can say the line out loud in a real meeting. Something like "we deliver a differentiated user experience in the collaborative document space" never leaves anyone's mouth. "Their free tier stops at 200 documents, and a team that keeps meeting notes usually hits that in about four months" gets used verbatim.

The content flows upward too. Which questions actually come up often is knowledge that exists only in the field, which is why new entries tend to appear after a lost deal gets reviewed.

Publishing the file isn't the end of it, either. Getting a new rep to the point of saying the content in their own words belongs to sales enablement. A card nobody has read is the same as a card that doesn't exist.

"We're running into them a lot more this quarter. Can we get a battlecard together?"

Encounters with one competitor have gone up, so a dedicated response document is worth building.

"The pricing on that battlecard is from last year. They changed their plans last month."

The material has gone stale, and using it as-is costs credibility instead of building it.

"That one's answered on the second line of the card. You can read it as written."

A prepared sentence exists, so there's no need to improvise.

At Pagedeck, Ravi writes the battlecards and Sofia uses them. After hearing "their free plan gives more storage" in three meetings in a row, Sofia passed it along and Ravi added the question with an answer underneath: the free plan here caps document count rather than storage, so a team that piles up short meeting notes runs into the other product's ceiling first.

Since then Sofia doesn't stop to think when the question arrives. What the card changed wasn't only the win rate but the time it takes for an answer to show up.

Plenty of people read a battlecard as a list of a competitor's flaws. The name suggests a fight and the page does contain weaknesses, so the reading is easy to arrive at. In practice it works more like an aid for a buyer deciding between two products. That buyer has usually already trialed or demoed the competitor, so a single inaccurate knock puts everything else said afterward in doubt. That's why the line acknowledging their strengths sits near the top. A card built as a hit list embarrasses the person holding it, and it ends up unopened.

The other mistake is treating it as a write-once document. Its file format suggests there's a finished state, but half the content describes another company, so it decays whether or not anyone touches it. The day they cut prices or ship the feature you used to win on, the card is wrong. An unmaintained card is worse than none: when a rep argues from last year's pricing and the buyer corrects them, what's lost in that moment isn't the point under discussion but the buyer's trust in the rep.