Skip to content

04Industry

Scaling & founder-led companies

There’s a stage every growing company hits where the founder quietly becomes the operating system. Decisions queue behind one person, quality depends on a few people, and every new client or market exposes a seam. The company needs operating discipline but can’t yet justify — or find — a full-time COO. That gap is exactly where a fractional one changes the trajectory.

Every founder-led company that grows far enough hits the same wall, and it rarely announces itself. The very thing that made the early company work — the founder in every decision, holding the standard in their head, catching what would otherwise slip — becomes the thing that caps it. Past a certain size the founder is no longer running the business; they are the business’s operating system, and a single person cannot scale. Decisions queue behind them. The team waits for sign-off that only one person can give. The week disappears into operational detail, and the work only the founder can do — strategy, the most important relationships, the next bet — gets squeezed into the edges.

What makes this stage genuinely hard is that it does not feel like a structural problem; it feels like a personal one. The founder concludes they need to delegate better, manage their time more tightly, work a little harder. But the issue is not effort or discipline — it is that the company outgrew improvisation and never replaced it with an operating model. Quality still rests on a few heroic individuals rather than on how the work is designed. Every new client, market or product line adds load the structure was never built to carry, and the cracks show up as missed delivery, firefighting and a leadership team that is permanently reactive. Growth starts feeling heavier rather than easier, which is the clearest signal the structure is straining.

The trap is that a full-time COO is both premature and hard to hire at this point — the complexity does not yet justify a permanent executive package, and operators of the right calibre are difficult to attract to a company still building its systems. That gap, between having outgrown improvisation and not yet being ready for a full-time operations executive, is exactly where a fractional COO changes the trajectory. The job is to take the operating console off the founder’s desk: install a cadence so decisions stop waiting on one person, make ownership unambiguous, build the quality and governance layer that holds under growth — and then document it and hand it back, to the team or to the full-time COO the company is finally ready to hire.

What tends to break

  • Every decision routes through the founder; the business waits.
  • Quality holds together on a few key people, not on the system.
  • Growth feels harder, not easier — the structure is straining.
  • A full-time COO is too much, too soon, and hard to hire.

How I help

  • Install a weekly operating cadence so decisions stop waiting on one person.
  • Make ownership of every critical process unambiguous.
  • Build the quality and governance layer that holds under growth.
  • Document it and hand it back — to the team or an incoming full-time COO.

Sound familiar?

01

The business pauses when the founder is away.

02

You’re firefighting more as you grow.

03

You know you need senior operations help, just not full-time yet.

The fit

Fractional COO

An operating partner inside the business — not a deck about it.

In depth

The operating detail for this sector.

When the founder becomes the bottleneck

The signal is rarely dramatic. It is the steady accumulation of decisions waiting on one person — a quote that needs the founder’s eye, a hire that needs their nod, a client issue nobody else feels authorised to settle. Each is small; together they are a queue that sets the speed of the entire company, and that speed is now one person’s available hours. The founder feels it as never having enough time, but the real problem is that authority has not been distributed. The first work of a fractional engagement is to find the decisions that genuinely need the founder and the far larger set that only reach them out of habit, then move the latter to where the work is. The business stops waiting the moment decisions stop routing through a single inbox.

Why quality on heroics does not scale

In a young company, quality is often held together by a few exceptional people who simply care enough to catch what slips. It works, and it hides the absence of a system — right up until the company grows past what those individuals can personally cover. Then the heroics run out: the people who held the standard are stretched too thin, or they leave and take the tacit standard with them, and quality becomes erratic in a way nobody can quite explain. The fix is not more heroes; it is to make quality a property of how the work is designed rather than of who happens to be watching. That shift, from depending on individuals to depending on the system, is what lets standards survive both growth and turnover.

Cadence is what replaces the founder’s instinct

Early on, coordination happens in the founder’s head — they hold the whole picture and steer by feel. That instinct does not scale, and nothing has been built to replace it, so as the company grows things start falling between people. A weekly operating cadence is the replacement: a short, disciplined rhythm where the right people look at the few numbers that matter, surface what is at risk, and make decisions that stick. It is not more meetings; it is fewer, sharper ones that take coordination out of one person’s head and put it into a structure the whole team can run. The cadence is how a company keeps its grip on operations once it is too big for any individual to hold it all.

Fractional, not premature — getting the timing right

The honest reason to go fractional at this stage is that a full-time COO is the wrong tool for the moment. The complexity does not yet justify a permanent executive package, and operators of real calibre are hard to attract to a company still building its systems — you risk overpaying for someone underused, or hiring below the level you actually need. A fractional COO gives you the seniority now, sized to what the business can absorb, and is structured to wind down rather than entrench. The aim is explicitly to make the role redundant: install the operating model, prove it holds, and hand it to the team or to the full-time COO you will be genuinely ready to hire once the systems and the scale justify one.

