Every PMM who's ever owned battle cards has had the same argument with the sales leader. Sales says the cards are stale. PMM says sales doesn't read them. Both are right, and the argument misses the real question: what's the update cadence that keeps the cards relevant without burning the PMM's Friday every week?
Three cadences exist. Most teams default to the wrong one.
Cadence 1 · Weekly
Weekly updates are appropriate when the category is moving fast and the sales team reads the cards before every call. That sentence has two conditions, and the second one is almost never true.
Weekly works for:
- Competitor-heavy categories during a consolidation window. M&A activity, major funding rounds, or a new entrant disrupting the top three vendors. These windows typically last two to three quarters.
- Sales teams that use battle cards as their primary comp research. This is rare. Most sales teams use recent-call notes and Gong snippets first, and battle cards second or third.
Weekly fails when the PMM is the only one tracking the cadence. A battle card updated weekly by a PMM whose sales team reads the card monthly is a PMM burning a day a week for no compounding value.
The test for whether weekly is right: in the last four weeks, how many changes you would have made to a card resulted in a visible sales-behavior change in the following week? If the answer is under 50%, weekly is too fast for your team.
Cadence 2 · Monthly
Monthly is the default and usually the right choice. Most categories change quickly enough that quarterly cadence produces genuinely stale cards (pricing from two quarters ago, competitor positioning that's been updated twice since the card was written) but slowly enough that weekly updates are wasted effort.
Monthly works for:
- Most mid-market SaaS categories. The median SaaS competitor updates their pricing page 2–3 times per year and ships meaningful positioning shifts 1–2 times per year. Monthly review catches these within six weeks of change.
- Sales teams with a monthly enablement ritual. If sales has a monthly call-review session or competitive-intel standup, the battle-card update fits into that rhythm and gets read.
Monthly fails when the review is scheduled but never produces changes. A PMM who reviews the cards monthly and updates them quarterly is running a monthly-reviewed quarterly cadence, which is the worst of both worlds — calendar cost without freshness benefit.
Cadence 3 · Event-driven
Event-driven updates trigger on specific competitive signals: a competitor pricing change, a product launch, a funding announcement, a messaging pivot on their homepage. No scheduled review — the trigger is the change.
Event-driven works for:
- Slow categories with periodic spikes. Some vertical SaaS categories see 18 months of quiet followed by a quarter of three major moves. Monthly review wastes time in the quiet months; event-driven catches the moves and ignores the noise.
- Teams with a competitive-monitoring infrastructure that reliably surfaces signals. This can be tooling, a dedicated competitive-intel role, or both. Without the infrastructure, event-driven cadence degrades to "we update when sales complains," which is too late.
Event-driven fails when the team has no monitoring infrastructure. The events happen; the team learns about them from a lost deal, not from a signal. That's not event-driven — that's reactive, and the battle cards are already obsolete by the time the team notices.
The real predictor
The right cadence is not determined by how fast your category moves. It's determined by how often your sales team reads the card, which is a function of the card's utility and the team's culture, not the category's volatility.
Most teams land on the wrong cadence because they ask the wrong question. The PMM asks "how fast does our category change," and that's a category question. The right question is "how often does our sales team engage with this artifact," and that's a culture question. Get the culture question right and the cadence follows. Get it wrong and you'll burn quarters of PMM time maintaining cards that nobody reads.
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.
How to Write Battle Cards for Pricing Objections
Most pricing battle cards re-argue the price. The ones sales reps actually use reframe the comparison — here's the five-section template, the three objections it has to answer, and the test for whether the card is working.