How does white label development work?
An agency lands a project its team cannot build. A partner firm builds it under the agency's name. Done well, the client never feels the seam.
The arrangement, defined
5 things that decide this
- 01White label development is an arrangement where one firm sells and fronts a software project while a partner firm builds it, with the client relationship, the brand and the margin staying with the seller.
- 02The commercial shape is one of two: the agency marks up the partner's engagement and owns delivery risk, or refers the work outright for a fee, with service-business referral norms commonly running 10 to 15 percent of first contract value.
- 03Three documents make it safe: an NDA, a non-circumvention clause so the partner cannot approach the client directly, and a communication protocol saying whose email, whose meetings and whose name appear where.
- 04Quality assurance stays with the agency even when engineering does not. The agency signs off what ships, because its brand is on the result.
- 05The question that separates good partners from cheap ones is post-launch: who monitors, who fixes, and under whose name, when something breaks in month seven.
The demand outgrew the bench
Marketing and design agencies keep getting asked for things beyond their bench: a client portal, an integration, an AI feature, a product build. Turning the work down sends the client shopping, and the shop they find may also sell what the agency sells. White labelling keeps the relationship and the revenue while someone with the right bench does the engineering.
Industry writing on agency operations points the same direction: agencies using white-label delivery partners report taking on multiples of the project volume they could staff alone. The model scales the agency's sales capacity instead of its payroll.
White label against referral
| Dimension | White label | Referral |
|---|---|---|
| Who the client contracts with | The agency. The partner is invisible. | The development firm, introduced openly. |
| Where the margin sits | Agency marks up the build and owns the relationship. | A fee, commonly 10-15% of first contract value. |
| Who carries delivery risk | The agency, contractually. The partner, practically. | The development firm, in the open. |
| When it fits | Recurring work, retainers, a service line the agency wants to own. | One-off projects outside the agency's story. |
Agree the boring parts before the first project
White label arrangements fail on logistics, not engineering. Whose Slack does the client join. Do partner engineers attend client calls, and introduced as what. Who writes the status update, in whose voice. Which side owns the spec when the client changes their mind. Every one of these has a right answer, and all of them belong in the partnership agreement rather than being improvised on project one.
Code ownership needs the same clarity. The clean pattern is that the client owns the code outright, through the agency, with no licence-back to anyone. An arrangement where the partner quietly retains rights is a problem deferred to the worst possible moment, which is due diligence.
- 01Put non-circumvention in writing, both directions, with a survival period.
- 02Run a small first project before promising a client anything large.
- 03Agree the escalation path for the day a deadline is at risk, while nobody is angry.
Agency questions
01Do clients ever find out, and does it matter?+
Sophisticated clients often assume specialist work involves partners, and the honest framing is that the agency directs a delivery team. What damages trust is concealment failing mid-project, not the model itself. Decide the disclosure line up front and hold it.
02How should an agency price white-labelled work?+
From the value of the outcome to the client, not from the partner's cost plus a habit markup. The agency is providing the relationship, the translation and the accountability, which is real work. Underpricing it is the fastest way to resent the model.
03Who handles the client's technical questions?+
The agency fronts them, with the partner supplying answers, or a partner engineer joins calls under the agency's banner. Both work. What fails is a client's technical question bouncing for days because the protocol never named an owner.
04What should the agency check about the partner's engineering?+
Ask to see a shipped production system and who runs it now, not a portfolio page. Review how they document, test and hand over. The agency cannot audit code quality directly, but it can audit the habits that produce it.
Related
- Staff augmentation →You interview every engineer. Decline anyone.
- Custom software development →Built for one business. Kept running after launch.
- Staff augmentation vs outsourcing →Which engagement model fits which situation.
- Dedicated development team →A standing team under your direction, without the hiring.
