First 100 Days Fractional COO Playbook: The Axis Method

Why This Matters Now

Most first-100-days playbooks for an Operations Architect tell you how to get comfortable in the seat. Ours is designed to make that seat unnecessary by day 90, documented and handed back. That is a different goal, and it requires a different sequence.

Lower-middle-market companies at $10M to $100M in revenue are not underperforming because they lack ambition. They are underperforming because the operating system was built on memory, goodwill, and tools nobody ever reviewed. The Axis Method makes that visible fast, then fixes it in a sequence that cannot be skipped. Every stage has a named output. The final output is a client who does not need us anymore. Learn more about the full engagement at our Operations Architect page or read the complete Axis Method breakdown.

Days 1–14: Diagnose Before You Touch Anything

The single most expensive mistake an Operations Architect makes is arriving on day one with a fix already in mind. I have spent a decade across Amazon, International Paper, Spirit Halloween, Maersk, and Levi Strauss touching roughly $3B in operational impact. (OAG receipt: cedric.career_summary) Every time I skipped a real Diagnose stage, I paid for it later. The Diagnose stage of the Axis Method exists to prevent that cost.

• Interview every owner of a recurring process. Document what exists, not what should exist.
• Run the OIL Framework interrogation layer: every system gets a question before it gets a fix.
• Map cash flow timing, headcount cost, and tool spend in one shared working doc, not a slide deck.
• Flag the three highest-risk single points of failure before recommending a single change.
• Most lower-middle-market businesses are running on memory and goodwill. The Diagnose stage makes that visible before it becomes a crisis.

The output of Diagnose is a single working document: every recurring process named, every tool listed with its monthly cost, and the top three single points of failure flagged in plain language. No recommendations yet. No roadmap. Just a receipt of what exists. That document becomes the foundation for every decision made in days 15 through 90.

Days 15–45: Stabilize (Stable Beats Elegant in This Phase)

Stabilize is not about building the right long-term system. It is about stopping the bleeding. The OIL Framework's Delete step runs hard here. Before a single automation gets considered, every duplicate tool, every redundant approval layer, and every vendor contract that nobody remembers signing goes through a cut decision.

• Pick the fix that works this week, not the one that might scale in theory next year.
• Apply DefaultFail thinking: assume the current system will break, then decide if it is worth keeping.
• Cut duplicate tools during this window. One client replaced a $199/month Jobber Grow plan and recovered approximately $1,500 per year before month two was over. (OAG receipt: mobile_mechanic.savings)
• Recurring SaaS charges, vendor contracts, and approval layers go through the OIL Delete step before anything gets automated.
• The goal of Stabilize is not elegance. It is a system that does not fall over when someone calls in sick.

DefaultFail is the operating mindset for this phase. You assume the current system will fail, then you decide whether it is worth rebuilding or worth deleting. Most lower-middle-market operations carry significant waste before the first automation workflow is even considered. Automating before you delete just makes a faster, more expensive version of the same problem. The OIL sequence, Interrogate then Delete, is non-negotiable here. See how operational waste compounds over time when teams skip this step.

Days 46–75: Document So the Runbook Outlives the Engagement

This is the phase most engagements stall in. Documentation feels slow. Clients want to keep building. But documentation is not a follow-up task. It is the actual deliverable. A stabilized process that lives only in someone's head is not stabilized. It is one resignation letter away from a crisis.

• Every stabilized process gets a written runbook. Not a Loom video. Not a Notion dump. A document a new hire can execute on day one.
• Name every tool, every trigger, every owner. If it cannot be handed off, it is not done.
• The runbook belongs to the operator, not to OAG. We write it to make ourselves removable.
• Cross-reference every runbook against the OIL Simplify step: if the written process still has unnecessary steps, cut them before they get institutionalized.
• If the written process is still complicated after the Simplify pass, the process itself was not simplified enough. Go back one step.

The OIL Simplify step runs inside Documentation, not before it. Writing a process down reveals complexity that verbal walkthroughs hide. Every runbook we produce gets a Simplify pass: if the written version has more than seven steps for a routine task, we cut before we publish. The runbook belongs to the client on day one of this phase. OAG holds a copy for reference during Hand-off, then it is gone. Visit the OAG blog for examples of runbook structures used in live engagements.

Days 76–90: The Hand-Off Is the Deliverable

Every other Operations Architect engagement ends with a final presentation, a summary deck, or a list of recommendations. Ours ends with a proof-of-run. The client executes the documented system live, with OAG watching, not guiding. If they cannot run it without us on the call, the documentation failed and we rewrite before day 90 closes.

• By day 90 the client runs the documented system without OAG on the call. That is the test.
• A clean hand-off includes a one-page process map per critical function, named owners, and a 30-day break-in checklist.
• We don't replace your operating function. We architect the system it runs on, then hand it back, documented, in 90 days.
• If the hand-off requires OAG to explain it, the documentation failed. Rewrite before day 90 closes.
• Exit criteria are set on day one, not day 90. The client knows what done looks like before OAG starts.

