When to Hire a COO
COO is the least defined title in a company. Two people with it can have almost nothing in common — one runs half the company, another runs internal operations, a third is effectively a very senior chief of staff. That vagueness is why so many founder-COO relationships fail: the role was never specified, so both parties filled in different versions and discovered the mismatch a year in. This page is about testing the conclusion before you commit to a search, because “I need a COO” is usually a diagnosis of a feeling rather than of a gap.
What’s inside
COO is four different jobs
What “I need a COO” usually means
Three conditions before you search
COO, chief of staff, or functional VP
Why founder-COO relationships fail
If you do hire one
Where Blomma fits
COO is four different jobs
Before anything else, decide which of these you mean. Each has a different profile, a different price, and a different set of decisions attached.
The second-in-command.Runs a large share of the company — typically everything except product and vision. Genuine peer to the CEO, sometimes a successor. Requires substantial authority and a founder genuinely willing to give it up.
The functional operator.Owns the operational functions specifically: support, ops, sometimes finance and people. This is a functional VP role with a bigger title, and it is frequently what companies actually need.
The scaler.Brought in to build the systems and processes a growing company lacks — planning cadence, metrics, hiring machinery. Often a fixed-term contribution rather than a permanent seat, which is worth acknowledging honestly.
The complement.Hired specifically to cover the founder’s weakest areas, whatever those happen to be. The most person-shaped version and the least transferable — when either party leaves, the role makes no sense.
Most founders who say “I need a COO” mean the fourth and describe the first. That gap is where the trouble starts, because the search attracts candidates expecting a second-in-command role.
What “I need a COO” usually means
Four more accurate diagnoses, each with a cheaper and faster fix.
“I am doing three jobs and two of them are not mine.”This is a functional hiring problem. Name the two jobs and hire against them specifically — a VP Ops, a finance lead, a head of people. Two targeted hires usually beat one ambiguous senior one, and they are considerably easier to search for.
“Nothing runs without me.”This is a structural problem, not a hiring one. Decisions route through you because authority was never distributed. A COO dropped into that structure becomes the second person everything routes through, and you have added a hop rather than removed one. Fix the decision rights first, and you may find you do not need the hire.
“I do not want to do the operational part of this job.”Legitimate and worth saying plainly. This is the narrow-the-role option — keep the CEO seat, hand over the parts that neither suit you nor need you. It is one of the genuinely good answers, and it works only if you are honest that it is what you are doing.
“I am not sure I should be CEO.”Sometimes the real one, and hiring a COO is the deferred version of a bigger question. Worth facing directly rather than resolving structurally, because a COO hired as a partial abdication produces an unclear company and an unhappy executive.
Three conditions before you search
One. You can name the role’s decisions.Five to eight specific decisions the COO owns without you. Not “runs operations” — actual decisions. If you cannot write them, the role does not exist yet and a search will produce candidates interviewing for four different jobs.
Two. You are genuinely willing to be overruled in their domain.Test it concretely: name a decision where you would accept their call over your instinct. If you cannot, you want a senior executor and should hire one, with a title that reflects it.
Three. There is enough scope to justify the seniority.A COO with three reports and no real authority is an expensive person with nothing to run. Count the reports, the budget, and the decisions. If the answer is thin, you need a VP or a chief of staff.
Add a fourth if you are considering the second-in-command version: your executives need to know whether they report to the COO or to you, and the answer must be unambiguous before the hire starts. Ambiguity here is the fastest way to lose an executive team.
COO, chief of staff, or functional VP
Three roles founders conflate. The distinction is authority.
A functional VPowns a function and its decisions. Right when the gap is a specific domain — operations, finance, people. Cheapest, clearest, easiest to hire, and the correct answer most of the time.
A chief of staffhas no functional authority and works through the founder — running the operating cadence, chasing decisions, preparing board material, taking on projects. Right when your problem is your own leverage and coordination rather than a missing function. Dramatically cheaper and faster to hire than a COO, and it is the answer to a large share of the situations founders bring to this question.
A COOowns multiple functions and their decisions. Right when there is genuinely a half-company to run and you are ready to stop running it.
The test that separates them: how much of the company would this person decide for? If the honest answer is “none, but they would make me more effective,” that is a chief of staff. If it is “one area,” that is a VP. If it is “most of the operating company,” that is a COO.
Why founder-COO relationships fail
The failure rate is high and the causes are consistent.
Undefined boundaries.The most common. Both parties assume different scopes, and the discovery happens through a conflict rather than a conversation. Everything in the conditions section above exists to prevent this.
The founder does not actually let go.The COO is given operations and the founder keeps deciding — in reviews, in hallways, by overriding. The COO becomes a coordinator, disengages, and leaves. The founder concludes the hire was wrong.
The company routes around them.Employees keep going to the founder because that is where the answers have always been, and the founder answers. Within a quarter the COO has a title and no gravity. Preventing this requires the founder to redirect people explicitly and repeatedly, which is tedious and is the entire job for the first six months.
The role was a proxy for the founder’s ambivalence about their own job.Hardest to fix, because no amount of role definition addresses it.
Mismatched expectations about succession.Some COOs take the role expecting to become CEO. If that is not on the table, say so before they accept.
If you do hire one
Five things that materially improve the odds.
Write the role definition before the search, with the decisions listed, and share it with candidates. The specificity will lose you some candidates, which is the point.
Tell your executive team exactly what changes, individually, before the hire starts. Who reports where, what the COO decides, what still comes to you.
Redirect people visibly for the first six months. Every time someone brings you something in the COO’s domain, send them to the COO. Do this twenty times and it takes; do it inconsistently and it does not.
Agree in advance how you will handle disagreements in their domain, including the fact that you will sometimes be overruled and how that gets communicated.
And set a real review at six months, on the role rather than the person — what turned out to be wrong about the scope. Almost always something is.
Where Blomma fits
The difficulty here is that the honest diagnosis is uncomfortable in two directions: either the role you want does not exist and you need two functional hires, or the thing you are really considering is narrowing your own job — which touches the larger question of whether you want to be CEO at all.
Blomma is an always-on AI career coach with no stake in the outcome. Use it to test which of the four archetypes you actually mean, and whether the cheaper alternative to it would solve your problem. Use it to write the five to eight decisions and check honestly whether you are willing to release them — the test most founders quietly fail. Use it to work through whether this is a hiring question or the deferred version of a question about your own role. And if you hire, use it to prepare the first six months of redirecting people, which is the unglamorous work that determines whether the COO gets any authority at all. Where the situation warrants a human who has held or hired this seat, bring one in..
A COO can be transformative, and the role is undefined enough that the hire is only as good as the specification. Most founders who feel they need one need two functional hires, a chief of staff, or clearer decision rights — all of which are faster, cheaper, and considerably less likely to end badly.