Success fee cloud optimization: define how savings are measured
Published and reviewed: 1 October 2026
Get a quote for my projectA success fee ties the provider's pay to a measured saving. It only works if both sides can measure the same thing, and most disputes come from definitions written too loosely at signature. These are the clauses worth negotiating before any work starts.

On this page
- Four terms that decide whether the fee is fair
- Realized versus avoided
- Commitments: the clause most often missed
- What counts toward the fee: decide each case in the contract
- Reversal, duration and audit terms
- Incentives and guardrails
- Questions for bidders
- Official sources
- Success fee questions from finance and procurement
Four terms that decide whether the fee is fair
- Baseline: the period and method used to say what the bill would have been. Fix the period, the cost type (billed, amortized, net) and how volume growth is handled.
- Eligible actions: the list of changes that count, with the date each one was approved. Savings from projects your team had already planned are excluded by default.
- Fee base: gross reduction, or reduction net of offsets such as extra storage and the one-time cost of making the change.
- Term: how many months each saving is counted, and whether the fee is paid monthly as savings materialize or in one payment.
Realized versus avoided
A realized saving shows up in the invoice after a change. Avoided cost is spend that never happened, such as a deployment sized down before launch or a service blocked from provisioning, and it can only be estimated against a counterfactual. The FinOps KPIs and Benchmarking capability asks for documented counterfactuals and post-action validation, which is the discipline a fee clause has to encode.
The safest structure pays on realized savings only. If avoidance counts, define its method in an annex, cap its share of the fee and forbid counting the same opportunity under both headings.
Commitments: the clause most often missed
Savings Plans, Reserved Instances and Google Cloud committed use discounts create a discount and an obligation at the same moment. AWS Savings Plans run for one or three years (Database Savings Plans for one year only) and can be returned only within seven days of purchase, in the same calendar month, for an hourly commitment of $100 or less and within a quota. Google Cloud's documentation says its commitments cannot be cancelled. A provider paid on the projected saving at purchase is therefore paid before the risk is known.
- Base the fee on the effective savings rate measured month by month, net of unused commitment. The FinOps Foundation defines it as savings generated divided by on-demand equivalent spend.
- Keep the purchase decision and signature with your team. The provider recommends and shows the downside case.
- Require utilization and coverage reports from the same data for the whole commitment term, or until the fee term ends.

What counts toward the fee: decide each case in the contract
| Situation | Suggested treatment |
|---|---|
| Idle resource removed with owner sign-off, billing drop visible | Counts, from the month after removal |
| Instance resized, then resized back for performance | Counts only for the months the smaller size ran |
| Savings Plan bought on the provider's recommendation | Counts as effective savings net of unused commitment, month by month |
| Usage fell because a product was retired or customers left | Does not count |
| Vendor list price falls, or your own discount changes | Does not count, unless the provider negotiated it under the scope |
| Tagging, dashboards and reporting improvements | No fee base. Price them as a fixed fee |
| Planned deployment cancelled after the provider's advice | Only if the avoidance method is already in the annex |
Reversal, duration and audit terms
- If a change is reverted, for performance or by a team decision, the saving stops counting from that date, and any fee already paid on it is credited.
- A fixed observation period per action, with a written check at its end.
- A shared ledger of actions in which each saving is traceable to a change record and to billing data.
- Audit rights over the ledger and the export queries, exercised by your finance team or a person you name.
- A dispute path with a named person on each side and a time limit for answers.
- A cap on the total fee and, if there is a minimum fee, a clear statement of what it covers.
Incentives and guardrails
A fee on counted savings pushes a provider toward actions that are easy to count and quick to show. That can mean commitments over architecture work, or aggressive rightsizing over reliability. Add guardrails: no change without the resource owner's approval, performance and availability targets that override a saving, and a review of any recommendation that raises your contractual obligations. Include your own cost in the comparison: a low fee can still require many engineering days.
Want a fee clause checked against your own situation? Get support on my project.
Questions for bidders
- How do you define the baseline, and what happens when volume changes during the term?
- Which of your past recommendations were reversed, and how did your fee treat them? Ask for the clause, not a client name.
- How do you treat commitments, and who bears the unused part?
- What data access do you need to verify savings, and for how long after the last action?
- What is the fee if no eligible saving is found, and what work do you deliver in that case?
Official sources
Official documentation used for this page.
- www.finops.org/framework/capabilities/kpis-benchmarking/
- www.finops.org/framework/capabilities/rate-optimization/
- www.finops.org/wg/how-to-calculate-effective-savings-rate-esr/
- docs.aws.amazon.com/savingsplans/latest/userguide/return-sp.html
- docs.cloud.google.com/docs/cuds-spend-based
- docs.cloud.google.com/compute/docs/instances/signing-up-committed-use-discounts
Success fee questions from finance and procurement
Is a success fee automatically lower risk?
It changes the incentives. Baseline ambiguity, minimum fees, commitment obligations and internal effort can still create risk. Read the contract and test the downside cases.
Can avoided costs count toward the fee?
Only under an agreed definition and evidence method. Keep them apart from observed bill savings so the same opportunity is never counted twice.
Who should sign commitment purchases?
Your team. The provider can recommend and model the downside, but the obligation is yours, so the decision and the signature should be too.
Continue your review
- FinOps consulting: cloud cost review and implementation scope
- Request a scoped FinOps quote
- How your request is handled: from enquiry to proposal
- FinOps KPIs: prove realized savings and business value
- Cloud cost audit pricing: scope, deliverables and exclusions
- Cloud cost optimization RFP: compare proposals side by side
Launch my project
Share the decision you need to make and get a quote scoped to it.
Launch my project