Finance Transformation: FP&A Modernization at a SaaS Operator

Numbers that arrived too late to matter

The operator was a roughly 90-million-dollar-ARR SaaS business growing in the mid-twenties, with the usual mix of self-serve and enterprise revenue and a finance team of nine. FP&A ran on a monthly close. The team spent the first eight business days of each month assembling actuals, then several more building a variance pack, so the board typically saw a commentary on results that were already five weeks old. The annual plan, set once and defended all year, drifted away from reality by the second quarter, and every reforecast was a fire drill that pulled the whole team off analysis for a week.

The cost was not just speed. Because assembling the numbers consumed the calendar, the analysts had little time left to interpret them. Variance commentary was thin and repetitive, scenario questions from the CFO took days to answer, and the finance function was seen internally as a scorekeeper rather than a partner. The executive team had circled the same question for several quarters: how does a function built for a monthly rhythm support a business that makes decisions weekly. The engagement was scoped to produce the operating model that answered it, along with the governance that would let the team trust AI in the workflow. The team had been burned before by a bolt-on analytics tool that produced confident numbers no one could trace, so a hard precondition of this engagement was that every figure had to carry its lineage back to the source. Trust, not speed, was the first thing that had to be earned.

Continuous planning, with AI drafting and humans approving

The redesign replaced the monthly cliff with a continuous rhythm, and it put AI in the drafting seat while keeping humans in the approval seat. A rolling 18-month forecast replaced the static annual plan. AI-assisted variance drafted a first-pass explanation of each material movement, tracing it to the driver and the source data, which an analyst then reviewed, corrected, and approved. A governed scenario library let the CFO run pricing, churn, and hiring scenarios on demand instead of commissioning a week of modeling. The non-negotiable rule was provenance: every AI-drafted explanation shipped with its source figures, the driver it attributed the change to, and the name of the analyst who approved it. No number reached the board without a human signature.

The build was sequenced so that trust was earned before scope widened, starting with the close itself and only later handing the CFO self-serve scenarios.

The design choice that made the AI trustworthy was refusing to let it decide anything. It drafted, traced, and explained, but a named analyst approved every line and the CFO signed the pack. Because each explanation carried its sources, a reviewer could confirm or correct it in seconds instead of rebuilding it, which is what turned AI assistance into genuine time saved rather than a second thing to check. The team measured this directly: the average time to review and approve a drafted variance line fell to under two minutes, against the fifteen or more it had taken an analyst to write one from scratch. That single ratio was the difference between AI as overhead and AI as leverage.

What moved in six months

• Close-to-insight time fell from 12 business days to 4, so the board reviewed commentary on results that were current rather than five weeks stale.
• Rolling-forecast accuracy on net revenue improved to within 3 percent at the one-quarter horizon, against a legacy annual-plan drift that regularly exceeded 10 percent by mid-year.
• The CFO could run a pricing, churn, or hiring scenario in the meeting it was raised, instead of commissioning a week of modeling.
• Analyst time shifted measurably from assembling numbers to interpreting them, and finance was pulled into commercial decisions it had previously only reported on.
• Every board number carried its provenance, source figures, driver, and approver, so AI-assisted commentary survived audit and board scrutiny without a black-box objection.

What we would tell the next CFO

• Replace the monthly cliff with a continuous rhythm. A rolling forecast that refreshes weekly beats a static annual plan that is wrong by the second quarter.
• Let AI draft, but never let it decide. Analysts approve every line and the CFO signs the pack, which is what makes the speed trustworthy.
• Ship provenance with every explanation. Source figures, driver, and approver attached to each line are what let AI-assisted commentary survive an audit.
• Sequence for trust before scope. Start with the close, prove the governed workflow, and only then hand the CFO self-serve scenarios.
• Measure the time reallocation explicitly. The real prize was analysts moving from assembling to interpreting, and that only sticks if you track it as a metric.

Before you start

• Map your close to a continuous feed and set a target for actuals to be current within two days rather than assembled over eight.
• Stand up a rolling 18-month forecast with versioned assumptions that are never overwritten, replacing the static annual plan.
• Define the AI variance contract: it drafts with driver and source, an analyst approves every line, and nothing reaches the board unsigned.
• Build a governed scenario library where each scenario carries its assumptions and a named owner, so on-demand runs stay auditable.
• Track the shift in analyst time from assembling to interpreting as an explicit metric, so the transformation is visible and defended.