If a fractional COO cannot tell you what the first ninety days look like, the engagement will drift. Here is the plan we run. It is not complicated, and that is the point.
Before day one: the diagnostic
Every engagement starts with a People, Process, Results diagnostic. We interview the founder and each member of the leadership team. We review the financials, the pipeline, and whatever scorecard exists. We watch how work actually moves through the company: how a client gets onboarded, how the month gets closed, how a hire gets made.
The output is a short document that says what is working, what is broken, and what we will do first. Founders are often surprised by how much of it they already knew and had not said out loud.
Days 1 to 30: install the cadence
The first month is about structure, and it is the least glamorous phase.
We install the weekly leadership meeting. Same day, same time, same agenda every week. We use an L10-style format: a scorecard review, a check on quarterly priorities, and a prioritized list of issues to solve in the room. The meeting runs ninety minutes and ends with decisions, not discussion.
We build the scorecard. Five to ten numbers, reported weekly, that predict the quarter. Not the financials. Leading indicators: proposals sent, jobs started, on-time delivery, cash collected, open positions. Getting these numbers to show up reliably every week is harder than it sounds and it usually takes the full month.
We set the quarter’s priorities. Three to five, each with a named owner and a definition of done. Everything else waits.
By day 30, the leadership team is meeting weekly with real numbers in front of them and knows what the company is trying to finish this quarter. That alone changes how the company feels.
Days 31 to 60: fix what hurts most
With the cadence running, the second month goes after the two or three processes the diagnostic flagged as the most painful. Usually one of them is a handoff: sales to delivery, delivery to billing, hiring to onboarding. Usually one of them is a role that has been undefined for so long that the person in it has no idea what they own.
We document the process as it should run, assign an owner, and put it into practice. We define the roles that have been vague and have the direct conversations about who is in the right seat. Some of those conversations lead to changes.
The founder’s role in this phase is to stop solving these problems personally. That is often the hardest part of the engagement.
Days 61 to 90: hand it to the team
The third month is about stepping back. The COO moves from running the meeting to coaching the person who will run it. Issues get solved by the managers, with the COO in the room but not at the front. The quarterly planning session for the next quarter is led by the leadership team, with the COO facilitating.
By day 90, the operating system exists and the team is running it. The COO’s job shifts from building to leading, and the scope of the engagement narrows accordingly.
What the founder should expect
You will spend more time in structured meetings in month one than you are used to. That is temporary.
You will hear things about your company from your team that you have not heard before, because the structure gives people a place to say them.
You will be asked to stop doing things. Decisions you have always made, problems you have always solved. This is where engagements succeed or fail.
You will see the scorecard tell you something in week seven that you would otherwise have discovered in month four.
What comes after
Some clients move to a lighter advisory rhythm: monthly reviews, quarterly planning, an on-call relationship. Some hire a full-time COO into the system we built. Some find that the leadership team is now strong enough that no COO is needed. All three are good outcomes. The engagement is measured by whether the company runs differently, not by how long it lasts.