How Gainshare Fees Are Calculated: The Math Behind 25% of Verified Savings
How is gainshare calculated? The formula is two lines long: savings equals baseline minus signed contract value; fee equals savings times 25%. The complexity is not in the math — it is in defining baseline, defining signed contract value, and verifying both to a CFO's countersignature. This article walks through the formula in detail, then runs three real-world enterprise software examples — Oracle, Microsoft EA, and AWS EDP — with the actual numbers and the actual gainshare invoices that resulted.
The formula in two lines
Gainshare fee = Savings × 25%
That is the entire commercial calculation. Everything else in this article is about what counts as baseline, what counts as signed contract value, and how the savings memo verifies both. For the contract clauses that make the calculation enforceable, see the risk-free software negotiation article; for the larger conceptual frame, the gainshare pillar.
Definition: baseline
The baseline is the vendor's first written proposal for the renewal or new purchase. Not a benchmark, not a database value, and not a number NoSaveNoPay invents. The document is the vendor's own pricing letter — the same letter the buyer would have used to authorise the renewal in-house, dated and on vendor letterhead. Buyer, advisor, and the buyer's CFO countersign the proposal as the savings baseline before any negotiation begins. This is the safeguard that prevents baseline inflation and makes the savings figure auditable. The gainshare definition and success fee entries cover the related contract vocabulary.
Three baseline edge cases worth knowing:
- Vendor has not yet issued a proposal. We wait. If timing requires action, we work from the prior contract's annualised cost grown by the vendor's published price increase — but that fallback is documented in the engagement letter, not assumed.
- Vendor proposal includes "list price" framing. The proposal itself is the baseline, including any list-price reference. We do not negotiate the baseline downward via methodology — the baseline is the document the vendor delivered.
- Multiple proposals during negotiation. Only the first written proposal counts. Later vendor counters are not new baselines; they are progress markers in the negotiation.
Definition: signed contract value
The signed contract value is the total commercial value of the signed agreement over its full term, calculated on the same basis as the baseline. If the baseline includes hosting, support, escalators, and overage true-ups, the signed value includes the same. If the baseline is over a 36-month term, the signed value is over a 36-month term. Apples to apples.
For multi-year contracts with annual escalators, both baseline and signed value are calculated on a total contract value (TCV) basis including all scheduled increases. Reducing escalators — a common gainshare move — flows directly through to the savings number. A baseline with 7% annual escalators and a signed agreement with 3% escalators on the same starting price still produces meaningful savings via the escalator differential.
Definition: verified savings
Savings becomes "verified" when the buyer's CFO countersigns the savings memo. The memo lists:
- The baseline document reference (vendor's first proposal).
- The signed contract reference (executed agreement).
- Total contract value of each, on the same basis.
- Savings calculation, by line item where line items exist.
- Gainshare fee = savings × 25%.
- Payment terms — net 30 from invoice.
The CFO countersignature is the gating event. No invoice is issued until the memo is signed. If the savings cannot be reconciled to the CFO's satisfaction, the engagement closes with no fee. This protects both parties: the buyer is never asked to pay for savings they cannot verify; the advisor is never paid for savings the buyer disputes.
Worked example 1 — Oracle ULA renewal
A US mid-cap manufacturer was renewing a 3-year Oracle Unlimited Licence Agreement. Oracle's first written proposal landed at $6.4M total contract value over 36 months. Through usage diligence, server-rightsizing analysis, and a multi-quarter negotiation, the renewal signed at $4.1M.
| Baseline (Oracle's first proposal) | $6,400,000 |
| Signed contract value (3-year TCV) | $4,100,000 |
| Verified savings | $2,300,000 |
| Gainshare fee (25%) | $575,000 |
| Net buyer outcome | $1,725,000 |
The buyer kept $1.725M of savings against a $575K gainshare invoice. Cash impact: net positive in month one of the new contract, by an order of magnitude. For service detail on this category of engagement, see Oracle negotiation.
Worked example 2 — Microsoft Enterprise Agreement renewal
A European financial services firm with 14,000 seats was renewing a 3-year Microsoft Enterprise Agreement that included E5 licensing, Azure consumption commits, and Copilot rollout pricing. Microsoft's first written proposal totalled $18.3M TCV. The signed agreement landed at $13.1M after Copilot pilot restructuring, MACC re-tiering, and term-flexibility moves.
| Baseline (Microsoft's first proposal) | $18,300,000 |
| Signed contract value (3-year TCV) | $13,100,000 |
| Verified savings | $5,200,000 |
| Gainshare fee (25%) | $1,300,000 |
| Net buyer outcome | $3,900,000 |
The gainshare fee on this engagement is the largest in our history — and the buyer was actively thrilled with it, because they kept $3.9M they would not otherwise have kept. The CFO summary memo recorded "best-priced renewal in 12 years of the EA programme." Service detail: Microsoft negotiation.
Worked example 3 — AWS Enterprise Discount Program
A US technology firm was committing to a 3-year AWS Enterprise Discount Program covering EC2, S3, RDS, and Lambda workloads. AWS's first proposal called for a $14M commit over three years for a 13% baseline discount. The signed EDP landed at $11M with a 21% effective blended discount after Graviton migration analysis and consumption profile restructuring.
| Baseline (AWS first proposal — committed spend × list) | $14,000,000 |
| Signed EDP commit value | $11,000,000 |
| Verified savings | $3,000,000 |
| Gainshare fee (25%) | $750,000 |
| Net buyer outcome | $2,250,000 |
Cloud commit engagements have an additional layer — workload migration recommendations that affect the savings calculation. We discount Graviton-driven future savings from the gainshare base because they accrue after signature and depend on the buyer's execution, not the contract. Service detail: AWS negotiation and cloud cost negotiation.
What does not count as savings
The integrity of the fee depends on disciplined exclusion of items that aren't really savings. We do not count:
- Scope reductions initiated by the buyer (the buyer dropped a module before negotiation began).
- Savings driven by external regulation rather than negotiation (a vendor mandated price cut, for example).
- Future savings that depend on the buyer's execution (e.g., committed-spend savings that require workload migration).
- Comparison against a "benchmark" or "should-cost" number rather than the vendor's actual proposal.
The companion article What Counts as Savings in a Gainshare Engagement covers this list in detail with worked exclusion cases.
Tiered pricing for very large engagements
For multi-vendor portfolio engagements where total savings expectation exceeds $5M, NoSaveNoPay sometimes uses a tiered rate: 25% on the first $5M of savings, 20% on the next $5M, and 15% above $10M. This is a commercial conversation, not a policy. The 25% flat rate remains the default for single-vendor renewals because simplicity beats optimisation at most engagement sizes.
Related reading from the gainshare series
- Gainshare vs fixed-fee advisory — the structural comparison.
- Gainshare vs hourly consulting — why hourly loses on software deals.
- Gainshare vs retainer model — for CFOs.
- What counts as savings — exclusion cases.
- Risk-free software negotiation — contract clauses.
- Gainshare engagement letter template — the SOW.
Run the math on your renewal
Send us the vendor name, the contract type, and the renewal window. We will return a free savings estimate showing the expected baseline, the expected signed value, and the expected gainshare fee — using the same formula above. No commitment. No fee until savings are countersigned.
Get a Free Estimate → Use the CalculatorFrequently asked questions
How is the gainshare fee calculated?
Gainshare fee = (baseline − signed contract value) × gainshare percentage. NoSaveNoPay's standard percentage is 25%. The baseline is the vendor's first written proposal for the renewal or new purchase. The signed contract value is the total commercial value of the signed agreement over its full term. Savings is the difference; the fee is 25% of that difference.
How is the baseline determined?
The baseline is the vendor's first written proposal for the renewal or new purchase. It is not a benchmark, not a database value, and not a number the advisor invents. Buyer, advisor, and the buyer's CFO countersign the baseline before negotiation begins. This is the safeguard that prevents baseline inflation and makes the savings figure auditable.
What if the contract is multi-year?
Savings is measured over the term of the new agreement. A 3-year contract with a baseline of $9M and a signed value of $6M produces $3M of savings — a $750K gainshare fee at 25%. Annualised, that is $1M of savings per year against a $250K annualised fee. The full fee is invoiced once, 30–60 days after signature, against the savings memo.
What if pricing escalates over the term?
Both the baseline and the signed value are calculated on a total contract value basis including all annual escalators. If the vendor's first proposal included 7% annual increases and the signed agreement caps escalators at 3%, the differential flows through to the savings calculation. Reducing escalators is one of the highest-value moves in any gainshare engagement.
How are savings verified?
The savings memo, countersigned by the buyer's CFO, lists the baseline document, the signed contract reference, the savings calculation by line item, and the gainshare fee. The memo is the verification artefact and the audit trail. No invoice is issued until the CFO signs the memo. If the savings cannot be reconciled to the CFO's satisfaction, the engagement closes with no fee.
Can the gainshare percentage be negotiated below 25%?
For very large engagements — multi-vendor portfolio engagements with eight-figure savings expectations — the percentage can sometimes be reduced via a tiered structure (25% on the first $5M, 20% above). For standard single-vendor engagements, 25% is the published rate and remains the simplest commercial conversation.
What happens if the buyer adds scope mid-negotiation?
Added scope is excluded from the savings calculation. If the buyer adds a new module worth $400K during negotiation, that $400K is not counted as a baseline increase or a savings decrease. We bill on the original scope's signed value compared to the original scope's baseline. Scope expansion is handled separately if the buyer wants negotiation support on it.
When is the gainshare fee actually paid?
Net 30 from invoice. The invoice is issued only after the CFO countersigns the savings memo, which typically happens 7–30 days after the signed contract. From contract signature to fee payment is therefore usually 30–60 days. The buyer realises savings over the full contract term; the fee is paid once, upfront, out of the realised savings.