What a Fractional COO Should Track in the First 90 Days

Fractional COOs join growing businesses to bring operating discipline without a full-time hire. The first ninety days determine whether leadership trusts the role: too much change early erodes confidence; too little leaves the same fires burning.

This guide lists priority metrics, meetings, and outcomes a fractional COO should establish first in a UK SME, before reshaping systems or software.

See fractional COO use case and strategy vs OKRs vs KPIs for context.

Days 1–30: map reality

Goals: Understand how decisions actually get made, not how the handbook says they should.

Activities:

• Interview functional leads: priorities, blockers, metrics they trust
• Collect existing KPI sources, OKR decks, management accounts format
• Attend one cycle of leadership, sales, and delivery meetings as observer
• Document decision bottlenecks and duplicate reporting

Outputs: one-page operating assessment shared with CEO. No major process changes yet.

Metrics to establish first

Prioritise metrics leadership will review monthly without heroic manual effort:

• Cash and runway (finance)
• Revenue vs plan and gross margin trend
• Pipeline coverage or backlog (commercial/ops)
• Utilisation or throughput (delivery)
• One customer health metric (retention, NPS, or churn)

Read good KPI examples for sector-specific additions.

KPI tracking with clear owners beats a twenty-slide metrics workshop nobody updates.

Days 31–60: install rhythm

Goals: Predictable leadership cadence before tool changes.

Activities:

• Implement or tighten weekly leadership agenda (see weekly leadership meeting)
• Launch monthly KPI review with five to seven metrics
• Align company OKRs to current quarter or facilitate lightweight reset if broken
• Assign executive sponsors to company objectives

Outputs: three consecutive weeks of leadership meetings held with actions logged.

Days 61–90: connect execution layers

Goals: Single view of priorities, metrics, and follow-ups.

Activities:

• Link OKRs to KPIs where key results should mirror live data
• Retire duplicate spreadsheets if a system of record is agreed
• Prepare first QBR or board pack with consistent definitions
• Propose one operational fix with measurable before/after (e.g. debtor days, overrun %)

Outputs: leadership can answer "are we on track?" from one dashboard or pack without a pre-meeting rebuild.

What to defer past day 90

• Full software replatform unless spreadsheets actively break decisions
• Complete OKR cascade to every individual
• Reorganisations without data showing the structural problem
• Long consultant-led process design

Trust comes from visible rhythm and honest metrics, not framework slides.

Working with founders and CEOs

Fractional COOs succeed when they:

• Publish a ninety-day plan with weekly milestones visible to CEO
• Fix one painful meeting before adding new meetings
• Show early wins in cash, delivery, or pipeline metrics leadership already cares about
• Escalate strategic misalignment to CEO, not functional blame

Common first-90-days mistakes

• Introducing enterprise OKR process to a fifteen-person company
• Metrics without owners or baselines
• Tool purchase before cadence exists
• Changing too many rituals before attending existing ones

Reporting progress to the CEO

Send a brief weekly note: meetings held, metrics updated, decisions blocked, one recommended change for next week. CEOs hire fractional COOs for rhythm and clarity; surprise reorganisations without data erode the relationship faster than slow progress on metrics.

By day ninety, leadership should answer three questions from one source: Are KPIs on track? Are OKRs moving? Are decisions from reviews closed?

Fractional COOs who document baseline metrics before changing process earn credibility faster than those who arrive with a new framework deck. Show the numbers first, then simplify rituals, then consolidate tools. When the ninety-day plan succeeds, extend with deeper OKR cascade or board reporting upgrades rather than replacing everything at once.

In regulated or investor-backed SMEs, align the ninety-day plan with reporting the board already expects. Map which metrics appear in management accounts versus operational KPIs before you rename or merge them. Clarity on definitions prevents the fractional COO from becoming the person who "changed the numbers" when the real issue was inconsistent labels across finance and operations.

Schedule a day-sixty checkpoint with the CEO to confirm the operating rhythm is stickier than the tools conversation. If meetings hold but metrics stay stale, fix data paths before buying software.

Next steps

• Draft your ninety-day plan using the three phases above
• Agree five KPIs with CEO before day thirty
• See Elevale pricing for a fractional COO stack: OKRs, KPIs, tasks, and reporting

Start your 14-day free trial and give fractional COOs one command centre for operating rhythm.