Every playbook that worked has an expiry date built into it. Nobody prints the date on the cover, so most businesses find out the hard way.
- A “playbook” is every repeatable habit that got you to your current size — pricing, qualification shortcuts, deal approvals, onboarding, even informal team norms — not just a sales script.
- Every playbook has an implicit half-life: it was built to handle a certain volume and complexity of deals, and starts degrading well before it visibly breaks.
- A playbook breaking isn’t a failure. It’s proof the business outgrew the constraints it was originally designed for — the fix is treating it as a living document, not a one-time project.
What “The Playbook” Actually Means
It’s easy to hear “playbook” and think of a sales script. The real playbook is much wider: the pricing approach that made sense for your first handful of customers, the qualification shortcuts that let you move fast with a small team, the informal way deals get approved, the way new hires get onboarded, even the unwritten norms about who makes which call. All of it was designed, explicitly or not, around the size and complexity of the business at the time it was built.
Playbook Half-Life
Every playbook has an implicit half-life. It doesn’t fail the moment the business outgrows it — it degrades quietly, well before anyone officially notices, because the early symptoms look like individual exceptions rather than a systemic problem. A pricing model built around twenty handpicked customers can absorb the occasional exception without anyone noticing a pattern. Scaled to two hundred accounts, those “occasional exceptions” become a daily occurrence, handled inconsistently by whoever’s closest to the decision — and margin leaks out through a hundred small, reasonable-sounding calls that nobody signed off on as policy.
The gap between when a playbook starts failing and when anyone notices is where most scaling friction quietly accumulates.
How Do You Know Your Playbook Has Broken?
The clearest sign is inconsistency where there used to be repeatability: the same action that reliably produced a predictable result six months ago now produces a different one depending on who’s doing it. When that happens, people don’t usually raise it as a systemic issue — they quietly build their own personal version of “how we do things,” because the shared version stopped covering the complexity of the actual work. A dozen quiet personal workarounds is what a broken playbook looks like from the inside, long before it looks like one from the outside.
This Isn’t Failure — It’s Evidence of Growth
A playbook breaking doesn’t mean the business did something wrong. It means the business is operating at a scale, deal complexity, or team size the playbook was never designed to handle — which is a good problem, mishandled. Treating that as a crisis misses the actual lesson: the playbook needs a deliberate owner and a review cadence tied to real growth milestones — headcount, deal volume, average deal size, new geographies — instead of being written once during an early “let’s document our process” project and left untouched for years.
A playbook doesn’t fail loudly. It fails one quiet workaround at a time, until the workarounds are the actual playbook.
If you can’t remember the last time you deliberately rewrote a piece of your playbook, it isn’t guiding your business anymore. It’s just old paper everyone’s quietly ignoring.
The $2m playbook wasn’t wrong. It was built for a $2m business, and it did exactly what it was designed to do. Blaming it for breaking at $10m is like blaming a ladder for not reaching the second floor. Rewrite it on purpose, on a schedule tied to how the business actually grows, and it stops being something that quietly expires and starts being something that scales with you.
Frequently Asked Questions
How often should a scaling business rewrite its playbook?
Tie the review to growth milestones rather than a calendar — a meaningful jump in headcount, deal volume, average deal size, or a new market — rather than waiting for an annual planning cycle to surface the gap.
What’s the first sign a playbook needs updating?
Inconsistency: the same action starts producing different results depending on who performs it, and people quietly build personal workarounds instead of flagging the shared process as broken.
Who should own the playbook as a business scales?
A named owner with the authority to update it, not a founder by default and not a shared document nobody’s accountable for — ownership is what turns “we should update that” into it actually happening.
Related reading: Revenue Plateau or Market Ceiling?
If you’re relying on habits that were built for a business half your current size, the Curve Diagnostic will show you exactly where they’re quietly costing you.
Take the Curve Diagnostic