What to look for in a white-label development partner

A good white-label partner lets you say yes to work you’d otherwise turn down. A bad one puts your client relationship at risk, eats your margin in fixes, and leaves you explaining delays you didn’t cause.

I’ve spent years on the agency side, leading client builds and acting as the main contact for the client, so I know what agencies need from the people behind them. These are the things that separate a partner you can rely on from one you’ll regret.

1. Who actually writes the code?

This is the most important question and the one most often skipped. Many “partners” are sales teams that pass work to whoever is available. Ask who will build your project, how senior they are, and whether that changes after you sign. If you meet a lead engineer on the sales call, make sure they are the one doing the work.

2. Will they stay invisible?

White label only works if your client never has a reason to wonder. Agree up front:

• They never contact your client unless you ask them to
• If they join a call, they join as part of your team, under your brand
• Your client’s work stays off their portfolio unless you give permission
• They are happy to sign your NDA before you share the brief

3. Who owns the code, and where does it live?

The answer should be simple: you and your client own everything, and it lives in your repositories and your hosting accounts from day one. Be wary of anyone who builds in their own accounts and “transfers it at the end”. That’s leverage you don’t want them to have.

4. Do they fit into your process?

A partner should use your Slack, your Jira or Linear, your Figma and your staging environments, not add another portal your team has to check. Time zones matter too. A UK partner working UK hours means problems get solved the same day.

5. Can they show quality, not just screenshots?

Portfolios show what something looks like, not how it’s built. Ask about the things your client will only notice when they go wrong:

• Performance: do their sites pass Core Web Vitals? Can they show real numbers?
• Accessibility: do they build to WCAG 2.1 AA as standard?
• Testing: what automated tests do they write, and how do they stop regressions?
• Monitoring: will they know when something breaks before your client does?

6. How do they estimate and handle change?

Every project changes. What matters is how they deal with it. Good partners estimate with clear assumptions, flag scope changes before doing the work, and never surprise you with an invoice. Ask how they handled the last project that went over.

7. What happens after launch?

Some agencies want to hand everything over to their own team. Others want the partner to stay on for support. Either is fine, but agree it before you start. Ask what a handover includes: documentation, a walkthrough, and code your own developers can pick up without calling them.

8. Does the pricing work with your margins?

Fixed-price projects protect you when the scope is settled. Day rates suit projects that are still evolving. Monthly retainers work for ongoing client support. A good partner will offer whichever model fits, and will be open about their rates so you can price your client work with confidence.

Red flags

• Nobody technical on the sales call
• Vague answers about who will do the work
• Code built in their accounts, not yours
• No questions about your client’s business or users
• An estimate with no assumptions written down

Questions for the first call

1. Who will build this, and can I speak to them now?
2. Can you work in our repositories, tools and brand from day one?
3. Will you sign our NDA and never contact our client directly?
4. How do you handle performance, accessibility and testing?
5. What happens when the scope changes?
6. What does handover look like if we take it in-house?

Start small

The best way to test a partner is a small, paid piece of real work: a single feature, a landing page or a performance audit. You’ll learn more in two weeks of working together than from any number of calls.

If you’re an agency looking for extra hands, here’s how we work with agencies. Everything above is how we’d want to be judged.