ESTIMATED READ TIME: 6 minutesMost agencies come to us with the same question, and it usually happens after talking about services, turnaround and price.
It’s “will my client know you exist?”
If you’ve spent years earning a client’s trust, bringing in someone outside your team feels like a risk. Not really a technical risk. A relationship one.
I’ve been building and maintaining WordPress sites for over 15 years, the last five of those as 40 North. In most conversations about white-label development, that question comes up last. People compare hourly rates, they compare turnaround times, and the visibility question surfaces later, usually at a bad moment, when a stray email signature turns up in a client’s inbox. So we put it first.
Visibility is a setting, not a policy
Plenty of development partners have one mode. They’re either fully hidden or fully credited, and you take what you get.
We think that’s backwards. How visible your partner should be depends on the client, the project, and sometimes the week. A long-standing client who would be rattled by a new name needs one thing. A client who keeps emailing you at 9pm about a plugin update needs something else.
We call it the Visibility Spectrum, and there are three settings.
Invisible. Fully white-label. The name 40 North never appears anywhere the client can see it. Every message routes through your team. We talk to you, never to them. You bill the client, you own the relationship, and if we’ve done our job the client has no idea anyone else was involved.
Rebranded. We work under your brand. You set up an email address at your domain, we operate from it, and to the client we’re simply your staff. We scale up when you’re slammed and step back when you’re not. This is the on-demand extension of your team.
Visible. The client knows we’re the technical partner. You can keep billing and the primary relationship while we’re named as the people doing the build and support. Or you can hand the ongoing work to us entirely, so you’re not managing maintenance you never wanted.
You pick the work first, then you pick how visible we are while we do it. An agency can buy a build at the Invisible setting and ongoing support at the Visible one. The flexibility is the point.
What to actually check before you sign anything
Visibility is the question people skip. These are the ones worth asking after it.
Who is actually doing the work?
Ask for names. A lot of white-label shops are a thin layer over a rotating pool of subcontractors, which means the person who learns your client’s site in March is gone by August. That churn is invisible on a rate card and expensive everywhere else.
We’re three people. Matthew, Brennan, and Jessica. We take on a handful of clients at a time on purpose, so you always know who is in your project.
What happens when something breaks on a Friday?
Not “what’s your SLA.” Ask what actually happened the last time a client site went down. You’ll learn more from the story than from the number.
Our average ticket turnaround is around 24 hours, and small things are often done in under 30 minutes. We also keep professional hours. We’re not going to promise you a 2am response, because a partner who promises that is either lying, burning out, shipping the work to a mediocre developer overseas, and none of those helps you in the long run.
How do they handle scope?
The failure mode in white-label work isn’t bad code. It’s a fuzzy quote that turns into an awkward conversation three weeks in, while your client is waiting. Ask how changes get tracked and who tells the client when something is out of scope. We quote the build, we ship the build, and changes go in writing.
Can they stay invisible when it counts?
If a partner offers full white-label, ask them how it actually works. Where does their name show up by default? Email signatures, support ticket footers, commit messages, the site’s admin footer, the WHOIS record on a domain they registered for you. Invisible is a discipline, not a checkbox, and most of the leaks are boring.
Do they understand they’re not your competition?
This one matters more than it sounds. A development partner who quietly wants your client relationship is a problem you’ll discover late. We don’t pitch our partners’ clients. When a direct referral comes to us, we’d rather route it back through an agency.
The part nobody puts on a rate card
The best white-label relationships we have are ones where the agency looks like the hero to their client, every single time, and we’re happy to stay off the marquee. Some of our partners have been with us since we launched.
That only works if the arrangement is honest from the start. You know who’s doing the work. Your client sees exactly as much of us as you decide. Nothing surprises anyone.
Rates and turnaround are easy to compare across three proposals in an afternoon. Whether a partner will still be a good fit in year three is harder, and it usually comes down to whether they were straight with you in week one.
If you’re weighing a development partner right now and want a second opinion on what to ask, send me a note. Happy to talk it through, even if we’re not the right fit for the project.
Matthew Christensen is the founder of 40 North, a WordPress development and support team based out of Redding, California. 40 North builds and maintains websites for agencies and businesses. This post is not legal advice.
