The Complete Guide to Hiring a Fractional COO

Introduction: why this guide exists

Hiring a fractional COO is one of the most misunderstood decisions a CEO can make. Some leaders treat it as a cheap substitute for a full-time executive. Others treat it as a consultancy by another name. Both views lead to bad hires, wasted fees and, worse, a business that is no better organised twelve months later.

This guide gives you a clear, honest framework for the decision. It covers what the role actually does, what it costs, the engagement shapes that work, how to evaluate candidates, and the red flags that should end a conversation early. It is written for the CEO or owner of a business that has outgrown its original way of working: typically somewhere between £1M and £20M in revenue, with a team large enough that you can no longer see the whole operation from where you sit.

Who this guide is for

You will get the most from it if several of these are true:

Your business has grown faster than the systems underneath it

Decisions queue up behind you, and you are the answer to most questions

You have a capable team, but no one owns the whole operation

You have tried a tool, a consultant or a manager hire, and the problem came back

You are weighing a full-time COO but are not sure the business can carry that salary yet

Who it is not for

If your business is pre-revenue, if you are looking for someone to do administrative work, or if you want a plan you can implement alone without anyone senior in the room, a fractional COO is the wrong tool. The guide will help you see why, and what to look at instead.

How to use this guide

Read Parts 1 to 3 to decide whether the model fits. Read Parts 4 to 6 to choose the right shape and shortlist candidates. Use Parts 7 to 9 when you are in conversations with specific people, and keep the appendices open during interviews. Part 10 is about your own role, because the single biggest predictor of success is not the quality of the fractional COO. It is how well the CEO works with them.

What you will walk away with

A clear test for whether growth has outpaced your systems

A way to compare a fractional fee against the real cost of your current friction

A choice between the three engagement shapes, based on where your constraint sits

A set of interview questions that separate operators from advisers

A scorecard and a proposal checklist you can use on any candidate, including us

One note on bias. This guide is published by Markinly, a fractional COO practice, so we have an interest in the answer. We have tried to write the guide we would want to read if we were on your side of the table, including the parts where the honest conclusion is that you should not hire anyone yet.

Part 1: What a fractional COO actually does

A fractional COO is executive-level operations leadership delivered part-time, typically one to three days a week, from inside your business. The role covers the same territory as a full-time COO: process, people systems, reporting, accountability and execution. What changes is the cost profile, and the expectation that the engagement builds systems which eventually run without them.

The job, in one sentence

A COO makes the business run predictably so that the CEO can spend their time on direction, relationships and growth. Everything else is detail.

The five territories

Every COO role, fractional or full-time, covers five areas. Where a candidate is weak on any of them, you will feel it.

What “embedded” really means

The word that matters most in the definition is inside. A fractional COO attends your leadership meetings, speaks to your team directly, owns specific outcomes and is accountable for results. They are not a visiting adviser who delivers a report and leaves. If the person you are speaking to describes their work mainly as recommendations, assessments or frameworks, you are talking to a consultant, which is a different (and sometimes perfectly good) product.

What a fractional COO is not

Not an assistant or administrator. They will not manage your diary or chase invoices. If those tasks are consuming your day, you need delegation and probably an operations coordinator, not an executive.

Not a salesperson or rainmaker. A COO makes the business deliver what is sold. They do not generate demand, although a well-run operation tends to improve retention and referrals.

Not a substitute for a CEO. They execute inside your direction. If the real problem is that you have not decided where the business is going, a COO will expose that fast, but cannot answer it for you.

Not a software installer. Tools are sometimes part of the answer. They are never the starting point.

A day in the life

To make this concrete, here is what a typical embedded day might look like for a business of around forty people:

Review the weekly scoreboard and flag the two numbers that moved

Sit in with the delivery lead to unpick why a project is late, and agree the fix with the people who own it

Rewrite an onboarding checklist with HR after a new hire stalled in week three

Run the leadership team’s weekly meeting, keeping it to the agenda and the issues list

Spend an hour with the CEO on the one decision that is blocking three others

Hand a newly documented process to the team member who will own it from now on

Notice how little of that is strategy slides. It is working alongside your people, in the detail, with a bias for leaving behind something that works.

The part-time advantage

Part-time is not a compromise. It is a design choice with real benefits:

Seniority without the full-time cost. You get someone who has seen your problems before, at a fraction of the commitment.

Pressure to build systems rather than dependency. A person with two days a week cannot be the bottleneck, so they have to make the business work without them.

Pattern recognition from several businesses. Good fractional operators bring what has worked elsewhere, adapted to you.

A natural end point. The engagement has an arc, which keeps both sides honest.

There are trade-offs too. A fractional COO is not in the building every day, cannot be everyone’s first call, and depends on your team to carry things between visits. Part 4 covers how the engagement shapes handle that.

Part 2: Do you need one?

