How to Scope a Fractional CFO Engagement

Define deliverables, expectations, and pricing structures for a successful engagement.

Why Scoping Matters

The #1 cause of fractional CFO engagement failure isn't bad hiring—it's unclear expectations. Vague scopes lead to misaligned expectations, frustration on both sides, and failed engagements. Studies show that well-scoped engagements have 70%+ higher success rates than poorly defined ones. A well-scoped engagement dramatically increases success probability and protects both parties.

Key Takeaways

  • Start with outcomes, not tasks—what results do you want, not just what do you want done?
  • Be specific about deliverables—what exactly will be produced, in what format, and when?
  • Define success metrics—how will you measure whether the engagement is effective?
  • Document everything in writing—verbal agreements aren't worth the paper they're printed on
  • Build in flexibility—needs evolve, scopes should adapt through agreed-upon processes

Step 1: Define Your Desired Outcomes

What decisions will this engagement help you make? List specific categories of decisions—pricing, hiring, capital allocation, expansion, fundraising

What problems are you trying to solve? Be specific—'cash flow issues' is vague; 'AR averaging 60 days when it should be 30' is specific

What does success look like at 90 days? At one year? Define measurable outcomes—not activities

What would the business look like if this engagement is wildly successful? Paint a specific picture

What would you consider a failure? Define what you're trying to avoid—this is often easier to articulate

Step 2: Define Specific Deliverables

What reports will they produce? Monthly? Weekly? What format? Be specific—'monthly P&L analysis with variance commentary' not just 'financial reporting'

What analysis will they complete? Financial models, budgets, forecasts? Define the models and their purposes

What meetings will they attend? Board meetings, management meetings, investor calls? Define attendance and preparation expectations

What processes will they design or improve? Document which processes and what improvement looks like

What decisions will they support or lead? Be explicit—pricing decisions, hiring approvals, capital allocation

Who will they interface with? Investors, banks, auditors, legal counsel? Define external relationship management

The Deliverable Trap

Be careful about defining engagement by time ('20 hours per month') rather than deliverables. Hours are a resource input; deliverables are outcomes. Focus on what you'll get, not how long it takes to get it. That said, time estimates help with pricing—find the right balance between outcomes focus and resource planning.

Step 3: Define Time Commitment and Availability

How many hours per week/month are included in the engagement? Be specific

What are the regular meeting times and cadence? Define standing meetings

How quickly can you expect responses to requests? Define SLA—24 hours for emails? 48 hours for substantive requests?

Is there a defined schedule or more flexible availability? Some CFOs work best with routine; others adapt

What happens if you need additional hours? What's the process for requesting more time? At what rate?

How is time tracked and reported? Will you receive timesheets? Invoices? How detailed?

Step 4: Define Pricing and Payment Terms

What is the base fee and what's included? Define clearly what's covered in the base price

Are there additional costs for out-of-scope work? Define the process and rates for additional work

How are expenses handled? Software, tools, travel—these add up and should be clarified

What's the payment schedule? Monthly in advance? Net 15? Quarterly? Define terms clearly

Are there any setup or onboarding fees? One-time costs should be explicit

What happens if scope changes significantly? Define the process for adjusting pricing

Total Cost Consideration

When comparing proposals, look at total cost, not just hourly or monthly rates. A higher hourly rate with fewer hours may be cheaper than a lower rate with more hours. Also consider what's included—some rates cover software and tools; others don't. Get all-in costs for accurate comparison.

Step 5: Define Success Metrics

What specific outcomes will indicate success at 30 days? Define early wins and quick assessments

What milestones should be achieved by 90 days? These are your first major checkpoints

What are the long-term success criteria at 6-12 months? These should align with your original outcomes

How will you measure whether the engagement is worth the investment? Define your ROI metrics

What would cause you to end the engagement early? Define termination triggers clearly

What would cause the CFO to recommend ending the engagement? They should have criteria too

The Check-In Cadence

Build regular check-ins into the engagement from day one. Weekly for the first month, then biweekly, then monthly as the relationship matures. These aren't status meetings—they're alignment conversations where you assess progress, address concerns, and adjust course. Don't skip them, especially early in the engagement.

Step 6: Define Roles and Relationships

Who does the CFO report to? CEO? Board? This affects communication and authority

Who manages the finance team day-to-day? Is this an advisory role or a management role?

What decisions can the CFO make autonomously? Define approval thresholds

What decisions require CEO approval? Define the boundaries clearly

How does the CFO interact with your accountant or auditors? Define relationships

What access to systems, data, and people will they have? Comprehensive access enables effectiveness

Step 7: Define Termination Terms

What notice period is required? 30 days? 60 days? Adequate notice allows for transitions

Are there any termination fees? Understand any early termination costs

What happens to work in progress? Who owns what? Define intellectual property

What happens to materials, processes, and documentation created? Ensure you have access

How is knowledge transfer handled? This is often overlooked—plan for it from the start

Are there non-solicitation or non-compete provisions? These protect both parties

Key Takeaways

  • Clear statement of desired outcomes—specific, measurable business results
  • Specific deliverables with timelines—what, when, in what format
  • Defined time commitment and availability—including communication expectations
  • Transparent pricing with what's included and excluded—including out-of-scope pricing
  • Success metrics and check-in cadence—how progress is measured
  • Roles, reporting, and decision authority—who does what and who decides
  • Termination terms and conditions—how the engagement can end

Getting Started

Use this framework to create a detailed scope before interviewing candidates—scope guides the search

Be willing to iterate on scope as you learn more about needs—first drafts are never perfect

Start with a clear scope but build in flexibility for evolution—scopes should be living documents

Document everything in writing—even small agreements become important if disputes arise

Frequently Asked Questions

Should the scope be in a contract?

Yes, absolutely. A detailed scope document as part of your engagement agreement protects both parties and ensures clear expectations. Without written scope, you're relying on memory and goodwill—both of which are unreliable.

What if my needs change during the engagement?

Build scope adjustment processes into your agreement. Define how changes are proposed, evaluated, and priced. Most successful engagements evolve—the key is managing change through clear communication and documented amendments. Don't let scope creep happen without formal acknowledgment.

Can I start with a smaller scope and expand later?

This is often the best approach. Start with a well-defined project or limited scope, validate the relationship, then expand based on demonstrated results and emerging needs. This reduces risk while allowing you to test the relationship. Just make sure expansion terms are clear from the start.

What's the difference between scope and contract?

Scope defines what you'll do; contract defines the legal relationship. The scope should be attached to or referenced in the contract, but they're different documents. Scope is operational; contract is legal.