The Overflow Capacity Model: Why Agencies Keep Me on Speed Dial

Here's a scenario that plays out at agencies constantly: a new project lands. It's a good one — solid budget, interesting brief, keen client. The agency won the pitch and everyone's buzzing.

Then someone checks the resourcing spreadsheet.

The senior dev is mid-project until March. The mid-level dev is on two projects already. The junior can handle some of it but not the complex bits. And the project needs to start next week.

This is where I come in. Not as a last resort, not as a compromise — as the plan. The overflow capacity model is, for a growing number of agencies, the smart way to handle development.

What Overflow Capacity Actually Means

In plain terms: I'm the development capacity an agency can access when they need it and release when they don't. I'm not on their payroll. I don't cost them anything when they don't have work. But when they sell a build, I'm available to start within days.

Think of it like a senior developer on retainer, except without the retainer fee. The arrangement works because of the relationship, not a contract.

The agencies I work with know my availability because we talk regularly. A quick Slack message — "Got a React build coming in late Feb, probably three weeks, you around?" — is usually how it starts. If I'm available, brilliant. If not, they plan accordingly. No drama either way.

How It Works Commercially

There are a few models and I've used all of them:

Day rate. The most common. I charge a daily rate, the agency bills their client at their rate (which is higher, obviously), and everyone's clear on what a "day" means. I typically work in half-day or full-day blocks. No tracking fifteen-minute increments.

Project rate. For well-scoped projects with clear deliverables, I'll quote a fixed price. The agency knows their cost upfront, which makes their quoting easier. I take the risk on estimation in exchange for more flexibility on how and when I work.

Retained hours. Rare, but some agencies buy a block of hours per month — say, 40 hours — at a slightly reduced rate. They use them for maintenance, bug fixes, and small features across their client portfolio. If they don't use the hours, they still pay. If they need more, they pay the standard rate for the overage.

Value-based. Once or twice, for projects where my specific expertise was the reason the agency won the pitch, we've structured it so I get a percentage of the project fee. Higher risk, higher reward. Only works with agencies I deeply trust.

The commercial arrangement matters less than the principle: both sides should feel like they're getting a fair deal. If the agency is making good margin on my work, great — that's their job. If I'm being paid fairly for my expertise, great — that's my job. Nobody needs to see the other side's numbers.

Why It's Better Than Hiring

Let's do some quick maths. A senior Laravel developer in London costs, fully loaded with NI, pension, benefits, equipment, and office space, somewhere around £80,000-£100,000 per year. That's roughly £7,000-£8,000 per month regardless of whether there's work to do.

A senior freelance developer at, say, £500-£600 per day costs that only when they're working. A three-week project is £7,500-£9,000. Then the cost drops to zero until the next project.

For an agency that has consistent work — 40+ hours per week, every week — hiring makes more sense. But most agencies don't have that. They have peaks and troughs. Some months they need 200 hours of development. Some months they need 40. Overflow capacity scales with demand. Permanent staff don't.

There's a quality argument too. A permanent junior-to-mid developer costs less but delivers less. An overflow senior who's built dozens of similar projects brings experience that a full-time hire at the same cost level simply can't. You're not paying for a bum in a seat. You're paying for someone who's seen this problem before and knows the fastest route to a solid solution.

Why It's Better Than Traditional Outsourcing

"But we could just use a dev agency for overflow."

You could. And some of them are great. But the model has structural problems:

You don't choose who works on your project. The outsourcing agency assigns whoever's available. You might get their best developer or their newest hire. You won't know until the code starts landing.

Communication overhead. Now you're managing a relationship with another agency who's managing their developer. That's two layers of project management, two sets of meetings, two invoices. It's clunky.

No continuity. Different developer each time. Every project starts with onboarding. Nobody knows your codebase, your conventions, your clients.

Their margins on top of yours. The developer charges X. The outsourcing agency charges X + 40%. You charge your client that + your margin. Everyone's taking a cut and the client's paying for it.

With a direct overflow relationship, you get the same person every time. They know your codebase. They know your standards. They can start a new project on day one without a week of onboarding. And there's one layer of margin, not two.

Building a Relationship That Lasts

The agencies I work with on overflow have been with me for years. That doesn't happen by accident. Here's what makes it sustainable:

Regular communication even between projects. A monthly check-in. "Anything on the horizon?" "Yeah, maybe a build in March." This lets me plan my availability and means the agency isn't scrambling when a project lands.

Quick ramp-up. Because I know the agency's stack, tools, and standards, I can go from "can you start Monday?" to productive commits on Monday. That speed is the entire value proposition.

Honest availability. If I'm not available, I say so immediately. If I'm partially available, I give specifics: "I can do three days a week for the next two weeks, then full-time." Agencies can work with honest constraints. They can't work with surprises.

Quality consistency. Every project, every time. The third project has the same code quality as the first. If anything, it's better, because I understand their codebase more deeply.

No lock-in. Either side can end the arrangement at any time. I don't do contracts that lock agencies into using me, and they don't do contracts that guarantee me work. The relationship persists because it works, not because someone signed a document.

The Economics From My Side

I'll be transparent about why this model works for me too. Having three or four agency relationships means I have a diversified income stream. If one agency has a quiet quarter, others are usually busy. It's more stable than relying on direct clients alone.

It also means less sales effort. I don't need to pitch agencies on working with me — they already know what I can do. When they have work, they call. When they don't, I focus on other things. The sales cycle is essentially zero.

And the work is often more interesting. Agencies serve diverse clients across industries. In any given month, I might work on a property platform, an e-commerce site, and a healthcare app. That variety keeps the work stimulating in a way that a single long-term product role sometimes doesn't.

Is This Right For Your Agency?

If any of these sound familiar, the overflow model might be for you:

You've turned down work because you couldn't resource it
You've delayed project starts because your team was stretched
You've hired a developer and then had nothing for them to do two months later
You've used outsourcing agencies and been disappointed by the inconsistency
You've got a specific technical need (Laravel, React, whatever) that doesn't justify a full-time hire

The model is simple. You sell the work. I build it. Your name is on it. And when the project's done, neither of us is paying for something we're not using.

It's not revolutionary. But after a decade of doing it, I can tell you it works. The agencies I work with keep coming back because the maths adds up and the work is solid. That's really all there is to it.

I've been embedded in agency teams for over a decade. If you're looking for senior development capacity you can trust, let's talk.