In the services industry, we have been conditioned to believe that a robust “About Us” page-a grid of smiling faces, usually nine or twelve or forty, complete with quirky hobbies and impressive titles-is a signal of stability. We treat a high headcount as a proxy for safety. We assume that a bigger roster means more brainpower applied to our specific problem.
This assumption is not just flawed; it is the primary reason why professional service engagements feel like a slow-motion collapse of expectations. I once held the conviction that hiring a firm with a deep bench was a hedge against project delays and technical bottlenecks. I was wrong. I had confused the size of the building with the quality of the focus.
I didn’t realize that in a service model, every additional person on the team page is not an asset for the client, but another mouth that the agency must feed by over-allocating their time across five other “priority” accounts.
A Rainy Monday at
Ninety-two Slack notifications greeted Marcus when he logged in at on a rainy Monday. Marcus is the senior developer at a mid-sized agency, one of those “nine faces” featured prominently on the team page. To the client, Project A, Marcus is the architectural lead. To Project B, he is the emergency support. To Project C, he is the guy who was supposed to finish the API integration last Thursday.
The immediate cognitive debt Marcus inherits before he even opens his IDE.
Six desks made of reclaimed oak line the east wall of the studio, and from the lobby, the scene looks like a hive of focused productivity. But if you walk the from the reception desk to the engineering bullpen, passing the industrial espresso machine that cost more than a used sedan, you see a different reality.
You see the flickering between browser tabs. You see the “Away” status on three different Slack workspaces. You see a human being whose cognitive load is being shredded by the friction of context switching.
The Central Paradox
This is the central paradox of the modern agency. They market a stock-the total number of talented people they employ-but they sell a flow-the actual hours and attention those people can spare. The team page is a claim about the roster, but it says nothing about availability.
Static list of faces, titles, and impressive credentials.
The fraction of actual cognitive space available today.
When a client signs a contract based on that roster, they are buying the impression of being the only priority while paying to be one of seven.
“An agency is just a factory where the inventory is invisible. If a factory has ten machines and tries to run fifteen different product lines simultaneously, the entire system grinds to a halt.”
– Elena B.-L., Supply Chain Analyst
Elena, who spends her days untangling the “bullwhip effect” in global logistics, pointed out that lead times skyrocket and quality drops in such systems. In the agency world, we don’t call it resource contention; we call it “being a dynamic, fast-paced environment.”
The metric that actually determines the success of a project is never found on a website and is almost never asked for in a pitch: How many concurrent projects does a builder here carry?
The Fraction of a Distracted Mind
If the answer is more than two, you aren’t hiring a developer; you are renting a fraction of a distracted mind. When a designer is allocated at to your project, they are not spending 31 percent of their best energy on you.
Designer Allocation
31%
The Fragmentation Tax: 20 minutes of every hour lost to “the cost of re-entry.”
They are spending the first hour of every day trying to remember what they did for you three days ago. They are losing of every hour to the “cost of re-entry.” By the time they actually reach a state of flow, a notification from Project B pings, and the cycle of fragmentation begins again.
I spent years advising founders to look for “full-service” depth, thinking that a specialist for every niche was the gold standard. I was wrong. I watched as projects were handed off like batons in a race where the runners weren’t looking at each other.
The strategist would dream up a vision, the designer would build a mockup that the developer couldn’t implement, and the project manager-handling six other accounts-would spend their entire day apologizing for the gap between the three.
The buyer’s frustration is rarely about the technical skill of the team. It is about the sensation of being managed rather than being served. It is the feeling of having to repeat yourself because the person you’re talking to hasn’t looked at your file since the last status call.
The Headcount Tax
This is the “Headcount Tax.” The more people an agency has, the more “coordination” is required, which usually means more project managers and more internal meetings, none of which actually move the needle on the client’s website or application.
To keep the lights on in a fancy Toronto or London office, the firm must maintain a high utilization rate. If Marcus isn’t billed out at of his capacity, the agency loses money. But a human being billed at 90 percent across four projects has zero “slack” in their system.
When Project A has a minor crisis-a stakeholder who only replies after or a sudden change in API requirements-the ripple effect ruins the week for Projects B and C.
The Dedicated Flow Model
The alternative to this fragmentation isn’t necessarily a smaller agency, but an agency with a different philosophy regarding “The Roster.” It requires moving away from the “Stock” model and toward a “Dedicated Flow” model.
When we looked at how
structures their work, the difference became clear. Instead of the “nine faces, four projects each” chaos, they lean into a model where a dedicated in-house team is assigned per project with fixed timelines.
Stock Model
The Traffic Jam
Dedicated Flow
High-Speed Rail
It sounds like a subtle distinction, but from a supply chain perspective, it is the difference between a traffic jam and a high-speed rail line. By fixing the timeline and the price up front, the agency removes the incentive to “hide” staff across dozens of projects.
The goal shifts from “how many hours can we bill Marcus for?” to “how quickly and effectively can this dedicated team launch this specific tier of work?”
Safety in Lack of Noise
For a founder or a marketing lead, the safety isn’t in the headcount. The safety is in the lack of noise. If you are comparing three agencies on a spreadsheet, and Agency A has fifty people and Agency B has ten, your instinct is to choose Agency A.
But if Agency A’s builders are each juggling five projects, and Agency B’s builders are focused on one or two, Agency B is actually the larger, more capable partner for your specific needs. They have more “available” brainpower, regardless of what the “About Us” page says.
The industry hides this because transparency about capacity is bad for sales. If an agency told you during the pitch, “We have a great team, but Marcus is currently at capacity and won’t really be able to think about your database schema until Tuesday of week three,” you wouldn’t sign.
The Discovery Shift
We need to start asking different questions during the discovery phase. Not “Who is on the team?” but “How many other people are they talking to today?” Not “What is your process?” but “What is your WIP (Work in Progress) limit for a single developer?”
If an agency can’t answer that, or if they give you a vague answer about “dynamic resource allocation,” they are selling you the illusion of a team. They are selling you the roster, but they are keeping the capacity for someone else.
The shift toward fixed-tier pricing and dedicated teams is a response to this exhaustion. When the price is published and the scope is defined-whether it’s a $3,500 Launch site or a $12,000 Enterprise build-the “stock” of the agency becomes irrelevant.
What matters is the “flow” of the project. You aren’t buying a fraction of a 40-person firm; you are buying a finished product delivered by a team that actually has the space to think about it.
I think back to that developer, Marcus, and his ninety-two Slack messages. He’s a talented builder. He wants to do good work. But he is trapped in a business model that treats his attention as an infinitely divisible resource. When we hire agencies based on headcount, we are complicit in that trap.
We are buying a ticket to a show where the actors are performing on three different stages at the same time.
The Honesty of “No”
Real expertise isn’t a long list of names. It is the ability to say “no” to the third concurrent project so that the first two actually launch on time. It is the honesty to publish a price and a timeline and stick to it, rather than hiding behind the “discovery call” curtain where capacity issues can be masked by sales talk.
In the end, the nine faces on the team page are just a photograph. They are a snapshot of a moment when everyone was standing still and smiling. But your project doesn’t happen in a snapshot. It happens in the messy, high-velocity flow of a workweek.
And in that flow, you don’t need a roster. You need a team that is actually there.