When to hire a COO — and when not to

Executive overview

Hiring a COO is expensive, disruptive, and a long-term commitment. Before making that move, three cheaper alternatives usually solve the problem first.

Work through them in order: EA, functional heads, fractional COO. Only hire a full-time COO when multiple overflowing buckets remain after exhausting all three.

The activity inventory is the decision tool — let it reveal what you actually need, not what you assume you need.

Try these before hiring a COO

• EA first: if you just need time freed up, an EA costs far less and handles administrative overflow
• Functional heads: if one domain is struggling, hire a CFO, CTO, or VP — not a COO
• A COO coordinates across functions; they don't substitute for deep domain expertise
• Fractional COO: a former senior exec working across multiple companies; useful for coaching, core projects, or testing the fit
• Scaling back core projects is another option — fewer projects may eliminate the need entirely

When a full-time COO is justified

• Activity inventory shows multiple overflowing buckets across different functions
• You need strong coordinating leadership, not another domain head
• The hire must return at minimum 2x salary, preferably 4x, in gross margin impact
• Four valid reasons to hire: increase efficiency, improve employee/customer satisfaction, grow company value, grow profitably
• Be prepared for organisational disruption — existing department heads may resent the new layer

The cost of getting it wrong

• Unnecessary COO = $250k+ in wasted salary plus disruption and commitment
• Strong existing ops heads make COO arrival politically difficult — expect pushback or resignations
• Short-term crisis? Use a consultant — easier to hire, no relationship dynamics, easy to exit
• Commitment is the hidden cost: a COO hire has long-term structural impact on the organisation