White-label web development, explained properly

White-label web development means a studio builds websites that go out under your agency's name. Your client deals with you. The work appears in your portfolio, not the builder's. Nothing in the footer, the code, the repository or the CMS admin says who actually did it.

That is the definition. The interesting part is everything the definition leaves out — and that is where agencies get hurt.

Why agencies use a production partner

Four reasons, in rough order of how often we see them:

Demand arrives in lumps

You win three projects in a fortnight, then nothing for six weeks. Hiring to the peak means carrying the cost through the trough; hiring to the trough means turning work away. A production partner converts a fixed cost into a variable one.

A capability you do not have and do not want full-time

You are a WordPress shop and the client wants Webflow. Or the design has scroll-driven motion and nobody in-house writes GSAP. Or the site fails Core Web Vitals and you need someone who has fixed that before.

Senior capacity, without a senior salary on the payroll

Small agencies often cannot justify a senior developer's full-time cost but badly need senior judgement on two projects a quarter.

Founder time

The most expensive thing in a five-person agency is the founder building websites at night instead of selling. A partner buys that time back at a knowable rate.

Three models, and when each one fits

Per project

You send a scope or a Figma file; you get a fixed price and a date. Best when your pipeline is genuinely lumpy and you want no commitment. The trade-off is that you are queued behind whoever booked capacity, and the effective hourly rate is the highest of the three.

Reserved monthly capacity

You buy a set number of senior hours each month at an agreed rate. Best once you have steady flow, because you can quote work before you have the people for it, and the rate is lower. The trade-off is that unused hours are usually use-it-or-lose-it, or roll over only partially — check which.

Staff augmentation

A developer joins your standups and works inside your process, billed monthly. Best for long builds and product work. The trade-off is that you are now doing the managing, which is a real cost that does not appear on the invoice.

A practical sequence: start per project, move to reserved capacity once you have used the same partner three or four times and can predict flow, and only consider augmentation when a single client's work is continuous.

How the margin actually works

The maths is simple and worth doing on paper before your first project, because the number that matters is not the discount off your own rate.

You quote the client for the outcome. You pay the partner for the production. Your margin is the difference, minus the time your own team still spends — and that last term is the one agencies forget.

• Scoping and briefing the partner: real hours, usually yours, usually senior.
• Reviewing what comes back before the client sees it. You cannot skip this and you should not want to.
• Client communication, which stays entirely with you. This is often the larger half of a project.
• The gap between what the client asked for and what the brief said, which someone has to absorb.

Agencies that make white-label work profitably tend to do two things: they write briefs properly, because a vague brief is paid for twice; and they treat the partner's price as a cost of goods rather than as a discount on their own labour. Agencies that struggle usually quoted the client as if the partner cost was the whole cost.

What "white-label" has to mean in the contract

"White-label" is a marketing word until it is a list of obligations. These are the clauses that matter, and every one of them exists because somebody got burned without it.

No attribution, anywhere

Not the footer. Also: not the theme folder name, the package name, the commit author, the CMS admin, the staging URL, the PDF metadata, or a "built by" comment in the source. Ask specifically about each — the footer is the one everyone remembers.

No client contact

The partner does not email, call or add themselves to your client's channels unless you introduce them, and then only where you are present. Worth stating, because "just checking one thing with the client" is how the arrangement unravels.

No portfolio use, no exceptions by default

The partner may not show the work, screenshot it, name the client or refer to it in a pitch. If they want a version of that right, it should be a specific written permission for a specific project, given by you.

Non-solicitation

The partner will not approach your clients for the duration and for a period after — typically 12 to 24 months. Also worth covering your staff in both directions.

IP assignment on payment

The design and the custom code become yours (or your client's) when you pay. Make sure it says on payment and not on completion, and that it covers work product created before a project was cancelled.

Accounts in your name

Your repository, your Webflow workspace, your client's host. No licence held in the partner's name, because a licence in their name is a dependency you did not agree to.

Confidentiality that survives the relationship

A mutual NDA that outlives the contract, and a stated way that files get deleted when you are done.

What happens if they disappear

The least romantic clause and the most valuable: a defined handover of code, credentials and documentation on termination, within a stated number of days.

The failure modes

Six ways this arrangement goes wrong. Four are preventable with process; two are only preventable by choosing a different partner.

1. The brief was a Figma link and a sentence. The build is technically correct and completely wrong, and nobody is at fault. Fixable: a written scope covering breakpoints, CMS behaviour, empty and overflowing content states, form destinations, and what happens on error.
2. Quality varies between projects because a different person built the second one. Fixable: ask who is on it, and expect a named answer.
3. You become the telephone. Client says something, you relay it, partner interprets it, you relay the result. Fixable: one shared channel, written decisions, and a weekly summary you can forward.
4. Timezone friction turns a two-day fix into a fortnight. Fixable, mostly, by batching feedback into one daily message rather than a trickle, and by agreeing one overlap window that both sides actually keep.
5. The partner is a reseller and the actual work is three layers down. Not fixable. Detect it by asking who specifically will build it and then speaking to that person.
6. They put your client's site in their portfolio. Not fixable after the fact, which is why the clause above exists.

How to trial a partner without risking a client

Never test a new production partner on a project that matters. The sequence that works:

1. Pay for something small and real — a landing page, one CMS template, a performance pass on an existing site. A few hundred to fifteen hundred dollars. Paid, not free: a free trial is delivered by whoever is spare.
2. Brief it exactly as you would brief a real project, including the parts you would normally leave until later. You are testing the process, not the pixels.
3. Watch four things: did they ask the questions a competent builder would ask; did it arrive when they said; how did they handle the one piece of feedback you deliberately made ambiguous; and is the handoff documentation any good.
4. Look at the code or the Webflow class structure, or have someone who can. Neat, maintainable and boring is what you want.
5. Then, and only then, put a client project through.

An agency that will not sell you a small paid pilot is either too busy for you or too keen to lock in a large commitment. Both are useful to know.

The offshore question, answered directly

Most white-label production capacity is in lower-cost countries, ours included — we are in Cebu, in the Philippines. There is no point pretending the cost difference is not part of why this market exists.

What matters is what you are actually buying. Cheap capacity and senior capacity are different products that are frequently sold with the same words, and the difference shows up in the same places every time: whether anybody asks about the CMS's empty states, whether the build survives a client pasting in three paragraphs where the design had one line, whether the redirect map exists before launch, and whether the handoff document is written for a developer or for nobody.

Judge a partner on the pilot and on the specificity of their questions, not on their postcode in either direction. A studio anywhere can be careless, and a studio anywhere can be excellent.

Questions to ask on the first call

• Who will build this, and what else are they on that month?
• Show me a handoff document you have given another agency, with the names taken out.
• What do you need from me in a brief before you will quote?
• What is your QA list before I see a build?
• What is your policy on client contact, and what has happened when a client contacted you directly?
• What are your rates — per project, per month, and what an urgent turnaround costs?
• What happens if the build is late, and what happens if my client cancels mid-project?
• Who owns the code and the accounts, and at what moment?

How we run white-label work — Our own terms, rates and process are published, including the pilot — so you can answer most of the above without a call.

In short

White-label development is a good arrangement when it converts an unpredictable cost into a predictable one, and a bad one when it is used to paper over a brief nobody wants to write. Get the contract clauses right once, write proper briefs, start with a paid pilot, and keep the client relationship entirely yours. The rest is just project management.