The agency operations manual: what to put in it (and how to build it)

Stop running your agency from memory

Every small agency hits the same ceiling: how much the founder can hold in their head. New hires take months to ramp because there's nothing to read. Decisions get re-made every quarter because nobody captured what worked last time. Onboarding a client looks different depending on who runs it. An agency operations manual fixes this not with bureaucracy, but with a single place that answers "how do we actually do this?" - so the answer doesn't have to come from a person every time.

It's also one of the few investments that compounds. Every documented process saves time every time someone does it again, and pays back in faster onboarding, more consistent delivery, and an agency that runs without you.

The six sections that cover almost everything

You don't need a hundred pages. You need six sections, each kept short and current:

1. Services. What you offer and don't offer, in one paragraph each, with scope and outcome. Kills the "can we do…?" debate.
2. Processes. Your SOPs - how each repeatable thing gets done, end to end.
3. People. The org chart, who decides what, and how decisions escalate. RACI lives here for cross-functional work.
4. Tools. The stack: what each tool is for, who has access, where credentials live, how to onboard someone to each one.
5. Templates. Reusable artefacts in one place - briefs, SOWs, proposals, status reports, the client onboarding checklist.
6. Governance. The handful of policies that matter: data, AI usage, security basics, brand.

Anything that doesn't fit one of these six is usually a sign it shouldn't be in the manual at all.

How to build it without a quarter-long project

The mistake almost everyone makes is trying to build the whole manual in one go - an "ops sprint" that runs out of steam at week three. Build it incrementally instead. Each time the team does something that will recur, write a short note while it's fresh and drop it in the right section. Three rules:

• Capture during, not after. Five minutes at the end of doing the thing is more accurate than an hour-long writeup a fortnight later.
• Every entry has an owner. A document without one expires in six months.
• Done beats perfect. A scrappy SOP that exists is infinitely better than the polished one that's still in someone's drafts.

After two quarters of this, you have a manual. After a year, you have an operational asset that materially raises the value of the business.

Where it should live

A manual stuffed in a wiki gets read once and forgotten. The best home is a team operations hub - one branded place your team lives in - where the manual sits alongside the work itself, not in a separate "documentation" silo. For the wider picture of why systemising matters and what else fits around the manual, see the systemise your agency guide.