Prying my eyelids open is a task I didn’t expect to be so fraught with physical peril today, thanks to a stray glob of peppermint shampoo, but here we are. My left eye is a weeping, crimson portal of minty regret, and the right one isn’t doing much better as I squint at a spreadsheet that is, quite frankly, more painful than the chemical burn. I am looking at Marcus, a VP of Sales who I’ve known for 12 years, and I am watching him come to the slow, agonizing realization that he has accidentally built a bureaucracy instead of a revenue engine. He has 102 people on his payroll now. Two years ago, he had 32. By every rule of industrial-era physics, he should be dominating the market. Instead, he’s drowning in a sea of his own making.

The math in the boardroom was seductive. It always is. They calculated that if a single rep could generate $442,000 in pipeline per year, then adding 82 more reps would result in a linear, predictable explosion of growth. It’s the kind of logic that makes sense if you’re stacking bricks or picking apples, but sales in the modern era is not a manual labor task; it is an information-processing task. And when you add humans to an information-processing task, you aren’t just adding capacity. You are adding friction. You are adding what I like to call the “Alignment Tax,” and it is currently bankrupting Marcus’s productivity.

I’m sitting here, rubbing my burning eye with a damp paper towel, trying to explain to him why his average revenue per rep has plummeted by 52%. He thinks it’s a training issue. He thinks he needs more “enablement.” I told him he needs to stop hiring and start deleting. We have this obsessive, almost pathological need to solve problems by adding more bodies, as if the sheer weight of human souls in a Zoom room could force a lead to convert. But the reality is that past a certain point, every new hire reduces the effectiveness of everyone else. It’s a sales-specific version of Brooks’ Law: adding manpower to a late software project makes it later. In Marcus’s case, adding reps to a complex sales cycle makes the cycle 82% longer.

The Silent Witness: Elena R.-M.

Let’s talk about Elena R.-M. for a moment. Elena is a closed captioning specialist who handles the transcripts for Marcus’s internal “alignment” calls. She exists in the periphery of this organization, a silent witness to the linguistic decay of a bloated team. She told me recently that she’s noticed a pattern. In meetings with 2 or 12 people, the language is sharp. It’s technical. It’s directed. But as soon as the invite list hits 22 or 32, the vocabulary shifts into a weird, defensive nebulousness. People start saying things like “circling back to the high-level synergy” or “leveraging cross-functional bandwidth.”

Elena R.-M. has probably transcribed 202 hours of these meetings in the last quarter alone. She sees the 12-second pauses when Marcus asks a direct question and 42 different thumbnails on the screen all look down at their keyboards, hoping someone else will unmute first. This is the sound of a company dying under the weight of its own coordination. Elena pointed out that in a typical 82-minute “All-Hands Sales Sync,” only about 12 minutes actually involve information that helps someone close a deal. The other 72 minutes are spent justifying why people haven’t closed deals yet. It’s a tragic, expensive theater.

I’m probably being too harsh because my eye is still stinging, but I’ve seen this movie 12 times before. The problem is that we treat humans as if they are interchangeable “units of scale.” We forget that every time you add a person, you create a new set of relationships that must be managed. If you have 2 people, you have 1 relationship. If you have 12 people, you have 66 relationships. If you have 102 people, you have 5,152 potential points of failure in communication. Marcus hasn’t built a sales team; he’s built a giant game of telephone where the original message-“Go find people with this problem and help them solve it”-has been garbled into “Please fill out these 22 fields in the CRM so your manager’s manager can make a prettier chart for the board.”

The Cost of Coordination

This is where the frustration peaks. Marcus spent $2,002,002 on new headcount last year, and his net revenue barely budged. He’s paying millions of dollars for people to talk to each other about why they aren’t talking to customers. The internal friction has become so loud that no one can hear the market anymore. I told him he should have spent that money on systems that remove the need for coordination. We’ve reached the limits of what human-heavy scaling can achieve. The future isn’t about having the most reps; it’s about having the most efficient pipeline velocity. That’s why platforms like FlashLabs are becoming the only way out of this trap. They allow companies to scale the output without the agonizing overhead of human management.

