What to white-label and what to keep in house

The outsourcing conversation usually gets framed as a cost question, which is why it usually gets answered badly. Cost tells you whether you can afford to move a task. It tells you nothing about whether moving it will quietly destroy the thing you are selling.

There is a better question, and it takes about a minute per task.

The definition-of-done test

Before the work starts, can you write down what finished looks like, precisely enough that somebody who has never met the client could tell whether it had been achieved?

If yes, the task is a candidate for white-label delivery. A snapshot import has a definition of done: fourteen checks, all passing. A brand rebuild has one: every asset matches the kit, no foreign name survives. A reactivation campaign has one: the list is segmented, the sequence is live, the replies route somewhere a human reads.

If no — if finished is a judgement call that depends on knowing this particular client — the task stays with you. Choosing which of three offers to lead with is not a specification. Deciding whether to tell a client their pricing is the actual problem is not a specification. Those are relationship decisions wearing a delivery costume.

What passes the test

• Sub-account builds and snapshot installs — repeatable, checkable, and identical enough across clients that a checklist genuinely covers them.
• Brand rebuilds and asset hygiene — tedious, high-volume, and pass or fail rather than better or worse.
• Technical configuration: domains, sender authentication, number provisioning, calendar wiring, integration plumbing.
• Campaign build-out from an approved brief — the sequences, the segments, the triggers, once somebody has decided what the campaign is.
• Tier-two support: the ticket that needs somebody to open a workflow and find out why a step is not firing.
• Documentation and training material, produced to your template and signed with your name.

What should never leave

Four functions, and the reason is the same each time: they are where your client decides whether to keep paying you.

1. Strategy. What the client should do next is the product. Everything else is execution of it.
2. The relationship. The person who calls when something has gone wrong should be someone the client has met and trusts. Never a routing rule.
3. Pricing and scope decisions. The moment somebody outside your business can commit you to work, you have a partner rather than a supplier.
4. Quality acceptance. Somebody on your side signs off before a client sees anything. Delegating the build is normal; delegating the standard is how agencies end up apologising for work they never looked at.

The grey zone, and how to resolve it

Two categories sit awkwardly in the middle, and both are resolvable by splitting them rather than assigning them.

Client communication

Strategic communication stays with you. Procedural communication — the onboarding sequence, the access request, the training walkthrough, the monthly report — can be produced elsewhere and sent under your name, because it is a template with a definition of done. Split on that line rather than trying to answer the question whole.

Copywriting

Offer copy is strategy. Sequence copy is production. The email that decides how the offer is framed stays in house; the eleven follow-ups that carry that framing forward do not have to.

What your client’s customer never notices

Run the split correctly and the end customer’s experience is seamless in a very specific way. They call the business they meant to call, a voice answers in that business’s name, the confirmation arrives from that business, and the reminder the day before comes from the same sender as everything else.

None of that reveals who built the workflow, and none of it should. The customer’s only signal is consistency, and consistency is a production property — which is precisely why production is the safe thing to move and judgement is not.

Putting it into practice

Take your current delivery process, write every task on a line, and mark each one with a single letter: S for specification-shaped, J for judgement-shaped. The S column is your outsourcing brief and maps cleanly onto a white-label fulfilment retainer. The scoped, one-off items in it — a campaign build, an integration, a custom workflow — map onto fixed-scope automation build-outs instead, because they finish rather than recur. The J column is your job description, and it should be the shorter list.

Most agency owners discover their J column contains four or five things and their week contains forty. That gap is the whole argument.

How to brief so the specification survives contact

A task that passes the definition-of-done test can still fail in delivery, and it usually fails for the same reason: the brief described the work rather than the outcome. Five things make a brief hold.

1. State the finished condition, not the steps. "Every sender identity resolves to the client’s domain" survives a change of method; "update the settings page" does not.
2. Name the checks. If you would inspect six things before showing the client, list those six things in the brief and ask for them back as a completed list.
3. Include the client-facing context, not just the technical spec. Somebody writing a reminder sequence needs to know what the business does and who calls it, or the copy will be generically correct and specifically useless.
4. Say what is out of scope explicitly. Ambiguity is always resolved in the direction of less work, and then discovered late.
5. Give one example of a previous output you were happy with. It is worth more than another paragraph of description.

A brief written this way takes twenty minutes and removes the two rounds of correction that otherwise make outsourcing feel slower than doing it yourself.

Review the split every quarter

The line between specification and judgement moves as your business matures, and it moves in one direction. Work that required judgement last year usually required it because nobody had written it down yet.

So every quarter, take the J column and ask a single question of each item: has this become predictable enough to specify? Onboarding calls, scoping conversations and even parts of strategy eventually acquire a shape. When they do, the shape can be written down, and once written down it can be delivered by somebody else to your standard.

The reverse almost never happens. If something moves from the S column back to the J column, it is usually a sign that the specification was wrong rather than that the work changed.

One warning about the review. Do not run it while you are busy, because a busy quarter makes everything look like it should be somebody else’s problem, including the four things that should never leave. Run it in the quietest week you have, when the answers are about the shape of the business rather than about the shape of your inbox.

The short version

White-label everything you can specify. Keep everything you must judge. The mistake is never outsourcing too much production — it is outsourcing one decision and finding out six weeks later that somebody else has been running your agency.