White label partner vs freelancers vs an in-house hire

White label partner, freelancer or in-house hire: how do they compare?

A freelancer is one person you manage yourself, paid hourly or per job. A white label partner is a studio with a team, a project manager and a contract written for agencies, usually paid a fixed price per project. An in-house hire is an employee on a salary. The right one depends mostly on how regular your web work is.

Each column wins some rows and loses others. There’s also a fourth option, a general outsourcing company, which suits long builds with a detailed specification; we compare it in how to outsource web development.

What is the difference between a white label partner and a freelancer?

Both do work that you sell under your own name; the difference is what comes with it. A freelancer sells one person’s time and skill. A white label partner sells a finished result from a team, with project management, testing, cover for absence and a contract that keeps the partner away from your clients.

• A freelancer designs or builds, and rarely does both to the same standard. A partner puts a designer, a developer, a tester and a project manager on the same job.
• With a freelancer, you write the tasks, chase the dates and check the result. With a partner, their project manager does the first two and you review.
• Freelancers mostly bill time. Partners mostly sell a fixed price for a fixed scope, so you can quote your client before work starts.
• A partner’s contract should already deal with your clients, your name, ownership and missed dates. With a freelancer you usually have to bring that contract yourself.
• When someone is away, a partner has other people. A freelancer has a diary, and your date moves with it.
• With a freelancer you talk to the person doing the work; with a partner, usually to the project manager. Some agencies prefer the first, and that’s a fair reason to choose a freelancer.

One note on words: “subcontractor” describes the contract, whoever the supplier is. A freelancer and a white label partner are both subcontractors when they do work you’ve sold to a client. We go through the terms in what is white label web design.

When is a freelancer the better choice?

Choose a freelancer when the job is small and clearly defined, it sits on one platform they know well, and you can review the work yourself. A freelancer you already trust is often the simplest way to get a contained piece of work done, and you get to talk directly to the person doing it.

• You already have one you trust. Someone who knows your clients and has delivered for you before is worth more than any process a new supplier describes to you.
• The job is small. A fix, a single template, a change to a site they built. Setting up a partner for two hours of work costs more effort than it saves.
• The skill is narrow. One unusual integration, one animation, one platform nobody else asks you for. Here a specialist beats a general team.
• You want to direct the work yourself. If you’re technical and like working alongside the person building, a freelancer gives you that. A partner puts a project manager in between.
• The scope will change as you go. Open-ended work suits hourly billing. A fixed price needs a fixed scope.

The limits are capacity and cover. One person can’t take three projects in the same month, and if they’re ill, your date moves. If you depend on one freelancer, keep a second you’ve already tested, keep the code and logins in your own accounts, and put the basics in writing: ownership of the work, confidentiality and no direct work for your client. The partner vetting checklist works for a freelancer too.

Are you a freelancer yourself, and want a team behind you for bigger jobs? See StudioPartner for freelancers.

When is an in-house hire the better choice?

Hire when web work keeps a developer or designer busy most of the year, when websites are your agency’s core product, or when you need someone in your office and in your client meetings. An employee builds a knowledge of your clients that no outside supplier can match. The cost is a salary that keeps running through the quiet months.

Four signs that a hire is the right call:

• Your web volume is steady enough to keep a developer busy most of the year.
• Web is your agency’s core product, and you want to build that capability, and the culture around it, in-house.
• You need someone in client meetings or in your office every day.
• You maintain one large, long-lived codebase, where knowing it deeply counts for more than knowing many platforms.

When is a white label partner the better choice?

Choose a white label partner when you sell websites regularly but not often enough to fill a salary, when the work spans several platforms, or when you’d rather not manage developers yourself. You get a team, a fixed price you can quote from, and a contract that keeps the partner away from your clients.

• Web work comes in waves. Three projects one month and none the next. Per-project pricing follows the work. A salary doesn’t.
• Clients ask for different platforms. A WordPress site, then a Shopify store, then a Webflow build. One person rarely covers all three well.
• You sell marketing, SEO or ads, and a client wants a website. You have no web team and don’t plan to build one. A partner lets you say yes and keep the account.
• You need design and build from one place. Two freelancers means a handover between them, and you manage it. A partner does that handover inside one team.
• You have promised your client a date. A partner can put a delivery date in a signed order and cover absence from its own team. Ask what happens if the date is missed.

What does each option cost?

Each is priced in a different way, so compare the pricing model before the rate. A freelancer usually bills by the hour or per job. A white label partner usually charges a fixed price per project, or a monthly plan. An employee costs a salary plus on-costs every month, whether or not there’s client work.

Freelancer and partner rates vary with country, seniority and platform, far too much for one market figure to be any use to you. The comparison that counts is your own: send the same brief to a freelancer and to a partner, get each quote in writing, and compare those.

When you do, add your own hours to the freelancer’s quote. Briefing, chasing and testing are part of the cost, and with a partner most of that work is inside the price.

What can go wrong with each, and how do you reduce the risk?

Each option fails in its own way. A freelancer becomes unavailable and nobody else knows the project. A white label partner passes the work to someone you never vetted, or gets too close to your client. A hire sits idle in a quiet month, or leaves with what they know. There’s a control for each of these.

The contract terms behind each control are in the risks section of the outsourcing guide, and the white label agreement template has a clause for each. It’s a starting draft, so have a lawyer look over it before you use it.

Can you use more than one?

Yes, and it often works well. One set-up we like is one in-house lead for the core platform, a white label partner for overflow and for the platforms the lead doesn’t cover, and a specialist freelancer for the occasional narrow job. Each one fills a gap the others leave.

• A hire and a partner. Your lead owns the core platform and the client meetings. The partner takes the months when three projects land at once, and the platforms your lead doesn’t build on. Your lead can review the partner’s work inside your own accounts.
• A freelancer and a partner. Keep the freelancer you trust for small jobs and the work they know. Send whole sites, and anything with a date you’ve promised, to the partner.
• A partner now, a hire later. Use a partner while web work is uneven. Once it has kept one person busy for a year, you have the evidence for a hire, and the partner becomes overflow.

Whichever mix you choose, keep the work in accounts you own. Then moving a project from one to another is an invitation, not a migration.

How do you choose between them?

Ask five questions in order: how many months of the year you have web work, how many platforms your clients ask for, who will manage and check the work, what your client must see, and what happens if the person is away for two weeks. The answers usually point to one option.

1. How many months of the year is there web work?

   Count last year’s projects by month. Work in ten to twelve months points to a hire. Work that comes in bursts points to a freelancer or a partner.

2. How many platforms do your clients ask for?

   One platform suits one person. Three platforms suit a team, because one person rarely builds equally well on WordPress, Shopify and Webflow.

3. Who will manage and check the work?

   If someone at your agency can write tasks, read code and test a build, a freelancer or a hire will work. If not, you need a supplier that brings its own project manager and its own testing.

4. What must your client see?

   If the work has to look like your own team’s, check the contract and the working set-up: whose email domain, whose accounts, and what stops the supplier dealing with your client.

5. What happens if the person is away for two weeks?

   If the answer is “the launch moves”, and you’ve promised your client a date, you need cover: a second freelancer, a second employee or a partner with a backup.

Then test before you commit. Give a new freelancer or a new partner one small, real job with a fixed scope and a date, and pay for it. The steps are in how to outsource web development, and the design side is in how to outsource web design.