What should an agency ask a white-label partner?
Every question on this list screens for one failure: silence under your brand when something breaks.
Answered in short
5 things that decide this
- 01Ask who actually writes the code, and whether the engineers you meet in scoping are the engineers on your client's project. Bench-and-switch is the industry's oldest trick.
- 02Ask what happens after launch: who monitors, who answers the pager, and what the response time is when your client's site breaks on a Saturday.
- 03Ask how bad news travels. A partner who has never missed a deadline is lying; a good one shows you how a slip got communicated and absorbed.
- 04Ask who owns the code, the infrastructure accounts and the credentials. The answer must be your client, in writing, with no licence-back.
- 05Ask what they refuse to build. A partner with no refusals has no standards, and their quality problems ship under your name.
Portfolio and price answer the wrong risk
Agencies vet white-label partners the way clients vet agencies: portfolio, rate, turnaround. Reasonable, and it misses the actual risk. Your client never learns the partner exists. When the build fails, the agency relationship fails, and yours is the name on it.
Industry guides on white-label partnerships report agencies taking on far more projects with a delivery partner behind them. That multiplier cuts both ways. One partner's quality problem spreads across every client you gave them.
So the vetting question is never can they build it. Plenty of shops can build it. The question is how they behave in month seven, when the launch glow is gone and something breaks at the worst hour.
- Price-first selection finds partners who priced out the parts you will pay for later: testing, documentation, and anyone answering after launch.
Ten questions, grouped by the risk they expose
People: Who writes the code, where, and do we interview them? What happens if we want someone replaced? Two questions, and they expose subcontracting chains a brochure never mentions.
Process: Show us a project that slipped and the emails that handled it. What does code review look like, and could our technical advisor join one? How do you test, and what shipped last month with a bug you caught late?
Aftermath: Who monitors production and answers the pager, at what response time, under whose name? What does handover include if we part ways? Who owns code, accounts and credentials?
Boundaries: What do you refuse to build, and when did you last tell a client no? White-label confidentiality terms, in writing, close the list: your client relationships stay yours.
- Referral economics are standard in this market, commonly a share of first-project value. Get the structure in writing before the first deal, never during it.
- ScopeYour client's problem, their engineers, your room
- Fixed termsPrice, ownership, confidentiality in writing
- Build in the openYour team sees the repo and the reviews
- Launch under your brandTheir name appears nowhere
- RunMonitoring and a named engineer behind you
The last node is the one to negotiate hardest. Launch day is easy; month seven is the product.
Related questions
01Should we tell clients we use a development partner?+
That is a positioning choice with respectable answers on both sides. What is not optional is contractual clarity: confidentiality terms that keep the partner invisible if you choose, and ownership terms that protect the client either way. Decide the story before the first project, never during a crisis.
02How do we trial a partner without risking a client?+
Give them an internal build first: your agency's own tooling, a reporting automation, something real with no client attached. You learn their communication rhythm, review quality and honesty under deadline on a project where the downside is yours alone.
03What margin structure is normal?+
Two models dominate: the agency marks up the partner's fixed price, or the partner pays a referral share on introduced work. Both are workable. What matters is that the model is written, symmetric in its expectations, and never renegotiated mid-project.
04When should an agency build in-house instead?+
When development is the product you sell most, hire for it. A partner fits when dev demand is spiky, or when clients ask for work beyond your stack, such as AI agents or complex integrations. It also fits when you want senior output without carrying senior payroll through slow quarters.
