How to build a competitor battlecard that stays up to date

A battlecard starts its life useful. Someone spends an afternoon building a clean one-pager for each competitor: where you win, where you lose, how to reframe the pitch, what to say when a rep hears "but their tool does X." For a few weeks it works.

Then the competitor changes their pricing, ships two features, and quietly drops the weakness the card was built to exploit. The card does not know any of this. It keeps handing reps the same lines, half of them now wrong, and the first sign anyone gets is a deal lost to an answer that used to be true.

The maintenance is the hard part, not the format. Building the card is an afternoon. Knowing what changed since you built it, every week, across every competitor, is the job nobody has time to keep doing. So the fix is not a better template. It is a system that keeps a good template accurate.

What sections a battlecard actually needs

A card a rep can use mid-call is short and structured. Each section earns its place by answering one thing the rep needs in the moment:

• A one-line frame. Who the competitor is, who they sell to, and the single sentence to lead with when the name comes up.
• Where you win. The two or three places your product is genuinely stronger, written as claims a rep can defend under a follow-up question.
• Where you lose. The places they are stronger, stated honestly, each paired with the reframe that keeps the deal alive.
• Pricing and packaging. Their tiers, what sits in each, and where the line falls between their plan and yours.
• Objection handling. The "but their tool does X" moments, each with a short rebuttal that is current, not the one that was true a quarter ago.
• Traps to set. The questions a rep can ask that surface a real gap in the competitor's offer.

Every one of those lines is a fact about the competitor on a given day. That is precisely why the card decays.

Why the half-life is short and quarterly is too slow

A battlecard is only as good as the day it was last accurate, and in a fast-moving market that half-life is short. Quarterly refreshes, which is how most teams run it, are far too slow. A competitor in an active category can reprice and ship several times in a single quarter, so a card reviewed every three months is wrong for most of its life.

The usual patches do not hold. A shared doc that everyone can update gets updated by no one, because keeping it current is somebody's side task and side tasks slip. A full competitive-intelligence suite keeps a feed current but hands you a firehose to read, and still leaves the translation, turning a raw change into a line a rep can say, up to you. Neither closes the gap between "the competitor changed" and "the card reflects it."

Which surfaces feed which sections

The maintenance stops being vague once you map each card section to the public surface that changes it. You are not watching everything. You are watching the specific pages that move specific lines.

• Pricing and packaging is fed by the pricing page. A tier that moves, a feature that shifts between plans, a new add-on all show up there first, and that same signal drives what to do when a competitor cuts their price.
• Where you win, where you lose, and objection handling are fed by changelogs and release notes. A shipped feature can erase a weakness you were exploiting or hand you a new advantage, which is the same discipline behind how to know when a competitor launches a new feature.
• The one-line frame and positioning are fed by blog posts and product-update emails, where a competitor signals who they are chasing next.
• Traps to set are fed by the same changelog and pricing surfaces, read for what is still missing rather than what shipped.

The cadence follows the surface, not the calendar. Detection runs on a tight interval so a change is caught within a day. The card edit happens the same week, off the interpreted change, not once a quarter off a research project. Watch daily, edit weekly, never wait for the quarter.

How an interpreted change becomes an updated line

The loop that keeps a card true is small enough to run in minutes, not afternoons:

1. Watch only the surfaces that change card lines: pricing, packaging, and shipped features.
2. When one changes, get the change interpreted, not just flagged. You need what moved, why it matters to your positioning, and which card line it touches.
3. Route the interpreted change to the section it affects.
4. Edit that one line and date it, so anyone reading the card knows how fresh it is.
5. Flag the deals in flight where the old line was in play, so a rep is not repeating it on the next call.

Here is the loop on one change. Say a competitor's changelog ships an entry adding SSO to their Team tier. Your "where you lose" section previously read: no SSO below their Enterprise plan, so mid-market buyers pay a premium for it. Interpreted, that entry says three things: they closed a gap you were selling against, it reaches every mid-market deal, and the line is now false. You rewrite it to "SSO now included on their Team tier as of this week; the remaining gap is [the actual gap]," update the matching objection-handling rebuttal, and tell the two reps with mid-market deals open. Total time, a few minutes. The alternative is a rep confidently repeating a dead line three weeks from now and losing on it.

The same loop handles a pricing move. Say their Pro tier goes from $49 to $59 and adds a usage cap. The pricing section gets the new number and the cap, the "where you win" line about your flat pricing gets a little stronger, and the reps working price-sensitive deals hear it before the prospect does.

The practical fix

The reason this rarely happens is not discipline, it is input. Nobody is going to reread five surfaces per competitor every week by hand, and a raw diff feed just moves the reading problem around. The fix is to treat the battlecard as a living document fed by a monitor, not a snapshot you rebuild from memory. Presagon watches the surfaces that actually change what belongs on the card and delivers each change already interpreted: what shipped, why it matters to you, and what to do next, tied to the line it touches. When the input is a stream of interpreted changes instead of a quarterly research project, the card stays true, and the rep in a live call is working from what is real today, not what was real last quarter.