The clearest test is this: growth has outpaced your systems. The business still works, but only because a handful of capable people, usually including you, hold it together through effort and memory. That works up to a point. Past it, every new customer, hire or product adds friction faster than it adds capacity.

The warning signs

These are the patterns we see most often. One or two on their own are normal. Four or more usually mean the constraint is operational.

Deadlines slip without a single cause. Every late project has a different explanation, which is itself the signal. The cause is the system, not the incident.

Decisions queue behind the CEO. Your team waits for you, not because they are weak, but because no one has been given clear authority or a clear standard.

Onboarding takes months. New hires learn by shadowing, because nothing is written down in a form they can use.

No one can see the whole workload. Understanding what is in flight requires a meeting, a spreadsheet chase or a conversation with three people.

Quality varies by who did the work. Customers get a different result depending on which team member handled them.

Good people are leaving or burning out. Often the best performers, because they absorb the most of the system’s slack.

You are firefighting. Your calendar is full of urgent problems and your strategic work happens at weekends.

Growth feels heavier, not easier. Revenue is up, margin and morale are not.

A ten-question self-diagnostic

Score each statement from 0 (not true) to 2 (very true). Be honest, and ideally ask a senior colleague to score it independently.

How to read your score. Zero to six: your systems are probably adequate for now; look at specific gaps rather than the model. Seven to thirteen: friction is real and worth measuring; a diagnostic conversation is sensible. Fourteen or more: the operation is likely constraining growth, and a structured intervention will probably pay for itself.

This is a simple screen, not a diagnosis. It is meant to give you an honest starting point for a conversation, not an answer.

Problems a fractional COO does not fix

Be cautious if the real issue sits elsewhere:

A weak proposition or no demand. Operations cannot fix a product people do not want.

A CEO who will not delegate. A COO needs genuine authority. If you intend to retain every decision, you are buying an expensive assistant.

A broken leadership team. If the senior team is in conflict, that needs addressing first, or in parallel.

A cash crisis. Urgent financial triage needs a different specialist.

A business that is too small. Under roughly £1M revenue, or with a handful of staff, a good operations manager and a few simple routines are usually better value.

Is it the right time?

There is a cost to waiting, and a cost to moving too early. Hire too early and you pay for structure the business is not ready to use. Hire too late and the founder-led improvisation hardens into culture, which is far harder to change. The best moment is usually when the pain is clear but the habits are not yet set: when you can name the problem, and the team is still willing to change how it works.

Part 3: What it costs, and what it replaces

A fractional engagement costs a fraction of a full-time COO, but the comparison that matters is not salary versus fee. It is fee versus the cost of the friction you are living with now. Most leaders never measure that second number, which is why most fee discussions go wrong.

The full-time comparison

A full-time COO in a UK small or mid-sized business typically commands a six-figure package before equity. The headline salary is only part of it. Add employer’s National Insurance, pension, benefits, bonus, recruitment fees (often a percentage of first-year salary), and the cost of a six-to-nine-month search. Then add the risk: a senior hire who does not work out is expensive to exit and slow to replace.

A fractional engagement scales with days per week, runs for a defined period, and avoids most of those fixed costs. You pay for the time you use, and you can change the shape as the business changes.

How fractional fees are structured

Structures vary, and the variation tells you something about the candidate. The common models are:

In every case, the fee should scale with days per week, not headcount or revenue, and the engagement should have a defined arc rather than an indefinite retainer. We cover both points again in Part 8.

We have deliberately not published a market rate here. Rates vary by region, seniority and sector, and any number printed in a guide goes out of date. Ask each candidate for a day rate and an expected number of days, and compare on total cost for the same period and the same deliverables.

The cost of chaos

The hidden number is what poor systems cost you each month. It has four components:

Wasted team effort. Rework, waiting, duplicated work, chasing information, fixing mistakes. In businesses without strong systems, a substantial share of team time goes here. We use 25% as a working assumption for businesses before systems are installed, but you should measure your own rather than rely on any benchmark, ours included.

Founder and CEO hours. Time you spend firefighting, deciding things others should decide, or filling gaps. Value it at what that time would earn if spent on growth.

Lost or stalled growth. Deals you could not take, launches that slipped, customers who churned because delivery was inconsistent.

Attrition. The cost of replacing good people who left because the environment wore them down.

A worked example

The figures below are illustrative. Replace them with your own before drawing any conclusion.

Against a figure like that, an engagement should be judged on whether it can credibly reduce the number by a meaningful share and keep it reduced after the engagement ends. If a proposal cannot be connected to a number you recognise, the proposal is not ready.

If you want to run this on your own business, use the Cost of Chaos calculator in our tools library before you evaluate any proposal, ours included.

What a fractional COO replaces, and what it does not

