What Counts as Savings in a Gainshare Engagement (And What Doesn't)
What counts as savings in a gainshare engagement is the strict contractual difference between the vendor's first written proposal (the baseline) and the signed contract value on the same scope and term. It includes price reductions, term restructuring, escalator caps, and audit liability avoidance. It excludes scope changes the buyer initiated, savings driven by external regulation, future savings dependent on the buyer's execution, and benchmark comparisons. This article walks through the strict definition, the five exclusion categories, and the rationale that protects both buyer and advisor from disputed invoices.
The strict definition
Verified savings in a gainshare engagement is the dollar difference between two documents: the vendor's first written proposal for the renewal (the baseline), and the executed contract on the same scope and term (the signed value). Both are calculated on a total contract value basis. The difference is savings; 25% of savings is the gainshare fee. This is the same formula covered in how gainshare fees are calculated — but where that article focused on the math, this article focuses on the harder question: what items belong on each side of the calculation.
What counts as savings — five inclusions
1. Price reductions on the same scope
The vendor proposed Oracle Database EE at $47,500/processor; the signed agreement landed at $32,000/processor on the same processor count. The differential — $15,500 × processor count — is savings. This is the most obvious form. Every gainshare engagement starts here.
2. Term restructuring
The vendor proposed a 3-year term with 7% annual escalators; the signed agreement is a 3-year term with 3% annual escalators on the same starting price. The escalator differential over the term — typically 8–14% of TCV — is savings. The savings memo lists the year-by-year price points to show the math.
3. True-up clause improvements
The vendor proposed annual true-ups at list price; the signed agreement includes true-ups at 75% of list for the duration of the term. If true-ups are reasonably forecastable, the savings on those true-ups counts. If they are speculative, they don't. The savings memo annotates the forecast basis.
4. Audit liability avoidance
In software audit defence engagements, avoided liability counts as savings — measured as the vendor's initial claim minus the final settlement value. A vendor claim of $4.8M settled at $1.1M produces $3.7M of avoided liability — a $925K gainshare fee. The savings memo references the vendor's audit demand letter as the equivalent of a baseline.
5. Cloud commit reductions
For AWS EDP, Azure MACC, Google Cloud CUD: a reduction in committed spend driven by negotiated terms counts. If the buyer brought a lower consumption forecast in and the vendor matched it, the differential against the original proposal is savings. If the lower forecast was already in the baseline, only further reductions count.
What does not count as savings — five exclusions
1. Scope reductions initiated by the buyer
The buyer enters the engagement having already decided to drop Salesforce Industries Cloud at renewal. The savings from not buying Industries Cloud is not gainshare savings — the buyer would have realised it regardless of whether NoSaveNoPay was engaged. The savings memo lists "buyer-initiated scope reduction" as an explicit exclusion.
2. Savings driven by external regulation
The vendor announces a global list-price reduction during the engagement that the buyer would have received as a renewing customer regardless of negotiation. The list-price differential is excluded. We bill only on the negotiation-driven differential beyond the public price change.
3. Future savings dependent on the buyer's execution
The buyer signs an AWS EDP that supports future migration to Graviton-based instances at 40% lower TCO. The Graviton savings are real, but they depend on the buyer's post-signature engineering execution — which is outside the negotiation. They are not counted in gainshare savings. Negotiated terms that enable the future savings count; the future savings themselves do not.
4. Comparison against benchmarks or "should-cost" numbers
Some advisory firms calculate savings against a benchmark database value, a "should-cost" model, or a market-rate index. NoSaveNoPay does not. The only valid baseline is the vendor's actual first written proposal. Benchmarks are useful negotiation inputs; they are not valid savings baselines because they are not what the buyer would have paid without the engagement.
5. Pricing reductions on items the buyer was dropping anyway
The vendor's baseline included a $200K module the buyer had already decided to terminate. The vendor "reduces" the module to $0 during negotiation. This is not savings — the buyer was going to drop it, the vendor's "reduction" is a no-cost concession. The savings memo lists the dropped module and the rationale for exclusion.
Edge cases the savings memo handles
| Situation | Counts as savings? | Rationale |
|---|---|---|
| Vendor reduces escalator from 7% to 3% | Yes | Negotiation-driven term improvement on existing scope |
| Buyer drops 200 seats before negotiation | No | Buyer-initiated scope reduction |
| Vendor announces global 10% list price cut | Differential only | External event; only the additional negotiated reduction counts |
| Vendor offers free Copilot trial in proposal | If priced in baseline, then yes | If the proposal showed Copilot at list, removing it from contract value is savings |
| Avoided audit penalty | Yes | Demand letter is equivalent of baseline; settlement is signed value |
| Future Graviton migration savings | No | Depends on buyer's post-signature execution |
| Multi-year escalator cap saves $1.4M in year 3 | Yes | Counted in TCV; the year 3 saving is part of total contract savings |
| Vendor refunds prior-year overpayment | No | Prior-period correction, not negotiation-driven |
How disputes get resolved
The savings memo is the single source of truth. If the buyer's CFO disputes any specific calculation line, the disputed line is removed from the savings number — and the engagement closes at the lower figure. In rare cases this means the entire engagement closes at $0 of fee. We accept that outcome rather than litigate the savings number, because the contract integrity is worth more than any individual invoice.
In four years of engagements, full-dispute closures have happened twice. Both times the buyer's CFO disputed an exclusion category we considered legitimate, and both times we accepted the closure rather than push back. The model only works if the buyer feels the math is theirs.
Why the discipline matters
The risk-free promise depends on the savings number being defensible. If the savings memo includes items the buyer is uncomfortable with — items that feel like the advisor "found" savings rather than "produced" savings — the buyer rightly disputes the invoice and the model collapses. The strict exclusion rules above exist to ensure every savings dollar on the memo is defensible to anyone — CFO, auditor, audit committee, or board. The full contractual frame is in risk-free software negotiation.
Related reading from the gainshare series
- How gainshare fees are calculated — the math.
- Risk-free software negotiation — the contract clauses.
- Gainshare vs fixed-fee advisory — the model comparison.
- Gainshare engagement letter template — the SOW.
- Gainshare vs hourly consulting — for advisors who bill the clock.
Services that most commonly use this savings definition: Oracle, Microsoft, SAP, Salesforce, AWS, ServiceNow, Workday, IBM, audit defence, and multi-vendor engagements.
Defensible savings, defensible fee
Send us your next renewal and we will walk through the savings definition before any signature. You see exactly which items will count, which won't, and what your CFO will be asked to countersign — before the engagement begins.
Get a Free Estimate → See the SOWFrequently asked questions
What counts as savings in a gainshare engagement?
Savings is the difference between the vendor's first written proposal (baseline) and the signed contract value on the same scope and term. It includes price reductions, term restructuring, escalator caps, true-up clause improvements, and any other commercial movement that reduces total contract value. It does not include scope changes initiated by the buyer or savings achieved independent of the negotiation.
What doesn't count as savings?
Five categories are excluded. (1) Scope reductions the buyer initiated before negotiation. (2) Savings driven by regulation or external events. (3) Future savings dependent on the buyer's execution. (4) Comparisons against benchmarks rather than the actual vendor proposal. (5) Pricing reductions on items the buyer was going to drop regardless of negotiation. Each exclusion is documented in the savings memo.
How are multi-year savings calculated?
Savings is measured over the term of the new agreement. A 3-year contract with $9M baseline and $6M signed value produces $3M in savings. The gainshare fee is calculated once against total contract savings; payment is net 30 from invoice issued after the savings memo countersignature.
What if the vendor lowers prices mid-engagement for unrelated reasons?
If a vendor announces a global list-price reduction during the engagement that the buyer would have received regardless, the differential is excluded from savings. The savings memo annotates this. We document the original proposal price, the announced list change, and bill only on the negotiation-driven differential beyond the public price change.
Does cloud commit reduction count as savings?
Reductions in committed spend (AWS EDP, Azure MACC, GCP CUD) count as savings against the baseline commitment if the reduction is driven by negotiated terms, not by lowered consumption forecasts the buyer brought in. Migration-driven future savings — e.g., Graviton refactoring — are excluded because they depend on the buyer's post-signature execution.
What about avoided audit penalties?
In audit defence engagements, avoided liability counts as savings — measured as the vendor's initial claim minus the final settlement value. The buyer's CFO and audit defence lead countersign the savings memo. NoSaveNoPay's standard gainshare rate of 25% applies to verified avoided liability the same way it applies to negotiated renewal savings.
Does removing shelfware count?
Removing licences the buyer was never going to renew does not count. Removing licences the vendor was proposing to roll forward in the baseline does count, because the baseline included them. The distinction is whether the licence was in the vendor's first written proposal — if yes, removal is savings; if no, it was already excluded.
How do disputed savings get resolved?
The savings memo is the single source of truth. If the buyer's CFO disputes a calculation, the disputed line item is removed from the savings number and the engagement closes at the lower figure — or, in rare cases, closes with no fee. Disputes are extremely rare because the baseline document is the vendor's own proposal.