What a Fractional CFO Actually Does in the First 90 Days

The first three months are not an assessment period. They are the period where cash gets controlled, a reporting cadence gets installed, and the two or three priorities that actually move enterprise value get named and started.

Most fractional CFO engagements fail quietly in the first month, and it is almost always the same failure. The CFO spends thirty days learning the business while the business waits, and by the time recommendations arrive the calendar has eaten the mandate. A senior operator does not need that runway. The learning happens while the work is already moving.

Days 1 to 30: control the cash and see the business

Cash first, because it is the only thing that ends companies. A rolling thirteen-week forecast goes live, built bottom up from receipts and commitments rather than from a bank balance, and it gets updated weekly with last week's variance explained in writing. In parallel comes the unglamorous work of reading the business: the customer list by revenue and margin, the contract base, the covenant package, the chart of accounts, and thirty minutes each with operations, sales and IT.

Days 31 to 60: install the cadence

A company gets the behavior its calendar rewards. One reporting package becomes the single source of truth, published on a fixed date, and the competing spreadsheets are retired rather than tolerated. The close gets timed honestly, the reconciliation backlog gets sized, and approval limits and payment controls are written down. This is also when the board and lender reporting gets rebuilt to answer the questions those readers actually ask.

Days 61 to 90: commit to the few things that matter

By now the noise has separated from the signal. The output is a short plan: what gets fixed this quarter, what is deliberately deferred, what needs investment, and which repetitive finance work is a candidate for automation once the data underneath it is clean. Deferring loudly is as valuable as fixing, because it stops the team from spreading itself across twelve half-finished initiatives.

What we commit to

None of this requires new software. It requires someone senior who has done it before, in the building on the days you need them.