A documented IT sourcing savings methodology is the difference between reporting 12 percent savings and seeing 12 percent fewer dollars leave the budget. Across our 198 program panel from 2023 to 2025, median realization sits at 72 to 84 cents per reported dollar of negotiated savings. Top quartile programs hit 92 to 98 cents. The 16 to 24 percentage point gap is structural, predictable, and addressable with six methodology elements that almost no median program runs consistently. Programs that close the gap recover 3 to 7 percent of addressable spend per year that was previously reported as savings but never arrived in budget.
Methodology notes: IT sourcing programs analyzed Q1 2023 through Q4 2025 across benchmarked contracts and 38 vendor categories. Sample weighted toward North America (60 percent), EMEA (27 percent), APAC (13 percent). Realization calculated as audited budget impact divided by reported negotiated savings, normalized for in year versus annualized accounting.
What savings methodology covers
A complete IT sourcing savings methodology is a documented set of six rules. The first rule is the baseline definition: what is the comparison point that savings are measured against. The second rule is the savings category set: which kinds of value count as savings and which do not. The third rule is the calculation formula: how is each savings category computed in dollars. The fourth rule is the reporting cadence: when and how are savings reported, with what level of audit support. The fifth rule is the audit process: how are reported savings validated against actual budget impact. The sixth rule is the compensation linkage: which savings metrics drive variable compensation and at what reporting level.
The 198 program panel shows that median programs run rules 1, 2, and 3 with some discipline, run rule 4 inconsistently, and almost never run rules 5 and 6. Top quartile programs run all six rules with formal documentation and a quarterly methodology refresh. The performance gap between top quartile and median is almost entirely concentrated in rules 5 and 6, not in the upstream rules that get most of the methodology debate.
Why methodology matters more than the negotiation
The negotiation produces the gross savings. The methodology determines whether the gross savings convert to budget impact. A program that produces 18 percent gross savings and runs at 75 percent realization delivers 13.5 percent budget impact. A program that produces 13 percent gross savings and runs at 95 percent realization delivers 12.4 percent budget impact. The two programs are essentially indistinguishable to the CFO, but the second program is far less stressful to operate because the headline number is close to the audited number. The methodology is the multiplier on the negotiation work.
Audit your savings realization
Send last 12 months of reported negotiated savings and the corresponding budget data. We audit the realization rate and surface leakage sources in 72 hours.
The four leakage sources
The 198 panel decomposes realization leakage into four sources. Each source has a typical contribution to the total leakage and a defined countermeasure.
| Leakage Source | Typical Contribution | Countermeasure |
|---|---|---|
| 1. Mid term scope expansion | 35-48% of total leakage | Scope cap clauses in contract; quarterly scope reconciliation |
| 2. Auto renewal escalation | 20-30% | Renewal calendar with three layer notice surfacing |
| 3. Migration and absorb costs | 14-22% | Net savings definition includes absorb cost |
| 4. Vendor true ups at renewal | 10-18% | Price protection caps; baseline drift audit |
Source 1: Mid term scope expansion
Mid term scope expansion is the largest leakage source. The negotiation produces a unit price reduction. The vendor responds by upselling additional scope inside the contract term (more users, more modules, more capacity) at the new unit price. The new scope is real business value, but it consumes the savings that the unit price reduction was supposed to deliver. The countermeasure has two parts. First, the contract must contain scope cap clauses that require renegotiation if scope exceeds a defined threshold (typically 15 to 25 percent above baseline). Second, the savings methodology must run a quarterly scope reconciliation that compares current scope to baseline scope and reports scope expansion as a separate line item rather than netting it against savings.
Source 2: Auto renewal escalation
Auto renewal escalation is the second largest leakage source. Contracts with auto renewal clauses where the notice date is missed renew on vendor standard terms with the standard uplift. The savings from prior negotiation are reset. The countermeasure is the renewal calendar with three layer notice surfacing. See the renewal calendar template. Programs that operate the three layer surfacing eliminate this leakage source on 95 to 99 percent of contracts.
Source 3: Migration and absorb costs
Migration and absorb costs apply to consolidation and platform absorb deals. The negotiation produces gross savings on the eliminated vendor cost. The migration consumes some of those savings (project cost, data migration, user enablement). The absorb produces a cost on the surviving platform (the Microsoft EA expands, the ServiceNow contract expands, the Datadog account expands). Reporting gross savings without netting absorb cost overstates the impact. The countermeasure is to define savings as net savings (gross minus absorb minus migration) and to require the absorb cost commitment in writing before reporting savings.
Source 4: Vendor true ups at renewal
Vendor true ups at renewal happen when the next renewal price baseline is reset to the higher of (current run rate, original list with annual escalation). Vendors structure contracts to allow this reset, especially on multi year deals where the year one price is heavily discounted and the renewal proposal anchors on year three. The countermeasure is price protection caps that limit the renewal uplift to a defined percentage (typically 3 to 5 percent annual) and baseline drift audit that catches the reset before signature. Microsoft EA price protection is the model clause; SAP, Salesforce, ServiceNow, and Workday all allow comparable structures in negotiated contracts.
Download the savings methodology kit
Get the full savings methodology pack with baseline definitions, savings category rules, calculation formulas, and the audit workbook.
Baseline definition
The baseline is the comparison point. A bad baseline produces unreliable savings regardless of the rest of the methodology. The 198 panel shows three common baseline definitions in use. Baseline A is vendor opening proposal: the gap between the vendor's first proposal and the signed contract. Baseline B is prior run rate: the gap between the prior contract's annual cost and the new contract's annual cost. Baseline C is normalized prior run rate: the prior run rate adjusted for inflation, scope drift, and category mix changes. Top quartile programs use Baseline C with Baseline B as the simpler primary report.
The Baseline A approach is theater. It reports savings on every deal because the vendor opening proposal always exceeds the signed contract by definition. A deal that closes 6 percent above prior run rate still reports 8 percent savings if the opening proposal was 14 percent above. The CFO does not see those savings in the budget; the budget is 6 percent worse. Baseline A is the largest single source of methodology error in the 198 panel.
Baseline mechanics by deal type
| Deal Type | Primary Baseline | Adjustments |
|---|---|---|
| Tier 1 renewal | Prior run rate normalized for scope and term | Strip out scope expansion; normalize term length |
| New procurement | Vendor proposal benchmark adjusted to deal size | Use external benchmark, not internal vendor list price |
| Consolidation deal | Sum of eliminated vendor costs minus absorb cost | Net out migration cost over realization period |
| Cloud commit | On demand pricing for committed usage | Adjust for drift period and committed usage realization |
| Cost avoidance | Reported separately from savings | Never combined with negotiated savings in headline |
Savings categories
The savings methodology defines which categories count. Top quartile programs use a five category set. Category 1 is hard price reduction: unit price decrease on the same scope. Category 2 is uplift avoidance: difference between vendor opening uplift and realized uplift, when the realized uplift is greater than zero. Category 3 is bundle conversion: value of bundled scope that the sourcing team converted into commercial savings. Category 4 is term value: value extracted through contract terms (price protection caps, scope caps, termination rights) that reduces future risk. Category 5 is cost avoidance: future spend not committed because of negotiation or consolidation.
The five categories must report separately. Mixing categories produces unauditable headline savings. The 198 panel shows that programs reporting a single combined savings number have median 14 to 22 percent overstatement in audit. Programs reporting the five categories separately have median 4 to 8 percent overstatement, recoverable through methodology refresh.
The audit process
The audit process is the rule that validates reported savings against actual budget impact. The audit runs on a quarterly cadence for Tier 1 and Tier 2 deals and on an annual cadence for Tier 3. The auditor is independent from the sourcing team and reports to finance, typically the controller's office or a procurement center of excellence. The audit compares the reported savings line by line to the budget delta on the same vendor over the same period. Variances above a defined threshold (typically 5 percent) get root cause analysis and methodology refresh.
| Audit Step | Frequency | Owner |
|---|---|---|
| 1. Pull reported savings register | Quarterly | Sourcing reporting |
| 2. Pull budget delta on same vendor | Quarterly | FP&A |
| 3. Reconcile and variance analysis | Quarterly | Procurement CoE or controller |
| 4. Root cause on variances > 5% | Quarterly | Procurement CoE |
| 5. Methodology refresh | Annual | Head of sourcing + CFO |
Build your audit process
Send your current savings register format. We design the audit process, define variance thresholds, and provide the reconciliation template in 72 hours.
Compensation linkage
Compensation linkage is the rule that ties variable pay to savings outcomes. The most common mistake is tying compensation to reported savings without realization audit. The sourcing team learns to report savings that do not arrive. The fix is to tie compensation to a three element combination: gross negotiated savings (60 to 70 percent weight), realization rate from audit (15 to 25 percent weight), and contract compliance (10 to 15 percent weight). The realization rate weight ensures that overreporting produces a compensation penalty downstream. The contract compliance weight ensures that the contract artifacts support the savings claims.
The 198 panel shows that programs with realization rate in compensation hit 92 to 98 percent realization. Programs with only gross savings in compensation hit 68 to 78 percent realization. The 20 to 30 percentage point gap is the compensation system effect. The compensation linkage takes 12 to 24 months to fully implement because the audit data has to mature before realization rate can be a fair compensation input, but the directional improvement begins in the first reporting cycle after announcement.
Reporting cadence and format
Top quartile programs report savings on a quarterly cadence with a defined format. The format is a five column table per deal. Column one: vendor and product family. Column two: deal date and term. Column three: savings by category (the five category set). Column four: reported savings (sum of categories). Column five: audited savings (from quarterly audit, lagged one quarter). The deal level table rolls up to a vendor level summary and a program level summary.
Programs that report in narrative form rather than table form produce audit gaps. The narrative format hides scope adjustments, double counts categories, and obscures which deals contributed which savings. Mature programs require the structured table format for any reporting that goes to finance or to the CFO.
How methodology connects to the KPI dashboard
The savings methodology produces the input to the savings realization KPI in the broader procurement KPI set. See the procurement KPI benchmark for the full KPI dashboard. The renewal calendar is the operational artifact that drives cycle adherence and cycle time: see the renewal calendar template. The negotiation playbook drives gross savings: see the renewal negotiation playbook. The categorization framework determines which deals run the full methodology rigor: see vendor categorization and ABM. The Tier 1 vendor approach is documented in Tier 1 vendor strategy. The vendor consolidation play that produces a distinct savings category set is vendor consolidation playbook. The team design that operates the methodology is IT sourcing team org design. For broader benchmark categories see the benchmarks hub, the vendor index, and the glossary hub.
Frequently asked questions
What is IT sourcing savings methodology?
The documented set of rules that defines what counts as savings, how savings are calculated, how savings are reported, and how savings are audited against budget. A complete methodology covers six elements: baseline definition, savings categories, calculation formulas, reporting cadence, audit process, and compensation linkage.
What is the typical gap between reported and realized savings?
Across our 198 program panel, median realization is 72 to 84 cents per reported dollar. Top quartile programs hit 92 to 98 cents. The 16 to 24 percentage point gap is the difference between savings the sourcing team reports and savings the CFO sees in the budget.
What causes savings leakage?
Four sources. Mid term scope expansion (35 to 48 percent of leakage). Auto renewal escalation (20 to 30 percent). Migration and absorb costs (14 to 22 percent). Vendor true ups at the next renewal (10 to 18 percent). Each source has a defined countermeasure in the methodology.
How often should savings be audited?
Quarterly for Tier 1 and Tier 2 deals. Annual for Tier 3. The auditor is independent from the sourcing team and reports to finance. Variances above 5 percent get root cause analysis and feed methodology refresh.
Build your savings methodology
Send your current savings methodology documentation. We benchmark against the 198 panel and deliver a methodology refresh plan in 72 hours.
Benchmark your contract against modelled deal cohorts, or decode an agreement free in about a minute.
Decode a contract free →Benchmark your own contracts
Your free Vera AI trial opens the benchmarking database, 1,341 benchmarks across 1,140 vendors, plus the negotiation guides, playbooks, and talking points for your own renewals. No card needed, a corporate email is all it takes.