How to Run the Annual Budget Process in 6 Weeks: A Week-by-Week Timeline for $5M–$50M Companies

A budget cycle that runs from September to February isn't thorough. It's late. By the time the board approves it, January actuals are already in and the first month's variance is against a plan nobody has signed.

The benchmark data is blunt about this. APQC's Open Standards Benchmarking, reported by CFO.com, puts top-performing organizations at 25 calendar days or fewer from setting budget objectives to delivering a usable budget. The median is 32 days. The bottom quartile needs 56 days or more. Those figures come from a survey of roughly 2,600 organizations, and they count weekends. Six weeks (42 days) is a realistic target for a $5M–$50M company that hasn't run a tight cycle before. If you're already at three or four months, cutting to six weeks is mostly a sequencing fix, not a staffing one.

Here's the calendar we'd run, starting in mid-September for a December year-end.

Before week 1: close the books and pick the baseline

Nothing in a budget cycle goes faster than the close that feeds it. If August isn't closed and reviewed by mid-September, the run-rate everyone builds from is guesswork, and you'll rebuild it in October.

Two decisions happen here, both owned by finance, both before any template leaves the building. First, the baseline: usually the latest rolling forecast for the current year, not last year's budget. Last year's budget is a commitment somebody made 12 months ago. The forecast is what's actually going to happen. Second, the level of detail: which line items get built bottom-up by department heads, and which get set as a percentage or a rate by finance. Rent, insurance, software renewals and debt service don't need a department head's opinion. Headcount and revenue do.

If you skip this and let everyone build everything, you get 40 tabs of noise and a consolidation problem.

Week 1: targets first, templates second

This is the step most companies get backwards. They send out templates, collect wishes, add them up, discover the total is $3M of EBITDA short of what the sponsor expects, and then start the real budget in week five.

Instead, week one is a single meeting: CEO, CFO, and the board or sponsor representative. It sets three or four top-down numbers for the year: revenue, gross margin, EBITDA, and if there's debt, the covenant headroom the plan needs to protect. For a PE-backed company these usually come straight out of the value-creation plan, so the meeting is short. For a founder-run company it's harder and more important, because without it the budget becomes a negotiation with no anchor.

Once the targets exist, finance turns them into department-level envelopes. Sales gets a bookings number. Ops gets a gross margin target. G&A gets a headcount ceiling. Then the templates go out with the envelope printed at the top, so nobody spends two weeks building toward a total the company can't accept.

What is a top-down budget? A budget where leadership sets the totals first and departments build detail underneath them. Bottom-up is the reverse. Six-week cycles are almost always top-down targets with bottom-up detail. Pure bottom-up is what produces the February finish.

Weeks 2 and 3: department builds

Department heads get ten working days. Not three weeks, not "when you can." Ten days is long enough to think and short enough that it stays a priority.

Finance's job during this stretch is to make the build easy. Prefill the template with the run-rate so managers are editing, not typing. Lock formulas and reference tabs. Set the drivers (headcount, price, volume, conversion rates) as inputs so that a manager who wants more revenue has to say where it comes from. Hold a 20-minute office-hours slot each day for questions. Most managers only need one.

What you're avoiding here is the 100% problem. The Association for Financial Professionals' 2025 FP&A benchmarking survey found that every single respondent, 100%, uses spreadsheets for planning and reporting at least quarterly. That isn't a knock on spreadsheets. It means your budget lives in files that people will edit freely unless you design them not to be. A template someone can break is a template someone will break, usually on day nine.

Week 4: consolidate and find the gap

Finance pulls every department into one model, checks it ties, and compares the total to the week-one targets. There is always a gap. Usually revenue is optimistic and expenses are higher than the envelope, at the same time.

This week is not a negotiation. It's a diagnosis. Where exactly is the gap? Which three or four assumptions drive most of it? Is sales assuming a ramp that history doesn't support? Did two departments both budget for the same new hire? Did anyone budget for the price increase the CEO already announced? Finance writes this up in one page with the numbers, and that page becomes the agenda for week five.

Build the cash view here too, not after approval. A P&L budget that clears EBITDA but breaches a covenant in March because of working capital timing isn't approved. It's a draft.

Week 5: the reconciliation meeting

The second of the two meetings that matter. Leadership team, half a day, one agenda: close the gap identified in week four. Every decision gets made in the room and logged. Cut the hire, delay the office move, raise the price, accept a lower EBITDA and take it to the board with a reason.

The reason this works is that the decisions have been framed. Nobody is looking at 40 tabs. They're looking at one page that says the gap is $1.8M and here are the six levers that move it. Groups make decisions like that in an afternoon. Groups asked to "review the budget" don't make them at all.

Finance then has the rest of the week to update the model, rerun the cash and covenant checks, and produce the board version: a one-page summary, the monthly P&L, the balance sheet and cash flow, headcount by month, and the key assumptions written in plain English.

Week 6: board approval and lock

Send the package five business days before the board meeting. That's non-negotiable if you want a decision instead of a discussion. Present the assumptions, not the spreadsheet. The board wants to know what you believe about growth, margin, hiring, and cash, and what happens if you're wrong on the big one. A downside case on the top two assumptions is enough. You don't need five scenarios.

Once approved, the budget is locked. Copy it to a read-only version and load it as the baseline for variance reporting. Changes from here go into the rolling forecast, not the budget. This is the part that keeps the whole exercise honest; a budget that gets "updated" in February is just a forecast with an approval stamp.

A few questions that come up every year

What if the board wants a stretch case and a base case? Fine, but approve one. The approved case is the one bonuses and variance reporting key off. The other is a sensitivity, and it can live in the forecast.

Should we budget monthly or quarterly? Monthly, always, for the P&L and cash. Seasonality and hiring timing disappear in a quarterly view, and your lender reports monthly anyway.

Can we really do this in six weeks with a three-person finance team? Yes, if finance does the prefill and target-setting work up front and department heads only handle their own drivers. The cycles that take four months aren't slow because of headcount. They're slow because the targets got set last.

The real fix

The single biggest lever isn't a tool or a template. It's moving the target conversation from the end of the process to the start. Every week you spend building without a target is a week you'll spend rebuilding once one shows up. Set the numbers in week one, make the two meetings count, and the rest is a schedule.

Plametrix runs annual budget cycles like this for growing and PE-backed companies as part of an outsourced FP&A service, from the baseline and templates through the board package and the locked variance baseline. If your budget season usually ends in February, this is a good year to try September to October instead.