Do I Need a COO or an Operations Manager?
By Brendan Levin. 20+ years scaling businesses, from teams of 8 to 600 and budgets from startup to $100m.
Key takeaways
- A COO is a strategic officer responsible for the whole operating system, not just one function.
- An operations manager owns execution inside a single domain within an existing system.
- If decisions still route back to you, adding either role relocates the dependency without fixing it.
- The honest test: take a full week away with no contact and watch what stalls. That is where the gap lives.
The distinction most founders miss
Most founders frame this as a seniority question. They think: I need something more than an ops manager but I am not sure I need a COO. That framing gets them stuck because seniority is not the variable. Scope is.
A COO is responsible for the operating system of the whole business: how direction gets set, how decisions get made without the founder, how work moves through the team. An operations manager is responsible for execution inside one part of that system, say, client delivery, or logistics, or finance operations. One designs and holds the whole machine. The other runs a specific part of it.
The problem is that most founder-led businesses under fifty people do not have an operating system yet. Direction lives in the founder's head. Decision rights are never written down. The operating rhythm is the founder making rounds. In that situation, a COO has nothing to build on top of, and an operations manager has no system to manage inside. You cannot hire your way out of a structure that was never built.
A concrete self-test: two questions that point to the real gap
Before you post a job description, answer these two questions honestly.
First: can you write down, right now, who in your business has the authority to approve a $5,000 spend without asking you? Not who you hope would handle it. Who actually has documented permission to act and tell you after? If the answer is nobody, or if you are not sure, the gap is structural, not staffing.
Second: if you took five consecutive working days away with no contact, what would pile up waiting for your return? List those things. Anything on that list is still running on you. A new hire dropped into that list does not remove you from it. It just adds someone who eventually learns to ask the same questions your team already asks.
What each role actually does, side by side
The table below is deliberately narrow. It describes what each role is responsible for in a business that already has an operating system in place. If yours does not, the right column for both is 'not applicable yet.'
| Dimension | COO | Operations Manager |
|---|---|---|
| Scope | Whole business | One function or domain |
| Primary output | The operating system works and improves | Execution within the system hits its targets |
| Decision rights | Holds authority across functions, below the CEO | Holds authority within one function, below the COO or CEO |
| Reporting line | Reports to the CEO or founder | Reports to the COO, or directly to the founder in smaller businesses |
| Right hire when | System exists, founder needs enterprise-wide coordination off their plate | System exists, one domain needs a dedicated owner to run it |
| Wrong hire when | No operating system exists yet | No operating system exists yet |
A real decision-rights threshold, written out
One of the fastest ways to see whether you have an operating system is to look at your decision-rights documentation. Most founders have none. Here is what a working threshold actually looks like, written at the level of specificity that makes it usable:
Any spend under $2,000 within an approved budget line: the owning person acts and tells the founder after. Any spend between $2,000 and $10,000: the owning person proposes, the founder approves within 48 hours. Any spend above $10,000 or outside an approved budget line: brought to the monthly leadership meeting for a joint decision.
That is one decision type. A real operating system has thresholds like that for hiring, client commitments, contract changes, and risk calls. The COO's job is to build and hold that whole map across the business. The operations manager's job is to operate within their slice of it. If no map exists, you are the map, and no hire changes that until the structure is built. How to set decision rights in your business walks through the full process.
When the answer is neither: the structure gap
Most founder-led businesses at the 10-to-50-person stage do not have a staffing gap. They have a structure gap. An executive operating structure is the set of documented agreements that lets the business run without the founder being physically present for every real call.
Hiring a COO into a business with no structure relocates the dependency onto the COO at a senior cost. If the COO leaves, everything routes straight back to the founder. Hiring an operations manager into a business with no structure gives you someone who is good at executing, with nothing clear to execute inside.
The honest sequence is: build the structure first, then decide what you still need to hire. Decide whether to hire or fix the structure first before you open the role.
If the structure exists: how to pick between the two roles
If you already have documented direction, working decision rights, and a standing operating rhythm, then the question is scope. Ask this: is the coordination problem company-wide, or is it contained inside one function?
If multiple functions are dropping things, if cross-functional priorities are colliding, or if you are still the one holding how marketing, delivery, and finance relate to each other, you have a COO-shaped problem. If client delivery is the single point that is breaking, or if finance operations needs a dedicated owner, you have an operations-manager-shaped problem.
Compare the operating advisor, fractional COO, and full-time COO options if you are unsure which type of senior operator fits your stage.
If you are not sure whether your business has a structure gap or a staffing gap, the free Founder Dependency Diagnostic maps where your week actually goes and shows you exactly what still runs on you.
Take the free diagnosticCommon questions
Can an operations manager grow into a COO role?
Sometimes, but not automatically. An operations manager who is very good at running one domain has learned to execute within a system. A COO needs to design and hold the system itself, which is a different skill. The honest test is whether the person can hold accountability across functions they do not directly control. Many strong operations managers find that genuinely uncomfortable, and that is not a flaw. It is just a different job.
My business is 15 people. Is that too small for a COO?
Size is the wrong filter. The right filter is whether an enterprise-wide operating system exists and whether the coordination problem is company-wide. At 15 people, most businesses do not yet have the structure that a COO would be running. The more useful question is whether you have documented direction, decision rights, and a working operating rhythm. If not, build those first. The hire decision becomes obvious once you can see clearly what is actually missing.
What is the difference between a fractional COO and a full-time COO for this decision?
The fractional versus full-time question is about cost and commitment, but the underlying role description is the same: a COO, at any fraction, is responsible for the operating system of the whole business. If your business needs enterprise-wide coordination and a system that does not yet exist, a fractional COO still needs something to build on. What a fractional COO actually does covers the role in more detail.
I keep getting asked to approve small things all day. Is that a COO problem or an operations manager problem?
Neither, initially. That is a decision-rights problem. The volume of approvals coming to you is a symptom of undocumented thresholds, not a headcount gap. Before you hire anyone, write down who can approve what, at what dollar or risk level, without involving you. Once those thresholds exist and are working, the remaining escalations will tell you whether the gap is in one function or across the whole business.
How do I know if I have a structure gap or a staffing gap?
Take a full week away with no contact and note everything that stalls or escalates to you by the end of it. Anything on that list is still running on you personally. Now ask: is each item stalling because the wrong person is in the seat, or because there is no documented agreement about who decides it and how? If the answer is mostly the latter, you have a structure gap. Staffing gaps are real but rarer than most founders assume at the early stages.
Does an operating advisor do the same thing as a COO?
No. An operating advisor installs the operating structure and hands it back to you in a short, defined engagement. A fractional or full-time COO runs the business day to day on an ongoing basis. If the business depends on you because the structure was never built, that is a structure gap. An advisor fixes the structure. A COO runs inside it once it exists. Compare the three options to see which fits your situation.