Brand BOS: why agency deliverables stop working at $20M revenue.
Most agency engagements produce artefacts. What companies need by the time they’re scaling is an operating system — governance, voice, and the apparatus to enforce it.
The artefact problem.
Below $20M, an agency engagement that produces a guidelines PDF, a few hero campaigns, and a quarterly content calendar is genuinely useful. The brand is small enough that one person can hold the whole thing in their head. The PDF is a memory aid.
Above $20M, the same engagement quietly stops working. Not because the work got worse — because the operating context changed. Now there are five marketers, three contractors, two regional partners, and a sales team that has started writing its own collateral. The PDF is no longer a memory aid. It is, at best, a reference document nobody reads. The brand is being executed by people who never met the strategist who wrote the deck.
What a Brand BOS replaces
- Voice rules become a writing harness — embedded in the tools the team actually uses, not a tone document in a shared drive.
- Guidelines become governance — a small council with explicit authority to approve, reject, and revise.
- Campaign briefs become a content intelligence pipeline — research, then output, then measurement, in a continuous loop.
- The agency relationship becomes a retainer with measurable P&L impact, or it gets terminated.
Why most companies don't do this.
Because it requires admitting that the brand has scaled past the point where one strategist can carry it. That admission is uncomfortable. It also costs the strategist their job, which is why they don't volunteer it.
A brand operating system is what you build the second time, after you've watched the first version fail at scale.
We build the second version first. The retainer ends when the system runs without us.