It can replace or defer: a full-time COO hire; a layer of senior management you cannot yet afford; a series of disconnected consultants; some of your own operational load.

It does not replace: your leadership team; a finance function; specialist functions such as HR, legal or IT; or the need to run your business. It makes those parts work together.

Judging ROI honestly

A sensible test has three parts:

Baseline. Agree at the start which two or three numbers will show improvement, and record where they stand today.

Attribution. Be realistic about what is caused by the engagement and what would have happened anyway. Be sceptical of any adviser who claims all of the improvement.

Durability. The most important question is whether the improvement is still there six months after the engagement steps down. That is the difference between a system and a sprint.

One caution. Beware of choosing on price alone. The cheapest option is rarely the lowest cost once you add the months spent on someone who cannot hold the seat. Equally, a premium fee is not evidence of quality. Evaluate on scope, evidence of past results, and handover plan (Parts 6 to 8).

Part 4: The three engagement shapes

Most fractional COO engagements fall into one of three shapes: Transformation, Embedded and Advisory. The right shape depends on where your constraint sits. If execution is failing, embed. If direction is the problem, advise. If both, transform first, then step down the intensity.

Shape 1: Transformation

A 90-day intensive that installs the core operating system. In practice that means five core processes designed and documented, an ownership map showing who is accountable for what, a weekly operating rhythm, and a scoreboard of the numbers that matter.

It works when: the business has capable people but no shared structure; the CEO is ready to make decisions quickly; and there is appetite for change across the leadership team.

It fails when: the intensity exceeds the team’s capacity to absorb it, or when no one is named to own the systems afterwards. A system without an owner decays within a quarter.

What to ask for: a named list of deliverables, a week-by-week plan, and a clear statement of what you and your team must do for it to work. Transformation is not something done to a business. It is done with it.

Shape 2: Embedded

One to three days a week for six to twelve months. The COO leads operations while building the systems and the team to run them, and takes accountability for specific operating results.

It works when: execution is the main problem, there is no senior operations leader, and the CEO wants to hand over operational leadership rather than advice about it.

It fails when: the COO is treated as a permanent fixture rather than a builder. Embedded engagements without a handover plan quietly turn into expensive part-time employment.

What to ask for: a defined arc, with stages. A well-run embedded engagement typically moves from diagnosis and stabilisation, to building and installing, to transferring ownership, and finally to stepping back. Ask the candidate to show you what month nine looks like.

Variation: stepped intensity. Many embedded engagements begin at three days a week and step down to two, then one, as internal owners take over. This can be a sound structure if the step-downs are tied to results rather than the calendar.

Shape 3: Advisory

A weekly structured session for leaders who want a thinking partner without the embedded days. The COO reviews the numbers, pressure-tests decisions, holds you accountable to your commitments, and supports follow-through between sessions.

It works when: you have a competent team that can execute, and what you need is a senior outside view, a sounding board and a source of discipline.

It fails when: the business actually needs someone to do the work. Advice does not clear a backlog. If sessions regularly end with “good idea, we will get to it”, move up to an embedded shape.

What to ask for: a standing agenda, written commitments after every session, and a review at 90 days to ask whether this is the right shape.

Choosing between them

Use these questions in order:

Is the main constraint direction or execution? Unclear priorities and shifting strategy point to Advisory. Slipping delivery and missing structure point to Embedded or Transformation.

Does your business have a senior operator today? If nobody holds the whole operation, you almost certainly need more than advice.

How much change can the team absorb at once? A fast install needs readiness. If the team is stretched, a longer Embedded arc is safer than a short Transformation.

How soon do you need results? Transformation compresses the timeline. Embedded gives you depth. Advisory gives you steadiness.

Do you want to be rid of operations, or better at it? The first is Embedded. The second is Advisory.

Combinations and step-downs

The shapes are not mutually exclusive. A common and sensible sequence is Transformation first, then Embedded at a lower intensity, then Advisory as the business runs on its own. Each step reduces cost and dependency. If a candidate offers only one shape and defends it as right for everyone, treat that as a signal. Their model may suit them better than it suits you.

A note on scope drift

The most common way for any shape to go wrong is scope drift: the engagement starts as one thing and quietly becomes another. Embedded work starts absorbing advisory conversations. Transformation turns into permanent operations management. Review the shape at the end of every quarter and write down whether it is still right.

Part 5: Fractional COO versus the alternatives

A fractional COO is one of six ways to solve an operations problem, and not always the best one. Choosing well means being clear about what each option actually delivers. The table compares them on the criteria that matter most.

Fractional COO versus full-time COO

This is the comparison most CEOs start with. The honest answer is that the two roles are not interchangeable at every stage.

A full-time COO makes sense when:

The business is large and complex enough to need a senior operator every day

You have operating systems in place that need continuous leadership, not installation

Revenue can comfortably carry the cost without distorting margins

