Most articles about white label development are written to sell one. They describe the benefit, which everybody already understands: an agency takes on work it cannot staff, and the client never knows. What they leave out is the operational detail that decides whether the arrangement survives its second project.
This is that detail, written for the agency considering it rather than for the buyer being sold it.
Decide the communication model on day one
There are three, and picking one by accident is the most common way these arrangements go wrong.
Fully behind the curtain. The agency is the only voice the client hears. Everything routes through one person on the agency side. Cleanest for the client relationship, slowest for delivery, and it turns the agency’s project manager into a full-time translator. It works when that person is technical enough to answer half the questions themselves.
Introduced as the delivery team. The client knows there is a partner and speaks to them directly on technical matters, with the agency owning the relationship, the commercials and the decisions. Faster, fewer misunderstandings, and it requires trust that nobody will go around the agency.
Badged. The partner’s engineers appear under the agency’s name in the client’s tools. Effective and the one with the most ways to leak: an email signature, a calendar invite, a commit author, a support ticket footer. If this is the model, the leak points have to be listed and checked, not assumed.
The model can change per client. What it cannot do is remain undecided, because the first time a client emails an engineer directly, everyone finds out what the model was.
The things that must be written down before the first project
- Who owns the code, and when. Usually the agency on payment, so it can be assigned to the client. Say it explicitly, including what happens to work in progress if an invoice is disputed.
- Where the repository lives and who has access after handover. A partner-owned repository that the agency cannot clone is a hostage situation waiting to happen.
- Response times, in hours, by severity, and what counts as each. “Urgent” means nothing until it has a number and a definition next to it.
- What happens outside working hours, which is the clause everyone skips and everyone eventually needs. Whether there is cover, what it costs, and how it is reached.
- Non-solicitation, in both directions, covering the partner approaching the client and the client approaching the partner.
- Who carries the professional indemnity, and whether the agency’s cover extends to work it did not perform.
- Data handling. If the client’s data touches the partner’s systems, there is a processor relationship and it needs papering, particularly under the DPDP Act.
Where the margin actually goes
White label work is priced on the assumption that the partner’s cost plus a markup equals a healthy job. Four things eat the difference, and all four are process failures rather than pricing errors.
Translated requirements. Every layer a requirement passes through loses fidelity. The client says it to the account manager, who writes a ticket, which the partner interprets. Two rounds of that and the build is subtly wrong, and the rework is unbilled.
Revision loops with no limit. The client revises with the agency, the agency revises with the partner, and nobody counts. Rounds have to be numbered in both contracts, and the numbers have to match.
Scope that arrives sideways. “While you are in there” is how a fixed-price project becomes a loss. The discipline is boring and works: anything not in the written scope gets a price before it gets a start date, however small.
Support after handover. The most commonly unpriced item in the industry. A project ends, the client keeps emailing, and the agency keeps forwarding. Either it is a retainer or it is a favour with an expiry date, and it must be one of those two in writing.
Quality control, because your name is on it
The agency carries the reputational risk and therefore cannot outsource the checking. What works is narrow and cheap:
- Someone on the agency side reviews the pull requests. Not every line, but enough to know what is arriving.
- A definition of done agreed in advance, covering tests, browser support, accessibility and performance, so “finished” means the same thing to both parties.
- Staging on the agency’s own infrastructure, so the work can be seen without asking.
- A short handover document per project: how it deploys, where the secrets live, what is not finished. This is the artefact that decides whether the agency can support the work when the partner is unavailable.
The failure modes worth naming
The partner is a reseller. Work is subcontracted again, sometimes twice. Ask directly who writes the code and where they sit, and ask to speak to them.
One person is the partner. Excellent until they are ill, and there is no continuity plan. Fine for small work, dangerous for anything a client depends on.
Time zones with no overlap. Workable with discipline, brutal without. Two hours of shared working time changes the character of the relationship entirely.
The pilot that was staffed with the best team. The first project goes beautifully and the second is a different set of people. Ask who will actually be assigned, by name, and whether that changes.
How to start one without betting a client on it
Give a small, real, time-boxed piece of work: something with a deadline that matters but a blast radius that does not. Watch what happens when the requirement turns out to be ambiguous, because that is the thing you are actually evaluating. Anyone can deliver a clear specification. What you need to know is what they do with an unclear one, whether they ask or guess, and how quickly they say so when something slips.
We take on white label delivery alongside our own client work, which is also why the constraints above are written from the inside. If you are weighing up a partner, our engagement models set out how we structure it, and the roles we staff are the same ones we place on our own projects.
How the commercials are usually structured
Three shapes cover almost all of it, and the right one depends on how well-defined the work is rather than on how big it is.
Fixed price per project. The agency knows its cost before quoting the client, which is the whole attraction. It only works when the specification is genuinely settled, and it pushes every ambiguity into a change request. Good for defined builds, poor for anything discovery-shaped.
A retained block of capacity. A number of days a month, reserved. Predictable for both sides, and it survives the reality that client work arrives unevenly. The clause that matters is what happens to unused days: rolling them forward indefinitely is how a partner ends up owing three months of work in a quarter they have already staffed.
Time and materials. Honest, flexible, and hardest to sell onward, because the agency is usually quoting the client something fixed. It suits maintenance and open-ended work far better than it suits a first project together.
Whichever is used, agree how estimates are given and how a variance is handled before the first one is wrong, because the first one will be wrong.
What the agency has to keep in-house
Outsourcing delivery does not mean outsourcing everything, and the parts that must stay are the parts that decide whether the client renews.
- The relationship. Discovery, expectations, and the difficult conversation when a date moves. Nobody else can have that conversation on your behalf.
- Enough technical judgement to review the work. Not to write it, but to know whether what arrived is what was needed. An agency with no technical read on its own deliverables is reselling, and clients work that out.
- The commercial relationship and the pricing. Never let a partner quote the client directly, however convenient it is once.
- Ownership of the accounts and the infrastructure. Domains, hosting, repositories and analytics in the agency’s or the client’s name, never the partner’s. This is the single thing that makes ending a partnership survivable.