Incremental Budgeting
What is Incremental Budgeting?
Incremental budgeting is a budgeting approach that uses the previous period's budget or actual spending as the base, adjusting it up or down by a percentage or for known changes.
Updated November 2026 · 5 min read
Incremental budgeting is the most common way organizations set budgets. Rather than building each budget from scratch, managers start with last year's budget or actual spending and adjust it for expected changes, such as inflation, growth targets, new projects or planned savings. A department that spent $10 million last year might receive $10.3 million this year, a 3 percent increase, with adjustments for specific known changes.
The approach is popular because it is quick, simple and stable. It also has well-known weaknesses: it tends to preserve existing spending patterns, rewards spending the full budget and does little to challenge whether costs are still necessary. For IT financial management, understanding these strengths and weaknesses helps leaders decide where incremental budgeting works well and where a more rigorous approach is needed.
Definition of Incremental Budgeting
Incremental budgeting is a method of preparing budgets by taking the prior period's figures as a starting point and making incremental changes. The changes may be across-the-board percentages, such as a 2 percent increase for inflation, or specific adjustments for known events, such as a new contract or a retired system.
The underlying assumption is that the prior period's spending was reasonable and that only the changes need to be justified. That assumption is often sound for a year or two, but becomes less reliable the longer the base goes without review. This contrasts with zero-based budgeting, in which every cost must be justified from zero each period.
How It Works
Budget owners receive their prior-year budget or actuals along with guidance from finance, such as an overall growth or reduction target. They then propose adjustments, explaining the reasons for significant changes.
Finance consolidates the proposals from every department, compares the total with the organization's financial targets and negotiates adjustments where needed. The final budget is usually close to the prior year, with targeted changes. In many organizations the whole cycle takes a few weeks, compared with several months for a full zero-based exercise.
Incremental and Zero-Based Budgeting
Zero-based budgeting requires each cost to be justified from scratch, as if the organization were starting fresh. It can uncover unnecessary spending but takes significant time and effort, especially for large, complex budgets.
Many organizations use a hybrid. They apply incremental budgeting to stable costs and use zero-based reviews for selected areas, such as the largest cost categories or areas where spending has grown rapidly, rotating these reviews over several years. This keeps the effort manageable while ensuring that no area of spending goes unexamined for too long.
Importance of Incremental Budgeting in IT Financial Management
Incremental budgeting is widely used for IT budgets, and its effects on technology spending can be significant over time. Understanding them helps IT finance teams decide where to apply more scrutiny.
The approach has clear benefits, but its weaknesses can accumulate if they are not managed.
Benefits of Incremental Budgeting
Incremental budgeting is efficient. It requires far less effort than building every budget from scratch, which matters when IT teams also need to run services and deliver projects. It also provides stability, since teams can plan with reasonable confidence that their funding will continue.
For stable, well-understood costs, such as long-term contracts, depreciation and core staffing, incremental adjustments are usually accurate enough. Rebuilding these costs from zero each year adds little value. Incremental budgeting also makes year-over-year comparisons simple, since each line can be compared directly with its prior-year equivalent through budget variance reporting.
Weaknesses and Risks
Because the starting point is last year's spending, incremental budgeting tends to lock in existing costs, including those that are no longer needed. Unused licenses, redundant applications and outdated contracts can persist for years. The longer a budget is set incrementally, the more of these costs tend to accumulate in the base.
It can also encourage managers to spend their full budget, since unspent funds may be removed the following year. And it can make it harder to shift investment from running existing systems toward new priorities, since each area's base is treated as a given, reinforcing a high share of run spending in the run, grow, transform mix.
How to Use Incremental Budgeting Effectively
Incremental budgeting works best when combined with regular reviews of the underlying costs and clear links between spending and value.
IT finance teams can apply practices that keep its efficiency while reducing its weaknesses.
Reviewing the Base Regularly
Organizations should periodically review the base itself, not just the increments. Rotating zero-based reviews across cost areas, such as software licenses one year and infrastructure the next, ensures every area is examined over a few years.
Data from software asset management (SAM), cloud cost tools and contract records makes these reviews faster, by showing usage, utilization and renewal dates that reveal costs that can be reduced.
Linking Budgets to Drivers and Value
Rather than applying a flat percentage, budgets can be adjusted based on cost drivers, such as expected changes in users, transactions or workloads. This makes increments more defensible and easier to explain. A collaboration budget that rises because headcount is forecast to grow 8 percent is easier to approve than one that rises by a flat percentage with no stated reason.
Linking budgets to the services and capabilities they fund, through approaches such as Technology Business Management (TBM), helps leaders see what each increment buys and decide where to invest or cut.
Examples of Incremental Budgeting in IT Financial Management
The examples below show incremental budgeting in practice and how its weaknesses can be addressed.
Both use illustrative figures.
In each, the base budget turned out to contain costs that no one had questioned for years.
A Standard Incremental Budget
An IT department's budget last year was $60 million. Finance sets a 3 percent increase for inflation, bringing the base to $61.8 million. The department adds $2 million for a new security program and removes $1.2 million for a system being retired.
The final budget is $62.6 million. The process took a few weeks, and most budget owners received figures close to their prior-year amounts. No one examined whether the $60 million base still reflected the organization's needs, which is the question the next example addresses.
A Zero-Based Review of Software Costs
The same organization runs a zero-based review of its $12 million software budget, which has been set incrementally for five years. The review finds $1.4 million of licenses with no active users and $800,000 of overlapping tools.
Removing these costs reduces the software base by $2.2 million, about 18 percent. The savings are redirected to transformation projects, and the organization schedules a similar review of infrastructure costs for the following year. Future incremental budgets for software now start from the reduced base, so the savings carry forward every year rather than appearing only once.
Conclusion
Incremental budgeting sets budgets by adjusting the prior period's figures for inflation, growth and known changes. It is efficient and stable, but it tends to preserve existing spending patterns and can allow unnecessary costs to persist.
In IT financial management, incremental budgeting works well for stable costs when combined with regular reviews of the base, driver-based adjustments and clear links between spending and value. This balance keeps budgeting efficient while ensuring technology spending continues to reflect current priorities.
Related terms
Budget Variance
Budget variance is the difference between a budgeted amount and the actual result for a period. It is favorable when costs come in under budget and unfavorable when they exceed it.
Run, Grow, Transform
Run, Grow, Transform is a model that classifies technology spending by purpose: running, growing or transforming the business. It shows how much of a budget maintains versus changes the business.
Software Asset Management (SAM)
Software asset management (SAM) is the discipline of managing software across its lifecycle, from request and purchase to deployment, use and retirement, to control costs, stay compliant and reduce risk.
Cost Driver
A cost driver is a factor that causes a cost to change, such as users, transactions or servers. Cost drivers are used to allocate shared costs and explain why spending rises or falls.