Budget Season Preparation

Budget season in most companies is a political exercise: each function requests 20% more than last year, finance cuts everyone by 15%, and the result is last year's budget with minor adjustments. This process produces a budget that nobody believes in and nobody is accountable for. The alternative is data-driven budget season — where every request comes with historical ROI, marginal return projections, and opportunity cost analysis. It takes more preparation. It produces a budget worth executing.

1. T-8 Weeks: Historical Performance Package Compile full-year actuals, ROI by function, marginal return by channel, and variance analysis. This data package is the evidence base for every budget request. Distribute it to all function leaders before requests are due. Requests without data get questioned. Requests supported by data get funded.
2. T-6 Weeks: Function Requests with Business Cases Each function submits a budget request with three components: (1) baseline spend to maintain current output, (2) incremental investment requests with projected ROI, (3) opportunities for spend reduction without output loss. This structure separates maintenance from growth and forces every incremental dollar to justify itself.
3. T-3 Weeks: Cross-Functional Optimization Bring all function requests together and optimize across boundaries. A $300K marketing request and a $200K sales request may be serving the same goal — pipeline generation — and only one of them needs to be funded. Cross-functional review prevents duplicate investments and identifies portfolio-level efficiencies that no single function can see.