Every agency that grows hits the same wall. The pipeline fills faster than the development team can deliver. Projects start slipping, the team is stretched, and the founder is turning down work or, worse, taking it on and hoping. It is a good problem in the sense that it means demand. It is a real problem in the sense that handled badly, it costs you clients, margin, and your best people.
The instinct is to hire. Sometimes that is right. Often it is not, or not yet. Hiring is the most expensive and slowest way to add capacity, and it is the hardest to reverse if the demand turns out to be a spike rather than a trend. Before you post a job, it is worth working through the actual decision. This is the decision tree we walk agency owners through.
First Question: Is the Demand Real and Sustained?
Before solving the capacity problem, be sure it is a capacity problem and not a one-off surge.
If you are slammed because three big projects landed in the same month and the pipeline behind them is thin, that is a spike. Hiring for a spike is how agencies end up overstaffed and cutting people six months later. Spikes are solved with flexible capacity, not permanent headcount.
If you have been consistently over capacity for two or three months, the pipeline is healthy, and you are regularly turning work away, that is sustained demand. Now the question becomes which form of added capacity fits, and permanent options are back on the table.
Be honest here, because the answer changes everything downstream. Most agencies feel the pain of a spike and reach for the solution to sustained demand. That mismatch is expensive.
Second Question: Is It a Volume Problem or a Skills Problem?
Capacity problems come in two shapes, and they have different solutions.
A volume problem is when your team can do the work, there is just too much of it. You have the skills in-house, you simply need more hands doing the same things.
A skills problem is when the work needs something your team does not have. A client wants a complex backend and your team is frontend-heavy. A project needs a specialism nobody on staff has. Here, more of the same hands does not help. You need a different capability.
This distinction matters because it rules options in and out. A volume problem can be solved with overflow capacity, a contractor, or a partner doing work your team already understands. A skills problem needs either a specialist hire, which is slow, or a partner who already has that capability, which is fast.
Third Question: How Predictable Is Your Pipeline?
The shape of your pipeline determines whether fixed or flexible capacity fits.
If your work is steady and predictable, with a reliable flow of similar projects, fixed capacity makes sense. A permanent hire is most efficient when you can keep them utilised month after month.
If your work is lumpy, with feast-and-famine cycles, big projects landing unpredictably, and quiet patches in between, fixed capacity is a trap. A permanent developer is a fixed cost against a variable revenue line. In the busy months they are essential. In the quiet months they are overhead you cannot easily shed, and that is how agencies erode their margin. Lumpy pipelines want flexible capacity that scales with the work.
Most agencies, honestly assessed, have lumpier pipelines than they admit. The predictable-demand agency that can keep a new hire fully utilised year-round is rarer than the hiring instinct assumes.
The Options, and When Each Fits
Working through those three questions points you at one of four routes.
Hire a permanent developer. This fits when demand is sustained, the pipeline is predictable enough to keep someone utilised, and the need is for skills you will want in-house long term. It is the right answer when you are confident the work will be there for the next year and you want the capability to be part of your core team. The costs are the slow timeline, the recruitment effort, and the commitment. You are taking on a fixed cost and a management responsibility, so be sure the demand justifies it.
Use freelancers or contractors. This fits a spike or a specific short-term gap. Contractors give you flexible, fast capacity without a permanent commitment. The trade-offs are reliability and management overhead: you are coordinating individuals, quality varies, availability is not guaranteed, and the management load falls on you. Good for filling a gap, harder to lean on as a core part of delivery. We go deeper on this comparison in freelance developer vs full-stack agency.
Partner with a white-label development studio. This fits sustained demand, a lumpy pipeline, or a skills gap you do not want to hire for. A white-label partner gives you a team you can scale up and down as the pipeline moves, delivered under your brand, without the fixed cost of headcount. It solves volume and skills problems at once, because a good partner brings a full-stack team rather than a single skillset. The trade-off is that you are trusting an external team with delivery, so the partner has to be genuinely reliable. Choosing the right one is its own exercise, which we cover in the white-label dev partner checklist.
Do nothing structural and manage demand instead. Sometimes the right move is to raise prices, lengthen timelines, or be more selective about which work you take. If the constraint is healthy and you would rather protect quality than grow volume, managing demand is a legitimate choice. It is the right call when you do not actually want to be a bigger agency, just a more profitable one.
The Mistake Most Agencies Make
The common error is defaulting to hiring because it feels like the grown-up move, the sign of a real, growing agency. But a permanent hire against a lumpy pipeline or a temporary spike turns a revenue problem into a cost problem. You solve this quarter's delivery crunch and create next quarter's utilisation problem.
The second common error is the opposite: refusing all outside help out of a belief that delivery must be in-house to be controlled. That belief costs agencies the work they turn away and burns out the team they do have. A reliable partner does not mean losing control. Handled well, it means more capacity with less risk than a hire. We have written about how agencies scale without hiring precisely because hiring is so often the reflex rather than the right answer.
A Worked Example
To make the tree concrete, take a common case. A ten-person agency has had three months of being over capacity. The pipeline is healthy and they are turning work away. So far this points to sustained demand, not a spike.
The work coming in is mostly the kind they already do, web builds in their usual stack, so it is a volume problem, not a skills gap. But their pipeline is lumpy: big projects land unpredictably, and between them are quieter weeks where a permanent developer would be underused.
Run that through the tree. Sustained demand rules in permanent options. A volume problem could be solved by a hire or a partner. But a lumpy pipeline makes a permanent hire risky, because the fixed cost sits against a variable revenue line and the quiet weeks become pure overhead. That combination points to a white-label partner: capacity that scales up for the big projects and down in the quiet weeks, with no fixed salary to carry through the troughs.
Change one variable and the answer changes. If the same agency had a steady, predictable pipeline of similar work, a permanent hire would become the efficient choice, because they could keep that person utilised. If the new work needed a specialism they did not have, the volume answer would shift toward a partner or specialist regardless of pipeline shape. The value of the tree is that it makes those variables explicit, so the decision follows the situation rather than the reflex.
How to Decide in Practice
Run your situation through the three questions. Is the demand a spike or sustained? Is it volume or skills? Is the pipeline predictable or lumpy?
Sustained, predictable, in-house skills you want long term points to a hire. A spike points to contractors or managing demand. Sustained but lumpy, or a skills gap, points to a white-label partner. And if you do not actually want to grow, managing demand is the honest answer.
The capacity crunch feels urgent, and urgency pushes agencies toward the fastest-feeling decision, which is usually hiring or panic-subcontracting. The better move is to spend an hour on these three questions first. The cost of the wrong structural decision is paid for a year. The cost of thinking it through is an afternoon.