[{"data":1,"prerenderedAt":4},["ShallowReactive",2],{"article-body-nine-weeks-to-build-a-budget":3},"\nThe Association for Financial Professionals' [2026 FP&A benchmarking\nsurvey](https://www.financialprofessionals.org/training-resources/resources/survey-research-economic-data/Details/afp-fpabenchmarking-survey-report-integrated-planning),\ndrawing on 332 corporate finance practitioners globally, contains a\ndamning number: the average annual budgeting cycle still takes 8.7\nweeks, and it has not shortened in three years. The same three years\nin which finance teams bought planning platforms, AI features and\ntransformation programmes at a pace Gartner's research documents.\n[84% of finance organisations under way with AI and 7% reporting high\nimpact](https://www.gartner.com/en/newsroom/press-releases/2026-06-08-gartner-says-cfos-need-structured-finance-ai-roadmaps),\nwith [45% of CFOs saying their AI investments lean toward\nproductivity](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.\n\nMoney in, cycle unchanged. Something about where the nine weeks\nactually go is being systematically misdiagnosed.\n\n## Where the nine weeks go\n\nAsk an FP&A team to log the cycle honestly and the time lands in\ncategories no one would call planning:\n\n- **Chasing and validating submissions**: the templates that come\n  back late, mis-keyed, or in last year's format, each requiring a\n  human to notice and negotiate the fix.\n- **Reconciling versions**: the consolidation that must be rebuilt\n  because a business unit resubmitted after the cut, and the\n  archaeology of establishing which of four circulating files is\n  current.\n- **Mapping and remapping**: cost centres reorganised mid-cycle,\n  new products squeezed into old hierarchies, the dimensional\n  bookkeeping that consumes analyst days and produces nothing a\n  decision maker ever sees.\n- **Rebuilding fragile logic**: the linked spreadsheets that break\n  under load, the allocations rerun after every assumption change,\n  the model that only its author can safely touch.\n\nSurveys of planning practice keep confirming the underlying\nreality: the large majority of finance teams still prepare data in\nspreadsheets before it ever reaches the planning system, and many\nrun the real process in parallel to the platform of record. The\nplumbing is not a residue the tools have not reached yet. The\nplumbing is the process.\n\n## Why faster plumbing is still the wrong target\n\nThe instinctive fix, and where that 45% of AI spend goes, is to\naccelerate the assembly. Faster consolidation, auto-filled\ntemplates, a copilot summarising the variances. Useful, and\ninsufficient, because a compressed version of the same cycle\nproduces the same artefact: a once-a-year point estimate, already\nageing on the day it is approved, defended thereafter against a\nreality that keeps moving.\n\nThe more valuable question is what the nine weeks were protecting.\nAn annual ritual whose length forces the organisation to plan\nrarely. Remove the plumbing properly and the cadence itself can\nchange:\n\n1. **Drivers instead of templates.** Most budget lines are\n   statistical consequences of a small set of drivers: volumes,\n   rates, headcount, mix. Model the lines from the drivers,\n   backtested against history, and the thousands of cells that\n   consumed submission rounds become computed defaults. Human\n   attention goes where it pays. The drivers themselves, and the\n   genuine judgement calls.\n2. **A rolling baseline.** With lines computed from continuously\n   updated drivers, a current baseline forecast simply exists, at\n   all times. The annual event stops being nine weeks of assembly\n   and becomes a decision layer on top of a living number: what\n   do we want to change, fund, or stop?\n3. **Odds on the outcome.** A budget built this way carries its\n   uncertainty honestly: not one number for year end, but a\n   distribution and the probability of hitting the target, updated\n   as the year moves.\n\n> The prize is not a seven-week budget. It is a finance function\n> whose scarce commodity, thinking, stops being rationed by\n> assembly work.\n\nThe AFP's own data points the same direction: the teams that run\nstructured scenario planning close their cycles in 8.1 weeks against\n9.2 for those that do not. The separator is not how fast the\nassembly runs but whether the process is built for thinking about\nalternatives. That gap does not come from accelerating the old\nprocess. The process was the problem.\n\n*Finance does not need more reports. It needs more time to\nthink.*\n\nDriver-based modelling, a continuously live baseline and odds on\nevery target are what the Prophesee Finance Suite's FP&A module\nreplaces the nine weeks with. Keep the judgement, lose the plumbing.\n[Start here](/contact).\n",1786833837935]