The Hand-off stage is also where the Axis Method proves its design. Most engagements that drag on indefinitely do so because the exit criteria were never written down. We set those criteria in the Diagnose stage and post them in the shared working document. By the time day 90 arrives, both sides already know whether the hand-off is clean. There are no surprises. The hand-off is the deliverable.

Days 91–100: Compound or Exit, Not Both

Days 91 to 100 are a buffer for operator confidence, not a window for new work. If the team is still stabilizing at day 91, the engagement needs a frank conversation, not a scope expansion. If the team is running clean, the Compound stage opens as an option.

• The Axis Method's fifth stage, Compound, is optional. It is for teams ready to layer growth onto a stable operating base, not teams still stabilizing.
• If OAG is still essential at month twelve, we did the job wrong. The engagement is designed to end.
• Some clients move from the Axis Method into a StackOS audit to cut SaaS spend once the operating system is stable. That is a separate scope.
• Days 91 to 100 are a buffer for operator confidence, not for new work. New problems that surface here go into a future engagement, not the current one.
• Exit criteria are set on day one. The client knows what done looks like before OAG starts.

Compound is the only stage where the engagement might extend. And even then, it runs on a separate scope with a new exit definition. The base engagement, Diagnose through Hand-off, is 90 days. That is the commitment. I run Obsidian Axis Group on $74 per month in total infrastructure cost. (OAG receipt: oag.monthly_run_cost) The point is that operational discipline is not expensive. It is intentional. The same principle applies to the engagement itself: it ends when it is supposed to end, not when it becomes comfortable.

Where the OIL Framework Lives Inside the 100-Day Arc

The OIL Framework, Interrogate, Delete, Simplify, Automate, is not a parallel track. It is the operating logic baked into each Axis Method stage. The sequence is non-negotiable. Skipping steps is how teams end up with Zapier workflows maintaining problems that should have been deleted two months earlier.

1. Interrogate runs in Diagnose (days 1–14). Every process, tool, and meeting gets one question: does this exist because it works, or because nobody deleted it?
2. Delete runs in Stabilize (days 15–45). Duplicate tools, redundant approvals, and vendor contracts with no clear owner are cut before any fix is designed.
3. Simplify runs in Document (days 46–75). If the written runbook is still complicated after a Simplify pass, the process was not simplified enough. Go back.
4. Automate runs last, after Stabilize and Document are done. The sequence is non-negotiable. Automating a broken process makes a faster broken process.

The OIL order matters because each step assumes the previous one is complete. You cannot delete effectively without interrogating first. You cannot simplify what has not been stabilized. You cannot automate what has not been simplified. Teams that jump straight to Automate, usually with Zapier or Make, are building speed on top of dysfunction. The result is more automated chaos. Learn more about how OAG defines and cuts operational waste at the glossary.

Axis Method vs. Standard Consulting: A Direct Comparison

The comparison above is not a dig at consulting firms. It is a scope clarification. Standard consulting is designed to produce recommendations. The Axis Method is designed to produce a running system the client owns. Those are different products at different price points. The right choice depends on what the client actually needs at this stage of their business. If you are at $10M to $100M in revenue and need someone to operate alongside you, not advise from outside, the Operations Architect engagement is the closer fit.

What a Clean Hand-Off Actually Looks Like

I want to be specific here because most descriptions of a fractional COO engagement hand-off are vague. A clean hand-off at OAG includes four things, all present before day 90 closes.

• A one-page process map per critical function, naming every tool, every trigger, and every owner.
• A written runbook for each mapped process, executable by a new hire with no prior context.
• A 30-day break-in checklist the operator uses after OAG exits, covering the most likely failure points in the first month of independent operation.
• A proof-of-run: the operator executes the system live, with OAG watching, not guiding. If they need us to explain a step, we rewrite that step before the clock runs out.

The Spirit Halloween engagement gives a sense of what this looks like at scale. A system running $75 per month replaced $48,000 to $96,000 per year in UKG, ADP, Dayforce, and Kronos licensing costs for approximately 500 associates. (OAG receipt: spirit_halloween.system_cost) (OAG receipt: spirit_halloween.headcount) That system was documented, handed off, and the client ran it without OAG on the call. That is what done looks like. See the full fractional COO glossary entry for how OAG defines the role versus the standard industry label.

Sources

1. Consultancy.eu. "Management consulting fees and rates worldwide." Consultancy.eu, 2023. https://www.consultancy.eu/news/5747/management-consulting-fees-and-rates-worldwide.

OAG receipts cited

• cedric.career_summary
• oag.monthly_run_cost
• spirit_halloween.system_cost
• spirit_halloween.headcount
• mobile_mechanic.savings