Comparisons

White-label development vs hiring in-house

Hire in-house when development work is steady enough to fill a full-time role for the foreseeable future; use a white-label partner when it comes in projects, or needs skills your team uses only now and then. A partner gives you capacity per project under your agency’s name, while a hire gives you a person you train, manage and pay every month.

The question agencies usually ask is about cost, but the better question is about shape. If the next twelve months hold a steady stream of build work, a developer on the team pays back the salary, learns your clients and your standards, and is there for the small changes that never justify a proposal. If the work arrives as one project, then nothing for six weeks, then two at once, a salary is paid through the gaps and the peaks still need help.

A white-label partner is paid per project and works under your name: your client deals with you, and the engineering happens behind the scenes. You keep the strategy, the design direction and the account. What you give up is daily control over who does the work, so the arrangement has to be written down before it starts: who the client sees, who owns the code and the accounts, how the price is fixed and what is handed over at the end.

Knowledge is the other trade-off. A hire keeps what they learn inside the agency. A partner keeps general know-how and gives you the project: the repository with its history, the hosting project, the CMS seats, the docs and a runbook. If the handover is a zip file and a password, the knowledge has left with the partner, and that is the risk to check before signing.

Many agencies end up with both: a small in-house team for the steady work and a partner for the peaks and the specialist projects, such as a web app, an integration or a Chrome extension. The two work best when the partner fits your process rather than asking you to fit theirs.

Side by side

AspectWhite-label partnerIn-house hire
How you payA fixed price per project, from a written proposalA salary and overheads every month
Time to startA written proposal within a few days of the briefThe time it takes to recruit, then onboarding
Whose name the client seesYours; the partner stays behind the scenesYours
Who owns the codeYou, once the invoices are paid (with us)You, through employment
ManagementAgreed scope and weekly previewsDay-to-day management, reviews and training
Quiet monthsNothing to payThe salary continues
Peaks and specialist workBooked per projectLimited to what the person knows and has time for
Knowledge after the projectIn the handover: repository, docs, runbookStays in the team while the person stays

When to choose White-label partner

  • Build work arrives as projects with gaps between them, or as peaks your team cannot absorb.
  • A project needs skills your team uses only now and then: a web app, an integration, a headless CMS, an extension.
  • You want a fixed price per project and the code, accounts and docs handed over at the end.

When to choose In-house hire

  • There is enough steady development work to keep one person busy for the foreseeable future.
  • Your clients need daily changes that would never justify a written proposal.
  • You want the knowledge of your clients’ sites to stay inside the agency, in a person.

An example from our own sites

This is how a white-label project runs with us: the brief in one call, a written proposal with a fixed price within a few days, weekly preview links you can show your client, and small sites built in one to two weeks. At handover you get the GitHub repository with its full history, the Vercel project moved to your team or your client’s, CMS admin seats, docs and a runbook. Project-specific code and assets are yours once invoices are paid, and work done under your brand never appears in our portfolio. On our agencies page, Modo Deco, a site we built for the BrandableWorks portfolio, is shown with its name replaced by a placeholder: that is what a white-label site looks like from the outside.

Questions

Is a white-label partner cheaper than hiring?
It depends on how steady the work is. A salary is paid through the quiet months; a partner is paid only for the projects it builds. Compare a year of salary and overheads with the projects you actually expect.
Will my client know a partner built the site?
Not from us. We work under your name, do not list the work in our portfolio, and sign an NDA if your client asks for one.
What happens after launch?
You can take everything over with the handover, or keep us on an optional retainer for fixes and upgrades, billed monthly with a three-month minimum.

Tell us what you're launching.

Book a 20-minute intro call, or email a few lines about what you're launching. We'll reply with a rough plan and a price range, whether or not we end up working together.