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

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

Related reading