Giving the founder their job back

The point of taking the operating console off the founder’s desk is not to push them aside — it is to give them back the work only they can do. A founder buried in operational detail is not doing the thing the company most needs from them: setting direction, holding the key relationships, making the next bet. Every hour spent approving routine decisions is an hour not spent on the future. A good engagement is measured partly by what the founder stops doing — and by whether the parts of the week the operating model was eating come back to them. The best outcome is a founder who is doing more of what made the company worth building, because the machinery underneath now runs without them in every loop.

When you are not ready for this yet

This is the wrong call at the wrong time in two directions, and I will say which one you are in. Too early, and there is not yet enough operation to systematise — the founder’s direct attention is still the right tool, and the cost of installing structure outweighs the gain; come back when the seams are actually showing. Too late or too large, and the complexity may genuinely justify a full-time COO now, in which case a fractional arrangement under-serves you and the honest advice is to hire the permanent leader. And in any case, if the founder is not truly willing to hand over real decision authority, no operating partner can succeed — the role becomes an expensive observer. I would rather get the timing and the fit right than take an engagement that cannot work.

Questions

Common questions.

The clearest test is what happens when you are away: if delivery slows, decisions pile up, and the team waits rather than acts, the company is running on you rather than on a system. Day to day it shows up as a queue of small approvals that only you can give — a quote, a hire, a client issue nobody else feels authorised to settle. Each is minor; together they set the speed of the whole company to your available hours. It feels like not having enough time, but the real issue is that authority has not been distributed to where the work happens.

Because the problem is structural, not personal. Delegation fails when there is no operating model underneath it — no clear ownership, no cadence, no agreed standard — so work handed off comes straight back, and you conclude you have to do it yourself. Better time management just rations a constraint without removing it. What actually frees a founder is installing the system that makes delegation safe: unambiguous ownership of each critical process, a rhythm that surfaces problems early, and quality built into how work is designed. Once that exists, decisions stop routing through you because they no longer need to, not because you are trying harder to let go.

It can be, and I will tell you honestly. If there is not yet enough operation to systematise — if your direct attention is still the right tool and the seams are not really showing — the cost of installing structure outweighs the gain, and you should wait. The signal to act is internal rather than a headcount: decisions queueing behind one person, quality depending on a few heroes, growth creating firefighting instead of leverage. Most often that lands somewhere between roughly fifty and a few hundred people, but the deciding factor is whether the operating model has stopped scaling cleanly, not the size of the team.

At this stage a full-time COO is often the wrong tool for the moment. The complexity does not yet justify a permanent executive package, and operators of real calibre are hard to attract to a company still building its systems — so you risk overpaying for someone underused, or hiring below the level you need. A fractional COO gives you that seniority now, sized to what the business can absorb, and is structured to wind down rather than entrench. The aim is to make the role redundant: install the operating model, prove it holds, and hand it to your team or to the full-time COO you will genuinely be ready to hire later.

No — the opposite. The point of taking the operating console off your desk is to give you back the work only you can do: direction, the key relationships, the next bet. A founder buried in routine approvals is not doing what the company most needs from them. The engagement distributes authority to where the work is and makes your managers clearer and stronger, not sidelined. A good engagement is measured partly by what you stop doing and whether the parts of the week the operating detail was eating come back to you. The best outcome is a team that runs without you in every loop.

Most run six to twelve months, and by design they end. The cadence is heavier during the early diagnosis and installation phases and lighter as ownership transfers to your team. The goal is never to make the company dependent on one more person; it is to install an operating model — cadence, ownership, measurement, documented playbooks — that your own people, or an incoming full-time COO, can run without me. The honest test of the work is whether a capable team could pick it up and keep it running after I leave. If they could, the engagement is finished; if not, it is not.

It is the structure that replaces improvisation: a weekly cadence where the right people review the few numbers that matter and make decisions that stick; unambiguous ownership of every critical process so work does not fall between people; a quality layer that makes good outcomes a property of how work is designed rather than of who is watching; and clear decision rights so authority sits where the work happens. Early companies run on the founder’s instinct holding all of this in their head. An operating model takes it out of one person’s head and puts it into something the whole team can run as the company grows.

You keep it. Because the engagement is built to end, the artefacts matter as much as the months: a documented operating cadence and who runs it, an ownership map for every critical process, a leadership scorecard with each metric defined, decision rights, and playbooks for the processes that carry the most risk. The handover is deliberate — to your existing team, or to the full-time COO the company is finally ready to hire. The aim is something durable rather than a rented pair of hands: an operating model your own people can hold and improve without me in the room.