Fractional COO for agencies: the founder's guide.

What does a fractional COO actually do in an agency?

Four jobs. Design the operating system the agency is missing. Run the delivery cadence and the team day to day for a period. Build the automations that remove the manual work. Hand the whole thing over documented. The order matters, and most of the value is in the first and last.

"Fractional" just means part-time and for a defined period. It does not mean advisory. A fractional COO who only produces recommendations is a consultant with a nicer title. The useful version sits inside your tools and your Slack, runs the Monday standup until your team can, and leaves with the systems working.

In a founder-led paid media or marketing agency the work tends to land in the same places:

• Client onboarding. From signed proposal to first report, as one repeatable flow instead of whatever the founder remembers to do that week.
• Delivery cadence. Daily standups, weekly reporting, clear owners, blockers surfaced before the client notices.
• Reporting. Spend pacing, ROAS and KPI scorecards pulled from the ad platforms on a schedule, so nobody builds a deck on a Monday morning.
• Team management. Check-ins, accountability, hiring support, and being the person the team goes to instead of you.
• Automation. The repetitive work in n8n, Make or Zapier: briefs, approvals, invoice chasing, Slack updates, research.
• Documentation. SOPs and playbooks written as the systems are built, not as a project at the end.

A typical week in the first month is two to three days inside the agency: mapping, running cadence, building. By month three it is a day or less, because the point is to need the fractional COO less, not more.

How do you know you need one?

The honest test is what happens when you step away. If delivery slows, decisions queue and the team waits, the founder is the system. That is the problem a fractional COO exists to fix.

The symptoms usually come as a set:

• The founder is the system. Work bounces back to you. Nothing is written down. Every decision routes through your inbox.
• Delivery does not scale. Every new client feels like starting from scratch. Month two is where the cracks show, and month two is where churn starts.
• Reporting is a tax. Hours of manual pulling every week that should be automatic.
• Tools, not a system. Slack, ClickUp, Sheets and Notion are all in use. None of them are joined up.
• No real week off in months. You are running sales, delivery, ops, hiring and finance from one desk. That is a job you cannot resign from, not a business you own.

If you want a number on it, the leak calculator on the homepage turns your hours, team size and churn into a monthly figure in about a minute.

Fractional COO vs ops manager vs VA vs full-time COO

They are four different jobs, and agencies tend to hire them in the wrong order: a VA into chaos, then promote the chaos, then a COO to fix what the first two hires could not. Match the seniority of the hire to the type of problem, not to how painful the problem feels.

A good ops VA runs a defined process with a right answer: invoicing, onboarding admin, scheduling, data entry. Hand one a chaotic agency and you get a faster mess, because the defined process is the missing part.

An ops manager drives a machine that already exists: trackers, standups, deadlines, the sales-to-delivery handover. Most are excellent at running a system and average at building one. If your systems are broken, an ops manager will manage the breakage very diligently.

A full-time COO owns the whole operation, and at the right size that is the correct hire. The worst thing you can give a new COO is a mess and a prayer.

The part nobody says out loud: the roles change at every stage, but the design problem never goes away. Someone has to build the machine at £15k a month and someone has to rebuild it at £150k. That is project-shaped work. Paying a full-time salary for it is how agencies end up overstaffed and still chaotic. Mapped to revenue, the order that holds up looks like this:

What does a fractional COO cost compared with hiring?

A full-time UK operations director runs £70,000 to £110,000 a year in salary before employer National Insurance, pension, recruitment fees and the three to six months it takes to hire. A fractional COO is engaged for a defined programme and scoped to the size of the operational problem, so the total is a fraction of that, and it stops when the job is done.

The cheaper comparison is the one founders rarely make: what they are already paying. If you spend 25 hours a week in delivery, client comms and approvals, at even a conservative founder rate of £150 an hour, that is around £16,000 a month of your time on work someone or something else could do. Add the team hours lost to manual admin and the revenue you replace every month because of churn, and the fractional COO is usually the smallest number on the page.

