Bottom-Up Budgeting

Bottom-up budgeting starts with the people closest to the work. Each team, cost center or service owner estimates what it will need for the coming year, including staff, software, infrastructure and projects. Those estimates are reviewed and rolled up, level by level, into a department budget and eventually the organization's total budget.

The approach draws on detailed knowledge that senior leaders do not have, and it gives budget holders ownership of the numbers they will be held to. Its main weakness is that the total often exceeds what the organization can afford, because each team tends to ask for what it wants rather than what fits the company's targets. For IT financial management, bottom-up budgeting is valuable for capturing the real cost of running services, but it usually needs to be balanced with top-down targets.

Definition of Bottom-Up Budgeting

Bottom-up budgeting, sometimes called participative budgeting, is a process in which budgets are prepared by the managers responsible for each area and then aggregated into higher-level budgets. Each cost center owner builds a budget for their area, which is reviewed by their manager and combined with others.

It is the opposite of top-down budgeting, in which senior leaders set the total budget and allocate it downward.

How the Process Works

Finance issues planning guidance, such as templates, timelines and assumptions for salary increases or inflation. Each budget holder then estimates the costs of their area for the coming year, line by line or by cost category.

Estimates are reviewed by managers at each level, who challenge assumptions and remove duplicates. The approved estimates are combined into department totals and then into the company budget.

If the total exceeds what the organization can afford, requests are sent back for reductions, which can take several rounds.

What Teams Estimate

In IT, bottom-up estimates typically cover staff and contractors, software licenses and subscriptions, cloud and hosting, hardware, telecom, maintenance contracts and planned projects.

Service owners often know which contracts are renewing, which prices are rising and which systems will need upgrades, information that would be hard to capture from the top.

Good estimates explain the assumptions behind them, such as user counts, contract terms and project scope, so that reviewers can test them. An estimate without assumptions is hard to challenge and hard to revise when conditions change.

Importance of Bottom-Up Budgeting in IT Financial Management

Technology costs are spread across many contracts, services and teams. Only the people managing them know the details of renewals, usage trends and upcoming work.

Bottom-up budgeting captures that knowledge. A service owner who manages a contract knows when it renews and what the vendor has signaled about pricing, and an infrastructure lead knows which hardware is nearing the end of support. A budget built without this information is likely to miss costs that are already committed.

It also gives budget holders a stake in the numbers, which tends to improve how carefully they manage spending during the year.

Accuracy and Ownership

Because estimates are built from known contracts, staffing and plans, bottom-up budgets tend to reflect the real cost of running services more accurately than a percentage applied to last year's total.

Budget holders who build their own budgets understand them better and are more likely to accept responsibility for meeting them. When variances occur, they can explain them because they know the assumptions.

This supports IT cost transparency, since the budget is tied to identifiable services and cost drivers.

Common Problems

Bottom-up budgets often include padding. Managers who expect their requests to be cut may ask for more than they need, and those who fear losing unused funds may build in contingency.

The process can also be slow, with many rounds of review and revision. And because each team focuses on its own needs, the result may not reflect company priorities, funding areas that matter less while underfunding strategic work.

These problems are why most organizations combine bottom-up estimates with top-down targets. The bottom-up estimates show what the organization actually needs, while the targets keep the total within what it can afford.