I’ve made the mistake of hiring too fast myself. I once hired 12 people in a single month because I was terrified of being the bottleneck in my own business. I thought I was buying freedom. What I actually bought was 22 hours of meetings per week where I had to explain my own vision to people who didn’t care about it as much as I did. It was a miserable year. I spent more time managing personalities than I did managing projects. Eventually, I had to let 8 of them go, and you know what happened? Our output stayed exactly the same. Actually, it improved. The remaining 4 people were suddenly able to move without checking in with 12 different stakeholders. We were leaner, faster, and significantly less annoyed with each other.

Marcus isn’t ready to hear that yet. He’s still in the “more is better” phase. He looks at his 102 reps as a sign of prestige. It’s a vanity metric for his LinkedIn profile. “Leading a team of 102+ professionals.” But those 102 professionals are currently tripping over each other in the same 42 accounts. They are sending redundant emails to the same CTOs. They are arguing over territory splits in the mid-Atlantic region. They are creating 22 different versions of the same pitch deck because they don’t like the font their colleague used. It’s a mess of ego and unnecessary activity.

The Illusion of Scale

The irony is that the more people you have, the less individual accountability survives. In a team of 2, you know exactly whose fault it is when the ball gets dropped. In a team of 102, the ball doesn’t just get dropped; it disappears into a black hole of “shared responsibility.” Everyone assumes someone else is handling the follow-up. Everyone assumes the marketing team already sent the white paper. Everyone assumes the VP has a plan. But the VP is just staring at a spreadsheet, nursing a headache and wondering why his 12th cup of coffee hasn’t given him the answer yet.

I finally rinsed my eye out properly, and the world is coming back into focus. It’s clearer now. The “scale through headcount” model is a relic of the 1922 assembly line. It worked when the work was visible and the output was physical. But in the world of high-ticket SaaS and complex consulting, the work is invisible. It’s cognitive. And cognitive work does not scale through volume; it scales through clarity. Every person you add to a cognitive workflow introduces a 12% chance of a misunderstanding. By the time you reach Marcus’s level of scale, the chance of a project being executed perfectly is essentially 0.2%.

I suggested to Marcus that he try an experiment. Take his 12 best reps-the ones who actually know the product and the customers-and put them in a separate “strike team.” Give them zero internal meetings. Give them no CRM requirements other than the basics. Let them use whatever tools they want. I bet him $222 that those 12 people would out-produce the other 90 reps combined within 82 days. He looked at me like I was insane. He couldn’t fathom the idea that 90% of his team might be redundant. He’s invested too much of his identity into the size of his kingdom to admit that the kingdom is mostly made of cardboard.

Elena R.-M. sent me a message later that afternoon. She had just finished captioning another “Strategic Alignment Session.” She said the most common phrase used in the meeting-occurring 42 times-was “I just want to make sure we’re all on the same page.” Think about that. They spent 82 minutes trying to get on the same page, which means they were never actually on the page to begin with. They were just talking about the page. They were debating the margins of the page. They were discussing who should be allowed to hold the pen.

The Clarity Imperative

We have to get comfortable with the idea of “thin” organizations. We have to stop equating headcount with health. A company with 22 people doing the work of 102 is a miracle of engineering. A company with 102 people doing the work of 22 is a tragedy of management. The shampoo is out of my eyes now, and I can see the data for what it is. Marcus doesn’t have a sales problem. He has a coordination problem. He is paying for 82 people to watch 12 people work, and he’s calling it a “growth strategy.”

If you find yourself staring at a similar spreadsheet, wondering why your “scaling” feels more like “slowing,” take a look at your calendar. If you see more than 12 hours of internal meetings per week, you aren’t a sales leader; you’re a professional referee. You are managing the friction you created by hiring too many people. It might be time to stop the “yes, and” of hiring and start the “no, but” of automation. The goal isn’t to have the biggest team in the building. The goal is to have the biggest impact on the market. And those two things, more often than not, are in direct opposition to each other. I’m going to go put some cooling drops in my eye and wait for Marcus to realize that the peppermint sting of the truth is actually the only thing that will save his Q4.