The Association for Financial Professionals asked 332 corporate finance practitioners around the world how long the annual budget takes to build. The answer, in its 2026 FP&A benchmarking survey, was 8.7 weeks. More strikingly, that number has barely moved in three years.
Those same three years saw a surge of investment in planning platforms, AI tools and transformation programmes. Gartner finds 84% of finance organisations under way with AI, while just 7% report high impact, and 45% of CFOs say their AI investments lean toward productivity rather than decision quality. Technology has changed. The budget cycle has not.
The obvious conclusion is that finance has been trying to solve the wrong problem.
Where the nine weeks really go
Ask an FP&A team to log a budget cycle honestly and very little of the time is spent planning. Teams chase submissions that arrive late, incomplete or in the wrong format. They rebuild consolidations because a business unit resubmitted after the deadline. They reconcile versions, remap cost centres, rerun allocations and work out which spreadsheet is actually the latest one.
Everyone says they are building a budget. Most of the effort goes into moving information around. That distinction matters. Planning creates decisions. Administration creates delay. And the two are often treated as the same thing.
Finance is automating budgeting, not planning
The instinctive response has been to accelerate the mechanics. Faster consolidations, pre-populated templates, automated variance commentary, AI-generated summaries. All of those help. None of them change the fundamental process. A budget assembled in seven weeks instead of nine is still an annual exercise built on assumptions that begin ageing the moment they are approved.
Most finance AI investment is aimed at producing the budget faster. The more important question is whether it produces better decisions.
A better target than speed
The goal should not be to accelerate budget assembly. It should be to reduce the amount of assembly required in the first place, and that changes the process completely.
- Compute the lines from their drivers. Most budget lines are not independent decisions. They follow from a small number of underlying drivers (e.g. volume, pricing, headcount and mix). Understand those relationships, test them against history, and thousands of budget cells become computed defaults rather than manual inputs. Finance stops discussing every line and starts discussing the assumptions that actually matter.
- Maintain a continuously current baseline. If the budget is driven by live operating assumptions, a current forecast already exists. The annual process becomes less about rebuilding the future from scratch and more about deciding what should change. What gets funded, what gets stopped, what gets accelerated. Those are planning questions.
- Put probabilities on outcomes. Traditional budgets present a single number. Reality rarely does. A forecast should describe a range of outcomes and the probability of hitting the target, updated as conditions change, so management discussion focuses on risk and intervention rather than explaining variances after the fact.
The organisations moving faster
The AFP's own data points in the same direction. Teams that run structured scenario planning close their cycles in 8.1 weeks, against 9.2 for those that do not. The difference is not that they consolidate data faster. It is that they spend less time assembling numbers and more time evaluating alternatives, because the process is built around decisions rather than administration.
Speed matters. But speed is not the objective. Better decisions are. Finance does not need more reports. It needs more time to think.
Budget lines computed from their drivers, a baseline that is always current, and probabilities attached to every target are how the Prophesee Finance Suite replaces the nine-week cycle. Keep the judgement. Lose the plumbing. Start here.