Writing Down How Your Agency Actually Delivers the Work
Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
Ask most agency owners how their team builds a campaign, sets up a client's reporting, or preps a launch, and the honest answer is "it depends who's doing it." The senior strategist does it one way, the newer hire does it another, and you — the owner — quietly do it a third way when you step in to save a slipping account. The work gets done, but the method lives in a handful of heads. The moment quality depends on which person happens to be assigned, you don't have a process — you have a set of individual habits you're hoping stay consistent.
That gap is invisible while your best people are on every account. It becomes painfully visible the first time they're on vacation, overloaded, or gone — and a client suddenly gets a deliverable that looks nothing like what they were promised. Writing down how the work actually gets done is how you make the good version the default, not the lucky outcome.
WHERE THE METHOD LIVES
In people's heads Written down as SOPs
───────────────── ─────────────────────
senior does it right ▇ everyone follows same steps ▇▇▇▇
junior guesses ░ junior ramps in days ▇▇▇▇
owner re-does it ░ owner reviews, not redoes ▇▇▇▇
quality swings ░░▇ quality holds ▇▇▇▇Owner symptoms
The same task comes out differently — sometimes worse — depending on who did it.
New hires take months to "get it," and you or a senior person carry them the whole way.
You keep getting pulled back into delivery to fix or redo work that missed the mark.
Why this happens
Agencies grow out of a founder's or a few experts' talent, and for a while that talent is the process. Nobody writes anything down because the people who know just do it. Then the agency takes on more clients than the experts can personally touch, work gets handed to whoever has capacity, and the unwritten standard doesn't travel with it. Every new person reinvents the method from scratch or copies whatever example they happened to see. The knowledge was never lost — it just never left the few heads it started in, so it can't scale past them.
Common mistakes
Treating SOPs as bureaucracy to avoid, rather than the thing that lets you delegate.
Documenting the ideal, not the real — writing an aspirational process nobody follows.
Writing it once and never touching it, so the doc drifts out of date and gets ignored.
Skipping the judgment calls — capturing clicks and steps but not why or when.
Making it so heavy nobody reads it, instead of a short, usable checklist.
Business consequences
When delivery lives in people's heads, your quality is capped by your best people's availability, and your growth is capped by how fast you can clone them — which you can't. Clients feel the swing: a great deliverable one month, a rushed one the next, and they start to wonder which agency they actually hired. Every new hire is a long, expensive ramp, and you stay trapped in delivery because you're the backstop for anything that goes sideways. The owner who writes the method down turns individual talent into a shared standard — work comes out consistent regardless of who's assigned, new people get productive in weeks instead of months, and the owner finally reviews the work instead of redoing it.
How experienced operators think about it
They see the documented process as the actual product of the agency, not paperwork about it. Their goal isn't a binder nobody opens — it's the shortest possible written path that lets a competent person deliver the work to standard without the expert in the room. So they document the real way the best version gets done, including the judgment calls and the "watch out for this" notes, then treat the SOP as a living thing that gets updated the moment reality changes. The test they use is simple: could a capable new hire follow this and produce work you'd send to the client? If not, the method is still trapped in someone's head.
Practical actions
Start with the work that hurts most — the deliverable that varies most by person, or the one you keep getting pulled into. Don't try to document everything at once.
Watch your best person do it and write down the actual steps, in their words, including the decisions they make without thinking.
Capture the judgment, not just the clicks — when to do X versus Y, what "good" looks like, the common mistakes to avoid. That's the part that's really in their head.
Keep it short and usable — a checklist or one-pager someone can follow on a live job, not a manual. If it's too long to use, it won't get used.
Have someone else run it and fix what's unclear. The gaps show up the moment a second person tries to follow it.
Assign an owner and a review date so the SOP gets updated when the work changes instead of quietly rotting.
Questions every owner should ask
If my best person on this account were out for a month, would the work still meet standard?
Which deliverables come out differently depending on who's assigned — and why?
Could a capable new hire follow what we've written down and produce client-ready work?
Frequently asked questions
We're too busy delivering to stop and document everything. Where do we even start?
Don't try to document everything — that's why it never happens. Pick the single deliverable that causes the most rework or varies most by person, and capture just that one, the next time someone does it well. You're not writing a manual; you're recording one process while it happens. One good SOP that ends a recurring quality problem earns its time back fast, and it proves the approach before you spend effort on the rest.
Won't rigid processes kill the creativity our clients pay us for?
SOPs should cover the repeatable delivery — how you set up reporting, run a launch checklist, QA a build, onboard an account — not the creative thinking itself. Documenting the mechanical parts is what frees your people to spend their judgment where it matters, instead of reinventing setup steps every time. Done right, an SOP captures judgment rather than replacing it: it tells someone when a decision is theirs to make and what to watch for when they make it.
Related articles
Running a Profitable Marketing Agency — the pillar.
Standardizing Deliverables So Quality Doesn't Depend on Who's Assigned — the output side of the same problem.
Controlling the Revision Rounds That Blow Up Your Budget — where inconsistent delivery leaks time.
Why Jobs Take Longer Than You Quoted — the universal problem this feeds.
Where Time Leaks on a Typical Job — where the hours actually go.
Every business has more decisions than time
Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.
Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.