If you run a small agency, or you are a business owner who has been pitched by one, you have probably met the phrase "white label". It gets used loosely, so here is a plain explanation of what it means, how the arrangement works in practice, and the questions worth asking before you sign anything.
The short definition
A white label agency does work that is delivered under another company's brand. The end client sees only the company they hired. Behind the scenes, a specialist partner builds the website, the software or the campaign. As one partnership glossary puts it, the reseller sells a product or service that someone else produced, under the reseller's own name.
The word "white" comes from products sold with a blank label, so any retailer can put their own on it. Supermarket own-brand cereal is the usual example. Agencies borrowed the idea for services.
How it works in practice
There are two parties and one client. The front agency owns the relationship: it takes the brief, quotes the project, handles invoices and answers the phone. The white label partner owns the delivery: it builds, tests and fixes. The client usually never hears the partner's name, and the partner does not contact the client directly unless the front agency asks it to.
A typical small project looks like this. A design studio signs a client who wants a booking site with online payments, in two languages. The studio does not employ a developer. It sends the scope to a partner, agrees a price and a deadline, and the partner delivers code and documentation under the studio's name. The studio presents it, handles feedback and sends the final invoice.
Agencies use this model mostly for work they would otherwise have to staff full time. Marketing teams use it for SEO and email production, and development shops use it for overflow engineering. The common thread is the same: the agency adds a service without adding payroll.
What the front agency gets
Three honest benefits come up again and again. Speed, because a partner already has a team and a process. A wider menu, because the agency can say yes to a request outside its core skill. And flexibility, because capacity grows when a project lands and shrinks when it ends, with no hiring or layoffs.
These are real advantages for a studio with four people and a client asking for a custom CRM.
Money works simply. The partner quotes a fixed price per project, and the front agency adds its own margin for the relationship, the project management and the risk it carries. Because the partner's price is written down before work starts, the agency knows its margin before it quotes its own client. Without that, a white label deal turns into guesswork, and the guesswork is paid by whoever signed first.
What can go wrong
The risks are mostly about control and trust, and they are worth naming.
Quality sits under your name. If the partner misses a deadline or ships buggy code, your client blames you, not them. Ask to see past work and ask who actually does the building.
You depend on someone else's availability. If your partner is full for six weeks, so are you. Agree on response times and capacity in writing.
Ownership can get muddy. Who holds the source code, the hosting account and the domain when the project ends? If the answer is "the partner", you have a problem the day the relationship stops. The safest setup is one where the client's own accounts hold everything and the partner works inside them.
Communication can get awkward. When a client asks a technical question, the front agency has to answer without having built the thing. A good partner writes short, clear notes so the agency can answer with confidence.
Questions to ask a white label partner
Before you commit to a first project, ask these:
- Will you sign an NDA and a non-solicitation clause, and will you stay invisible to my clients?
- Who owns the code, the hosting and the API keys at the end?
- Can I see two finished projects, and can I speak to the person who built them?
- How do you handle a change request halfway through?
- What do you do when something breaks after launch, and who answers?
If the answers come quickly and in writing, that is a good sign. Vague answers on ownership are the one to take seriously.
Is it only for agencies?
Mostly, yes. If you are a business owner who needs a website or a piece of software, you do not need a white label arrangement: you can hire a development team directly and keep one fewer layer between you and the people doing the work. White label makes sense when you resell the work to your own clients. If you are not sure which side of that line you are on, look at who your client is. If it is a customer of yours, you are the front agency.
How we handle it
At Kaishift we work with agencies this way: the agency keeps the client, we do the build, and our name stays off the project if the agency prefers. We design systems so they run on the client's own cloud, repositories and API keys, which removes the ownership problem above. You can read how the programme works on our agencies page, see what we can build under the web design and custom development services, or book the free 30-minute call and talk through a project you are weighing.
