- Development is the agency department that scales worst: a designer can juggle several projects at once, a senior developer can’t without losing output.
- The cost of the bottleneck doesn’t show up in your books, but it does show up in turned-down projects, piled-up delays and margins that never improve.
- The fix isn’t always hiring. Often it’s changing how you get technical capacity.
There’s a moment in the life of almost every agency when growth stalls without anyone deciding it should. Clients keep coming, proposals keep going out and the design and strategy team is doing fine. And yet projects pile up, deadlines slip and profitability doesn’t improve even as you bill more.
When that happens, the cause is usually in the same place: the development department can’t absorb the demand the rest of the agency generates.
The symptom most agencies ignore for too long
The problem rarely hits all at once. It starts quietly: a project that takes a bit longer than planned, a client who asks about their website more often than usual, a proposal lost because the timeline was too long. These signs get written off as one-offs until they become the norm.
The clearest indicator is how many opportunities you turn down or postpone for lack of technical capacity. Hardly any agency tracks it, and those that start writing it down usually find it isn’t an isolated case, it’s a steady leak of projects.
Why development doesn’t scale like the rest of the agency
An account manager can handle 5 clients in parallel fairly efficiently. A designer can switch between 3 projects at different stages without losing momentum. A senior developer doesn’t work that way.
The cost of context switching
Programming requires a state of deep focus that takes a good while to reach. Every interruption (a meeting, an urgent question from another project, a change request from a client) breaks that state and forces you to rebuild it. On a day with several interruptions, a developer can spend more time getting back on track than writing code.
That’s why one technical person split across 2 projects doesn’t perform like 2 half-people: they deliver less, because part of the day goes into leaving one project and getting back into the other.
Inherited technical debt
Every project that ships with shortcuts (code that works but is poorly structured, quick fixes nobody will clean up later) adds weight to the next one. Whoever maintains that project over the coming months will need time to understand what’s there, fix what the shortcuts left behind and make new code coexist with old decisions. We cover this in more detail in what technical debt is and why it destroys projects that seemed solid.
In an agency that moves fast, that debt builds up silently until maintaining existing projects takes more of the team’s time than building new ones.
The gap between what gets sold and what can be delivered
Sales and account teams live at a different pace from the technical team. Proposals close in weeks; what was promised takes months to build. The gap between those 2 speeds is where the most common tensions arise: timelines that seemed reasonable when the contract was signed and become impossible once the technical team already has 2 other projects underway.
The math nobody does: what the bottleneck really costs
It doesn’t appear on any line of your books, but you can estimate it with simple numbers.
Turned-down or postponed projects
Try it with your own numbers. If your agency turns down or postpones 2 projects a month for lack of technical capacity and the average deal is €5,000, that’s €120,000 a year in revenue that never comes in. Even if you’d only closed some of them, the figure would still be serious.
The cost of delays on active projects
Every week of delay has a direct cost (team hours you can’t bill) and an indirect one: the client relationship suffers and the odds of repeat business drop. Picture a €8,000 project that runs 2 weeks late and needs 25 more hours than quoted. At an internal cost of €50 an hour, that’s €1,250, more than 15% of the project price, and in practice it comes straight out of your margin.
The opportunity cost of an underused technical team
When the technical team spends most of its time on maintenance and fixes instead of new development, the agency is paying a senior profile for work that could be handled another way. Retention suffers too: good developers leave when the work becomes monotonous.
Why hiring more doesn’t always solve the problem
The instinctive answer is to hire. Sometimes that’s the right call, but it doesn’t always work.
Onboarding time
A new developer usually takes several months to become fully productive in an agency. During that time, someone on the team has to explain how things are done and how existing projects are built. That time comes out of a team that’s already maxed out, so hiring can make the problem worse for the first few months.
The real total cost
A senior developer in Spain typically earns between €40,000 and €60,000 gross a year, depending on the city and profile, and more in Madrid or Barcelona. On top of that come the employer’s Social Security contributions (around 30% extra), equipment, licenses, space and management time. The total cost to the agency easily lands between €55,000 and €85,000 a year. And it’s a fixed cost that doesn’t go away when work slows down.
The real extra capacity it adds
A new hire doesn’t add one person’s worth of capacity from day one. As a rough guide (it varies a lot by profile and project), they might contribute around 30% in the first 3 months, 60% in the next 3 and 100% from the sixth month on. If the bottleneck is urgent, hiring won’t fix it in time.
What separates agencies that scale from those that stall
Agencies that manage to grow without development becoming their ceiling usually have one thing in common: they’ve separated the technical capacity they need from the headcount they have.
That can take different forms. Some work with an external technology partner that takes on the projects the in-house team can’t handle, often on a white-label basis, so the client keeps dealing only with the agency. Others have redesigned their processes to cut technical time per project without lowering quality: reusable components, project templates, documentation and less work done from scratch.
In every case, they’ve stopped treating technical capacity as a fixed resource and see it as something that flexes with demand. That said, not all outside help works the same way: a technical partner is not the same as a provider of hours, and the difference shows exactly when the pressure is highest.
Checklist: is development your agency’s bottleneck?
These signs mean the problem already exists, even if it doesn’t show up in your books yet:
- You’ve turned down or postponed more than one project in the last 3 months for lack of technical capacity.
- Projects in development run, on average, 20% over the quoted time.
- Your technical team regularly works on more than 2 projects at once.
- Maintaining existing projects eats up more than 30% of available technical time.
- Your proposals include longer timelines than the client expects because the team has no room sooner.
- You’ve lost a client in the last 6 months because of delays or recurring technical problems.
- Your developers have gone more than 6 months without working on anything technically new or challenging.
If you check 3 or more, the bottleneck is already hurting the business. If you check 5 or more, it’s clearly limiting your growth.
Frequently asked questions
At what agency size does the technical bottleneck become a real problem?
From the first project you turn down for lack of technical capacity. It isn’t about size, it’s about the imbalance between the demand your sales team generates and the capacity of your technical team. A 5-person agency can have it just as much as a 50-person one.
Isn’t this just a project management problem?
Good project management reduces the impact, but it doesn’t eliminate the problem. If the available technical capacity isn’t enough for the demand, reorganizing the work doesn’t add capacity: it just spreads the shortfall differently.
How do I tell this problem apart from plain bad planning?
Bad planning causes delays on specific projects. A technical bottleneck causes systematic delays on every project, quarter after quarter, however you plan. If the pattern keeps repeating, the problem isn’t planning, it’s capacity.
At Baqueiro we work as a technology partner for agencies that need senior technical capacity without adding headcount. If you recognize the pattern this article describes in your agency, tell us about your situation and we’ll look at your options together.