The Association for Financial Professionals' 2026 FP&A benchmarking survey, drawing on 332 corporate finance practitioners globally, contains a damning number: the average annual budgeting cycle still takes 8.7 weeks, and it has not shortened in three years. The same three years in which finance teams bought planning platforms, AI features and transformation programmes at a pace Gartner's research documents. 84% of finance organisations under way with AI and 7% reporting high impact, with 45% of CFOs saying their AI investments lean toward productivity rather than decision quality.
Money in, cycle unchanged. Something about where the nine weeks actually go is being systematically misdiagnosed.
Where the nine weeks go
Ask an FP&A team to log the cycle honestly and the time lands in categories no one would call planning:
- Chasing and validating submissions: the templates that come back late, mis-keyed, or in last year's format, each requiring a human to notice and negotiate the fix.
- Reconciling versions: the consolidation that must be rebuilt because a business unit resubmitted after the cut, and the archaeology of establishing which of four circulating files is current.
- Mapping and remapping: cost centres reorganised mid-cycle, new products squeezed into old hierarchies, the dimensional bookkeeping that consumes analyst days and produces nothing a decision maker ever sees.
- Rebuilding fragile logic: the linked spreadsheets that break under load, the allocations rerun after every assumption change, the model that only its author can safely touch.
Surveys of planning practice keep confirming the underlying reality: the large majority of finance teams still prepare data in spreadsheets before it ever reaches the planning system, and many run the real process in parallel to the platform of record. The plumbing is not a residue the tools have not reached yet. The plumbing is the process.
Why faster plumbing is still the wrong target
The instinctive fix, and where that 45% of AI spend goes, is to accelerate the assembly. Faster consolidation, auto-filled templates, a copilot summarising the variances. Useful, and insufficient, because a compressed version of the same cycle produces the same artefact: a once-a-year point estimate, already ageing on the day it is approved, defended thereafter against a reality that keeps moving.
The more valuable question is what the nine weeks were protecting. An annual ritual whose length forces the organisation to plan rarely. Remove the plumbing properly and the cadence itself can change:
- Drivers instead of templates. Most budget lines are statistical consequences of a small set of drivers: volumes, rates, headcount, mix. Model the lines from the drivers, backtested against history, and the thousands of cells that consumed submission rounds become computed defaults. Human attention goes where it pays. The drivers themselves, and the genuine judgement calls.
- A rolling baseline. With lines computed from continuously updated drivers, a current baseline forecast simply exists, at all times. The annual event stops being nine weeks of assembly and becomes a decision layer on top of a living number: what do we want to change, fund, or stop?
- Odds on the outcome. A budget built this way carries its uncertainty honestly: not one number for year end, but a distribution and the probability of hitting the target, updated as the year moves.
The prize is not a seven-week budget. It is a finance function whose scarce commodity, thinking, stops being rationed by assembly work.
The AFP's own data points the same direction: the teams that run structured scenario planning close their cycles in 8.1 weeks against 9.2 for those that do not. The separator is not how fast the assembly runs but whether the process is built for thinking about alternatives. That gap does not come from accelerating the old process. The process was the problem.
Finance does not need more reports. It needs more time to think.
Driver-based modelling, a continuously live baseline and odds on every target are what the Prophesee Finance Suite's FP&A module replaces the nine weeks with. Keep the judgement, lose the plumbing. Start here.