When an Agency Should Reach for Overflow Capacity, Not a New Hire

An agency I spoke to recently had won a project worth more than they'd normally take on in a quarter. Good problem to have, except their two developers were already booked solid, the deadline was six weeks out, and a recruitment process for a third hire was going to take longer than the project itself. They ended up delaying the client's launch by a month while they figured it out.

That situation is more common than people admit. Agencies don't usually have a permanent capacity problem. They have a lumpy one. Some months there's more work than hands, some months there's less work than salaries. Hiring solves the first problem and creates the second.

Why hiring is the wrong tool for a short-term gap

A new developer hire in the UK typically takes six to twelve weeks to find, another few weeks to onboard properly, and then you're carrying their salary whether or not the pipeline stays full. If the project that triggered the hire finishes and the next one doesn't land for a month, that cost doesn't pause. Agencies feel this most sharply with senior or specialist roles, where the pool of candidates is small and the salary expectations are high.

Hiring makes sense when the extra capacity is permanent: you've genuinely outgrown what the current team can deliver, month after month, and you can see that continuing. It makes far less sense when the gap is a single project, a skills mismatch, or a deadline that landed badly.

What overflow and white-label capacity actually looks like

The alternative is bringing in someone experienced for the length of the gap, not the length of a career. In practice that means:

• Overflow development: extra hands on a project the agency is already running, so the in-house team isn't stretched thin trying to hit a deadline alone.
• White-label development: the work is done under the agency's name, with the client dealing with the agency throughout. The client never needs to know a subcontractor was involved.
• Skills the agency doesn't have in-house: a client asks for a Laravel backend, or a React front end with a proper API behind it, and it's not something the current team does day to day.

None of this requires a contract, an interview process, or a commitment beyond the project. When the work is done, the relationship can simply pause until the next time it's needed.

Scenarios where this is the obvious call

• A client project has a fixed deadline (a launch date, a funding milestone, a trade show) and the current team is already committed elsewhere.
• A senior developer leaves mid-project and someone needs to pick up the codebase without a six-week gap while a replacement is found.
• A client's request falls outside the agency's usual stack, and it's a one-off rather than a new service line worth building permanently.
• The agency wants to bid on bigger work than it currently has the bench strength to deliver, without committing to headcount before the work is confirmed.

What to check before bringing someone in

Overflow capacity only works if the handover is clean. A few things worth confirming before the work starts:

• Who owns the code. It should sit with the agency or the end client, not with whoever wrote it. Get this agreed in writing before, not after.
• Who the client talks to. If it's white-label, the agency stays the single point of contact. If the client is talking directly to a contractor, that should be a deliberate decision, not an accident.
• How the codebase gets documented. Someone parachuting into a project for six weeks and leaving no notes is worse than not bringing them in at all. Ask what happens once they're gone.
• Whether the stack matches. Bringing in a specialist who works in a completely different framework to the rest of the codebase creates its own maintenance headache later.

These are the same questions you'd ask before commissioning any bespoke work, and they're worth having answered clearly before the first line of code gets written, not discovered halfway through.

Where I fit into this

I work as overflow and white-label capacity for agencies across the UK, mostly on Laravel, PHP, MySQL and React builds, plus API work and integrations when a project needs to talk to systems it doesn't already connect to. Because it's just me, there's no handoff between people on a project and no junior picking up a task they've never seen before. You get direct contact with whoever is actually writing the code, for as long as the project needs it and no longer.

If you want to see how a project actually runs day to day, how I work covers the process from first conversation through to launch. And if you're an agency thinking about this as a standing arrangement rather than a one-off, the partnerships page goes into what that looks like in practice.

The point isn't to avoid hiring altogether. It's to save the hiring decision for when the extra capacity is genuinely permanent, and to have a way of covering the gaps that aren't.