MenuClose
Solutions
Product
Templates
Pricing
Resources
The B2B sales and proposal glossary

Every deal runs on its own vocabulary. This glossary defines the terms behind RFPs, proposals, and modern sales workflows, in plain language, for the teams who live them.

A battlecard is a short internal reference that tells a seller how to compete against a named competitor: where that competitor is strong, where they are weak, and what to say when a buyer raises them. It is written for use during a live conversation, not for reading.

Why it matters in B2B sales

Competitive questions arrive without warning and get answered badly under pressure. A rep who has not thought about a rival before the buyer names them either overstates, which the buyer can check, or goes quiet, which reads as concession. Both cost more than the comparison itself would have.

The consistency matters as much as the content. Without a shared position, five reps give five different accounts of the same competitor, and buyers who compare notes, or who move between vendors, notice. A battlecard is how a company decides once what its position is rather than leaving it to whoever is in the meeting.

What goes on a battlecard

A one-line summary of the competitor and who they typically sell to. Where they genuinely win, stated honestly, because a card that claims a rival has no strengths gets ignored by the reps who have lost to them. Where they are weak, with specifics rather than adjectives. The traps: questions a buyer can ask that expose the weakness without you making the claim yourself.

Then objection handling, the two or three things buyers say when comparing you, with a response that concedes what is true before answering. Pricing shape, since how a rival charges often matters more than what they charge. And proof: a customer who switched, a comparable win, a public source. Keep it to one page. A three-page card is a document nobody opens mid-call.

Battlecard vs competitive analysis

A competitive analysis is research: market position, funding, product depth, roadmap, written for whoever is setting strategy. A battlecard is an extract of it aimed at one moment in one conversation, and most of the analysis does not belong on it.

The failure mode is treating them as the same artifact. A battlecard built by pasting the analysis into a template is comprehensive and useless, because the rep needed three sentences and got fifteen. Write the analysis for the company and the card for the call. The same discipline applies to sales enablement material generally: usable beats complete.

A concrete example

A vendor loses three deals to the same rival in a quarter. The debriefs show the same pattern: the rival's implementation is faster, and the vendor's reps had been arguing feature depth instead. The revised card concedes the implementation point, names the deployment sizes where the gap closes, and gives reps two questions about long-term configuration cost. Win rate against that rival moves over the following two quarters, mostly because reps stopped arguing a point they were losing.

How it shows up in a modern proposal workflow

Battlecards decay faster than almost any sales asset, because competitors ship, reprice, and reposition, and nothing prompts a review. The material that would keep them current sits in win rate data and loss debriefs that never reach the person maintaining the card. Cobl keeps deal material in one workspace, so what a lost deal revealed about a competitor stays attached to the record rather than ending in a call summary nobody reads again.

A card that is eighteen months old is worse than none, because a rep will trust it in front of a buyer who knows better.

Frequently asked questions

How long should a battlecard be?

One page, and one screen is better. The card is consulted during or immediately before a call, so anything requiring scrolling or study will not be used. Depth belongs in the underlying analysis that the card points to.

How often should battlecards be updated?

Quarterly at minimum, and immediately after any significant competitor announcement or a cluster of losses to the same rival. Assign an owner, because cards without one are updated when someone is annoyed enough to do it, which is not a schedule.

Should you name competitors in customer-facing material?

Battlecards are internal, and most companies keep them that way. Public comparison pages are a separate decision with legal and brand implications, and they need a higher standard of accuracy because a competitor will read them.

Who should write battlecards?

Usually product marketing or sales enablement, built from loss debriefs, win interviews, and input from the reps who actually face the competitor. Cards written without rep input tend to describe the competitor a company wishes it had.

Respond to your next RFP with Cobl

Cobl reads the RFP and generates the full response set: go/no-go, answers, technical proposal, pricing, and slides, built on your own rules.

See Cobl in action