The short version: Abacum works with finance teams running annual planning. The average annual budget still takes 8.7 weeks, unchanged in three years, because most of the cycle is waiting rather than modelling. The median company produces five versions before it is done.

There is one number in AFP’s benchmarking survey I have trouble explaining away.

The average company takes 8.7 weeks to produce an annual budget. That is the same figure as three years ago. In between, FP&A technology spend hit record levels and roughly four in five teams put AI somewhere in the process.

I sell planning software for a living. This is not the number I would have picked.

Average time to produce an annual budget: 8.7 weeks in 2023 and 8.7 weeks in 2026, unchanged despite record FP&A technology spend and roughly four in five teams adopting AI. Source: AFP 2026 FP&A Benchmarking Survey.

Average time to produce an annual budget. Bars drawn to scale on the same measure. Source: AFP 2026 FP&A Benchmarking Survey.

So either the software does not work, or it has been fixing something that was never the bottleneck.

APQC settles it. In their benchmarking, most of the budget cycle is not work at all. It is waiting for inputs or responses. The median company produces five versions of the budget before it is done. Five versions is the number worth staring at, because a faster model does not remove a single one of them.

The blank cell problem

Only 12% of teams publish their macro assumptions before submissions open.

Picture what that means on the ground. Templates land in a department head’s inbox. There is a cell asking for next year’s growth rate and nobody has told them what rate finance is using. So they guess, and they guess in the direction that protects their budget. Forty percent of teams report their first draft came back over-optimistic, which is the polite description of the same event.

Finance cuts it back. The department learns that submissions get cut, so next year they open higher. APQC calls this the car dealership dynamic, where both sides start at a number neither believes and then spend weeks walking to the middle. That is where your five versions come from, and not one of them is a modelling problem.

Nine weeks is a distance, not a speed

APQC has top performers finishing the annual budget in 25 days or less. At the 75th percentile it takes about 50. Same work, double the time, and the gap is mostly handoffs.

The most useful finding in their data is also the most counterintuitive. Top performers tend to start later. Waiting means you budget against actuals rather than against a forecast of actuals, so the first draft lands closer to real and there is less to argue about. Starting early feels responsible and buys you an extra round of fiction.

The AFP data points the same way. Teams who build their scenarios before the cycle opens, rather than in reaction to questions, finish in 8.1 weeks against 9.2 for everyone else, which AFP wrote up here. Four days is a small prize, and that is rather the point. Nothing moves this number much, because the number is set by how many times work changes hands.

Four decisions that cost nothing

Publish the assumption pack with the templates. Rates, headcount ceilings, macro inputs, the growth number you will defend to the board. Every input you leave blank is a guess you pay for in round two.

Say out loud that you will not haircut submissions. Then do not. The padding only stops once departments believe the first number is the real one, and that takes a cycle or two of proof.

Cap the versions at two, and say so at kickoff. If the median is five and you name no limit, you will get five. A first draft that might be the last one gets written more carefully.

Start a week later than feels comfortable. You will be working from more actuals and fewer assumptions, and you will spend less of December reconciling a plan built in October to a year that already moved. The mechanics of all four are in our guide to building budgets that drive business performance.

Where the software does help

I am not arguing against the tools. That would be a strange position for me, and it would also be wrong. Faster modelling is real and it matters a great deal once the coordination is sorted. What no platform will do on your behalf is decide who submits what, in which order, against which assumptions, and whether their first number will be taken seriously. Those are calendar and trust decisions, and they are free. I went through the process mechanics in Planning Orchestration.

If FY27 lands at nine weeks again, do not start with the model. Count the versions.

Get ready for budgeting season with Abacum

In this article

The blank cell problem
Nine weeks is a distance, not a speed
Four decisions that cost nothing
Where the software does help

Frequently Asked Questions

How long should the annual budgeting process take?

The average annual budget takes 8.7 weeks according to AFP's 2026 FP&A Benchmarking Survey, and three-quarters of teams have 12 weeks or less in total. APQC puts top performers at 25 days or less. In Abacum the assumption set and the plan live in the same place, which removes the rework rounds that make up most of the difference between fast and slow cycles.

Why does the annual budget take so long?

Most of the time goes into rework rather than modelling. Only 12% of teams publish macro assumptions before submissions open, so departments guess at inputs, and 40% report first-draft misses from over-optimistic projections. Each guess costs a round. The cycle length is set by how many times a number changes hands before it is final.

Does FP&A software shorten the budget cycle?

Not on its own. The average cycle has stayed at 8.7 weeks across three years of record FP&A tech spend, because software compresses the modelling step and the modelling step was never the binding constraint. Tools shorten the cycle when they are paired with sequencing decisions: published assumptions, a round cap, and dependencies run in order. Abacum is built to hold both the plan and those assumptions in one system.

How much time can CFOs save with an automated FP&A tool?

Abacum customers typically recover days per reporting cycle, but hours saved is the weakest case a CFO can take into a budget review. The stronger measure is decision latency: how long it takes from a variance appearing to somebody acting on it, and how many rounds a plan takes to reach sign-off. Time saved only counts once it changes a decision. See the platform.

How can CFOs easily adjust budgets for unexpected changes?

Build the scenarios before you need them rather than after. AFP found teams running structured scenario planning complete the budget in 8.1 weeks against 9.2 for those who do not, because pre-built scenarios remove a round of modelling when assumptions move. Abacum lets you run those scenarios against a live plan instead of rebuilding a model each time the question changes.

What should go in a budget assumption pack?

The inputs departments would otherwise guess at: rates, headcount ceilings, macro assumptions, and the growth number finance will actually defend. Publish it in the same email as the templates. Only 12% of teams do this before submissions open, which is why over-optimistic first drafts are the most commonly reported cause of budget rework.

How many rounds should an annual budget take?

Two, and the cap should be stated at kickoff. Most cycles have no round limit, so they get one by exhaustion around week eight. Naming the cap in advance changes what departments submit the first time, because a first draft that might be the last one is written differently from one that is expected to be negotiated.

Explore FP&A with Abacum

See how connected planning, reporting, and data workflows help finance teams make faster, more confident decisions.

Financial planning

Build connected budgets, forecasts, and scenarios that stay current as the business changes.

Financial reporting

Turn trusted planning data into clear reporting, variance analysis, and stakeholder-ready narratives.

Finance integrations

Connect ERP, CRM, HRIS, and operational data so the plan reflects what is happening now.

Stop managing your platform and start managing the business.

Get the AI-native foundation you need to keep data trustworthy, models current, and decisions aligned—all on your own terms.

Stop managing your platform and start managing the business.

Get the AI-native foundation you need to keep data trustworthy, models current, and decisions aligned—all on your own terms.

Stop managing your platform and start managing the business.

Get the AI-native foundation you need to keep data trustworthy, models current, and decisions aligned—all on your own terms.

Join us for Summer Fridays - 20 minutes on Thursday to take back your weekend
Join us for Summer Fridays - 20 minutes on Thursday to take back your weekend
Join us for Summer Fridays - 20 minutes on Thursday to take back your weekend