You’ve probably felt it before you named it. Decisions backing up, important work slipping between teams, your calendar filling with things only you can touch. The business is growing, but you’re not scaling with it.
At some point, two options come into view: a chief of staff, or a COO. They both sound like senior hires that solve the problem. They are not the same hire, and they don’t solve the same problem.
The choice you’re facing
A chief of staff and a COO are senior hires that solve different problems. A CoS multiplies the founder: coordinating across functions, keeping priorities moving, and making sure decisions produce follow-through. A COO owns operations, running a repeatable delivery system so the business executes without the founder present. The question is which of those two things you are actually missing.
Vistage UK describes the CoS as a “brain partner” and bridge between the CEO and the rest of the business, a role built around coordination and decision velocity rather than operational ownership. The distinction matters because a business with poor coordination and a business with an absent operational owner can look similar from the outside. They need different fixes.
When founders in the £5m-£10m revenue range feel stretched, the instinct is often to reach for a COO. Monkhouse and Company argue that this is frequently the wrong sequence: the immediate problem is usually a stretched founder, not a missing operator. A CoS, at this stage, can restore capacity without adding a full operating layer the business may not yet be ready for.
When a chief of staff is right
A CoS is usually the right hire when the main bottleneck is CEO capacity: getting priorities agreed, ensuring cross-team decisions land, and keeping follow-through from slipping. Talent Edge links rising demand for the role to the 30-50 employee mark, the point at which the CEO’s work shifts from personally pushing priorities to ensuring the system works across others.
Three conditions tend to make the case. First, important work is living in the cracks between functions, with no single owner to resolve the gaps. Second, leadership meetings are generating updates rather than decisions. Third, priorities are shifting faster than the team can absorb, usually because the founder hasn’t had time to arbitrate.
The Chief of Staff Network notes that before making the hire, the CEO should test whether these tasks genuinely belong with an executive coordinator, or whether they reflect something deeper. If the functions themselves are working but the orchestration between them has broken down, a CoS is a clean fit. If the functions themselves are not working, the problem sits one level down and the CoS will not solve it.
Inflection points also sharpen the case. A fundraise, an international launch, or a significant product rollout all demand coordination and decision speed. At these moments, a CoS often creates more value than adding another functional manager would.
When a COO is right
A COO is the better hire when the business already has a repeatable operating model and needs an executive owner for day-to-day delivery. Monkhouse and Company place the threshold at roughly 100 people, the point at which the scale typically justifies a full operational executive and the structure can absorb one without creating confusion about who runs what.
The key diagnostic is whether the business has a known machine that someone needs to run, rather than a coordination problem the founder needs help managing. When the answer is the former, a COO adds real value: accountability for delivery, management of functional leaders, and the authority to make operational calls independently of the founder.
A COO hired too early, before the operating model is settled, tends to create a different set of problems. The role demands clear functional accountability to work well. If the business is still working out how it operates, the COO becomes another person the founder has to manage rather than someone who takes genuine weight off them.
What it costs to get this wrong
Getting the hire wrong in either direction is expensive. A CoS brought into a business that needs operational leadership can become a high-cost patch: adding coordination overhead without fixing the underlying delivery gaps. A COO hired before the operating model is repeatable can produce confusion rather than structure, particularly if functional leaders haven’t been established first.
The less obvious cost is authority. A CoS working well operates with real delegated authority from the founder. If the founder treats the role as a sophisticated administration job and withholds meaningful decision-making, the appointment fails regardless of the person in the chair. The Chief of Staff Network is direct on this point: the relationship requires clear expectations and the willingness to hand over real responsibility, not just access to the diary.
There is also a regulatory dimension for businesses where a CoS would coordinate AI projects or digital programmes. The FCA’s £17.5 million fine against Capita in 2025 for inadequate cyber and outsourcing controls, and the ICO’s £14.8 million fine against Advanced Computer Software Group following a ransomware attack in 2024, both point to the same pattern: coordination without governance is not a defence. If a CoS becomes the de facto gatekeeper for AI adoption across the business, the compliance obligations under UK GDPR and the vendor controls the NCSC recommends still sit with the business. The CoS can orchestrate them. The business still owns them.
What to ask before you decide
Five questions tend to separate the two decisions cleanly, and working through them honestly before you brief a recruiter saves months of the wrong hire. They distinguish a founder who needs more capacity from one whose business needs an executive to run operations, and they surface the third possibility: that neither is the right next move.
Is the real problem execution coordination, or a missing function owner? If tasks are slipping because nobody is ensuring follow-through across teams, that’s a coordination gap. If specific functions such as finance, people, or delivery have no clear leader, filling those roles will do more than any generalist hire.
Will this person be a genuine proxy, or an expensive assistant? A CoS who cannot make decisions in the founder’s name adds process without adding capacity. Be honest about whether you’re willing to delegate real authority, not just administrative work.
What decisions will they own, and which stay with you or the functional leads? If this question is hard to answer, the role isn’t ready to be hired into.
What does success look like in 90 days? Faster decisions, fewer dropped actions, a cleaner leadership cadence, or a specific project delivered are all valid answers. “Things feel less chaotic” is not.
If you hire this role, what do you stop doing? The hire adds capacity only if it frees the founder’s time for work that matters. Without that answer, you’re adding a person rather than removing a constraint.
If you’re working through this decision now and want to pressure-test the specifics against your own business, Book a conversation.
