MI Solutions
Insights/Budgets and finance
Budgets and finance

Software Spend Forecasting: Inflation, Uplifts and Headcount Drivers

A driver-based approach to forecasting software spend: general inflation, vendor price uplifts, headcount growth, efficiency savings and contingency, with an example.

By the MI Solutions SAM team10 min read2 exhibits

A forecast built on a single growth percentage hides what is really happening. Some contracts will rise with vendor price increases; others scale with headcount; some will shrink because you plan to reclaim or retire. Driver-based forecasting makes each of those forces explicit, so the forecast can be explained, challenged and adjusted.

Five drivers

DriverApplies toExample assumption
General inflationContracts with CPI-linked increases3%
SaaS price upliftTagged contracts with expected vendor increases7%
Headcount growthPer-user products tied to hiring4%
Efficiency savingsContracts with planned reclaim or consolidation−6%
ContingencyUnplanned needs2%

The forecast as a bridge

Exhibit 1
A driver-based forecast explains every dollar of changeBaseline to projected software spend, $K (illustrative $14.2M portfolio)$14,200KBaseline+$180KInflation+$520KSaaS uplift+$310KHeadcount−$430KEfficiency+$280KContingency$15,060KProjectedAxis starts at $13,000KIllustrative. Each driver is applied only to the contracts it affects, so its dollar effect differs from itsheadline percentage.

Top-down vs driver-based

Exhibit 2
A single growth rate drifts away from realityMonthly software spend, $K: actual vs a top-down 6% forecast vs a driver-based forecast,illustrative$1,100K$1,150K$1,200K$1,250K$1,300K$1,350KJanFebMarAprMayJunJulAugSepOctNovDecTop-down 6% $1,255KDriver-based $1,295KActual $1,279KIllustrative. The driver-based forecast follows renewals and hiring through the year; the top-down linecannot.

The actuals line stops in September, the latest closed month, which is why it is shorter.

How to build it

  1. Start from the contract baseline

    Next year's value of every agreement at current terms.

  2. Tag contracts

    With the drivers that apply to each.

  3. Apply each driver

    Only to its tagged contracts.

  4. Add contingency

    As a separate line, not hidden in other drivers.

  5. Show the bridge

    And the assumptions, to finance.

  6. Update

    As negotiations conclude and hiring plans change.

Forecast review each month

How MI One helps

Frequently asked questions

How accurate can a software forecast be?

With contract-based baselines and explicit drivers, most organizations stay within a few percent, with variances explained by timing and consumption.

Should savings be in the forecast?

Yes, as their own driver, so finance can see the assumption and track delivery.

How far ahead should we forecast?

Twelve months in detail, and three years at the driver level for planning multi-year agreements.

See where your software budget goes

Bring your five largest vendors to a 30-minute call. Our SAM experts will show you where the savings usually hide, and how fast MI One can surface them.