You have the time and capacity to run a proper search

A fractional COO makes sense when:

The main need is to design and install how the business runs

The business cannot yet justify, or safely carry, a full-time executive

You want to test what a COO would own before committing to a permanent hire

You need experienced help now rather than after a six-month search

There is also a useful third path. Some businesses use a fractional engagement to define the role, build the systems and then hand over to a permanent hire, who inherits something that works. A good fractional COO can help you recruit their own successor.

Fractional COO versus operations manager

An operations manager keeps the current machine running. A COO redesigns the machine. If your problem is that the work is not being coordinated, a manager may be the right answer. If your problem is that the structure itself no longer fits the business, a manager lacks the authority, and often the experience, to change it.

A useful test: would the person need to renegotiate roles, reporting lines or priorities across the leadership team to succeed? If yes, you need executive standing, not a better manager.

Fractional COO versus consultant

This distinction matters more than any other, and it is where most disappointment comes from. A consultant advises. A fractional COO operates. The consultant’s deliverable is usually a document; the COO’s deliverable is a working business.

Many consultants are excellent. If you need a specific piece of analysis, a market review or a specialist assessment, a consultant is often the right and cheaper choice. The problem arises when a CEO hires a consultant for an execution problem, and then discovers they have a well-written plan and no one to carry it out.

The test: ask what the person will be personally accountable for in month three. A COO names outcomes. A consultant names deliverables.

Fractional COO versus coach

A coach develops you. A COO develops the business. The two are complementary and often benefit from working together, but one does not stand in for the other. If you find that you understand your leadership challenges well and still cannot get the business to change, a coach is unlikely to be the missing piece.

Fractional COO versus an implementer of a branded operating system

There are well-known operating frameworks, and certified implementers for some of them. They can be very effective, particularly where a business wants a complete, prescribed method. Two points are worth weighing:

Prescribed versus adapted. A pure framework gives you a clear, consistent structure but may not map neatly onto every business. Some operators use a blended approach, borrowing what fits from several methods.

Method versus leadership. A framework is a set of tools. It does not run your operation. Be clear whether you want a method installed or a leader embedded, or both.

If a candidate is certified in a specific system, ask what they do when the system does not fit. If a candidate is not certified, ask how they decide what to use instead.

Combining options

Some of the best outcomes combine approaches: a fractional COO to lead the build, a specialist for a technical area such as finance or HR systems, and a coach for the CEO. The rule is to avoid paying two people to do the same job, and to be clear about who is accountable for the overall result.

Part 6: Finding, shortlisting and interviewing candidates

The best way to evaluate a fractional COO is to test for operating experience, not presentation. Anyone can describe a framework well. Far fewer can tell you what they did on a Tuesday in month four of a difficult engagement, and what happened next.

Before you look: write the brief

Spend an hour writing down the following. It will sharpen every conversation and expose weak candidates quickly.

The constraint. In two or three sentences, what is stopping the business growing or running smoothly?

The outcomes. What three results would make you call this a success in twelve months?

The authority. What decisions will the COO make without asking you? What stays with you?

The people. Who will they work with directly? Who will resist?

The numbers. Which metrics matter, and where are they today?

The budget and arc. What can you invest, and over what period?

A candidate who reads this brief and asks sharp questions is a good sign. A candidate who ignores it and pitches their standard package is telling you how they work.

Where to look

Our view: warm referral is the best channel by a wide margin. If you cannot find one, treat every other source as the start of a due diligence process, not the end of one.

Building the shortlist

Aim for three candidates. Fewer gives you no comparison. More wastes time and invites decision fatigue. Apply four filters:

Operated, not advised. Have they held operational accountability for a P&L, a team or a function, rather than only advising those who do?

Relevant scale. Have they worked in businesses of your size and stage? Running a 2,000-person company is not the same skill as installing systems in a 40-person one.

Relevant context. Sector experience helps but is not essential. Experience with your kind of problem usually matters more.

Evidence of handover. Can they point to a business that runs well without them now?

The first conversation

Use the first call to listen, not to be sold to. A strong candidate will usually:

Ask more questions than they answer in the first twenty minutes

Want to understand the numbers before discussing a solution

Be willing to say what they would not do, or what is outside their strengths

Describe past work in specifics, including things that went badly

Be wary of a candidate who has a diagnosis before you finish describing the problem.

Interview questions that separate operators from advisers

The full list is in Appendix A. These are the most revealing:

“Tell me about an engagement that did not go to plan. What did you do?” Real operators have stories. How they handle failure tells you more than any success.

“What did you personally own, and what did you recommend that others owned?” This pins down the line between doing and advising.

“How does this engagement end?” The answer should be specific and early, not vague and late.

“What would you want me to stop doing?” A good COO is willing to challenge the CEO.

“What would make you decline this work?” Candidates who accept everything are selling, not selecting.

