The most common pricing battle card in circulation looks like this: a price comparison grid, three bullets on "value," and a closing line about ROI. A PMM writes it, sales reads it once, and nobody references it in a live call. Then the company loses the next price-sensitive deal and the PMM gets asked why the battle card didn't work.
The reason it didn't work is that the card was designed to re-argue the price, which is the wrong fight. By the time a buyer raises a price objection, they have already decided the price is too high. Arguing the number is arguing with a conclusion the buyer has already landed on. A battle card that re-argues the price loses; a battle card that reframes what the buyer is comparing against can win. The structure below is what the useful version looks like.
The three pricing objections a card has to answer
Before any structure, the card has to be built around the actual objections sales reps hear, not the ones the PMM imagines they hear. Pull the transcripts from the last twenty price-sensitive deals. You will find three objections, and a well-built card answers all three with equal weight.
The first is "you're more expensive than [competitor]." A literal price comparison. The buyer has quotes in hand.
The second is "we don't have the budget for this right now." A timing objection dressed as a price objection. The real issue is that the buyer can't get the amount approved this quarter; the price is fine, the line item isn't.
The third is "we can build this internally with existing tools." An alternative-cost objection. The buyer believes the cost of your product is higher than the cost of doing without it.
Each of these wants a different response. The card that answers all three looks different from the card that treats them as the same objection.
All three parts have to be present. A reframe without evidence is a sales platitude; evidence without reframe is a defensive grid.
The five-section battle card structure
The card that sales actually uses has exactly five sections. Any longer and reps stop reading; any shorter and the card doesn't give reps enough to work with in a live conversation. Each section answers one of the three objections above, directly.
Section 1 · The reframe (top, 40 words max)
The first forty words of the card tell the rep what to reframe. Not what to say — what to reframe. "Don't argue the price against [competitor]. Reframe to total-cost-of-decision over 18 months. Our price is 1.4× theirs; the implementation gap is 4×, and that's their actual cost." Reps can adapt the language to the call. What they need on the card is the strategic move.
Section 2 · The three objection scripts (middle, one per objection)
Each of the three objections gets one short script — a single sentence to say out loud, and two sentences of backing evidence the rep can cite if the buyer pushes back. The scripts are the part of the card reps will cut and paste into their own notes, so they have to be speakable, not written.
What each objection script must have
Section 3 · The comparison the buyer should be making (visual)
A small grid — three columns max — that shows the comparison after the reframe. Not the price-per-seat comparison; the total-cost-over-18-months comparison, or the implementation-risk comparison, or whichever comparison supports the reframe from Section 1. This is the anti-pricing-grid move. The rep is giving the buyer a different frame, not a rebuttal to the buyer's frame.
Section 4 · The proof bench (specific customers, not logos)
Three named customers — with a one-line outcome for each. The outcome has to be specific enough that it could be independently verified. "Logo A saw 23% reduction in [specific metric] over 12 months, documented in [named case study]." The generic logo wall on the back of the card does not help the rep; the specific outcome attached to a named customer in a relevant segment is the strongest signal.
Section 5 · The landmine the rep should watch for (bottom, 30 words max)
Every competitor has one thing they will try to make the conversation about, because they are better at it. Name that thing. "Competitor X will pivot to their integration with [tool]. That integration is real and we don't have the equivalent. Acknowledge it and pivot back to [our stronger ground]." Reps who know what's coming handle it better than reps who are surprised by it.
The objection the card cannot answer
Some price objections are not answerable by a battle card. When the buyer's budget is genuinely lower than your price by a factor of two, no reframe will close the gap. The card's honest job is to help the rep identify this case quickly so they can redirect — either to a different tier, a phased implementation, or a disqualification.
A good pricing battle card includes one sentence on disqualification. "If the buyer's total budget for this year is under $X, you are not going to close them. Exit gracefully and leave the door open." The alternative — a rep spending six calls trying to shrink the product to fit the budget — costs the rep cycles and rarely produces a healthy customer at the end.
The first thing I teach new reps is that the price objection is often the buyer asking you to give them a reason to pick you over the cheaper option. The battle card that makes it a debate makes them pick the cheaper option. The battle card that gives them a reason wins the deal.
Testing whether the card is working
A battle card is not working just because the PMM shipped it. The card is working if three things are true, and failing if any one of the three isn't.
First: reps use it in the first six weeks. Sales enablement metrics — download counts, search counts in the tooling — should show uptake in the first month. If no rep is searching the card, the card isn't findable or isn't credible. Fix the findability first, the credibility second.
Second: win rate on the named objection moves in the right direction over one quarter. Track the objection tag on closed deals. The win rate on "you're more expensive than X" should improve, even by a single point, within a quarter of the card shipping. No movement means the card isn't being used in the moment it matters.
Third: reps rewrite the card on their own. The highest-signal indicator that a card is useful is that reps start making personalized versions. They add their own customer anecdotes, rework the phrasing to match their voice, cut sections that don't fit their book. This means the card became infrastructure. Reps don't rewrite cards they don't use.
Maintenance budget
The pricing battle card goes stale faster than any other battle card. Competitor pricing pages change quarterly; your own pricing changes less often but still meaningfully once a year. The maintenance budget is a thirty-minute quarterly review by the PMM, plus an ad-hoc update within two weeks of any competitor pricing change.
A card without a maintenance budget becomes actively harmful within two quarters — reps cite stale competitor prices, buyers catch it, and the card's credibility with the sales team collapses. PMMs who resist writing battle cards because "sales will stop using them anyway" usually have an unmaintained-card problem, not a card-design problem. Maintenance is cheaper than the first write; budget for it from day one.
The pricing objection is the single most common loss driver in B2B SaaS deals above $25K ACV. A card built around reframes, specific evidence, and admitted trade-offs will move the needle where a price-rebuttal grid will not. The five-section structure is durable; the content inside each section has to be maintained. Both parts matter.
Battle Cards
Auto-updating per-competitor rebuttal kits. Each card updates when Competitor Signals detects a material move.
See how it worksOne sharp positioning read, most Thursdays.
Field-tested frameworks, teardowns, and pattern notes from our working library. No "Top 10" lists. No launch roundups. Unsubscribe whenever.
Keep reading
How to Build Battle Cards That Sales Actually Uses
Tactical guide to battle cards that field reps open during live deals — not the ones that rot in Drive two weeks after they ship.
Battle Card Template for Feature Launches
When a competitor ships a feature, sales has 72 hours before buyers start asking. A compressed five-section battle card template built for the feature-launch window.
Win/Loss Review Template for B2B SaaS
A working template for turning lost and won deals into pattern data — the five questions, the tagging taxonomy, and the one spreadsheet that keeps the loop honest.