An SME does not need a COO simply because it reaches a particular revenue or headcount threshold. Two companies of comparable size may have radically different needs depending on their model, complexity, growth rate and the founder’s role.
The useful question is therefore not “are we large enough?” but “is our decision and execution system still appropriate for what the company has become?”
The first signal: the founder becomes the interface between every function
In a small company, it is normal for the founder to connect sales, marketing, delivery, finance and customer relationships. Early on, this centralisation can even be an advantage: decisions are fast and coherence is protected.
The problem begins when the company grows but the architecture does not. Functional leaders exist, yet cross-functional issues continue to escalate:
- trade-offs between sales and delivery;
- customer promises that are difficult to fulfil;
- competing priorities;
- resource allocation;
- incidents spanning several teams;
- projects without an overall owner.
At that point, the founder is no longer simply leading the company. They are personally performing the operational coordination function.
The second signal: managers optimise their function, not the system
A sales director may hit targets while placing excessive pressure on operations. A marketing team may generate leads without improving pipeline. A support function may install a tool without achieving adoption.
This does not mean those leaders are performing badly. It means that no one sufficiently owns the interfaces.
The COO’s role is precisely to make functions work together: expose trade-offs, align measures, clarify handovers and resolve problems that do not belong to any single department.
The third signal: growth damages quality or margin
A healthy company should learn and improve as it grows. When each new customer adds disproportionate coordination, rework or errors, growth is revealing a fragile operating system.
Symptoms may appear gradually:
- longer delivery times;
- inconsistent data between tools;
- customers receiving different answers;
- teams creating their own procedures;
- managers consumed by emergencies;
- reporting arriving too late to support decisions.
A COO is not there to “put a process everywhere”. The role identifies the few mechanisms that protect quality and profitability without making the company rigid.
The fourth signal: strategic projects do not land
A CRM redesign, new market, offer change, automation, reorganisation or AI programme rarely fails because of a lack of ideas. It fails because it must coexist with day-to-day work without a sufficiently strong owner.
When the leadership team decides but the organisation cannot state clearly:
- who resolves trade-offs;
- who delivers;
- in what order;
- with which resources;
- against which success criteria;
the company needs cross-functional execution capacity. That capacity may be provided by a COO, transformation director or fractional leader depending on the duration and intensity required.
The fifth signal: the founder’s absence would immediately slow the company
One simple question often reveals operational maturity: what would happen if the founder were unavailable for three weeks?
If important decisions, critical relationships and trade-offs would remain blocked, the risk is not only workload. It is the absence of a transferable operating system.
A COO can work on:
- genuine delegation of decisions;
- escalation thresholds;
- operating reviews;
- data quality;
- useful documentation;
- manager accountability.
Does that mean recruiting immediately?
Not necessarily. Needing a COO function does not always mean a permanent full-time role is the first answer.
A Fractional COO may be appropriate to:
- diagnose and design the role;
- install the first operating cadences;
- own a limited portfolio of issues;
- prepare the team for a future organisation;
- test whether the need genuinely justifies recruitment.
An Interim COO can act quickly during transformation or a vacancy. A permanent hire makes sense when the workload and responsibility will remain daily and enduring.
The right time is when complexity becomes structural
A COO is not a status symbol or another management layer. It is a response to complexity that can no longer be absorbed healthily by the founder and functional leaders.
The right moment comes when interfaces, trade-offs and cross-functional execution become a job in their own right. Waiting too long costs energy, quality and opportunities. Hiring too early creates an unclear role.
The decision should therefore begin with a precise diagnostic: where is execution being lost, who absorbs that loss today, and which operational capacity needs to exist tomorrow?