The COO role is the most context-dependent hire in the C-suite. Whether a platform needs one at all depends on the CEO, the thesis, and where the company sits in the hold period.
A COO search that begins with “we need someone to take operational work off the CEO” will produce a mediocre hire.
The mandate needs to be specific before sourcing begins. Is this executive responsible for organic operational scaling, M&A integration, or both? Does the CEO need a complement or a lieutenant?
Does the platform have the infrastructure to absorb a senior operations executive, or does that executive need to build it? We answer these questions before the spec is written, not after the first slate disappoints.
Thesis alignment is as critical for the COO as for any function. Organic growth platforms need an operational architect: building the processes, systems, and management infrastructure that allow the business to scale without the CEO becoming the bottleneck.
Roll-up consolidation platforms need an integration engine: an executive who standardizes operations across a growing entity count and maintains quality through rapid change.
Blended platforms need both simultaneously, which is the narrowest COO sourcing pool and the search that benefits most from careful upfront calibration.
Margin-improvement platforms need an executive who owns the operating model, branch economics, procurement leverage, and the KPI architecture that makes those levers visible to the board.
Add-on-heavy platforms need an executive who can absorb acquired companies without losing operating momentum — standardizing operations as the entity count grows.
Some CEOs are operators themselves and need functional leaders, not a COO who creates a layer. We have this conversation before the spec is written.
Mandate definition, thesis-specific profile calibration, the EBITDA-driver vs. integration-engine distinction, and a framework for when the role is additive vs. redundant.
Gated download. A Falcon Partner reviews every request; the Blueprint is shared the same business day.
When the CEO’s highest-value work is being consumed by operational management that a qualified deputy could own. The threshold is usually a combination of revenue scale, entity complexity from add-ons, and the CEO’s own profile. Not every platform needs a COO, and adding one to the wrong CEO creates more friction than it removes.
Organic growth needs a process and systems builder. Roll-up needs an integration specialist. These are different skill sets with materially different sourcing pools. A COO who excels at one often struggles with the other.
