[{"data":1,"prerenderedAt":4},["ShallowReactive",2],{"article-body-nine-weeks-to-build-a-budget":3},"\nThe Association for Financial Professionals asked 332 corporate\nfinance practitioners around the world how long the annual budget\ntakes to build. The answer, in its\n[2026 FP&A benchmarking survey](https://www.financialprofessionals.org/training-resources/resources/survey-research-economic-data/Details/afp-fpabenchmarking-survey-report-integrated-planning),\nwas 8.7 weeks. More strikingly, that number has barely moved in\nthree years.\n\nThose same three years saw a surge of investment in planning\nplatforms, AI tools and transformation programmes. Gartner finds\n[84% of finance organisations under way with AI, while just 7% report high impact](https://www.gartner.com/en/newsroom/press-releases/2026-06-08-gartner-says-cfos-need-structured-finance-ai-roadmaps),\nand\n[45% of CFOs say their AI investments lean toward productivity](https://www.gartner.com/en/newsroom/press-releases/2026-07-20-gartner-survey-shows-45-percent-of-cfos-say-their-ai-investments-lean-towwards-productivity-while-20-percent-say-these-investments-lean-towards-decision-quality)\nrather than decision quality. Technology has changed. The budget\ncycle has not.\n\nThe obvious conclusion is that finance has been trying to solve\nthe wrong problem.\n\n## Where the nine weeks really go\n\nAsk an FP&A team to log a budget cycle honestly and very little of\nthe time is spent planning. Teams chase submissions that arrive\nlate, incomplete or in the wrong format. They rebuild\nconsolidations because a business unit resubmitted after the\ndeadline. They reconcile versions, remap cost centres, rerun\nallocations and work out which spreadsheet is actually the latest\none.\n\nEveryone says they are building a budget. Most of the effort goes\ninto moving information around. That distinction matters. Planning\ncreates decisions. Administration creates delay. And the two are\noften treated as the same thing.\n\n## Finance is automating budgeting, not planning\n\nThe instinctive response has been to accelerate the mechanics.\nFaster consolidations, pre-populated templates, automated variance\ncommentary, AI-generated summaries. All of those help. None of\nthem change the fundamental process. A budget assembled in seven\nweeks instead of nine is still an annual exercise built on\nassumptions that begin ageing the moment they are approved.\n\nMost finance AI investment is aimed at producing the budget\nfaster. The more important question is whether it produces better\ndecisions.\n\n## A better target than speed\n\nThe goal should not be to accelerate budget assembly. It should be\nto reduce the amount of assembly required in the first place, and\nthat changes the process completely.\n\n1. **Compute the lines from their drivers.** Most budget lines are\n   not independent decisions. They follow from a small number of\n   underlying drivers (e.g. volume, pricing, headcount and mix).\n   Understand those relationships, test them against history, and\n   thousands of budget cells become computed defaults rather than\n   manual inputs. Finance stops discussing every line and starts\n   discussing the assumptions that actually matter.\n2. **Maintain a continuously current baseline.** If the budget is\n   driven by live operating assumptions, a current forecast\n   already exists. The annual process becomes less about\n   rebuilding the future from scratch and more about deciding what\n   should change. What gets funded, what gets stopped, what gets\n   accelerated. Those are planning questions.\n3. **Put probabilities on outcomes.** Traditional budgets present\n   a single number. Reality rarely does. A forecast should\n   describe a range of outcomes and the probability of hitting the\n   target, updated as conditions change, so management discussion\n   focuses on risk and intervention rather than explaining\n   variances after the fact.\n\n## The organisations moving faster\n\nThe AFP's own data points in the same direction. Teams that run\nstructured scenario planning close their cycles in 8.1 weeks,\nagainst 9.2 for those that do not. The difference is not that they\nconsolidate data faster. It is that they spend less time\nassembling numbers and more time evaluating alternatives, because\nthe process is built around decisions rather than administration.\n\nSpeed matters. But speed is not the objective. Better decisions\nare. Finance does not need more reports. It needs more time to\nthink.\n\nBudget lines computed from their drivers, a baseline that is\nalways current, and probabilities attached to every target are how\n[the Prophesee Finance Suite](/solutions/finance/fpa) replaces the\nnine-week cycle. Keep the judgement. Lose the plumbing.\n[Start here](/contact).\n",1786984936944]