What a Fractional COO Does and When to Hire One

The title can be read as administration or back-office management. In a fractional COO engagement it means something broader and more consequential: the operating system of the business.

That system is made of a small number of things — how work flows from a commitment to a delivered outcome, who decides what, which numbers are watched, and how often the people responsible look at them together. When those are clear, the business scales without the founder in the middle of every decision. When they are not, growth makes the ambiguity more expensive.

• The operating cadence. The weekly, monthly, and quarterly rhythm of reviews, decisions, and follow-through, and the discipline to keep it running when the week gets busy.
• Process and workflow design. How work actually moves between teams, where it stalls, and what gets documented so it does not depend on tribal knowledge.
• Metrics and accountability. The few measures that reflect whether the business is working, who answers for each one, and what happens when it slips.
• Systems and tooling. Whether the systems in use reflect how the business works — including the CRM, project tooling, and reporting that leadership relies on.
• Organisational clarity. Roles, responsibilities, and reporting lines, so ownership is written down instead of negotiated in each situation.
• Cross-functional arbitration. Settling the trade-offs between sales, delivery, finance, and marketing that no single department head can settle alone.
• Capacity and planning. How demand, staffing, and delivery capacity are matched so growth does not simply convert into chaos.

The emphasis is on own rather than advise. A fractional COO is accountable for the operating rhythm continuing to function, not only for recommending that one exist.

• Not an executive assistant. The role is not calendar management or inbox triage. It is structural work on how the business operates.
• Not a project manager. A project manager runs one initiative to completion. A COO owns the system those initiatives run inside.
• Not a full-time COO. Part-time hours mean prioritisation. Expect the role to focus on the few constraints that matter rather than every process that could be improved.
• Not a rescue for a broken business model. Operational discipline makes a sound model run better and makes an unsound one fail faster, which is useful but not the same thing.
• Not permanent. The intended outcome is capability the business keeps, with a documented operating system and internal people who can run it.

The clearest signal is that the founder or owner is still the operating hub of the company. In practice it can show up like this:

• Every cross-functional decision ends up in the founder’s calendar or inbox.
• Delivery quality depends on who happens to be on the project rather than on a defined process.
• Each department reports its own numbers, and nobody can assemble a single view of the business.
• Handoffs between sales, delivery, and finance are where things quietly go wrong.
• Key knowledge lives with two or three people and cannot be looked up anywhere.
• Hiring adds capacity but does not add throughput, because the work has no clear path through the company.
• Priorities conflict between teams and get resolved by escalation rather than by design.

• The business is too small to have meaningful cross-functional complexity, and the constraint is simply capacity.
• What is missing is one specific technical system, not the operating layer around it.
• Leadership is not prepared to change how decisions are made, or to let a process be standardised.
• The underlying issue is the offer, the market, or the pricing rather than how the work gets executed.

In the first two cases a narrower engagement — a process improvement project, or a systems implementation — may be the better use of money.

The first 90 days can be organised into three phases: observe, build, then run. Building before observing produces an operating model for a company nobody has watched closely.

Phases vary with size, scope, and starting point. They describe the work, not a guarantee of results.

Judging an operating role on a single month of revenue is the wrong test. The better question is whether decisions are getting faster and the business is getting easier to read:

• Fewer decisions reach the founder, and the ones that do are genuinely strategic.
• Team leads can state their numbers and their targets without preparation.
• Handoffs between functions stop being the place where quality drops.
• New hires become productive against a documented process rather than a mentor’s memory.
• Reported metrics match reality, including when the news is bad.
• Priority conflicts get resolved by an agreed method rather than by escalation.

Legacy Leadership Group works on the operating layer described here: operational consulting and business structure, process improvement and workflow design, SOP creation and documentation, KPI and performance systems, CRM strategy and implementation, organisational design and role mapping, and business continuity and change management. Broader executive-level guidance across strategy, systems, and people sits under fractional executive advisory.

That combination matters because operating problems cross boundaries. A process that stalls is connected to how roles are defined, which is connected to what gets measured, which is connected to the systems holding the data. Working on one without the others risks improvement that quietly reverts.

If you are trying to work out whether the constraint is operating discipline, leadership capacity, or something else entirely, that is a reasonable first conversation to have. Start a conversation with where the business is today. To see how the operating work is organised, the services pages describe each capability.

If the friction is concentrated at the handoff between sales and delivery, building a repeatable sales process defines the stages, exit criteria, and ownership that make that handoff reliable.

If the operating problem shows up as a pipeline that cannot be read, how to diagnose a weak B2B pipeline covers the stage-level numbers worth watching. For the comparable senior role on the revenue side, see what a fractional sales leader does and fractional CRO vs. VP of Sales.