An agency signing a white-label partner is trusting a stranger with its client relationships. This post lists the questions to ask any partner, including us, what weak and good answers sound like, and how each played out in a real engagement: a dedicated pod we ran inside a US agency’s own tools for its multi-location healthcare client.
What should be in writing before anything else
First, a client non-solicitation clause with a real duration, not a verbal assurance. Ask what stops the partner approaching your client once it holds the contact details, and how long that survives the engagement. Ours runs through the work and for 12 months after the last assignment for that client ends, and it is in the agreement.
Second, an NDA signed before any client data moves. A partner comfortable receiving client information before the paperwork exists is telling you how it will treat the paperwork generally. If you are still deciding whether to white-label the work or refer it, that decision comes first.
- 1Does the work recur as a steady queue, not a one-off project?NoOne-off: a clean referral serves the client better
- 2Is it free of licensed or regulated professional liability?NoNo margin justifies that risk under your brand
- 3Does someone on your side have time to review the output?NoUnreviewed, it is a referral with your logo on the risk
- 4Is an NDA signed before any client data moves?NoKeep the data back until the paperwork exists
- 5Is client non-solicitation in the agreement, with a real duration?NoA verbal assurance is not enough: put it in writing
The questions, and what a good answer sounds like
Most lists of questions stop at the question. The useful part is knowing what to listen for. The last column shows what the answer was in the healthcare engagement, as recorded in the case study.
| Ask | Weak answer | Good answer | In the healthcare engagement |
|---|---|---|---|
| Who exactly does the work, and is it the same people each time? | “Our bench allocates the best available people” | A named team that stays with your account | A dedicated pod, the same people throughout, rather than capacity drawn from a shared bench |
| Whose tools, templates and voice will you work in? | “We deliver in our formats; you can re-brand it” | Yours: your tracker, your templates, your reporting cadence | The agency’s project tracker and templates, and its standups; reports in its own templates |
| Where does quality review happen? | “Your team reviews before it goes to the client” | Inside the partner, before handover | Work reviewed and tested inside the pod, so the agency’s producers stopped being the quality gate |
| What is in writing about your client? | “We would never approach them” | A clause with a named duration, and a named contact | NDA-backed, client-protection terms in the contract, a named contact on our side |
| Can I see your rates before a project exists? | “Pricing is on request, per project” | A rate card in hand before the first brief | Our partner bench starts with a signed NDA, then the rate card and capability pack, with no project required |
The second row matters more than it looks. A partner that delivers in its own formats pushes a translation step onto you for every deliverable, and that step quietly eats the margin the arrangement exists to create. We chose to work entirely in the agency’s systems for that reason, although delivering in ours would have been easier for us.
The proof question: ask about a time capacity was tight
Logos tell you a partner has done business with someone. They say nothing about how it behaves when a deadline is at risk. So ask for a specific time capacity was tight, and what the end client saw.
A weak answer is some version of “we have never really had that problem”. That is either untrue, or true only because the partner has not yet carried enough volume to be tested.
Here is our answer from the healthcare engagement. The agency was winning work faster than it could deliver, and the backlog had become a risk to its main client relationship. We triaged the whole backlog into quick wins, structural work and things that should never have been promised, then rebuilt the client-facing schedule around what could actually ship.
The first fortnight was slower than either side wanted, because working inside someone else’s tooling and client history takes a real ramp. And the approval chain, not delivery capacity, set the pace: in healthcare the reviewers’ queue competes with clinical and legal priorities. The record of the outcome is in the healthcare delivery case study.
The part to probe is what happens when something slips. White-label cover is easy while everything is on schedule. It is tested when the agency has to explain a delay to its client in its own voice, which only works if the partner reports the problem early and completely enough for the agency to own it.
Questions about access and endings
Ask who else can see your client’s information once it is in the partner’s systems, and what happens to that access when the engagement ends. It feels adversarial to ask a company you are about to trust, which is why it gets skipped, and why it is worth asking of anyone, including us.
Ask too what the partner does if your client contacts it directly. The answer you want is that it tells you and resolves the enquiry through you. That is what we commit to, in writing, on our partner bench.
When white-label is the wrong arrangement
Good answers to every question above still do not make white-label right for every job. It is the wrong arrangement when:
- The work is a single one-off project. The overhead of a partnership is not worth one invoice, and a clean referral serves the client better.
- The work carries licensed or regulated professional liability. Presenting someone else’s regulated work under your brand is a risk no margin justifies.
- Nobody on your side can review the output. An unreviewed white-label deliverable is a referral with your logo on the risk.
It works best when the work recurs as a steady queue, sits next to what you already sell, and someone on your side has time to review it.
