You sell websites, but you do not build them in-house, so you are looking for a partner to build them under your brand. It is a genuinely important decision, because this partner will be doing work your name goes on, and if they get it wrong, it is your client who is unhappy and your reputation that takes the hit, not theirs.
The temptation is to judge candidates on their portfolio and pick the one whose work looks best. That is the wrong test. The real risks in a white label relationship sit in how they communicate and support, not in whether they can build an attractive site. This article sets out the five questions that actually tell you whether a partner is safe to put your brand on, and why the answers matter more than anything in their folio.
Why the portfolio is the least useful thing you are shown
When you start evaluating white label partners, the first thing anyone shows you is their portfolio, and it is the thing you should weight the least. That is not because build quality does not matter, it is because build quality is table stakes. Any partner worth considering can produce a good-looking, functional website. If they could not, they would not be in business offering the service. So a nice portfolio tells you only that they clear the minimum bar, which nearly all of them do.
The things that actually determine whether a partnership works, or blows up in your face, are almost never visible in a portfolio. How they communicate. Whether they stay behind your brand or step in front of it. What happens when a live site breaks on a weekend. Who owns the work if you part ways. How they handle a client who keeps asking for changes. These are the factors that decide whether the relationship makes your life easier or becomes a recurring headache, and not one of them shows up in a gallery of finished sites.
So look past the folio quickly. The questions below are where the real evaluation happens, because they probe the things that genuinely vary between partners and genuinely affect you.
Question one: who does the client actually hear from
The entire point of a white label partnership is that your client experiences the work as coming from you. So the first question is about every point where the partner could accidentally, or deliberately, become visible to your client. And there are more of those points than people expect.
Think through the full journey. When an email goes to the client, whose name and address is on it? When a staging or preview link is sent, whose branding does the client see when they open it, yours or the partner's? When the client has a support question and it gets answered, whose name is on the reply? When an invoice or a piece of documentation reaches them, whose brand is on it?
Each of these is a moment where the partner can quietly surface in front of your client and break the illusion that you built the site. A good white label partner has thought this through and stays invisible by default, with their branding nowhere the client can see it. A careless one lets their own name leak through in a staging URL or a support signature, and suddenly your client knows you outsourced the work. Ask specifically how each of these touchpoints is handled, because "we're white label" is easy to say and the detail is where it is actually proven.
Question two: what happens after launch
A website is not finished at launch, it is just beginning its life, and this is where a lot of partnerships quietly fail. So the second question is about everything that happens after the site goes live. The build is the easy, visible part. Support is the part that tests the relationship.
Ask what support actually looks like once a site is live. What hours is the partner available, and do those hours suit your clients? If something breaks, how does a support request reach them and how is it handled? And critically, who fields the problem when a client's site goes down on a Saturday, when the issue is urgent and the client is looking to you for an answer?
You need to know whether the partner is reachable and responsive when it matters, or whether a weekend outage means your client sits broken until Monday while you have nothing to tell them. Rather than fixating on a specific promised response time, which is easy to quote and hard to verify, focus on understanding how support genuinely works, who is on the other end and when. A partner's white label web development is only as good as what happens the first time something goes wrong after launch, so probe that scenario specifically before you commit.
Question three: who owns the build
This is the question people forget to ask until it is too late, and it is one of the most important. You need to know, up front, who owns what. Who owns the code the site is built on? Who owns the content? And, the crunch question, what happens to all of it if you and the partner stop working together?
The time to settle ownership is before the first build, not after a relationship has soured. If you have not agreed it, you can find yourself in a position where sites you sold to your clients are effectively controlled by a partner you no longer want to work with, and moving them is difficult or impossible. That is a genuinely bad place for an agency to be, because your clients are yours but the thing you sold them is held by someone else.
Ask plainly what you would be able to take with you if the partnership ended: the code, the content, the hosting, the client sites. A straightforward partner will give you a clear answer and be comfortable putting it in writing. One who is evasive on ownership is telling you something, and it is worth hearing before you build a book of clients on top of them.
Question four: how are revisions scoped
The fourth question cuts through a common piece of marketing that sounds generous and causes problems: unlimited revisions. It is worth understanding why unlimited revisions and a fixed timeline cannot both be true at once.
If revisions are genuinely unlimited, then a project has no defined end, because the client can always ask for one more change, which means the timeline cannot be fixed. If the timeline is fixed, then revisions must be bounded in some way, or the deadline is meaningless. A partner who promises both is either not being straight with you or has a definition of one of those terms you have not been told. Neither is comforting.
What you actually want is a clear, honest scope: how many rounds of revisions a build includes, what counts as a revision versus a new request, and what happens when a client wants more. That clarity is what lets you resell the service confidently and set your own client's expectations accurately. Vague generosity on revisions is a problem waiting to happen, usually at your expense, so ask exactly how revisions are scoped and prefer the partner who gives you a straight, bounded answer over the one who promises the world.
Question five: what will they not do
The last question is counterintuitive, because you are looking for a partner willing to say no. Ask what they will not do, and treat clear limits as a good sign rather than a drawback.
It seems backwards, but a partner who agrees to absolutely everything is harder to resell than one with honest boundaries. A partner who tries to be all things risks overcommitting, missing deadlines and doing a mediocre job across too wide a range, all of which lands on your brand. A partner who is clear about what they do well and what they do not take on is a partner you can rely on, because their yes means something.
Clear limits also make the relationship easier to manage: you know exactly what you can promise your clients and what you need to source elsewhere, rather than discovering the edges of their capability mid-project. So when a potential partner tells you plainly that a certain kind of work is not something they do, do not count it against them. Count it in their favour. It is far easier to build a dependable, resellable service on a partner with honest boundaries than on one who says yes to everything and delivers unevenly.