When an owner tells me they need a COO, I ask them what broke last week. The answer sorts them faster than anything on a resume.
One owner describes a week where they signed off on purchase orders at 11pm, approved a hire they had never met, and missed their kid's game to walk a site the super could have walked. That is one problem. Another describes a bid that went out late because the estimate, the contract, and the schedule live in three heads that never talk. That is a different problem. A third describes a business that runs fine without them for two weeks, and an owner who wants to hand the whole operation to someone and go build the next thing. That is a third problem.
All three said the same four words. I need a COO. Only one of them was right.
I have sat in that chair. I ran operations as an SVP and as a COO, scaled a business from $5M to past $20M, and built the operating spine across an eleven-business portfolio. The most expensive mistakes I watched owners make were not bad hires. They were the right hire aimed at the wrong problem: a $250,000 executive dropped on top of a business that needed a system, or a founder who systematized for two years when they should have handed off the keys.
Three owners say I need a COO. They mean three different things.
/ SECTION 01The three problems wearing one title
"COO" is a title, not a diagnosis. Underneath it sit three failures that produce the same surface complaint (the owner is stretched, things slip, growth feels heavier than it should) and demand three different fixes.
- A capacity problem. You are the bottleneck. Every decision, approval, and judgment call routes through you, and you have run out of hours. The work is not too complex. There is too much of it landing on one desk.
- A systems problem. The way the business runs was built for a smaller company. It worked at $5M on relationships and memory. At $20M the handoffs drop, nobody owns the middle, and the same fires restart every month because no system holds the fix in place.
- A leadership problem. The business needs a second person who can own operations and a P&L, lead the team, and make the calls you make, so you can go do the two or three things only the owner can do.
Hire a full-time COO for problem three and you have made the right move. Hire one for problems one or two and you have bought an expensive person to sit on top of a mess they did not create and often cannot clear. They will spend year one building the system that should have existed before they arrived, and you will wonder why the senior salary is not buying senior results.
/ SECTION 02Problem one: capacity, and why a COO is the wrong fix
The capacity problem feels like the strongest case for a COO. It is usually the weakest.
Here is the tell. Write down every decision you personally touched last week. Now mark each one with a simple question: did this need my judgment, or did it need someone to own it? A pricing exception on a strategic account needs your judgment. Approving a $400 tool purchase, signing a routine PO, answering the same scheduling question for the third time: none of those need you. They need an owner who is not you.
If most of your list is the second kind, you do not have a leadership gap. You have a delegation gap and no system to delegate into. A COO will not fix that. A COO with nothing to delegate into becomes the most expensive version of you, and now there are two bottlenecks instead of one.
The $250K bottleneck
A capacity problem hired as a leadership problem produces a predictable failure. The COO arrives, finds no operating system to run, and starts absorbing the owner's overflow to be useful. Six months in, they are doing the owner's old inbox at four times the cost, the owner is still the real decision-maker, and both of them are frustrated. The fix was never a bigger title. It was written processes, clear ownership, and the discipline to route work away from one desk.
The honest move at this stage is often to do neither. Build the first real systems: a documented approval matrix, an ops coordinator who owns scheduling and purchasing, a weekly rhythm that surfaces problems before they reach you. That work is cheaper than a COO and it is the foundation any future COO would need anyway. Skip it and you are not hiring a leader. You are outsourcing your own lack of a system, at a premium.
/ SECTION 03Problem two: the spine, and why you embed
The systems problem is the one most owners misread, because it shows up right when revenue is climbing and everything feels like a growth problem. It is not. It is a structural one.
The business that got you to $20M ran on a spine built for a smaller company: a few key people who remember everything, handoffs that work because everyone sits close, decisions that route through the founder because the founder is still in every room. That spine does not scale. It cracks in a specific pattern. Estimates and contracts stop talking to each other. Projects hand off with gaps nobody owns. The same problem gets solved four times because the fix lived in a conversation, not a system.
This is real work, and it has a shape: someone with operator authority has to go in, find where the spine has cracked, and rebuild it. Written processes. Clear ownership of the middle. A cadence that catches problems early. Systems that hold a fix in place after the person who made it moves on.
You do not need to buy that work permanently. You need it built, installed, and handed back working. That is the case for embedding an operator instead of hiring one.
- The job has an end state. Once the spine exists and the team can run it, the intensive work is done. A permanent COO hired for a finite build is overhead the day the build finishes.
- The fix needs cross-functional authority that staff cannot credibly hold. An outside operator can make estimating, operations, and finance change how they work in a way a peer who reports to the same owner usually cannot.
- A fixed window forces the work to ship. Internal teams have day jobs, and the spine rebuild loses every week to the fire in front of them. A defined engagement makes it the priority until it is done.
This is the work I do, so read the next line as an interested party. If you can build the spine with the people you already have, build it with the people you already have. The frameworks in these notes are free for exactly that reason. You bring in an outside operator when the fix requires a system you do not have the capacity or the standing to build in a reasonable window, and you need it measurable and handed back working rather than added to a list that never clears.
/ SECTION 04Problem three: leadership, and when you actually hire
Sometimes the answer is a COO. A real one, full-time, on the payroll.
You are at this point when three things are true at once. The business is large and complex enough that operations need a dedicated leader every single day, not a project with an end date. The operating spine already exists, so the COO runs a system instead of inventing one. And you, the owner, have work that only you can do (raising capital, key relationships, the next market, the vision) that the operations seat is actively crowding out.
The order matters. Build the spine, then hire the COO to run and extend it. Hire the COO first and you have handed a systems problem to a leadership hire, and the most common result is an expensive year of them building what should have been built already, followed by a quiet parting when the results never match the salary. The best COO in the market cannot lead an operating system that does not exist. They can only build one, and building one is a different job than leading one.
Build the spine first. Then hire the person to run it.
A COO hired onto a working spine, with a real mandate and a founder who has actually let go, is one of the highest-leverage hires a company ever makes. A COO hired to paper over an owner who will not delegate, onto a business with no system underneath, is one of the most expensive.
/ SECTION 05The same decision at four different sizes
Revenue does not decide the move by itself. But the problem you are most likely facing changes as you grow, and so does the right answer. Here is how the decision usually breaks by stage.
The numbers are markers, not thresholds. A $12M business with a genuine second-in-command need should hire one, and a $40M business still running on the founder's memory should build the spine before it hires anyone senior to run it. Use the stage to find the problem you are most likely facing. Then let the problem, not the revenue line, pick the move.
/ SECTION 06How to tell which one is yours
Run these three questions in order. They map to the three problems, and the first one you answer honestly with a yes is usually your answer.
- Is most of what lands on my desk work that needs an owner, not my judgment? If yes, you have a capacity problem. Build the delegation system before you hire anyone senior. The move is often to do neither.
- Do the same problems keep coming back because the fix lives in a conversation and not a system? If yes, you have a systems problem. The spine needs rebuilding. Embed an operator to build it in a fixed window and hand it back working.
- Does the business already run on a system, and is the operations seat the thing keeping me out of the work only I can do? If yes, you have a leadership problem. Hire the COO, and actually let go.
Most owners want the answer to be number three, because it is the one that lets them keep everything else the same and buy their way out with a hire. It rarely is. The businesses that scale cleanly are the ones that name the real problem first, even when the real problem is that they never built the thing a COO would need to lead.
Run the three questions on your own business this week. If the answer is a COO, go hire a good one. If the answer is the spine, you can build it yourself, and these notes will keep handing you the frameworks to try. If you want it built and handed back working in a fixed window instead, that is the offer.
The frameworks are free. The work is the offer.