Penguin Ops does not publish a price list because the scope is set by the leak, not by a package. It is scoped on the diagnostic call, after two weeks inside the agency, and every engagement is month to month after the programme.

What does a 90-day engagement look like?

Two weeks of diagnostic, then build and run, with the team running delivery without the founder by day 90. At Penguin Ops the four stages are Map, Gap, Loop and Free, and each one ends with something the agency keeps.

Weeks 1 to 2: Map

Trace every workflow end to end. How a lead becomes a client, how work is briefed, built, checked and reported, and every point where it routes back to the founder. The real flow, not the org chart. This produces a written leak map and a prioritised build plan.

Weeks 2 to 3: Gap

Rank the gaps by hours and margin recovered, not by how interesting they are to fix. Missing owners, undocumented steps, tools doing half a job, reports built by hand every Monday. The top three go first.

Weeks 3 to 10: Loop

Build, test and refine with the team in the room. Onboarding flow, delivery cadence, reporting, team check-ins and the automations behind them. First systems are live inside 30 days. Each loop closes when the team runs it without the fractional COO in the call.

Weeks 10 to 13: Free

The founder steps back from delivery and into the work only a founder can do: pipeline, hiring, partnerships, a week off. Everything is documented and handed over. The test of the work is whether the systems outlive the engagement.

What should you get back at the end?

If any of it still depends on the fractional COO being present, the job is not finished. The handover should include the documents, the systems and the people running them.

• SOPs and playbooks for every process that was built, written as it was built
• A client onboarding flow that runs the same way for every new client
• A delivery cadence the team runs itself: standups, weekly reporting, owners
• Reporting that builds on a schedule from the ad platforms
• The automations, with documentation and someone on the team who understands them
• A team that no longer routes every decision through the founder

Ask about this before you sign anything. "What do I keep if you leave on day 91?" is the question that separates operators from advisers.

When is a fractional COO the wrong hire?

More often than people selling fractional services admit. It is the wrong call when there is no operation to run yet, when the real ask is a tool rather than a process change, or when the founder is not ready to let someone else run things.

• Pre-revenue or a handful of clients. You need clients before you need systems. Fix sales first.
• You want a tool, not a process. Buying ClickUp does not create a delivery cadence. If the question is "which software", the answer is cheaper than a COO.
• AI before the workflow exists. An agent on top of an undocumented process automates the chaos. Systems first, then AI where it earns its place.
• You need someone in the building every day. That is a full-time hire. A fractional COO is deliberately not that.
• You will not give access. If an outsider cannot see the tools, the numbers and the team, they cannot map the leak. The engagement will stall at the diagnostic.

How do you evaluate a fractional COO?

Ask whether they have done it inside an agency, whether they build or only advise, what the handover contains, how they measure the result, and what the commitment is. The answers tell you more than the title.

• Have you run operations inside an agency, not just consulted to one? Agency delivery has its own failure modes: the sales-to-delivery handover, month-two churn, reporting that eats weekends. Someone who has lived them moves faster.
• Do you build, or do you recommend? You want the person who opens n8n and writes the SOP, not the one who sends a deck about it.
• What exactly is handed over? See the list above. Get it in writing.
• How will we know it worked? Founder hours out of delivery, churn in months two and three, hours to produce the weekly report. Pick the numbers at the start.
• What is the commitment? A defined programme, then month to month. Lock-ins are a tell.

What it looked like in practice

Before Penguin Ops, I was Head of Operations at a paid media agency. Churn was around 40%. Clients were leaving in months two and three, which is the signature of a delivery problem, not a sales problem. The root cause was the handover: sales closed, delivery found out by Slack, and every client's first month was improvised.

We documented a 30-day onboarding process and automated the handover. Churn across months two and three went from 10% to 0% on the next cohort. Over the following eight months overall churn came down to under 10%, and revenue went from £50k a month to £200k with the same core team. No new hires until the systems could support them.

I learned the underlying discipline earlier, in my father's multi-site pharmacy business, where a missed step is not a late deliverable. It is a patient. The pharmacies ran on paper SOPs long before anyone called it operations. Systems before software, and well before AI.