Reference checks that mean something

Ask for two or three references, including at least one from an engagement that ended more than a year ago. The older reference is the one that tells you whether the work lasted. Ask them:

What was the situation when the COO started?

What specifically changed, and what would you attribute directly to them?

What happened after they stepped back?

Was there anything you would want to have done differently?

Would you hire them again, and for what?

A candidate who cannot or will not provide references from past clients should have a good explanation. Confidentiality is a legitimate reason. Having no one to call is not.

Chemistry and trust

Competence is necessary but not sufficient. You will be working closely with this person, sharing sensitive information and relying on their judgement. Ask yourself:

Would I want them in a difficult leadership meeting?

Do they tell me things I would rather not hear, in a way I can take?

Would my team accept their authority?

Do I trust them with confidential information about people and money?

If the answer to any of these is no, no amount of experience will rescue the engagement.

A paid diagnostic or trial

Before committing to a long engagement, consider a short, paid diagnostic. It tests the working relationship, gives you a concrete output, and lets the candidate demonstrate how they think. A candidate who insists on a long commitment before showing you anything is asking you to take on all the risk.

Many practitioners, including us, offer an initial diagnostic conversation at no charge. Use it to test fit, not to extract a free plan.

Part 7: Red flags when evaluating candidates

The red flags that matter most are the ones that predict dependency, not the ones that predict incompetence. A fractional COO who plans their own handover is the one whose systems will outlast them. The signs below are ordered by how much damage they usually do.

Red flag 1: They lead with a tool

“You need ClickUp.” “You need Monday.” “What you need is a CRM.” When a candidate recommends software before they have mapped how your work actually flows, they are selling a solution to a problem they have not yet diagnosed. Tools amplify whatever process sits underneath them. Install one on a broken process and you get a faster, more expensive version of the same mess.

What good looks like: the candidate asks how work moves today, who touches it, where it waits, and only then discusses whether technology helps. If a tool is the right answer, they can explain why, and what happens to the process if the tool is removed.

Red flag 2: They deliver reports instead of working alongside your team

A 60-page assessment is not an operating improvement. If the proposal is built around audits, reviews, decks and recommendations, ask what changes in the business on day 91. If the answer is “you will have a roadmap”, you have bought consulting, not operations leadership.

What good looks like: deliverables are working things: a documented process the team uses, a meeting that runs, a scoreboard people read, a role with a named owner.

Red flag 3: They cannot name the industries they have operated in

The word that matters is operated. Advising a business and running part of one are different experiences, and the gap shows up under pressure. Ask for specifics: which businesses, what role, what accountability, what size, what outcome.

What good looks like: a clear account of where they held operational responsibility, what was at stake, and what they would do differently now.

Red flag 4: They have no answer to “how does this engagement end?”

This is the most important question in the guide. If a candidate cannot describe the end state, the transfer of ownership and the signs that they are no longer needed, then dependency is the business model. Their incentive is to stay.

What good looks like: a specific description of what your team will own at the end, how the handover happens in stages, and what the candidate will measure to know it has worked.

Red flag 5: One model for everyone

If every conversation leads to the same package at the same price, the package is the product and you are an input. Different businesses have different constraints, and the right engagement shape (Part 4) varies accordingly.

Red flag 6: Vague or inflated claims

Be cautious of:

Percentage improvements with no baseline, no time period and no explanation

Case studies where the client is anonymous and nothing can be checked

Claims of results across implausible numbers of industries or business types

Credentials that cannot be verified

A fair discount applies to confidentiality. Many real clients will not be named. But a candidate should be able to explain what they did in enough detail for you to judge it, and to put you in touch with someone who can confirm it.

Red flag 7: Reluctance to be measured

Ask a candidate how you will know it is working. If they resist agreeing a baseline, resist agreeing metrics, or insist that results are too intangible to measure, be cautious. Operations is one of the most measurable disciplines in business.

Red flag 8: They flatter you

A good COO will challenge your assumptions, sometimes directly. If every conversation is agreeable, you are either hearing what you want to hear or being sold to. Notice whether the candidate ever says something you would prefer not to have heard.

Red flag 9: They want the whole team to change except you

Most operating problems have a component that sits with the CEO: unclear priorities, last-minute changes, reluctance to delegate, a habit of overriding decisions. A candidate who never mentions this is either not seeing it or not willing to say so. Either is a problem.

Red flag 10: Pressure to commit quickly

Artificial urgency (“the price goes up on Friday”, “I only have one slot left”) is a sales tactic, not an operating one. A serious operator would rather lose the engagement than start with the wrong client.

A quick reference

What to do when you see one

One red flag is a question, not a verdict. Raise it directly and see how the candidate responds. A good operator will engage with the concern and may even agree with it. A weak one will get defensive or change the subject. How they handle your challenge during the sales process is the best preview you will get of how they handle it during the work.

