A fractional COO runs the operations of a company on a part time basis, typically one to three days per week. The role carries real operating authority over process design, team accountability, systems, and execution of the growth plan. The engagement is ongoing leadership, not a report.
Most companies asking this question do not have a leadership vacancy. They have an execution gap that makes every plan look unrealistic. Naming that gap correctly is where the role starts earning its keep.
Confusion around the title comes from pairing an executive rank with a part time schedule. The rank is real, and the schedule is the only fractional element. Separating the role from consulting projects and from full time hires makes the rest of the picture clear.
The Bottleneck the Role Exists to Remove
Companies between 1 and 25 million dollars in revenue hit a predictable constraint. Decision volume outgrows the founder while remaining too small to justify a full time executive team. Work still gets done, but only because specific people remember to do it.
That is not a system. It is stress ownership, and it produces a recognizable kind of chaos. Growth stalls each time headcount grows, the owner approves everything, and a two week vacation breaks the machine.
These are process gaps wearing the costume of people problems. Treating them as people problems is how companies churn through managers without improving anything. The theory of constraints names the real situation plainly. When the owner is the constraint, improving anything else improves nothing.
The Work Itself
A fractional COO owns outcomes rather than recommendations. Four areas absorb most of the effort, and each converts improvisation into procedure.
Process architecture. The operator documents how work should flow, removes steps that exist by habit, and installs the checklists and handoffs that let the company run without heroics. Documented process is not bureaucracy. It is how a company scales judgment beyond the founder.
Accountability structure. An operating cadence arrives first because it changes behavior fastest. A weekly leadership rhythm, a scorecard with named owners, and decisions made once instead of revisited monthly. Companies that run EOS or similar operating systems will recognize the shape.
Systems and reporting. Numbers must earn trust before they can be useful. A simplified balanced scorecard discipline forces the company to watch more than the bank balance, and it usually matters more than any single process fix.
Execution of the plan. Strategy usually exists while execution capacity does not. Quarterly commitments get pulled from the annual plan and driven to done, following the arc in the first 90 days of a fractional COO. Diagnosis precedes change every time.
What the Role Is Not
A consultant studies a problem and hands over recommendations, a split examined fully in fractional COO vs operations consultant. A fractional COO implements and stays accountable for whether the implementation held. One writes a finding when something breaks, while the other retrains the team that week.
An operations manager runs the existing machine at the direction of leadership. A fractional COO redesigns the machine and sits inside leadership. Companies needing task execution should hire the manager, covered on the fractional operations manager page, and the permanent hire comparison lives in fractional COO vs full time COO.
Free 20-Minute Operations Review
Dealing with a specific operational bottleneck? Kamyar Shah works with founders and CEOs to identify the root cause and build a fix.
Coaching is the third neighbor worth separating. Coaching develops the owner, and operations leadership relieves the owner. Both serve human capital, but only one leaves systems behind when it ends.
A Typical Week, Concretely
On a two day per week engagement, roughly half the time runs the operating cadence. Leadership meeting, one on ones, scorecard review. Another third builds whatever system that quarter requires, and the remainder absorbs escalations plus the vendor or hiring decisions that need executive judgment.
Between engagement days, structure holds because it was built for absence. Department heads run their own numbers against a RACI style decision map written in week one. Owners consistently report that the discipline of absence forces the delegation they had been avoiding, which is the quiet second product of the engagement.
Economics follow the same logic. Decisions at this size need executive quality, but decision volume does not fill a five day calendar. Buying judgment by the day matches cost to actual need.
What the First Two Quarters Produce
Month one produces a diagnosis the owner can verify against lived experience, plus a cadence that actually meets. Months two and three produce documented core processes, a working scorecard, and usually one structural decision the company had deferred for a year. Calm beats drama, and compounding beats both.
Quarter two produces depth. Reporting becomes reliable enough to price from. The leadership team resolves conflict inside the cadence instead of routing it through the owner, and hiring aligns to the constraint rather than to the loudest department. None of this is dramatic, which is the design.
Consider a mid-market services firm whose owner approved every quote personally. Engagements that install a pricing authority matrix in the first quarter report the same early effect. Quote turnaround drops from days to hours, and the owner recovers the calendar first, the margin second.
Cost, Duration, and the Deliberate Ending
Pricing runs as a monthly retainer tied to committed days. Published cost benchmarks by revenue tier break down the ranges, and the rates and cost breakdown covers pricing models. Committed days force prioritization, and prioritization is half the value.
Engagements run six to eighteen months and end deliberately. Either the systems run without the COO, or the company has grown into a full time hire, often recruited and onboarded by the departing executive. An engagement without a defined ending is a subscription rather than a plan.
Where Engagements Go Wrong
Three failure patterns account for most disappointments, and all three are preventable at the contract stage. Delegation theater leads the list. An owner who hires operations leadership and keeps making every operational decision has purchased an expensive observer, and the written decision map exists to prevent exactly that waste.
Scope sprawl comes second, because operations touches everything and drift dilutes the work that justified the retainer. Strong engagements hold a quarterly scope. Everything else gets logged for the next planning cycle.
Measuring activity instead of outcomes closes the list. Meetings held and documents produced are inputs, while cycle times, margin points, error rates, and recovered owner hours are the outputs that matter. An engagement showing no movement on those numbers by quarter two has earned a hard conversation.
The Human Capital Dividend
The least advertised output of the role is what happens to the team. Managers who spent years executing verbal instructions start running documented processes they helped write, and the change reads as promotion even when titles stay flat. Retention follows, because people leave chaos more often than they leave companies.
Hiring compounds the same way. A company with documented systems onboards a new manager in weeks rather than quarters, since the job is learnable from artifacts instead of oral tradition. Structure is empathy at scale, and it recruits.
Organizations that adopt the cadence without the operator report a softer version of the same gains, which says something useful about the mechanism. The structure does part of the work on its own. The executive exists to install it faster, hold it through the uncomfortable first quarter, and know which exceptions matter.
Questions Owners Ask Before Committing
Does the executive manage employees directly? Yes, within the engagement scope, with department heads reporting on operational matters while the owner keeps final authority on strategy and compensation. How many clients does one operator carry? Two to four is the honest ceiling, and buyers should ask directly.
What does the company keep at the end? Documented processes, the cadence, the reporting infrastructure, and a team trained to run all three. An engagement whose systems leave with the executive failed, whatever the invoices say.
Timing questions come up in the same conversations. Most owners start looking a year after the symptoms became obvious, usually after a failed manager hire or a stalled quarter forced the issue. Earlier is cheaper, since operational fixes compound over quarters and a late start forces triage. Firms that engage while cash is still healthy get the causes fixed rather than the bleeding.
Reading the Fit Honestly
The signal is almost always the founder. When the owner is the bottleneck and growth stalls at every scaling step, the missing function is operations leadership. When the problem is one bounded project, a consultant costs less, and when the problem is task volume, a manager costs less still.
Matching the role to the actual gap protects everyone, including the operator. The work of Kamyar Shah spans more than 650 engagements across companies from 1 to 25 million dollars in revenue, and the successful ones share three traits. The company was ready to delegate, the executive was an operator rather than an advisor, and the engagement had a finish line.
Buyers who want to test candidates against that pattern can follow how to vet a fractional COO. Every system the operator builds teaches the company how to think. What the company keeps is worth more than the calendar days it bought.
