Why "Just Hire a COO" Doesn't Solve It
The operating system has to exist before someone can run it
9 min read
A founder I spoke with last year described it like this: they had just closed their Series B, the board was pressing for operational maturity, and three people on the leadership team had started routing decisions through the founder that should not have required founder input. So they hired a COO. The candidate was strong. Former VP of Operations at a well-known growth-stage company, strong references, a clear track record of running complex teams. The offer was north of $280K all-in, with a meaningful equity grant.
Within four months, the COO was overwhelmed. Not from lack of ability, but from the absence of anything to operate within. There were no documented decision rights, no escalation criteria, no shared understanding of who owned what. The COO spent most of their time doing the same reactive work the founder had been doing, just from a different seat. The leadership team, who had never been given a clear framework for how to operate independently, kept routing decisions upward. The only thing that changed was the name at the top of the message thread.
By month six, the founder and the COO were having the difficult conversation. By month eight, the COO was gone. The founder told me they felt embarrassed to bring it up at the next board meeting, and quietly went back to doing everything themselves.
This story is not unusual. It is, in my experience, the most common outcome when founders try to hire their way out of an operational problem before the operational infrastructure exists.
The Data Behind the Pattern
The anecdotal pattern has real numbers behind it. HubSpot co-founder Brian Halligan has estimated that at least 50% of C-level executives hired into startups are gone within 18 months. Data from Carta's analysis of over 185,000 startup employees found that median tenure at startups is just 2.0 years, with a 25% chance an employee has left within the first 15 months. And the VP Sales role, which shares many of the same structural dynamics as an operations hire, fails at a rate of 67% within the first 18 months according to Bridge Group research.
The pattern isn't limited to operations. It shows up every time a startup hires a senior leader to fix a problem that is structural rather than staffing-related. The hire doesn't fail because the person lacks capability. The hire fails because the foundation they need to succeed doesn't exist yet.
The Title Trap
There is another layer to this that most founders don't see until they're in it. When a board says "you need operational leadership," the default move is to search for someone who already has the title. A former COO. A VP of Operations from a well-known growth-stage company. Someone who ran the machine at a company the founder admires.
But running a machine and building a machine are fundamentally different skill sets. A COO who thrived at a 500-person company with an established operating rhythm, a mature leadership team, and documented processes is not necessarily the person who can walk into a 60-person company where none of that exists yet and build it from scratch. The context they operated in was the product of years of foundational work that someone else did before they arrived.
As Warby Parker co-founder Neil Blumenthal has noted, hiring talent from large established companies can be a mistake because those hires often thrive in environments with fully built-out systems, while startups need entrepreneurial problem-solvers who can create those processes from scratch. The right hire is often someone a few layers down from the star executive, someone who built the playbook rather than inherited it.
What a company at the Series A or B stage usually needs is not someone who managed an existing operating system, but someone who knows how to design and install one inside a company that has never had one. That's a different background, a different way of thinking, and a different set of experiences. Hiring by title alone misses this distinction, and it's one of the most common reasons the hire doesn't land.
Why the Foundation Has to Come First
A COO needs an operating system to run. That sounds obvious, but most Series A and B companies do not have one. They have tools like Notion and Asana and Linear. They have meetings. They have smart people who care about the work. But they do not have documented decision rights, escalation criteria, clear ownership boundaries, or an operating rhythm that connects daily work to strategic objectives.
Without these foundations, a senior operations hire walks into a building with no wiring and is asked to turn on the lights.
The problem compounds because the very things the COO needs to build, like decision frameworks and ownership maps, require the founder's institutional knowledge and judgment to create. Nobody else in the company knows why certain decisions are made the way they are, what trade-offs were considered, or where the real priorities sit. That knowledge lives in the founder's head, and it has never been extracted into something the team can reference independently.
So the COO either waits for the founder to provide context on every decision, which recreates the bottleneck in a different shape, or they make decisions without that context and get it wrong, which erodes trust and creates more work for everyone.
Three Questions Before You Write the Job Description
Rather than a checklist, think of these as the diagnostic questions that separate companies that are ready for an operational hire from companies that need to build the foundation first.
Can your leadership team describe, without checking with you, who owns what categories of decisions and at what point something should escalate? If the answer is no, you don't have decision rights mapped. This is the single most important piece of operational infrastructure a growing company can install, because it is what removes the founder from the center of every choice. When a Series A company grows from 5 to 8 direct reports to the CEO, every one of those people needs to know exactly what they own and what still needs to go up the chain. Without that map, the default is to route everything to the founder, and no hire will change that pattern.
Are your workflows designed for how this company actually works, or were they borrowed from a company ten times your size? The workflow that manages customer escalations at a 100-person startup is different from the workflow at a 2,000-person enterprise. When a new operations hire brings the enterprise version, the team pushes back because it feels like overhead, and they are usually right. The right workflow is the one that fits the current complexity and has room to grow, not the one that was optimized for a company operating at a completely different scale.
Could your team make good decisions for two weeks if you were completely unreachable? If the honest answer is no, the reason is almost never a lack of talent. It is because the founder has context and judgment that nobody else has been given access to. Extracting that context into documented criteria, priority systems, and escalation playbooks is what enables a team to make good decisions without checking in first. This is the part most people skip, and it is the part that makes the difference between a COO who thrives and a COO who gets stuck in the same reactive loop the founder was in.
If you can answer yes to all three, you are ready for a COO. The system exists, and now you need someone to own it, improve it, and extend it as the company grows. Most founders I talk to are not there yet. They think they are, because they have hired smart people and given them good titles, but the infrastructure underneath those roles was never built.
The Real Cost of Getting the Sequence Wrong
A failed senior operations hire is not just a $250K to $350K financial loss, though the financial cost is real when you add total compensation and recruiter fees. It is a six-to-eight-month setback during the phase of your company's life when you can least afford one. And the damage compounds in directions founders don't always see at first.
The team, who watched the founder champion this hire and set expectations around it, loses confidence that the operational problems are fixable. The best people on the team, the ones who were quietly hoping things would get better, start updating their resumes. The board, which recommended the hire or at least supported it, starts asking harder questions about the founder's ability to build the right team. And the founder, who went into this with genuine hope that relief was coming, absorbs the failure as personal evidence that they are not cut out for this stage of the company.
That last part is the most damaging, because it leads founders to double down on the one approach that is guaranteed to make things worse: doing everything themselves again. The same pattern that created the problem becomes the response to the failed attempt to solve it, and the cycle accelerates.
The Middle Ground Most Founders Don't Know Exists
The conversation tends to be framed as two choices: either fix it yourself or hire someone full-time. In practice there is a third path, which is to build the operating system first, as a focused engagement, and then bring in the person who will run it.
This is the approach I use at Foundational Operations. The work is structured, time-bound, and designed to install the decision rights, workflows, and founder-extracted frameworks that a company needs before it can support a senior operations hire. When the engagement ends, the team owns and runs the system. If and when a COO joins later, they have something to build on rather than starting from zero.
It is not the right approach for every company, but for founders at the Series A or B inflection point who are weighing a COO hire and feeling uncertain about whether the timing is right, the foundation work is usually the thing that needs to happen first.
Key Takeaway
The instinct to hire your way out of operational strain is understandable, and eventually a senior operations leader is the right move. But the operating system has to exist before someone can run it. Decision rights, workflows, and the founder's judgment encoded into frameworks the team can use are the foundation that makes an operational hire succeed rather than fail.
Build the system first. Then hire the person who will take it further than you ever could.
If you're weighing a COO hire and want to see where the structural gaps are before you spend six months and $300K finding out, the Founder Bottleneck Audit will show you in five minutes where you are in the founder dependency cycle and where to focus first.