What Is SaaS Fractional CFO?

A SaaS fractional CFO connects contract, billing, service-delivery, customer, cash, and ledger data. The work is useful only when revenue policy and operating metrics use written definitions that can be reproduced.

Revenue recognition is the foundation

Under accrual accounting, advance collections may create a contract liability until the related service is delivered. The exact pattern depends on contract terms and the applicable reporting framework, so the policy and source data should be documented.

Getting this right is not optional and it is not merely presentational. It changes what the business appears to be.

The metrics that matter

• Recurring revenue, monthly or annual, distinguished from total revenue including one-off items
• Gross margin, with hosting, support, and delivery costs properly included in cost of sales
• Net and gross retention, which describe whether the existing base grows or shrinks by itself
• Customer acquisition cost, fully loaded, including salaries and not merely advertising
• Payback period, meaning how long acquisition cost takes to recover
• Churn, by customer and by revenue, which are different numbers

A SaaS CFO should define these consistently, reconcile them to source data, and report them on an agreed cadence. Preserve approved definition changes so readers can understand effects on prior comparisons.

Deferred revenue and cash timing

Advance and monthly billing create different cash timing. Recognized revenue follows delivery and the applicable policy, so cash and reported performance may move differently as the billing mix changes. Model the billing assumptions and reconciliation explicitly.

What the engagement covers

• Revenue recognition policy and its correct application
• Metric definitions, and reporting them consistently
• Unit economics traceable to the ledger rather than asserted in a deck
• Cash and runway modelling under different billing mixes
• Diligence preparation, since these are the numbers examined most closely

Separate CFO, controller, and bookkeeping work

Bookkeeping records activity, controller work owns close quality and accounting policy, and CFO work uses reliable information for financing, planning, pricing, hiring, and board decisions. A fractional engagement may coordinate all three, but the scope should name who prepares, reviews, approves, and implements each deliverable.

Build a reproducible data model

Map the contract system, billing platform, payment processor, product or usage data, payroll, customer master, and general ledger. Define customer, subscription, product, start date, cancellation, expansion, contraction, discount, credit, refund, and currency fields. Reconcile the metric dataset to the ledger before presenting it.

Write every metric definition

For recurring revenue, churn, retention, acquisition cost, lifetime value, gross margin, burn, and runway, state the population, period, numerator, denominator, exclusions, currency treatment, owner, source, and version. Keep operational metrics distinct from accounting measures and label non-GAAP or management measures clearly.

Link the forecast to decisions

Model new business, renewals, expansion, contraction, churn, pricing, billing cadence, collections, headcount, infrastructure, contractors, and other operating costs. Use base, downside, and upside cases. Every material assumption should have an owner, source, review date, and an action that changes if the result moves.

Establish the operating cadence

A practical cadence may include close review, metric reconciliation, forecast refresh, cash and runway review, department variance discussion, board-package preparation, financing work, and an action log. The CFO should make unresolved data limitations visible rather than converting them into false precision.

Define handoff and continuity

Require exportable models, metric dictionaries, revenue memos, close calendars, board files, source maps, access lists, decision logs, open issues, and contact records. State backup coverage, response expectations, change-order rules, and the process for transitioning work to an internal hire or another provider.

Revenue-policy deliverable

The engagement should produce or update a memo that identifies contract types, material terms, billing events, delivery evidence, accounting conclusions, presentation, required estimates, system rules, reconciliations, exceptions, and review ownership. Route technical conclusions to the appropriate accounting professional.

Create a contract-to-billing-to-ledger test for representative new sales, renewals, upgrades, downgrades, usage charges, services, credits, refunds, cancellations, and foreign-currency activity. Reperform the test after material product or contract changes.

Board-package control

Every reported number should have a definition, source, preparer, reviewer, cutoff, comparison period, and reconciliation where applicable. Separate actual results, forecast, targets, and management estimates. Explain changes through named drivers and preserve the version distributed to decision-makers.

Engagement acceptance questions

Ask which decisions the CFO owns, which remain with founders, what close quality is required, which metrics need rebuilding, how quickly source data is available, who maintains models, which meetings are included, and what outcome would justify renewing or ending the scope.

A useful first ninety-day plan prioritizes data mapping, close reliability, revenue policy, metric definitions, a baseline forecast, cash visibility, and the decision calendar. Sequence work by decision risk and dependency. Board formatting should not outrun the reliability of the underlying records.

Review the scope quarterly against current decisions, risks, team capability, data quality, and the planned internal finance organization.