Why I'll Just Hire Someone Is the Most Expensive Decision Consulting Firms Make — Altvina People vs. Process

Published May 8, 2026 · People vs. Process · 7 min read

Why "I'll Just Hire Someone" Is the Most Expensive Decision Consulting Firms Make

Why the founder reflex to solve owner-as-bottleneck with a senior hire fails so often, and what diagnosis-first hiring looks like when it actually sticks.

Quick real-world example before we get into the failure modes. This came up between my co-founder Jay and me when we were standing up Altvina last year.

Jay wanted to bring in an assistant right away. The volume of work involved with standing up a business and setting up the processes was a lot, and he was overwhelmed by it. Which is fair. He's a COO for another company, so it isn't like he doesn't know how to do this. It was just a lot of work and he wanted the help.

I had to remind him of the bigger goals. Hiring isn't always the right first choice. Not that it isn't going to be important. Not that it won't eventually be the right call. Just that it shouldn't be what we lead with.

We looked at our other options instead. Where could we do more with less? Where did we genuinely need human help versus where were we reaching for a hire because the work felt heavy? It was a useful dialog. The hire conversation didn't go away. It just got better-shaped before we had it.

That same conversation is one a lot of founders need to have with someone, and the rest of this post is about why hiring without it usually stalls out.

Here's the contrarian take, before the setup. In a firm where the owner is the bottleneck, "I'll just hire someone" is often the highest-risk version of a reasonable decision.

I know how that lands. Hiring is what every reasonable, exhausted leader is told to do. Boards say it. Peer founders say it. Coaches say it. The advice is sound in the long run, and that's what makes the timing problem so easy to miss.

The sentence shows up in different forms. "I think we just need to hire a Director of Operations." Or: "I've been telling myself I need a strong number two for two years now." Sometimes more decisively: "We're starting the search next month. I just need someone to take this off my plate." Each version is a tired and capable leader doing exactly what they're supposed to do. Recognizing they're overloaded. Moving to fix it.

This is the closing piece in a five-part week on the owner-as-bottleneck pattern. The contrarian one. Worth sitting with before the search begins.

Why the conventional wisdom sounds so right

It's a common pattern in founder-led consulting, fractional, and learning-agency firms in the five-to-thirty-person band. Many are either searching for a senior operations leader, recently hired one, or preparing to do so. The advice is everywhere: hire your COO, get a strong number two, take it off your plate.

It sounds right because the symptom is real. You're overloaded. Your inbox is the routing layer. Senior people defer to you on calls inside their stated scope. The work that should be yours (strategy, positioning, the next service line) is what you keep deferring. A senior operations hire would, in principle, absorb a share of what's routing through you.

It also sounds right because hiring is visible. A search is a thing you can announce. A new hire is a thing your team can see. Diagnosis is invisible work, and when a leader is exhausted, doing the visible thing feels better than doing the diagnostic thing. That isn't a character flaw. It's leadership under load.

Hiring is the right answer in the long run. It's the wrong first move. The cost of that ordering is what the rest of this post is about.

What happens when the senior hire lands inside an undiagnosed firm

When a senior hire lands inside an undiagnosed owner-as-bottleneck firm, three things tend to happen, and often all three, roughly in this order.

The new hire inherits a workflow only the founder can execute. This often gets named, usually wrong, as a "wasn't the right fit" problem. The deeper truth is that the workflow the hire was brought in to run isn't actually a workflow. It's a set of decisions the founder makes by feel, every week, that have never been written down. The hire asks reasonable questions. How do we decide which deals to pursue? What's the quality bar on a deliverable? What's the pricing rule for an out-of-scope ask? And gets "it depends, here's how I think about it." A few quarters in, the hire is either making calls the founder would have made differently and getting overruled, or kicking decisions back to the founder. Either way, they aren't actually running anything.

The founder still becomes the routing hub by default. This is the surprising one. Most founders expect the senior hire to absorb the routing layer, and for a few weeks it can look like it's working. Then the messages drift back. Clients still want the founder on the call. Senior staff still cc the founder on hard questions because that's what they've always done. The hire gets looped in but not authorized. The firm's behavior hasn't changed, even though the org chart has. The founder ends up routing through and managing one more senior person, which is worse than where they started.

