Blog
Fractional COO

The 90-Day Operating System Install — A Founder's Guide

Atif AliAtif Ali5 min read· Updated

Founders considering a fractional COO or operating system install usually want to know one thing before anything else: what actually happens, week by week. Not the pitch, the actual sequence. Here it is, phase by phase, with what 'done' genuinely looks like at day 90.

Days 1–30: Diagnose

This phase produces one deliverable: a written operations audit naming the two or three highest-friction workflows in the business — not a generic framework, a specific list built from interviews, a stack audit, and mapping every place a decision currently routes back to the founder. No process gets changed yet. Changing things before the diagnosis is complete is how you end up optimizing something that wasn't actually the constraint.

Days 31–60: Install

The meeting rhythm and scorecard go live — a weekly cadence, a short list of measurables with owners, a place everyone can see the same numbers. In parallel, the two highest-friction workflows named in the audit get rebuilt end to end, not patched. By day 60, someone other than the fractional operator should be able to run at least one of them.

Days 61–90: Automate and hand off

Repetitive work that's been running manually moves into automation — the busywork identified during the install phase, not new scope invented late. Ownership of each rebuilt workflow formally transfers to a named internal person. This is the phase that's most often skipped by advisory-only engagements, because it's also the phase where the engagement's value stops being visible in a deck and starts being visible in whether the business runs without the operator in the room.

What 'done' actually looks like at day 90

  • A written audit exists and named the real bottlenecks, not generic ones
  • A weekly scorecard is live, with owners, reviewed on a fixed cadence
  • The two highest-friction workflows are rebuilt and run by someone other than the operator
  • At least one piece of repetitive work has moved into automation
  • A named internal owner exists for what was installed — the business doesn't depend on the operator staying forever

What the founder needs to commit to

  • Time in the first month for interviews and a review of the audit findings
  • Attendance at the weekly meeting once it is live, without cancelling it when the week gets busy
  • Willingness to hand specific decisions to named people, and to leave them there
  • A decision-maker available within a day or two when the install needs a call made
  • Patience with the first few weeks of the scorecard, which will feel clumsy before it feels useful

What the diagnostic interviews cover

In the first month, each member of the leadership team, and usually a few people below them, is interviewed individually. The questions are practical: what does a normal week look like for you, where do you wait on someone else, what decisions do you have to escalate, what would you fix first if you could, and what has been tried before that did not stick.

Alongside the interviews, the tools the business runs on are reviewed: the CRM, project management, accounting, communication and any automations. The goal is to find where work and decisions actually flow, which is often different from what the org chart suggests. The audit at the end of the month names specific workflows and specific decision bottlenecks, with evidence from the interviews behind each one.

What can derail the 90 days

  • Scope creep in the middle month, when every newly discovered problem gets added to the install
  • A key leader who quietly opts out of the meeting rhythm or the scorecard
  • Treating the audit as optional reading instead of the basis for every decision that follows
  • Automating in the final month before the rebuilt workflows have been run manually long enough to stabilise
  • No internal owner identified by day 60, which leaves nobody to hand over to

What happens after day 90

At day 90 there are usually three paths. The business runs the installed system itself, with the internal owners holding it. The engagement continues at a lower intensity for another quarter, focused on the next set of workflows from the audit. Or a full-time operations leader is hired into a role that is now clearly defined by the work already done. Which path is right depends on how well the handoff landed, and that should be judged against the day-90 checklist rather than how anyone feels about it.

Related reading

Common questions

Yes, though the scope is smaller. With a small team the audit may find a single core bottleneck, and the install focuses on that plus a lightweight meeting rhythm and scorecard.
Atif Ali

Atif Ali

Fractional COO and EOS Integrator. Ten years in the operator seat across the US, UK and Australia — and the person who builds the automation instead of subcontracting it.

More about Atif

Want to see what this looks like for your specific bottlenecks?

Thirty minutes, no pitch deck — just a map of what the first 90 days would actually involve.

Book a call