A Fractional COO's First 90 Days: The Week-by-Week Plan, With Deliverables

Ninety days is long enough for a fractional COO to change how your business runs and short enough that any drift shows up in the calendar, which is why the fractional COO first 90 days deserve a plan written down before anyone signs. Provider pages tend to describe the role and the rate but rarely the sequence, so what follows is the operator's version: what happens in each phase, which numbers get pulled, and the specific deliverables you should expect at each checkpoint, so that you can hold any provider to them, whether that provider is Vitori or anyone else.

The plan assumes a founder-led technology services business somewhere between 20 and 60 people, a fractional COO working two to three days a week, and a founder who has admitted, at least privately, that too much still runs through them.

Before day one: agreeing what the fractional COO first 90 days are for

A good engagement starts with a short written brief that names the felt pain, whether that is delivery slipping, margins eroding or a board asking awkward questions about founder dependency, together with who the fractional COO reports to and what authority they hold. If the brief cannot say whether the COO is advising the leadership team or making changes directly, the first month will be spent negotiating that rather than doing the work.

Weeks 1 to 4: the diagnostic

The first month is diagnosis, and it should be deliberately time-boxed, because discovery expands to fill whatever time it is given.

Weeks 1 and 2: interviews and the numbers

The fractional COO should interview the founder at length, then every member of the leadership team, then a handful of people closer to delivery, since the people doing the work usually describe the bottleneck more accurately than the people managing it. Alongside the interviews, the numbers to pull are the ones that show whether the operation can carry the growth:

• Gross margin by client and by project over the last four quarters, not just the blended figure.
• Utilisation and bench, broken down by role, so that one lumpy quarter can be separated from a structural problem.
• Pipeline coverage against the resourcing plan, which shows whether sales and delivery are working from the same forecast.
• Project overruns and write-offs, and where in the lifecycle they tend to appear.
• A log of the decisions the founder made in the last month, which is often the most revealing document in the whole diagnostic.

Weeks 3 and 4: where the bottlenecks usually are

In our experience the constraints cluster in a few familiar places: the founder acting as routing layer for approvals nobody else feels able to give, a handover from sales to delivery that relies on memory, resourcing managed in a spreadsheet one person understands, and leadership meetings that report on the past instead of deciding anything. We assess these against the three pillars of the Operational Scale Framework, Growth, Delivery and Operations, and place each pillar on one of four maturity stages from Build to Enterprise, because a business is rarely at the same stage in all three and the gap between them is usually where the pain comes from.

Day 30 deliverables: a written diagnostic of no more than a few pages, a maturity assessment across the three pillars, a ranked list of three or four priorities rather than a long catalogue of observations, and an agreed 60-day plan with owners and dates.

Days 30 to 60: quick wins, cadence and decision rights

The second month is where changes start shipping, and a founder should be able to point to something that works differently by the end of it.

Quick wins that earn credibility

Quick wins are small, visible fixes that relieve pressure without redesigning anything, such as a single resourcing view that sales and delivery both use, a standard handover document for every new contract, or a rule that no project starts without an agreed margin target. Their purpose is partly practical and partly political, since a team that sees one change stick is far more willing to accept the larger ones that follow.

Installing the operating cadence

Cadence means the rhythm of meetings and reports through which the business steers itself: typically a weekly leadership meeting that works from a short scorecard, a monthly review of margin and utilisation, and a quarterly session that resets priorities. The fractional COO should run these at first and then hand them to the people who will own them, because a cadence that only works when the COO is in the room has not been installed.

Drawing up decision rights

This is usually the hardest part for founders, and it involves writing down who decides which things, up to what limits, and when a decision must come back upward. We cover the method in detail in our decision rights playbook, but the short version is that approving hires, pricing exceptions and client escalations are where founder involvement tends to be heaviest and least necessary.

Day 60 deliverables: at least two shipped quick wins with evidence that they are being used, a documented cadence already running for several weeks, a signed-off decision rights matrix, and a scorecard the leadership team reviews without prompting.

Days 60 to 90: operating model changes that hold

The third month moves from fixes to the structural changes that the diagnostic identified, which might mean redefining a delivery lead role so it carries real margin accountability, separating account management from delivery so that one person is not doing both badly, or building a resourcing process that no longer depends on the founder's memory.

Success is measured against the baseline taken in weeks 1 and 2, so that the conversation at day 90 is about movement in margin, overruns, founder decision load and meeting quality rather than about how busy everyone has been. Not every number will have moved in 90 days, and an honest provider will say which ones are lagging indicators that need another quarter to show.

Day 90 deliverables: the priority changes implemented and owned by named people, a comparison against the day-one baseline, a short written operating model covering structure, decision rights and cadence, and a clear recommendation on what happens next, including the option of stopping.

What a bad first 90 days looks like

The failure patterns are easy to recognise once named. The first is endless discovery, where interviews continue into month two and the output is a thicker report rather than a shorter list. The second is the shadow founder, where the fractional COO becomes the new routing layer and the business is just as dependent as before, only on someone else. The third is activity without shipping, where there are workshops, frameworks and slide decks but nothing in the business works differently at day 60. If you see any of these, raise it at the next checkpoint rather than waiting for the renewal conversation you will otherwise dread.

A fractional COO who is still diagnosing at day 60 has not started the job.

Honest reasons to end the engagement at day 90

Stopping at day 90 is often the right outcome rather than a failure. The changes may have held and the leadership team may be running the cadence themselves, in which case continued support would be a comfort rather than a need. The diagnostic may have shown that what the business needs is a permanent operations leader, which we discuss in fractional COO vs full-time COO, and the best use of the remaining time is shaping that hire. Or the real constraint may sit elsewhere, in finance or in the commercial model, and a fractional COO is not the right answer to every operational problem.

How Vitori runs its own first 90 days

Our engagements follow the sequence above because it is the one we hold ourselves to: a fixed diagnostic phase against the Operational Scale Framework, then a focused partnership against three or four agreed priorities, with ongoing embedded support offered only where it is genuinely needed. Under the Operator model we embed as fractional leadership and implement the changes directly, rather than handing over recommendations for someone else to carry out, and you can see more of how we work before deciding whether that suits you.

To give an anonymised illustration of the shape, a typical engagement with a founder-led services firm finds Delivery a stage behind Growth, because the business has been winning larger contracts faster than it has built the resourcing and handover processes to deliver them, and the 90 days are then spent closing that gap and moving the founder out of day-to-day approvals. We do not publish client names or invented figures, but we will walk any prospective client through the deliverables from past engagements in a first conversation.

Where Vitori fits

If you are close to hiring a fractional COO, the checkpoints in this article are worth putting into the contract, whether with Vitori or anyone else, because they turn a vague engagement into one you can measure. Consultants who diagnose and leave have their place, but it is a different purchase. What we offer is an operator who stays accountable until the changes hold, working to a named method, with the aim of leaving you a business that runs, and scales, without the founder in every decision. If that is the conversation you need, you can contact us here.