When Project Pricing Fits a Fractional COO
Project pricing fits when operations scope has a defined deliverable. Process redesign for one function. ERP rollout. Post-merger integration. Org structure overhaul. Quarterly planning system build. Each has an output, a deadline, and a way to know it is done.
Most fractional COO retainer engagements should have started as projects. The buyer hired a COO "to fix operations" without defining what fixed looked like. Six months in, both sides feel the engagement drifted. Project pricing forces the scope conversation upfront, which is usually the conversation the engagement most needs.
Typical Project Pricing
| Project Type | Typical Fee | Duration |
|---|---|---|
| Process redesign (one function) | $20,000-$50,000 | 6-12 weeks |
| ERP or core systems rollout | $40,000-$120,000+ | 12-24 weeks |
| Post-merger integration (PMI) | $50,000-$150,000+ | 10-20 weeks |
| Org structure redesign | $25,000-$75,000 | 6-12 weeks |
| Quarterly planning system build | $15,000-$40,000 | 4-10 weeks |
| Operational diligence (buy-side) | $25,000-$80,000 | 6-12 weeks |
| People ops infrastructure build | $20,000-$60,000 | 8-14 weeks |
Fees vary with company size and how much the operator delivers vs how much they direct. A process redesign where the fractional COO designs the workflow and trains the team runs lower than one where they personally implement and operate it. The hands-on premium applies here too.
Pros of Project Pricing
- Outcome alignment. The fee maps to a deliverable. Both sides care about the same thing.
- Forced scoping. Operations work is notoriously vague. A fixed fee forces the conversation about what done means.
- Predictable budget. The project shows up as a single line item. Easier to approve, easier to track.
- Senior talent willing to engage. The strongest fractional COOs prefer projects to retainers because the scope is bounded and avoids drift across the company.
Cons
- Higher loaded rate. Project pricing typically lands at $400 to $700 per hour effective, vs $300 to $500 on a retainer. The COO is pricing scope drift risk into the upfront fee.
- Change orders are friction. Operations scope shifts surface frequently because the work uncovers system problems no one knew about.
- Limited continuity. When the project ends, the engagement ends. If ongoing operations leadership is needed, the project model is the wrong fit.
- Handoff risk. Operations deliverables that no one inside the company can operate end up shelved. Build handoff into scope.
How to Scope a Clean Operations Project
Strong fractional COO project contracts include four artifacts in the scope definition.
1. Concrete deliverables. "Process redesign" is not a deliverable. "Documented end-to-end process for [function], stakeholder map, RACI for the 8 most common decisions, training material for internal owners, and metric definitions tied to operational KPIs" is.
2. Decision rights. Specify who owns final calls on operating model decisions, vendor choices, and structural changes. Operations projects stall when decision rights are not clear, especially when restructuring affects multiple functions.
3. Stakeholder map. Name the people across functions who must approve, must be consulted, and must be informed. Operations projects touch more departments than any other type of fractional engagement.
4. Completion criteria. What does done look like? "New process running for 60 days with all team members trained and metrics tracked" is concrete. "Process implemented" is not.
Comparison to Retainer
| Need | Best Model | Why |
|---|---|---|
| Ongoing operations leadership | Retainer | Scope is open-ended |
| Defined deliverable, finite scope | Project | Fee maps to outcome |
| Strategic advisory only | Hourly or advisor retainer | Volume is unpredictable |
| Pre-revenue startup | Hybrid (cash + equity) | Cash constrained |
For retainer model context, see fractional COO retainer and fractional executive engagement comparison.
Contract Terms That Matter
Milestone payments. Standard structure for projects past $25,000: 25 percent at kickoff, 25 percent at first milestone, 25 percent at second milestone, 25 percent at completion. Lump-sum-on-completion creates cash flow risk for the operator.
Change order protocol. Define the threshold. A common rule: any scope expansion requiring more than 5 percent additional hours triggers a written change order. Operations projects discover scope creep faster than other types because they touch multiple systems and stakeholders.
Authority during the project. Operations work requires authority. Specify what the COO can decide unilaterally, what requires CEO approval, and what is informational only. Without explicit authority, the project produces recommendations no one acts on.
Project-to-retainer conversion. If both sides anticipate ongoing engagement after project completion, write a conversion clause. "Project may convert to monthly retainer at $X for Y hours upon mutual agreement." This avoids friction at exactly the wrong moment.
Knowledge transfer. Build 2-4 weeks of overlap with internal operations team into scope. Documentation, runbooks, and internal training should be in the deliverable list. Most operations projects fail at the handoff.
Common Failure Modes
Three patterns explain most failed fractional COO project engagements. Stakeholder buy-in collapses in week 8 because the COO did not engage department heads early enough. The deliverable becomes a deck no one acts on. The fix: include department heads in milestone reviews, not just final review.
The internal team cannot operate the new process or system. The deliverable is technically correct but operationally orphaned. The fix: scope handoff explicitly. Document. Train. Stay engaged for 2-4 weeks post-launch as a backstop.
Scope drift dressed as "while you're in there." Mid-project asks pile up. The fix: written change order protocol triggered at any 5 percent expansion. No exceptions.
For broader cost context, see fractional COO cost and fractional COO operations playbook.
When Not to Use Project Pricing
Avoid project pricing when scope cannot be defined upfront. Greenfield ops design at pre-product-market-fit, novel cross-functional initiatives, and exploratory operations work all live with too much ambiguity for a fixed fee. Hourly or retainer with regular re-baselining works better.
Avoid it when the engagement is genuinely ongoing operations leadership. If the company needs operational ownership for the next 12 months, dressing up retained leadership as a project produces friction at the worst moment.
FAQs
How much does a fractional COO charge for an ERP rollout?
An ERP or core systems rollout typically runs $40,000 to $120,000+ over 12 to 24 weeks. The fee depends on company size, system complexity, and how much hands-on implementation is in scope. Larger mid-market rollouts and integrations with multiple downstream systems push toward the high end.
What does fractional COO project pricing typically cover?
Common projects: process redesign, ERP rollout, post-merger integration, org structure overhaul, quarterly planning system build, operational due diligence, and people ops infrastructure. Each has a defined deliverable, a deadline, and explicit completion criteria.
Is project pricing more expensive than a retainer?
The effective hourly rate is typically 30 to 50 percent higher under project pricing because the COO absorbs scope drift risk. The total cost is often lower because the engagement ends when the project completes. Total cost depends on whether ongoing operations leadership is needed afterward.
How do milestone payments work for operations projects?
Standard structure for projects past $25,000: 25 percent at kickoff, 25 percent at first milestone, 25 percent at second milestone, 25 percent at completion. For projects under $25,000, 50/50 split (kickoff and completion) is common. Avoid full-payment-on-completion because of the cash flow risk to the operator.
What about handoff after the project completes?
Operations project handoff is the most common failure point. Build 2-4 weeks of overlap with the internal operations team into scope. Documentation, runbooks, and internal training should be in the deliverable list. Without explicit handoff, deliverables get shelved and the project value evaporates.
Should the COO have authority during the project?
Yes. Operations work requires authority to be effective. Specify what the COO can decide unilaterally, what requires CEO approval, and what is informational only. Without explicit authority, the project produces recommendations that go unacted, and both sides feel the engagement failed.