The operating format: what your business runs on

Your operating format is the documented set of systems, rules, and defaults your business runs on: how leads are generated, how they are followed up, how work is delivered, what you charge, who you decline, and how you know it is all working. Most firms of five to fifty staff do not have one written down — they run on the founder's memory and habits instead. The operating format is what turns a founder-dependent practice into a business that runs the same way whoever is at the desk.

What counts as an operating format?

It is the written layer between strategy and daily work. Not a 200-page operations manual nobody reads — a small set of live artefacts: checklists, sequence templates, pricing rules, a dashboard, a handful of standing decisions. Each one answers a question that would otherwise be answered by interrupting the founder.

The test is simple. When a competent new hire asks "how do we do X here?", the format either answers them or it does not. Every question it cannot answer is a question routed to a person — and in small firms, that person is nearly always the same one.

Why is "it's all in my head" a business risk?

Because it makes the founder the format. When every non-routine decision needs the founder's memory, then throughput is capped at the founder's hours, and hiring adds cost without adding much capacity — each new person increases the volume of questions flowing to the top. That is the core argument of The Founder-as-Bottleneck Report: the constraint is not effort, it is design.

The pattern usually starts in sales. The founder closes every deal personally, which works — until it becomes the reason nobody else can. Founder-led sales is an asset first and a bottleneck later, and the same arc repeats in delivery, pricing, and reporting. An undocumented business is also a fragile one: it cannot be delegated, audited, or sold, because the operating knowledge walks out of the building every evening.

What belongs in the format?

Six layers cover most B2B service firms. Each needs an artefact, not an intention.

Fixed pricing deserves particular attention: it is only possible once delivery is formatted, and it changes the economics of everything you sell — hourly billing is a trap precisely because it monetises the absence of a format.

How do you document it without stopping the business?

You do not schedule a documentation project. You capture the format as a by-product of work already happening. The mechanism, step by step:

• When a task is done for the second time, then whoever does it writes the steps as they go — a rough checklist, not prose. Twenty minutes, once.
• When a decision escalates to the founder, then the founder answers it and writes the rule that would have made the escalation unnecessary.
• When a document exists, then the next occurrence routes to the document first; the founder is only consulted when the document fails.
• When the document fails, then it is corrected the same day by the person who found the gap — the format stays live because using it and maintaining it are the same act.

Run that loop consistently and most recurring operations are commonly covered within about 90 days, without anyone stopping client work to write a manual.

What changes once the format exists?

Four things, in practice. Delegation becomes a handover of documents rather than a year of apprenticeship. Fixed-price offers become safe, because delivery cost is finally predictable. Reporting becomes trustworthy, because numbers are produced by the system rather than compiled by hand. And the founder's calendar starts to show white space — which is the point. The format does not remove the founder from the business; it removes the business's dependence on the founder's constant presence.

The honest first step is an inventory: list every recurring question that currently ends at your desk. That list is your missing format, in order of urgency.

---

Next step: the Growth System Audit — £450, seven days, credited against any build — maps where your growth system leaks and what to build first.