The moment a founder decides to hire a COO, something important has already happened: the company has outgrown what one person can hold in their head.
That’s a real threshold. Crossing it requires a different kind of help — someone who can carry the operational complexity so the founder can focus on what only they can do.
But the hiring process often undoes the good work before it starts.
The most common mistake
Founders hire for the problem they have today, not the company they’re building for the next three years.
If operations are chaotic, they hire someone who’s good at process. If the team is growing fast, they hire someone who’s done scaling before. Both can be the right call. But neither is automatically right — because the constraint today usually isn’t the constraint that matters in eighteen months.
The result is a COO who solves the immediate problem and then gets in the way of what comes next. Not because they’re bad at their job, but because the job was defined too narrowly.
What to hire for instead
Before writing the job spec, answer two questions:
What is the single biggest thing that will break if we double? Not what’s painful now — what fails at scale. That’s the operational challenge the first COO needs to be able to handle.
What does the founder need to stop doing? Not delegate — stop. The things that should never have been in their calendar, but are. The COO’s first mandate is usually to take those over completely.
The answers to both questions shape the profile more than any list of requirements.
The fractional option
For many companies at the point of needing their first COO, a fractional arrangement makes more sense than a full-time hire.
The company gets senior operational leadership at a fraction of the cost. The scope is bounded — which forces clarity about what actually needs to change. And if the fit isn’t right, the risk is contained.
The cases where fractional doesn’t work are the same cases where full-time often fails too: when there’s no real mandate, when the founder isn’t ready to genuinely hand things over, or when “COO” is being used as a title to paper over a structural problem that needs a different fix.
Hiring your first COO is a significant decision. Getting clear on what you’re actually solving for is the most useful thing you can do before you start.