Part 8: Scope, contracts and handover by design

A good engagement agreement does three things: it defines what will change, it defines who is accountable, and it defines how the engagement ends. Most disputes with advisers trace back to one of those three being left vague.

This section is practical guidance, not legal advice. Have your own lawyer review any agreement before you sign it.

Define the outcome, not the activity

A weak scope reads: “Provide fractional COO services two days per week.” A strong scope reads: “Within 90 days, install five documented core processes with named owners; implement a weekly leadership rhythm; produce a scoreboard of ten metrics reviewed weekly; reduce average order-to-delivery time from the agreed baseline.”

The first describes time. The second describes what you will have. Time is an input. You are buying the outcome.

The elements of a sound scope

The defined arc

We recommend a defined engagement arc over an open-ended retainer, for a simple reason: a deadline concentrates effort and keeps both parties honest. An open retainer creates a comfortable arrangement in which neither side has a reason to ask whether the work is done.

That does not mean you cannot extend. It means every extension is a decision: you review results, confirm the need and agree a new scope, rather than drifting into another quarter.

Handover by design

Handover should be planned from the first week, not improvised in the last. A well-designed handover has four features:

Named internal owners. Each system, process and rhythm has a person in your business who owns it. If no one can be named, the system will not survive.

Staged transfer. The COO moves from doing, to doing with the owner, to watching the owner do it, to stepping away. Each stage has a visible marker.

Documentation people actually use. Short, practical and kept where the team works. A manual no one opens is not a handover.

A test. The COO deliberately stays away from a process or meeting and checks that it runs. If it does, the handover has worked.

Ask every candidate to describe, for a past engagement, how the handover was staged and what they measured to confirm it held.

Authority and reporting lines

The most common cause of fractional engagements failing is not capability but authority. A COO who cannot make decisions, or whose decisions are routinely overridden, cannot succeed. Agree at the outset:

Who the COO reports to, and how often they meet

Which team members they can direct, and which they can only advise

What spending or hiring decisions they can make

How the team will be told about the COO’s role, and by whom

Write it down, announce it, and then honour it. Nothing undermines a COO faster than a CEO who reverses a decision in a corridor.

Confidentiality, data and conflicts

A fractional COO will see sensitive information about your people, finances and customers. The agreement should cover:

Confidentiality. Clear terms on what stays confidential, and for how long

Data protection. How personal data is handled, particularly if the COO works across several clients and their systems

Conflicts of interest. Whether the COO works with competitors, suppliers or customers, and how that is managed

Intellectual property. Who owns the documents, systems and frameworks created during the work. You will normally want to own what was built for you.

Notice, exit and what happens if it is not working

Build in a way out, for both sides. Typical provisions include a short notice period, a review point after the first 30 to 60 days, and clarity on what happens to work in progress if the engagement ends early. A candidate who resists any exit provision may be more interested in the contract than in the result.

Also agree in advance how disagreement is handled. Many problems become serious because there was no agreed route for raising them.

Employment status

Depending on your country and how the engagement is structured, tax and employment rules may treat a long-term, embedded contractor as closer to an employee than you intend. This varies considerably between jurisdictions. Take advice on your own position, particularly for embedded engagements of six months or more, and for any arrangement where the COO is integrated into your management structure.

Common contract mistakes

Paying for days without defining deliverables

Open-ended terms with no review point

No agreement on who owns the work product

A scope that is silent on what the COO can decide

Ambiguity over unused days, expenses and additional work

Treating the signed agreement as the end of the conversation, rather than the start of a working relationship

Part 9: The first 90 days and how to measure ROI

The first 90 days decide whether the engagement builds momentum or drifts. A good start is visible within weeks: the constraint is named, a few quick wins land, and the team understands what is changing and why.

A typical 90-day arc

Every business differs, but a sound start usually follows this sequence.

What the first two weeks should include

A kick-off with you, covering the brief, authority, boundaries and how you will work together

A short announcement to the team, in your voice, explaining the role and the purpose

Access to the data, tools and people the COO needs

A series of one-to-one conversations with senior team members and a sample of frontline staff

Agreement on the two or three metrics that will define success, with today’s baseline recorded

A fixed weekly check-in with you, which should survive the busiest week

If two weeks pass and none of this has happened, ask why.

Quick wins matter, within limits

Early, visible improvements build credibility with a sceptical team and with you. Good quick wins are small, concrete and quickly reversible: a meeting that finally has an agenda, a recurring problem that finally has an owner, a report that finally shows the number you wanted. Be wary of an engagement that is all long-term build and no early evidence. Equally, be wary of one that chases quick wins at the expense of foundations.

The scoreboard

A scoreboard is a short list of numbers that tell you whether the business is healthy, reviewed on a regular schedule. For most small and mid-sized businesses, ten or fewer measures are enough. The mix should reflect your model, but typically includes:

