© 2026 Procr
Most SaaS budgets are built from last year's invoices. That approach worked when contracts renewed at the same price, on a predictable annual schedule, with one line item per vendor. None of those conditions reliably hold anymore. The result is a growing gap between what finance teams plan for and what vendors actually charge.
The standard SaaS budgeting method is simple: find last year's spend, add a small growth buffer, and submit. For teams with a handful of well-managed contracts, that process is workable. For most mid-market teams, it produces a budget that is structurally wrong before the fiscal year begins.
Three dynamics have made this worse since 2023. First, SaaS inflation is running at 12.2%, according to Vertice's 2026 SaaS Inflation Index. That is 4.5 times the general consumer price inflation rate in G7 countries. A flat rollover budget understates your actual spend by that margin before accounting for usage growth.
Second, contract structures are more complex. Many vendors have layered consumption-based charges, AI feature add-ons, or true-up provisions on top of their base subscription pricing. Zylo's 2026 SaaS Management Index found that 78% of IT leaders experienced unexpected charges tied to consumption-based or AI pricing models in the previous 12 months. These are not mistakes or edge cases; they are the result of pricing terms that buyers agreed to but did not fully model at budget time.
Third, spend is decentralised. Business units now control 81% of SaaS spend, while central IT directly manages just 15%, per the same Zylo report. Finance teams building budgets from IT's view of the world are missing the majority of vendor spend from the start.
A standard SaaS budget failure is not usually caused by one large surprise. It is caused by several medium-sized surprises arriving throughout the year from different directions.
1. Escalation clauses you did not price into next year
Most enterprise SaaS contracts include an annual escalation clause, typically 3-5% annually, sometimes tied to CPI with a floor, sometimes a fixed rate. At renewal, the vendor applies this increase automatically, often before any negotiation conversation takes place. Across a $2M annual SaaS portfolio, a 5% average escalation adds $100,000 that was never in the budget.
The actual increases applied in 2025 and 2026 frequently exceed those contractual escalation rates because vendors are resetting pricing at renewal rather than applying the written escalator to the prior year's rate. Vertice data shows SaaS inflation at 12.2% across the market, and SaaStr's 2025 pricing analysis found an 11.4% industry-wide average price increase. Finance teams budgeting for 3% annual increases are materially underestimating renewal costs.
2. True-up charges and usage-based overages
True-up clauses require a buyer to pay for any usage above the contracted seat or volume count at the end of the measurement period. For seat-based tools, every user added mid-year who was not in the original contract generates an incremental charge at renewal. For consumption or API-based tools, the charges accumulate in real time.
Teams that adopted AI features from existing vendors have often discovered this firsthand. Vendors routinely price AI capabilities as consumption-based add-ons, making the per-user cost variable and difficult to forecast. A 200-seat contract that adds 50 seats mid-year and uses AI features intensively can generate a true-up charge 20-30% above the original contract value. Zylo found that 78% of IT leaders reported unexpected charges from these models in the past year.
3. Auto-renewals at list price after a missed notice window
Most SaaS contracts auto-renew if the buyer does not act within a specified cancellation or renegotiation window, typically 30 to 90 days before expiration. Missing that window does not just mean losing the chance to cancel; it means accepting the renewal on whatever terms the vendor has set, usually list price with the escalation clause applied.
The average enterprise manages around 211 SaaS renewals per year, according to Zylo, and nearly 60% of procurement leaders identify unintentional renewals as a top source of budget waste. For mid-market teams without a dedicated renewals calendar, several of those renewals will pass unmanaged each year, locking in costs that were never evaluated.
4. Licence waste embedded in the run rate
Unused licences are a structural budget problem, not a one-time oversight. Zylo's 2026 SaaS Management Index found that organisations leave an average of 36% of their SaaS licences unused. Those licences appear as an operating cost in next year's budget by default unless someone actively reviews utilisation before the renewal date.
For a mid-market team with $3M in annual SaaS spend, 36% unused licences represents roughly $1.08M in spend that could potentially be reduced at renewal. Budgets built from renewal invoices never capture this opportunity because they assume the current contract size is the right one.
5. Shadow IT and decentralised purchasing
When business units procure software without central visibility, those purchases do not appear in the finance team's view of SaaS spend until the credit card bill arrives, the contract auto-renews, or an invoice gets coded to the wrong budget line. With business units controlling 81% of SaaS spend, finance teams at mid-market companies commonly discover that total SaaS outlay is 15-30% higher than what they tracked in the prior year's budget.
Gartner projects that by 2027, 25% of enterprise software overspending will come from unused entitlements and redundant tooling, much of it from decentralised purchasing that bypassed any procurement review.
Fixing SaaS budget reliability does not require a large investment in tooling. It requires a different process, applied consistently.
Step 1: Build a complete contract inventory before you open a spreadsheet
The budget should start with every active vendor contract, including the ones sitting in department expense accounts that never went through procurement. Each entry needs five fields: vendor name, annual contract value, contract end date, notice period, and contract type (fixed seat, consumption-based, or true-up provision).
This inventory is the budget's foundation. Without it, every downstream number is an approximation that will be wrong in ways you cannot predict. Teams that have done this exercise consistently report finding 10-20% of renewals they had no previous visibility into.
Step 2: Classify each contract by cost variability
Fixed-price contracts with no consumption component are predictable within the bounds of the escalation clause. Consumption-based contracts, hybrid pricing contracts, and contracts with true-up provisions are variable and require separate treatment.
For fixed contracts, budget at the contract value plus the escalation rate. If the escalation clause allows CPI or 5%, whichever is higher, budget at 7-8% above current to build a conservative cushion. For variable contracts, build a range: a base case at flat usage, a mid case at 10-15% usage growth, and an upside case at 30% usage growth including AI features. Submit the mid case as the official budget number and document the full range for your CFO or VP Finance so they understand the exposure before year-end.
Step 3: Flag every renewal with a notice window of 90 days or less
Contracts with short notice windows require active calendar management. A 30-day notice period on a $200,000 contract means the renegotiation window opens just three weeks before most finance teams even start the conversation.
Map every renewal date to a calendar alert set 120 days before expiration. That is the date someone needs to own the renewal decision, not begin thinking about whether to renew. Tropic data shows that teams engaging vendors six months ahead save 39% more than those waiting until the final 30 days.
Step 4: Apply a renewal buffer by contract tier
Tier contracts by annual contract value. For contracts over $100,000, apply a 10-15% renewal buffer above the current ACV to account for escalation, potential true-up charges, and the risk of a pricing reset at renewal. For contracts between $25,000 and $100,000, use 7-10%. For contracts below $25,000, a 5% buffer or de minimis assumption is usually sufficient since variance on small contracts is unlikely to be material in aggregate.
This tiered approach allocates budgetary cushion proportionally without over-reserving across the entire portfolio.
Step 5: Review actual versus budget quarterly, not annually
SaaS spend variance compounds quickly. A mid-market enterprise managing $8M in SaaS implemented quarterly spend reviews and reduced year-end budget variance from 14% to 4% within two quarters, according to CloudEagle case data. The change was not tooling; it was a scheduled review where someone compared actual invoices against the budget plan and explained variances before they became year-end surprises.
Quarterly reviews create the feedback loop that annual budgeting lacks. Unexpected charges surface in Q1 instead of Q4, when there is still time to adjust.
Consider a mid-market operations company with 180 employees and $2.8M in annual SaaS spend. Prior to 2025, their finance team built each year's budget from the prior year's invoices with a flat 5% growth assumption. Actual year-end spend consistently ran 12-18% above budget.
After building a complete contract inventory for the first time, the team found six contracts with auto-renewal provisions and 30-day notice periods that had never been flagged in prior budget cycles, three contracts with true-up provisions that had generated unexpected year-end charges for two consecutive years, and 14% of licences across their top five tools assigned to employees who had left the company.
None of these findings required new software. They required someone sitting down with the actual contracts.
The 2026 budget came in within 4% of actual spend at mid-year, versus a prior record of 18% over. The inventory changed what the budget could do.
The pattern holds consistently: budget accuracy improves when the budget is built from contract data rather than invoice history. The two are not the same thing.
Zylo's 2026 SaaS Management Index found that median SaaS spend per employee is $9,455, with an average of $11,530. For a 150-person company, that implies a realistic SaaS budget range of roughly $1.4M to $1.7M annually. Teams spending significantly below that range are likely undercounting shadow IT and department-procured tools that have not been centralised in any finance system.
Vertice's 2026 SaaS Inflation Index reports SaaS inflation running at 12.2% across the market. While individual contracts may increase less depending on escalation clause caps, budgeting only for the contractual floor of 3-5% will understate actual renewal costs for most portfolios. A conservative planning assumption for 2026 is an 8-10% aggregate portfolio increase year-over-year, with higher buffers for any vendor that has publicly announced pricing changes.
Model three scenarios for each consumption-based contract: flat usage, 15% growth, and 30% growth. Budget at the mid case and document the upside exposure for senior finance stakeholders. If the contract includes a true-up provision, calculate the exposure at the 30% growth scenario and include that as a separate line-item risk in your budget narrative so it does not surface as a surprise at year-end.
Start the internal review 120 days before contract expiration. Use 90 days as the latest point at which someone has formal ownership of the renewal decision. For contracts over $100,000, initiate vendor conversations no later than 90 days out. For contracts with 30-day notice periods, the 120-day internal trigger is the only way to preserve enough runway to negotiate meaningfully rather than simply accepting what the vendor proposes.
Zylo's 2026 SaaS Management Index found that 36% of licences are unused on average, representing $19.8M in preventable spend annually for the average enterprise. For mid-market companies, the absolute dollar figure is smaller but the utilisation rate is comparable. On a $2M SaaS portfolio, 36% unused implies roughly $720,000 in licences that could be reduced or eliminated at the next renewal cycle, with no impact on active users.
Procr
See what Procr does with your real vendor portfolio.