Short answer
With white-label development, your agency sells a software project under its own name while an external developer does the technical work. You keep the client relationship and the margin without hiring a development team. It works well for integrations, portals, web applications and building designs, provided scope, ownership, confidentiality and communication are agreed in writing first.
What is white-label development?
White-label means work is delivered under someone else’s brand. For a web agency or design studio this means: you sell a project to your client, you are the point of contact, and an external development partner builds the software. The client sees your name on the quote, the invoice and the end product.
The difference from simply hiring a freelancer lies in the agreements. With white-label it is settled up front who talks to the end client, whether the developer may be named and who owns the code. That lets you offer the work confidently as your own service.
When does it make sense for an agency?
White-label development pays off when there is client demand but no permanent development capacity. Familiar situations:
- A client asks for an integration with their CRM, accounting or web shop, and your team mainly builds websites.
- You design a client portal or dashboard in Figma but have nobody to build it as a working application.
- Your developer is fully booked and a new project would have to wait for weeks.
- You want to offer AI or automation without hiring someone first.
- A full-time developer is too expensive for the varying number of projects per year.
It is less suitable when the work is the core of your own service and you need it every day. Then an in-house developer makes more sense over time.
White-label or referral: the difference
There are two common ways to work with an external developer. Which fits depends on how much you want to manage yourself.
| White-label | Referral | |
|---|---|---|
| Client relationship | Stays with the agency | Moves to the developer |
| Brand towards the client | The agency | The developer |
| Project management | Agency coordinates, developer builds | Developer handles everything |
| Agency earns | Margin on the project | Referral fee |
| Good fit when | You want to keep the client and repeat work | You do not want to manage the project |
What it costs and how the margin works
With white-label you pay the developer an agreed project price and set your own price towards the client. The difference is your gross margin, which covers your own sales, project management and other costs.
| Item | Amount |
|---|---|
| You sell the project to the client | €8,000 |
| You pay the development partner | €5,500 |
| Your gross margin, before own costs | €2,500 |
With a referral it is the other way round: the developer contracts the client and pays you a fee. A range of 5 to 15% of the project value is a reasonable starting point, depending on how much you contribute to the sale. For a €5,000 project at 10%, that is €500.
For referrals, also agree how long an introduction counts, when the fee is paid (on signature or on client payment) and which clients are excluded.
What to put in writing first
Most problems in partnerships do not start in the code but in what was never agreed. At minimum, agree on:
- Who the contracting parties are and who owns the end-client relationship.
- Scope, deliverables and acceptance criteria.
- Timeline, dependencies and how changes are handled.
- Price, VAT, invoicing and payment milestones (for example a deposit and milestones).
- Ownership of the code and the right to reuse generic components.
- Confidentiality and access to client systems.
- GDPR roles and a data processing agreement when personal data is involved.
- Hosting, backups, monitoring and maintenance after delivery.
- Whether the developer may be named to, or contact, the end client.
- Liability, termination and handover.
How a white-label project runs
Brief
You share a short description of the project, preferably with designs or examples.
Scope and estimate
The developer asks questions, describes the scope and gives an estimate.
Agreement
Responsibilities, price and timeline are put in writing.
Build and test
Development in short iterations, with progress per milestone.
Acceptance
You review the result and coordinate acceptance with the client.
Delivery
Go-live and handover, optionally followed by maintenance.
What to look for in a partner
- Real work you can inspect, with an honest description of what the partner did.
- An estimate with assumptions and exclusions, not a price without questions.
- Direct access to the person building, so questions do not pass through several layers.
- Clear agreements on code ownership and handover, so you do not become dependent.
- Willingness to start with a small, paid pilot project.
A small pilot is the safest start. You see how the collaboration works in practice before building a larger client project on it.
A client project you cannot build yourself?
I work white-label or through referrals for agencies. Start with a small, paid pilot project.