Throughput. How much work is moving through the business, such as orders, projects or cases completed

Quality. Errors, rework, returns, complaints

Speed. Lead time from request to delivery; time to onboard a new hire

People. Retention, capacity and utilisation, open roles

Commercial. Margin, cash conversion, pipeline coverage

Each measure should have an owner, a target and a threshold at which it triggers a conversation. If a number has no owner, it is a statistic, not a measure.

Measuring ROI at 90 days, six months and twelve months

The most important column is the last. Improvement during the engagement is expected. Improvement that persists after it is the real return.

What a good review meeting looks like

At every quarterly review, expect the COO to cover four things without prompting:

Results against baseline, including the numbers that have not moved

What is working and what is not, and what they would change

What the team now owns, and what still depends on the COO

A recommendation on shape and scope for the next period, including stepping down or ending if that is the honest answer

A COO who recommends their own reduction is demonstrating exactly the behaviour you hired them for.

Signs the engagement is going wrong

You still have no clear answer to “what exactly has changed?”

The team is more confused about who owns what, not less

Meetings have multiplied without decisions improving

Documentation exists but nobody uses it

The COO is increasingly doing the work rather than transferring it

Reviews focus on activity, not results

When you see these, raise them at once, in the weekly check-in, not at the quarterly review. A good COO will welcome the challenge. If you are still unsatisfied after a direct conversation, use the review and exit provisions you agreed in Part 8.

Part 10: Your role as CEO

The single biggest predictor of success is not the quality of the fractional COO. It is whether the CEO changes how they work alongside them. A strong operator inside a business whose CEO keeps overriding, bypassing or ignoring them will produce a worse result than an average operator with real backing.

This part is deliberately direct. Most of what follows is uncomfortable, and most of it applies to almost every CEO we have met, including the best ones.

Five commitments that decide the outcome

1. Give real authority, and use it publicly. Tell the team what the COO owns and that their decisions stand. Then support them in the first moment a decision is unpopular. If the team learns that a COO’s decision can be reversed by asking you, they will ask you.
2. Route questions through the system. The habit that most often undermines a COO is the CEO answering operational questions directly in hallways, chats and calls. Every time you do, you teach the team that the old route still works. Redirect: “That is for [owner]. Take it to them.”
3. Protect their time and the weekly rhythm. The fixed check-in and the leadership meeting are the spine of the engagement. Missing them is a message. If they are the first things you cancel when you are busy, the business will conclude that operations is optional.
4. Accept being challenged. You hired someone senior to see what you cannot. If every observation is met with an explanation, the COO will learn to stop offering them. Ask them regularly: “What am I doing that is making this harder?”
5. Let go of what you have handed over. The hardest part for most owners is not delegating in theory but tolerating a different way of doing things in practice. A process run slightly differently from how you would run it is not a failure. A process that runs without you is a success.

Preparing your team

The team’s first reaction to a new senior person is often suspicion. They may wonder whether the COO is there to cut headcount, to replace them or to judge them. Silence fills with rumour. Address it directly:

Explain why. “The business has grown and the way we work has not kept up. This is about making it easier for you to do good work.”

Explain what changes and what does not. Be clear about what is on the table and what is not.

Explain how they will be involved. The best systems are built with the people who use them, not imposed on them.

Say what the COO is not here to do, including, if it is true, that this is not a redundancy exercise.

Then watch for the people who engage early. They are your internal owners of the future.

Common CEO mistakes

What changes for you

If the engagement works, your role changes. You spend fewer hours answering operational questions and more on direction, customers, partners and growth. You stop being the place where decisions go to wait. Your calendar becomes less reactive.

That shift can feel unfamiliar, even unsettling. Many owners define themselves by being the person who solves everything. Being replaced in that role by a system can feel like a loss before it feels like a relief. It is worth naming this in advance, and deciding what you want your time to go toward once it frees up.

When to step down, extend or end

The right moment to reduce the engagement is when the evidence shows the business can run without the COO for a defined period. The right moment to extend is when there is a specific, measurable next objective that justifies it. The right moment to end is when neither is true.

A useful discipline: at every review, ask the question “If we stopped today, what would break?” If the answer is “nothing”, the work is done. If the answer is “a lot”, the handover has not worked yet, and that is the thing to fix next.

Appendices

These tools are designed to be used, not read. Print them, copy them into your own notes, and use them in every candidate conversation.

Appendix A: Interview questions

Experience and track record

Describe the businesses where you held operational accountability. What was your role, what was the size, and what did you personally own?

Tell me about an engagement that did not go to plan. What happened, and what did you do?

What is the clearest example of a business that runs well today because of work you did, and runs without you?

Which results can you point to with a baseline, a time period and someone who can confirm them?

Diagnosis and approach

