The question I get asked most, once a founder is past "what is a fractional COO", is a more practical one: what will you actually do? It is a fair question. Operations is easy to talk about in the abstract and hard to picture in practice. So here is the honest version of a first 90 days, phase by phase.
A quick caveat before the detail. No two businesses are the same, and a good operator adapts to what they find rather than running a fixed playbook. But the shape below holds across most engagements, because the sequence matters more than any single fix.
Days 1 to 30: understand before you touch anything
The fastest way to lose trust and break things is to arrive with answers. The first month is about earning the right to have them.
I spend it learning how work actually moves through the business, not how the org chart says it does. That means talking to people at every level, sitting with the teams who do the work, and following a few real jobs end to end to see where they stall, loop back, or fall through the cracks. I look at the numbers you already have and, just as usefully, the ones you do not.
By the end of the month you get something concrete: a clear, prioritised picture of what is actually broken, what it is costing you, and the order I would fix it in. Not a vague audit. A short list you could act on tomorrow, with the reasoning behind each item.
Days 31 to 60: fix the highest-leverage things first
With the map in hand, the second month is about doing, not planning. But not everything at once. I start with the one or two fixes that unlock the most, usually the ones removing you as the bottleneck or stopping the biggest leaks.
That often looks like giving a critical area a single clear owner, redesigning a process that everyone had quietly worked around, or connecting two systems that were being bridged by hand. The point is momentum. Early, visible wins buy the room to tackle the deeper structural work, and they prove the approach to a team that has probably seen change efforts fizzle before.
Through this phase I am in the work, not sending instructions from the side. The person who found the problem is the person implementing the fix.
Days 61 to 90: embed it so it holds
A fix that depends on me is not a fix. The third month is about making the changes stick without me holding them up.
That means the new processes are documented and the team is actually running them, ownership is clear enough that decisions stop routing back to you, and there is a simple operating rhythm in place: a reliable cadence around the few numbers that matter, so problems surface early instead of at the deadline. The goal is a business that runs on its system, not on any one person's memory.
By day 90 you should be able to feel the difference. Not everything is solved, real operational change takes longer than a quarter, but the worst leaks are closed, the biggest bottleneck is smaller, and you can see a clear path for the rest.
What you should expect to see
If it is going well, three things are true at the 90-day mark. You are spending less time firefighting and more time on the parts of the business only you can do. At least one thing that used to depend entirely on you now runs without you. And you have a clear, honest view of what is left, with the work sequenced rather than piled up.
What you should not expect is a transformation deck and a consultant walking out the door. The whole point of working fractionally is that the same senior person stays in the work until it is real.
If that is the kind of help your business needs, the best first step is usually a short, fixed-fee Operations Audit, so you can see the diagnosis before committing to anything ongoing. Tell me what is breaking and I will tell you straight whether I can help.