Growth vs. Friction Driven Hires

How process friction compounds through rising headcount

There's a moment that happens in almost every growing B2B company. Things start to feel harder than they should. Onboarding takes longer. Support tickets pile up. Renewals require more manual chasing than they used to.

The response is almost always the same: hire more people.

It feels like the obvious fix. More capacity for more volume. And for a while, it even seems to work — the backlog shrinks, the immediate pressure eases. Then growth continues, and the same pressure returns. Except now there are more people involved, and the pressure is bigger.

What's Actually Being Scaled

Adding headcount to a process increases the capacity of that process. What it does not do is change the process itself.

If onboarding takes three weeks because of a disorganised handoff from sales, adding a second onboarding specialist means two people now each spend three weeks per customer instead of one. The throughput improves. The friction per customer does not. You haven't fixed the handoff — you've hired someone to absorb it twice.

This is the core problem with treating headcount as the answer to friction: it scales the workload, but it also scales whatever is wrong with the workload. Every inefficiency, every workaround, every piece of tribal knowledge that exists because no one wrote it down — all of it gets replicated across more people, doing more volume, more often.

The friction doesn't go away. It gets bigger, in proportion to the team that's now managing it.

The Point Where It Stops Working

For a while, this approach produces results that look like progress. Revenue grows. Headcount grows roughly in proportion. The ratio feels manageable.

Then, at some point — and every company seems to discover this point for themselves, usually with some surprise — the ratio stops holding. Revenue keeps growing, but headcount needs to grow faster to keep pace. Coordination costs increase. More people means more handoffs, more meetings, more places where information needs to travel between people who don't have full context on each other's work.

This is the point where additional people start producing less additional output than the people before them did. Each of them adds to the overall friction in the system, while inheriting their own friction as a starting condition.

Beyond a certain point, adding people to a broken process doesn't just fail to fix it. It actively makes the process harder to fix — because now more people, more habits, and more workarounds are built on top of the original flaw.

The Architecture Question

The alternative isn't "don't hire." Growing companies need more people. The alternative is asking a different question before hiring: Is this role needed because of growth, or because of friction?

Growth-driven hiring adds capacity to a process that works. Friction-driven hiring adds capacity to a process that doesn't — and disguises the friction as a headcount problem, which makes it look solvable through budget rather than design.

The distinction is important because the two types of hire have very different returns. A growth hire scales with revenue. A friction hire scales with the problem — and the problem, as it compounds across stages, tends to grow faster than revenue does.

Why This Is Hard to See From the Inside

Friction-driven hiring rarely announces itself as such. It arrives as a reasonable, specific request: onboarding is underwater, we need another specialist. Support response times are slipping, we need another agent. The renewal team is stretched, we need another account manager.

Each request, on its own, is true. The team genuinely is underwater. The work genuinely isn't getting done. But the underlying question — why is this team underwater at this volume, when the process should be able to handle it? — rarely gets asked, because there's no time to ask it. There's only time to hire and move on.

This is how companies end up with revenue operations teams that are larger than they should be, doing work that a well-designed process wouldn't require in the first place. The individual decisions that were made may have looked correct in isolation, but in context of the whole, they produced an oversized team.

The Fix Scales Differently

A process fix, unlike a headcount fix, doesn't need to grow with revenue. Fix the onboarding handoff once, and it stays fixed at twice the volume, ten times the volume, fifty times the volume. The fix is a one-time investment with a return that compounds as the company grows — the opposite of friction-driven hiring, where the cost compounds and the fix never arrives.

This is the case for addressing friction before scaling further. So that the growth can build on a clean foundation without inherited friction Because growth on a fixed process is growth that gets cheaper over time. Growth on a broken process is growth that gets more expensive — and the expense shows up as headcount that never quite catches up.

---

The Revenue Engine Risk Assessment identifies where friction is masquerading as a capacity problem — before it becomes a headcount problem. Take the assessment →