Based on what I have told you, what do you think the constraint is, and what would change your mind?

What would you want to see and who would you want to talk to before proposing anything?

How do you decide between fixing a process, changing a role and changing a tool?

What do you do first in the first two weeks, and why?

Working with me and my team

How do you handle a team that is resistant or exhausted by change?

What would you want me to stop doing?

How do you handle a disagreement with the CEO?

What authority do you need to be effective, and what do you do if you do not get it?

Handover and exit

How does this engagement end?

What does month nine look like?

How do you stage the transfer of ownership, and how will we know it has worked?

What would make you recommend that we stop earlier than planned?

Commercial

How is your fee structured, and what is included?

What happens if scope changes, or days go unused?

How do you handle confidentiality, and do you work with competitors or suppliers?

What would make you decline this engagement?

Appendix B: Candidate scorecard

Score each candidate from 1 (weak) to 5 (strong) on each criterion immediately after the conversation, before you compare notes with anyone else. Multiply by the weight and add up the totals.

Treat any score of 1 on operating experience or handover as disqualifying, whatever the total.

Appendix C: Proposal checklist

Before you sign, confirm that the proposal includes each of the following:

☐ A written statement of the constraint, in language you recognise

☐ Two or three outcomes, with baselines and target dates

☐ Named deliverables that are working things, not documents about work

☐ The engagement shape, and the reason it fits

☐ Days per week and how unused days are treated

☐ The COO’s authority, reporting line and decision limits

☐ What you and your team must provide

☐ A defined arc with quarterly reviews

☐ A staged handover plan with named internal owners

☐ Fees, payment terms and the treatment of scope changes

☐ Notice period and exit provisions for both sides

☐ Confidentiality, data protection and conflict terms

☐ Ownership of documents and systems created for you

☐ Reference contacts you have actually spoken to

☐ Legal review of the agreement and advice on employment status

Appendix D: Frequently asked questions

Is a fractional COO the same as an interim COO? Not quite. An interim COO normally covers a full-time seat for a limited period, often to fill a vacancy or manage a transition. A fractional COO works part-time, usually across more than one client, with a focus on building systems. The two overlap, and some practitioners offer both.

How many days a week do I need? It depends on the shape. Transformation is front-loaded and intense. Embedded engagements typically run one to three days a week. Advisory work is often a single weekly session. Start with the smallest commitment that can move the constraint, and review it.

Will my team resist a part-time executive? Some will at first. Resistance usually fades when the COO is visibly useful, when authority is clear and when the CEO backs the role. It grows when the COO seems peripheral or when the CEO undermines them.

Can a fractional COO work remotely? Some of the work can be done remotely, particularly advisory and analysis. Embedded leadership works best with real presence, because much of the value comes from being in the room. Ask each candidate how they would split on-site and remote time and why.

What if I outgrow the engagement or want to hire full-time? That is a good outcome. Many businesses use the engagement to define the role, build the systems and recruit a permanent COO. Ask candidates whether they will help with this, and how they would hand over.

How is this different from hiring an operations manager? An operations manager keeps the current machine running. A COO redesigns it, with executive authority across functions. See Part 5.

What if it does not work? Build in the review points and exit provisions in Part 8, and raise concerns early. A good operator would rather end an engagement that is not working than collect fees for it.

How long until I see results? Most businesses should see signs of progress within the first 30 to 60 days: a named constraint, a working rhythm and early wins. Material improvement in the numbers typically takes longer, and the real test is whether the results last once the COO steps back.

Appendix E: Glossary

Constraint: the single factor most limiting the business’s growth or performance at the current time

Operating rhythm: the fixed schedule of meetings and reviews through which the business is run

Scoreboard: a short list of the numbers that show the state of the business, reviewed on a fixed schedule

Ownership map: a document showing who is accountable for each function, process and result

SOP: standard operating procedure; a documented, repeatable way of doing a task

Handover: the staged transfer of ownership of systems from the COO to your team

Embedded: working inside the business, as part of the leadership team, rather than from outside it

Scope drift: the gradual change in what an engagement covers, without a formal decision

How to start well

Start with diagnosis, not commitment. A serious operator will map your constraint before proposing anything. That is exactly what the free 60-minute Ops Diagnostic is for. Bring your three biggest frustrations and your current numbers. You will leave with your constraint named and three quick wins, whatever you decide afterwards.

Before the call, have these ready:

Your three biggest operational frustrations, in plain words

Your headcount and rough revenue range

The five numbers you would want to see weekly, if you could

What you have already tried, and what happened

Your own result from the Cost of Chaos calculator

This guide is a starting point, not a prescription. If you take one thing from it, make it this: judge any fractional COO, including us, on whether they can tell you exactly how the engagement ends, and prove it from the businesses they have already left behind.

Book your free Ops Diagnostic at markinly.com