How to choose a white label development partner

Most guides to this decision are about quality: look at the portfolio, check the reviews, ask about the stack. Reasonable, and not where agencies actually get hurt.

The arrangements that go wrong are rarely the ones where the code was bad. They are the ones the agency could not leave. The partner held the repository, or the client's hosting account, or the only person who understood the build, and by the time that became clear there was a live client in the middle of it.

So these questions are about reversibility and access, not about skill. Skill is visible in a portfolio. The rest is not visible until it matters.

Will the same engineers stay on my account?

The single question with the most predictive power, and the one most likely to get a slippery answer.

A pool model means whoever is free picks up your ticket. It works for discrete tasks and fails for anything with history, because nobody accumulates the knowledge of why your client's checkout behaves the way it does. Six months in, you are still explaining context that a stable team would have internalised in week three.

A good answer names people and commits to them in writing, and tells you what happens when one is ill or leaves. A bad answer is "we assign the best available specialist", which is the pool model in a nicer suit.

Whose process do we use?

If the partner imports their board, their sprint cadence and their definition of done, you now run two processes with a translation layer between them, and every status question crosses a boundary.

A good answer is "yours", followed by questions about your board and your branching rules. A bad answer describes their methodology.

Can I talk to the engineers directly?

An account manager between you and the work adds a day to every question and removes the detail from every answer. It also hides the thing you most need to know, which is whether the people doing the work are any good.

A good answer puts you in a shared channel with the engineers. A bad answer is "your dedicated account manager will coordinate", which means you cannot assess the team and will not know about a problem until it is a delay.

In whose name are the repositories, servers and accounts?

This is the one that turns an inconvenience into a hostage situation. If the partner's organisation owns the GitHub repo, their account holds the hosting, or their email receives the domain renewal, leaving them is a negotiation rather than a decision.

A good answer is yours or your client's, from day one, with the partner added as a member. A bad answer is "we manage all of that for you", however helpfully it is phrased.

We found the inverse of this on our own infrastructure: a client's live site was quietly serving two dozen images from a staging host we controlled. Nobody did it deliberately. It just accumulated, and it would have broken the moment the tidying-up happened.

What happens when my client changes the brief halfway through?

Clients change briefs. The question is what that costs and how fast you find out.

A good answer distinguishes small changes that fit inside the current cycle from changes that alter the shape of the work, and re-estimates the second kind in writing before starting. A bad answer is either "no problem, we are flexible", which means the cost appears later without warning, or a change-request process measured in weeks.

Who answers when it breaks on a Friday evening?

Most of the time nothing breaks. The arrangement is defined by the exception.

A good answer is a named person, an agreed response window, and honesty about what falls outside it. A bad answer is a support email address, or a promise of 24/7 coverage from a team of six, which cannot be true.

What is the notice period, and what happens on the last day?

Ask for the exit to be described concretely: what is handed over, in what state, and how long it takes.

A good answer is short and boring, because a partner who has done clean handovers can describe one from memory. A bad answer is vague, or involves a fee, or has never happened before.

The cheap way to test all seven

Do not take the answers on trust and do not start with the big project. Give a bounded first piece of work: something real, small enough that losing it costs a fortnight, with a defined end.

You learn more from one two-week engagement than from any number of reference calls, because every one of the questions above gets answered by behaviour rather than by sales copy. If the first piece goes well, the second can be larger. If it does not, you found out cheaply and with no client exposed.

When white label is the wrong answer

Worth saying, since this is on an agency's own site.

If the work is the thing your agency is known for, keep it in house. Subcontract the capability you sell and you eventually cannot sell it, because nobody on your staff can speak to it in a pitch.

If the project is small enough for one freelancer and short enough to supervise directly, a freelancer is cheaper and simpler. The overhead of a partner arrangement only pays back across repeat work.

And if you are subcontracting mainly to be cheaper, check the arithmetic again including your own management time. The case for a partner is capacity you can turn on and off, not a lower hourly rate.

Our own answers, in one place

Published rather than left to a sales call, so you can compare them against whoever else you are speaking to.

Question	Smart-UI
Same engineers?	Named in the contract, not a pool
Whose process?	Yours. Your board, your branching rules, your cadence
Direct access?	Shared channel with the engineers, no account manager
Who owns the repos?	You or your client, from day one
Mid-build changes?	Small ones inside the cycle, larger ones re-estimated in writing first
Out of hours?	Named contact and an agreed window, written down
Exit?	Notice, handover, and you already hold everything
Confidentiality	NDA before the first call, nothing published without written approval

If that comparison is useful, the detail is on our agency page, and a longer account of how an embedded team works in practice is in employ or contract a team.

And if you are weighing a partner right now, send the scope and the deadline and you will have a fixed price within 48 hours, under NDA if you prefer.