The firm pays the salary, the founder's time, and the cost of the failed transition, all at once. Founders rarely sit down and add this up. The salary is the smallest line. The founder hours, the ramp, the exit, and the opportunity cost of what didn't get built while the founder was absorbing the failure all stack on top.

None of this is the new hire's fault. (And honestly? The people who land in these roles are usually excellent. That's the part that breaks my heart a little.) They're being asked to operate a system that was never designed to be operated by anyone other than the founder.

The math leaders rarely run

The cost is rarely just the salary.

Compensation is the headline number. Ramp time at full pay against partial output is real. Founder time during onboarding is real and rarely costed. Severance and a second search are real if the hire doesn't stick. Opportunity cost (the service line that didn't launch while the founder was absorbing the failure) is usually the largest line and the one founders are least likely to count.

Across an 18-month window, a failed senior hire in a firm of this size easily compounds into six figures across all of these categories combined.

The expensive part isn't the salary. It's the failed transition.

What changes when diagnosis comes first

Diagnosis before hiring isn't a stalling tactic. It's a two-to-six-week piece of work that changes the hire on three concrete dimensions.

It changes what role you're actually hiring for. Firms in this pattern often start the search assuming they need a senior generalist (Director of Operations, Head of Ops, COO). Diagnosis often reveals something different. The right hire might be a delivery lead, because the bottleneck is delivery quality. Or a revenue operator, because the bottleneck is the founder being the only seller. Sometimes a senior hire isn't the right move at all. It's a process redesign that lets the existing senior team take ownership of decisions routing through the founder by habit. The role you find after diagnosis is narrower, more concrete, and substantially more hireable. (And often $40-60k less in compensation, because the role is real instead of compound.)

The new hire walks into a different firm. A diagnosed firm has written down the decision rules. How pricing exceptions get made. What the quality bar on a deliverable looks like. When an account team can change scope without founder sign-off. The rules don't have to be perfect. They have to exist. A hire stepping into a documented set of decisions can run them. A hire stepping into "ask the founder" cannot. That difference is most of what determines whether the hire sticks.

The firm's behavior shifts, not just the org chart. Senior staff defer because deferring is faster than deciding. Clients escalate because the founder responds. Diagnosis surfaces those defaults and gives the firm a chance to change them before the hire arrives, so they walk into a firm that has already started behaving differently, not one where they have to fight for authority on day one.

Sometimes diagnosis says: hire. The role is clear, the decisions are documented, the firm is ready. The point isn't that hiring is wrong. It's that hiring without diagnosis is the most expensive version of the right idea.

Closing: the week in review

Monday named the pattern. Founder-led service firms in this band almost always organize themselves around routing decisions through the founder, and the pattern is invisible from the inside because things still ship.

Tuesday added up what that costs. Growth that doesn't happen. Founder-dependent client risk. Founder-burnout pricing. Valuation drag.

Wednesday published the eight-question diagnostic.

Thursday described what a pre-hire operational Blueprint actually produces.

Today closes the arc with the contrarian read on the most common founder response: hiring first.

If the search is already underway, none of this is meant to make you feel bad about it. It's meant to add one step in front of it. Run the diagnostic. If the results say the role you've written is the right role and the firm is ready, the search continues with sharper inputs. If they say something else, you've saved the firm the most expensive version of the right idea.

Continue the series

This is part 5 of a 5-part series on the Routing Hub pattern. The full arc:

Want the Routing Hub Diagnostic?

Run the 8-question version.

Get the diagnostic

Content and Accuracy Disclaimer

At Altvina, we leverage advanced AI tools to assist in creating informative and insightful content. While AI aids in drafting and gathering information, we rigorously fact-check all content to ensure reliability.

Should you notice any inaccuracies or outdated information, please contact us immediately. Your feedback helps us maintain high standards of accuracy and transparency.