For agencies and studios
Keep the relationship. Hand over the production.
Your margin problem and your quality problem are the same problem: output scales by adding people, and every person added is another interpretation of the brand. This puts the interpretation in a file instead.
The problem
Volume scales by headcount. Voice does not.
An agency's economics run on the gap between what a client pays and what delivery costs. Delivery cost is people, so growth means hiring, and every hire has to learn each brand from a deck, a call, and whatever they can infer from past work.
That inference is where consistency goes. Not dramatically, and not in a way that shows up in a single deliverable. It shows up as a client saying that something feels off and not being able to say why, three months into a retainer, on work that passed internal review.
The usual response is another review layer, which costs senior time on junior output and slows delivery. The margin gets worse and the drift does not stop, because a review catches an instance and never removes the cause.
What it costs
Where the margin actually goes.
- Senior time on rework
- The most expensive people on the team spend their hours correcting output rather than producing strategy, and the correction is the same correction on a different brand next week.
- Onboarding, repeatedly
- Every new hire re-learns every brand. Every departure takes that knowledge with them. Neither cost appears as a line item.
- Capacity that arrives in steps
- You cannot hire a third of a person. Winning one account too many means hiring ahead of revenue and carrying it, or turning the work down.
- Churn you cannot attribute
- A client who leaves because the work stopped sounding like them rarely says that. They say the budget changed.
Why the usual answer does not hold
A style guide is not a specification.
Most agencies already have brand guidelines. They cover logo clearance, palette, and a paragraph on tone that says something like confident but approachable. That is not enough information for someone to write a sentence with, which is why every writer produces a slightly different version of the brand and every reviewer corrects toward their own.
A working specification is a different document. It names the vocabulary that belongs to this brand and the vocabulary that does not. It sets sentence rhythm against real examples. It lists the terms that must never appear. It is specific enough that two different people produce recognisably the same brand, and specific enough that a check can run before a human ever sees the draft.
Once that exists, capacity stops being coupled to headcount, because the constraint moves from who is available to what the specification says.
What gets installed
What sits underneath your delivery.
- A specification per client
- Derived from that client's published material and your existing guidelines. It is your document; it goes in your repository, and it is an asset you can show in a pitch.
- Blocked-term lists per client
- Checked at the pipeline before anything reaches your reviewer, so senior time is spent on judgement rather than on catching the same word again.
- Production capacity
- Video, short-form, and written work produced against the specification, in whatever volume the scope names. White-labelled or co-branded, your call.
- Your review gate, not ours
- Work lands in your queue. You approve, you send back, and you are the one talking to the client either way.
- Reporting you can forward
- Written, on a fixed rhythm, in a form you can pass to the client without rewriting it first.
Control and ownership
You stay the agency. Nothing about that changes.
Stays human
- Strategy, positioning, and the client relationship
- The specification's contents, which you sign off per client
- Approval before anything reaches the client
- Every conversation the client is part of
Yours to keep
- Each specification, in your repository
- The render templates, reusable across your roster
- Every source file and export
- The reporting format, as your artefact
How it gets done
How it starts, usually with one account.
- 01
Pick the account that hurts most
Usually the highest-volume one, or the one where drift has already been raised. One account is enough to see whether this works.
- 02
Build that client's specification
From their published material and your guidelines. You review it before anything is produced against it.
- 03
Run one cycle under your gate
Production lands in your queue at your standard. You will send things back in cycle one. Those corrections go into the specification.
- 04
Compare cycle two against cycle one
The measure that matters is how much came back. If it has not dropped, the specification is not specific enough and that is ours to fix.
- 05
Add accounts
Each new account is a new specification and the same pipeline. This is where the economics change, because the second account costs less to add than the first.
Proof
One shoot, packaged for three different audiences.
Renarda showed up once with the stories. The funder cut, the community cut, and the training material all came out of that same afternoon, each cut for the audience it had to reach.
- 1
- Shoot days behind the whole libraryA single afternoon of footageProduction records · April 13, 2026
- 0
- Founder hours on productionShe showed up once with the storiesInternal workflow measurement · April 13, 2026
- 67
- Videos from that one shootProgram docs 18, outreach 22, funder reels 12, training 15Production records · April 13, 2026
- 5
- Publishing workflows runningOn schedule, without the founder in the loopProduction records · April 13, 2026
The full account, including reach figures with their capture date and paid spend stated, is on the Winnin’ Against Addiction™ case study.
How to decide
Whether to bring this in.
This is the right call when
- Delivery capacity is the constraint on taking more work
- Senior people are spending hours on rework rather than strategy
- Clients have raised consistency, even vaguely
- You want to keep the relationship and the margin, and only move the production
It is the wrong call when
- The agency's differentiation is the specific people who make the work
- Volume is not the issue and the work is bespoke each time
- You need someone in client meetings
- The real problem is pricing rather than capacity
Objections
The reasonable worries.
- Our clients will find out
- White-labelled means white-labelled: your accounts, your reporting format, your name on the work. Whether you disclose it is your decision and we have no position on it.
- We would be handing over our craft
- You are handing over execution against a specification you wrote and signed off. The judgement about what makes the brand good stays entirely with you; it just stops being re-explained to a new person every quarter.
- This will be worse than our juniors
- Cycle one is the test, under your gate, on one account. If more comes back than your current process produces, you have lost one cycle and gained a specification you keep either way.
- We already tried outsourcing production
- Almost certainly to people working from a brief. The difference here is that the brief is a versioned file with a checkable term list attached, and corrections go into it rather than into a Slack thread.
Questions
Asked before the call.
Can we resell this?
Yes, and most partners do. You price to your client; we scope to you. What you charge is not our business.
Who owns the specification?
You do, in your repository. If the engagement ends you keep every specification built during it, and they remain useful whoever produces against them.
How fast can you take on a new account?
The specification is the slow part and it takes days rather than weeks once we have the client's published material. Production against an existing specification starts immediately.
Do you work directly with our clients?
Only if you want us to. The default is that you are the only party the client talks to.
Read next
Where this connects.
- Compared with a traditional agency is written for the buyer on the other side of the table, which is useful reading if you are deciding how to position against it.
- The system walks the pipeline from specification through to publishing.
- How we work covers white-labelling, data handling, and continuity in detail.
Bring one account and see what comes back.
Thirty minutes to scope a single client, run one cycle under your gate, and compare the rework against what you get today.