Fractional COO Project Scope Template

The most common failure mode in COO engagements is not that the wrong person was hired — it is that scope was defined in terms of leadership qualities rather than operational outcomes. "We need someone to help us execute better" is not a scope. A well-scoped COO engagement has specific operational deliverables, a defined hour commitment, explicit boundaries on what the COO owns and does not own, and a written offboarding plan. This scope-of-work template covers the elements that matter. Core scope elements: define the operational areas the COO owns (team operations, project delivery, vendor management, or all of the above), specify the hour commitment and meeting cadence (weekly leadership team meeting is typical), define what success looks like at 90 days with specific milestones, and specify what the COO does not own (the CEO still owns product and engineering unless explicitly delegated). The scope should also include a written escalation process for when operational decisions need leadership input — without this, the COO will spend the engagement waiting for decisions rather than driving execution. For project-based COO engagements (e.g., "build the operational infrastructure for our next phase of growth"): define the specific deliverable, the timeline, and the offboarding plan before signing. Use a monthly retainer for ongoing operational leadership. Use fixed-price or capped hours for project-based engagements. Use it before signing any fractional COO engagement. The thirty minutes spent here prevents months of ambiguous engagement and billing disputes.