White label or hiring a developer: the math for a small agency
A mid-level developer in the US costs roughly $95,000–130,000 a year once taxes, benefits and equipment are added, and needs about seven billable projects a year to break even. A white label partner costs nothing when there is no work. Hiring wins when you have predictable volume above that threshold; partnering wins when volume is lumpy, which for most agencies under twenty people it is.
Every agency hits this. Enough web work is coming in that briefing a freelancer each time has become the bottleneck, and someone says: maybe we should just hire a developer.
Maybe. Here is the arithmetic.
What hiring actually costs
The salary is not the cost.
| Line | Annual, mid-level US developer |
|---|---|
| Salary | $75,000 – 95,000 |
| Payroll tax and benefits | $15,000 – 25,000 |
| Equipment, software, seat | $3,000 – 6,000 |
| Recruitment, amortized | $2,000 – 4,000 |
| Total | $95,000 – 130,000 |
Then add the parts nobody budgets: four to eight weeks before they are productive, the senior time spent onboarding them, and the fact that one person cannot do design, front end and infrastructure well no matter what the CV says.
The break-even
At roughly $110,000 all in, and assuming a partner would have charged you $8,000 for an equivalent custom build, you need about fourteen builds a year before hiring is cheaper on a pure cost basis.
Fourteen. That is more than one a month, every month, without a gap.
Adjust it for your own numbers and the shape holds: hiring wins on steady high volume, partnering wins on lumpy volume. The question is not which is cheaper in the abstract. It is whether your pipeline is flat or spiky.
The part that decides it
Most agencies under twenty people have spiky pipelines. Three projects land in March, nothing closes in July, two more arrive in September.
A salary does not care about that shape. It arrives every month at the same size. In the quiet months you are paying for capacity you are not selling, out of margin you earned in the busy ones.
A partner costs nothing in July.
That single asymmetry is why agencies with uneven pipelines that hire anyway often end up chasing work to justify the hire — taking projects at thin margins to keep someone busy, which is a worse business than the one they had before.
Where hiring genuinely wins
This is not an argument that hiring is wrong. It wins on four things, and they matter:
Knowledge stays. An employee accumulates context about your clients that a partner never will.
Speed on small things. A twenty-minute fix does not need a brief, a quote and a ticket.
Standards. Someone in the room who cares about the code the way you care about the design.
Client confidence. “Our developer” lands differently than “our partner”, particularly with enterprise clients.
If those four are worth more to you than the flexibility, hire. Just hire knowing the break-even, not hoping it works out.
The arrangement that usually works
Agencies that solve this properly tend to land in the same place: one person in house who knows the clients and holds the standard, plus a partner for overflow and for the skills that person does not have.
It costs more than either option alone. It also removes the failure mode of both — the idle salary in a quiet quarter, and the outsourced project nobody internally understands.
Our side of it
Our books hold two or three agency projects at once, priced per project, with nothing to pay between them. A landing page from 950 €, a site up to eight pages from 2,900 €, a store from 4,500 €.
That is the flexible half of the arrangement above. If your volume is steady enough to justify a hire, hire — and we will tell you that on the call rather than after you have signed.
Common questions
At what point does hiring become cheaper?
Roughly when you have enough steady work to keep one person busy most of the year. Below that, you are paying salary through the quiet months out of margin earned in the busy ones, which is the same money you would have kept by paying per project.
Can we do both?
Most agencies that get this right do. One person in house who knows the clients and the standards, and a partner for overflow and for skills that person does not have. It costs more than either option alone and removes the failure mode of both.
What about the knowledge staying in house?
It is a real argument and the strongest one for hiring. A partner's knowledge leaves when the project ends. Mitigate it by insisting on handover documentation as a deliverable rather than a courtesy, which you should be doing regardless.
