Questions we answerTeam structure and leadership
When should a startup hire a COO?
When operational load is genuinely holding the business back and there is a defined remit to own — not when a founder wants to stop doing the parts of the job they dislike.
Free · a few minutes · starts from “I'm not sure how to structure the team”
The short answer
When operations have become a real constraint on growth, when there is a definable remit — which functions, which decisions, which outcomes — and when the founder is genuinely willing to hand those over rather than supervise them. It is too early when the role is described mostly as "the things I don't want to do": that is a collection of tasks, not a job, and it attracts either a very expensive assistant or a senior person who leaves within the year. A chief of staff or an operations lead often fits the real need better.
A COO is one of the most commonly mis-scoped hires in a growing company, because the title covers everything from running a large organisation to being the person who finally sorts out invoicing.
The question that clarifies it is what the role decides. If the answer is nothing much, the need is real but the title is wrong — and the wrong title costs a great deal more.
Is it really this?
Worth checking before you spend anything. These are the signals that tend to tell the two apart.
Signs it is
- You can name the functions the role would own and the decisions it would make alone.
- Operational problems are visibly limiting growth rather than merely being annoying.
- There are enough people for coordination itself to be a job.
Signs it's something else
- The role is described as the things the founder finds tedious.
- The company is small enough that the COO would have almost nobody to lead.
- What is actually missing is one function's leadership — finance, or delivery — rather than all of them.
What's usually behind it
- A founder whose week has filled with operational work and who wants it back.
- Growth that has outpaced the systems holding it together.
- Several functions with no senior owner, which nobody wants to fix one at a time.
What people usually get wrong
- Hiring a COO to avoid deciding what the operating model should be.
- Recruiting someone from a much larger company into a role with no team and no infrastructure.
- Giving the title without the decisions, and being surprised when they leave.
The options, and when each one fits
In no particular order. Which of these fits depends on your situation, not on the question you typed.
Hire a COO
There is a real operating remit, enough scale for it, and a genuine handover of decisions.
Hire an operations lead
The work is real and hands-on but does not need an executive's authority yet.
Fractional operating support
You need senior judgement about the operating model before committing to a permanent role.
When doing nothing is the right call
Writing down what the role would decide is a week of work and frequently resolves the question. If the list is short, the answer is a different hire. If it is long and you are not ready to give it away, the hire will fail whenever you make it.
What the diagnostic asks
- How the team is arranged and where decisions currently route.
- Who owns what today.
- Whether anyone internal could take part of it.
- Whether the team is growing, and whether the role is fundable.
“I don't know” is always an answer. Nothing is assumed on your behalf.
The routes it weighs
Every diagnostic weighs all ten routes. These are the ones that tend to matter for this question — a description of the rules, not a promise about your answer.
Recruit
Recruit a new person for a durable, sizeable need that is central to the team.
Redistribute
Move ownership of the work to where it fits, and make that explicit.
Process improvement
Change how the work flows — remove steps, name an owner, fix the hand-offs.
Specialist support
Bring in a freelancer, consultant or specialist for a defined piece of work.
Do nothing yet
Record the issue, set a revisit date, and decide what would change your mind.
Develop
Build the capability in someone already in the team, with time and support.
What changes the answer
- A definable remit with real decisions attached supports a senior operating hire.
- A list of tasks rather than outcomes suggests a different, cheaper role.
- An unwillingness to hand over decisions makes any version of this hire fail.
Get your own read
A handful of short questions, then the strongest route for your situation, what's also credible, what we still don't know and what would change our view. No account, no setup.
Related questions
- Do I need a chief of staff?A chief of staff multiplies one leader's capacity across whatever matters that quarter. It works where the bottleneck is genuinely that leader — and disappoints where the problem is missing functional ownership.
- Everything comes back to me — what do I do?Decide which decisions genuinely need you, hand the rest over with the authority to go with them, and write down what only lives in your head. Most founders are the bottleneck because nobody has been told where the line is.
- Do I need a management layer?A layer is justified by the number of decisions and people one person can hold, not by headcount milestones. Added to unclear ownership, it makes the ambiguity more expensive.
- Should I use a fractional executive?Fractional works where you need senior judgement rather than senior capacity, and where someone internal can carry the execution between sessions.
- Is my team too small?Team size only means something against the work. The useful question is whether what is being asked of the team is achievable by the people in it, arranged the way they are.
- Do I need a CTO or a lead developer?One sets technical direction and builds a team; the other builds the product well. Most early companies need the second and advertise for the first.