We Audited 40 Sales Playbooks. The Median One Was Wrong Within Five Months.

Every playbook we've ever opened for a client audit starts the same way: title slide, version number, publish date. "Q2 2026 Discovery Playbook, v3." Nobody ever asks the second question, which is when it stops being true. We started logging that answer across 40 cross-client content audits — SaaS, professional services, a couple of manufacturers, one insurance broker who insisted on calling it a "battle deck" — and the median piece of core sales content was carrying at least one materially false claim within five months of its own launch date. Not stale in the vague, needs-a-refresh sense. Wrong: a competitor claim that no longer held up, a price point that had moved twice since, an ICP description built around a segment the company quietly stopped chasing eight weeks after the deck shipped.

Five months. Most content calendars we've seen run on a two-quarter refresh cycle. Do the arithmetic and the average playbook spends roughly half its working life being confidently, silently incorrect, in front of customers, in the mouths of reps who have no reason to doubt it.

What counted as "wrong"

We didn't grade on vibes. A claim failed the audit if it contradicted a verifiable source of truth at the time it was in active use: the live price sheet, the competitor's current public positioning, a named executive confirming the ICP had shifted, a case study logo that had since churned. We logged the publish date and the earliest date such a contradiction could be evidenced, then measured the gap in weeks. Content that was merely dated in tone, or badly designed, or using last year's font, didn't count. Only claims a customer could catch out.

That's a strict test, and it's still the test that matters, because it's the one your buyer is running whether you asked them to or not. Across 40 audits and roughly 260 individual assets — battlecards, discovery scripts, objection-handling sheets, ROI one-pagers, case studies — the median gap was 22 weeks. Five months, near enough.

The decay curve isn't flat, and that's the finding that actually matters

The five-month headline is an average of things that don't decay at the same speed, and almost no company's refresh calendar reflects the difference.

A battlecard is typically wrong before most companies have even finished the first QBR of the quarter it launched in. A case study can coast for the better part of a year on the same shelf. Treat both with one blanket "review every six months" entry and you get the worst of both: the battlecard is wrong for roughly three months before anyone looks again, and the case study gets reviewed twice as often as it needs, burning review time that should have gone toward the thing that was actually rotting.

We cross-checked decay speed against usage frequency on a subset of the audits using a Sales Content Effectiveness Calculator, and the correlation is the uncomfortable kind: the fastest-decaying content — competitive claims, pricing — is also the content reps open most often, mid-call, under pressure, the moment a prospect drops a competitor's name or a number that doesn't match what's in the deck. That's exactly the content you can least afford to have wrong, and it's the content going wrong fastest.

The publish date is the wrong field to be tracking

Ask a RevOps lead when a playbook was last touched and you'll get an answer inside five seconds. Ask when it's next due to be checked for accuracy and you'll get a shrug, or a reference to "the next refresh cycle" — a calendar entry, not a claim about whether the content is still true. A publish date tells you when something was correct. It says nothing about how long that was ever going to last, and everyone in the room already knows the two aren't the same thing; they just haven't been asked to write it down.

The fix doesn't require more content, more review meetings, or a bigger enablement headcount. It requires one additional metadata field, assigned at creation rather than bolted on during some future clean-up sprint: an expiry date, set by shelf-life class — fast (8–12 weeks) for anything competitive or pricing-related, medium (16–24 weeks) for ICP and objection content, slow (28+ weeks) for discovery frameworks and case studies — plus a named owner accountable for re-verifying or retiring the asset by that date, not just refreshing it whenever the next scheduled cycle happens to land.

We've started building the expiry field into client content operations as a mandatory column in a Sales Content Calendar Template, sitting next to the publish date rather than replacing it. It costs about five minutes per asset at the point of creation. The alternative is what turned up in 40 audits: playbooks ageing invisibly, at different speeds, with a launch date on the title slide standing in for a promise the content was never built to keep.

The actual discipline

None of this is a content problem. It's a metadata problem, and a fairly small one — the difference between asking "when was this true" and never asking "when will this stop being true," at the one moment it's cheap to answer: when the thing is written, not eight audits later when someone like us finds it.

A playbook with a publish date and no expiry date isn't current. It's just recently wrong, and nobody's checked yet.