White-label vs in-house developer: which costs less?

For most agencies, a white label developer works out cheaper than an in-house developer until you have enough steady development work to keep someone busy for most of the year. A developer on a £50,000 salary costs roughly £60,000 a year once employer National Insurance, pension and basic overheads are added, before any recruitment fee, and you pay that whether there's a project or not. White label costs more per day, but only on the days you use it.

The short answer

• Hire in-house when you have predictable, year-round demand for the same kind of work and want the skills inside the business.
• Use white label when demand is uneven, a project needs specialist or senior skills, or you're testing a new service.
• Do both when you have a steady base of work plus peaks. Many agencies end up here.

What does an in-house developer really cost?

Salary is only the start. Here's an illustrative example for a mid-level developer on £50,000, using 2026/27 rates. Salaries vary a lot by region and seniority, with London and senior roles typically higher, so swap in your own numbers.

• Salary: £50,000
• Employer National Insurance: 15% on earnings above £5,000 a year, so about £6,750
• Workplace pension: the auto-enrolment minimum is 3% of qualifying earnings (between £6,240 and £50,270), so about £1,300. Many employers pay more.
• Equipment: a capable laptop, screen and accessories, typically somewhere around £1,500 to £3,000, replaced every few years
• Software and services: development tools, design licences, testing services and so on, typically a few hundred to a couple of thousand pounds a year
• Training: courses, conferences and time spent learning

That puts the ongoing cost at roughly £60,000 to £62,000 a year. Smaller employers may be able to reduce their National Insurance bill through the Employment Allowance, but it applies to the business as a whole and may already be used up by existing staff. Check current rates and eligibility on gov.uk.

Then there are the one-off and hidden costs:

• Recruitment. If you use a recruitment agency, fees are commonly somewhere around 15% to 25% of first-year salary, so roughly £7,500 to £12,500 for this role.
• Time to hire. Finding, interviewing and waiting out a notice period can easily take a few months, during which the work still needs doing.
• Onboarding. A new developer won't be fully productive in their first weeks.
• Management. Someone has to set priorities, review their work and support their development. If nobody in the agency can review code, that's a real risk.

Utilisation: the number that decides it

The real question isn't the annual cost. It's the cost per day of work you can actually bill.

A year has around 260 working days. Take off 28 days of statutory holiday (including bank holidays) and allow for sickness and training, and you're left with roughly 220 available days. Not all of those are billable. Developers also spend time on internal projects, pitches, admin, fixing things under warranty, and waiting for content or feedback.

Using £61,000 as the yearly cost, here's how the cost per billable day changes with utilisation:

• 80% billable (about 176 days): roughly £350 per billable day
• 65% billable (about 143 days): roughly £430 per billable day
• 50% billable (about 110 days): roughly £555 per billable day

These figures leave out recruitment, management time and office costs, so the true numbers are higher.

Compare that with outside help. Experienced UK freelance and white label developers often charge somewhere in the region of £350 to £650 a day, with senior specialists higher. Our guide to web developer day rates in the UK goes into the ranges.

So the pattern is clear. A fully busy in-house developer is usually cheaper per day. A half-busy one can cost as much as, or more than, buying days from a partner, and you carry the risk of quiet months.

When does hiring an in-house developer win?

• You have a steady pipeline of similar projects in one stack, all year round
• You run lots of small retainers with frequent changes across many clients
• Development is a core part of what you sell, not an occasional add-on
• You want to build a team and train junior developers over time
• Fast turnaround on small requests matters to your clients
• You already have someone senior to manage and review the work

When does white label win?

• Demand is uneven. Big projects arrive in clusters, then things go quiet.
• You need specialist skills, such as mobile apps, headless CMS builds, e-commerce or performance work, which one generalist hire won't cover.
• You need senior expertise. A senior developer or technical lead costs considerably more to employ than a mid-level one, and you may only need that level for part of each project.
• You're testing a new service. Sell a few projects before committing to a salary.
• You need to start soon. A partner can often start within weeks. Hiring usually takes longer.
• There's nobody to manage a developer. A lone junior hire without senior oversight is a risky setup for both the agency and the developer.

The hybrid model

Many agencies settle on a mix. Two common shapes:

• In-house for the steady base, white label for the peaks. An in-house developer handles maintenance, small changes and retainers. A partner takes larger builds, overflow and specialist work.
• White label technical lead, in-house delivery. A senior partner owns architecture, hosting and code review, while a less senior in-house developer builds alongside them and learns.

The hybrid only works if everyone shares the same setup: your repositories, your project board, your coding conventions and your deployment process. That way work can move between people without a painful handover. If you're new to working with partners, our guide on how to outsource web development as an agency covers how to set this up.

Questions to help you decide

1. How many billable development days did we sell in the last 12 months, and how evenly were they spread?
2. How much work did we turn down, delay or squeeze because we lacked capacity?
3. Is demand for one type of build and one stack, or several?
4. Who in the agency could manage and review a developer's work?
5. Could we comfortably carry a developer's cost through a quiet quarter?
6. Do our clients need skills that one hire couldn't cover?

If your answers point to steady, predictable demand, hiring is probably right. If they point to peaks, gaps and variety, white label is likely to protect your margins better. It's also worth knowing how partners price their work: our guide to white label development pricing models compares fixed price, day rate and retainers.

If you'd like to try white label on a small project first, have a look at how our white label development for agencies works. We're happy to give you a straight answer on whether it suits your workload.