Battlecard Examples: Three That Work and Why Most Get Ignored

The short answer: a battlecard works when it is built around the situation a rep is in, not the features you ship. Three sections do the heavy lifting — where you genuinely win, where you genuinely lose, and a named proof point under every win claim. The feature grid that most battlecards lead with is the part nobody uses.

Why most battlecards go unopened

Two failures, both structural.

They are written as feature comparison tables. A grid of checkmarks has never persuaded a buyer and cannot be spoken aloud on a call. A rep needs a sentence they can say, not a matrix they would have to interpret in real time.

They are organised by product area. That is how marketing thinks about the product. It is not how a rep experiences a deal. Mid-call, a rep is in a situation: a competitor was just named, the budget got challenged, a security review appeared. They need the answer in seconds, and browsing by feature does not get them there.

There is a third failure that is really a symptom. Reps do not trust cards with no losses in them, because they have personally lost those deals. A card that claims you win everywhere tells the rep it was written by somebody who has not been on these calls, and they stop opening it.

The five sections that earn their place

1. The competitor, honestly, in one sentence. If your description is a caricature, your rep loses credibility the moment they meet a buyer who knows the product well. Describe what the competitor is genuinely good at.

2. Two or three situations where you win. Situations, not features. "When the team has no dedicated writer" is a situation. "Better AI" is not.

3. One or two where you lose. This is the trust section.

4. Discovery questions that reveal which situation this is. More valuable than the claims, because they tell the rep whether to push or qualify out.

5. A named proof point under each win claim. The part that is almost always missing and the part that makes the rest usable.

That last one is worth dwelling on. A rep will not risk an unbacked claim in front of a sceptical buyer. Give them a named customer, a real number and its source, and the claim becomes sayable. Leave it empty and the claim stays on the page.

Example one: versus a cheaper, lighter tool

Competitor described honestly: fast to start, genuinely cheaper, and good enough for teams that need a testimonial wall rather than full customer stories.

Where we win

• ●The team has no writer and needs the finished asset, not a collection widget. Proof: [named customer, role]. Went from 2 published stories a year to 11 in six months.
• ●Sales needs proof by segment, not a single wall of quotes. Proof: [named customer]. Replaced a generic quote page with four segment-matched stories; cites them in every late-stage deal.

Where we lose

• ●The buyer genuinely only wants to collect and display short quotes. That is what the competitor is for, and pushing past it produces a bad-fit customer who churns.

Discovery questions

• ●"When you publish one of these, who writes it today?"
• ●"Are you sending different proof to different segments, or the same page to everyone?"

Notice the loss is a real loss with a reason, and the discovery questions would let a rep disqualify honestly. That is what makes the win claims credible.

Example two: versus an enterprise incumbent

Competitor described honestly: the category's most established name, deep programme features, and the safe choice for a large customer marketing team.

Where we win

• ●Nobody owns customer marketing full time. The incumbent's programme depth becomes overhead when there is no one to run it. Proof: [named customer, role]. Two-person marketing team; first story published in week one.
• ●Procurement timeline matters. Self-serve versus a contact-us motion. Proof: pricing published at [price]; no demo required to start.

Where we lose

• ●A dedicated customer marketing team of three or more with an existing advocacy programme. The incumbent's depth is a genuine advantage there.
• ●Enterprise procurement requiring specific certifications we do not hold yet.

Discovery questions

• ●"Who owns customer stories today, and what else is on their plate?"
• ●"Is there a security review, and what does it require?"

The second loss is the kind teams delete from battlecards. Leaving it in is what makes a rep believe the first two claims.

Example three: versus doing nothing

The most common competitor in B2B and the one most battlecards omit entirely.

Described honestly: free, and the status quo has real momentum. Nobody gets fired for continuing to not publish case studies.

Where we win

• ●Sales is actively asking for proof and marketing cannot supply it. The cost of nothing is already being felt. Proof: [named customer, role]. "Our reps were asking for a case study in [segment] every week and we had none."
• ●A deal was lost, or slowed, for lack of a reference.

Where we lose

• ●No one is asking. If sales is not requesting proof, the pain is not present and the deal will stall regardless of what you send.

Discovery questions

• ●"When did a rep last ask you for a customer story? What did you send?"
• ●"Has a deal ever slowed down because a prospect wanted to talk to a customer?"

The second question is the sharpest in the whole document, because it converts an abstract need into a remembered event.

What this asks of your proof library

Look back at the examples. Every win claim carries a named customer and a figure, and each is matched to a segment.

That is the real constraint. If your battlecards have empty proof sections, the problem is not battlecard design — it is that you do not have enough customer evidence. No amount of formatting fixes an empty citation.

The audit that usually produces an uncomfortable answer:

If you would rather have it scored than eyeball it, the free proof point checker runs exactly these four checks per segment and names the gap that costs you most.

Most teams find one strong row and several empty ones. The empty rows are where competitive deals get stuck, because those are the conversations where generic proof does the least work. 6sense's 2025 study of around 4,000 buyers found buying groups average 11 members — one story cannot serve all of them, and it certainly cannot serve them across segments.

Where the proof comes from

The gap between "we need a proof point per segment" and "we have one case study from 2024" is a capture problem, and it is the reason enablement libraries go stale.

Uplift Content's 2024 survey of 115 SaaS customer marketers found each case study consumed roughly 12.7 hours of active work but around two months of elapsed time, with the top blockers being finding willing customers, identifying metrics and getting approval. Nobody is going to run that process once per segment per competitor.

The way out is to capture once and derive many. StoryVoice records a five-minute voice conversation with your customer, computes the headline figure from the before-and-after they stated, and produces the case study in their own voice — plus a sales email, a pull quote, a LinkedIn post and an X post from the same interview. The pull quote and the computed figure are exactly what a battlecard proof line needs, and the sales email is what the rep sends afterwards.

Try it on material you already have: paste an old call transcript or interview notes into the free AI case study generator. No email required. If the material is too thin for an honest story it says so rather than inventing a number, which is the behaviour you want from anything feeding a competitive conversation.

The honest verdict

Delete the feature grid. Write three situations, one loss, four discovery questions and a named proof point under every claim, and keep the whole thing on one screen.

Then check whether you can actually fill the proof lines. If you cannot, you have learned something more useful than a battlecard: you have found which competitive conversations you are walking into unarmed — which is the same shortage behind everything else sales asks marketing for, and the reason evidence is worth treating as a system rather than a content project. And when a card needs the fuller artifact behind it, turning a case study into a sales deck covers the one-pager and the six slides reps actually use.

Fill your empty proof lines — first case study free, no credit card required.

---

Sources: 6sense 2025 B2B Buyer Experience Report (~4,000 buyers); Uplift Content 2024 SaaS Case Study Survey (115 customer marketers).