.png)
AWS
Microsoft Azure
Google Cloud
Key takeaways
1
Measure the vendor’s additional savings against your existing Azure rates, discounts, and optimization process. Keep savings you already receive visible in the comparison.
2
A hypothetical 20% fee on $200,000 in incremental savings leaves $160,000 after the fee. Another $10,000 in added costs reduces the retained benefit to $150,000.
3
Confirm the fee base, unused commitment costs, reconciliation process, and exit obligations before signing. A forecast alone does not establish what you will retain.
An Azure optimization proposal puts a savings estimate in front of you. Before signing, decide whether the service will improve your budget enough to justify the work and financial obligations it brings.
Savings can come from changing how resources are used, improving the rates paid for them, or both. The worked example below uses commitment optimization, but the same evaluation applies to rightsizing, scheduling, and removing idle resources.
Your proposal may produce a different result because the fee can apply to a different savings base. Calculate the charge in dollars, then deduct other added costs to determine the benefit your business retains.
Then compare that baseline with cloud cost under the proposed service, before its fee:
Savings can come from changing how resources are used, improving the rates paid for them, or both. The worked example below uses commitment optimization, but the same evaluation applies to rightsizing, scheduling, and removing idle resources.
Short Answer
If a vendor generates $200,000 in additional Azure savings and charges 20% of that amount, you keep $160,000 after the vendor fee. The 20% rate is illustrative, not a Usage.ai price quote.Your proposal may produce a different result because the fee can apply to a different savings base. Calculate the charge in dollars, then deduct other added costs to determine the benefit your business retains.
Establish the Azure Savings the Vendor Actually Adds
Start with what your environment would reasonably cost without the new vendor during the evaluation period. Include negotiated rates, existing reservations or savings plans, applicable licensing benefits, and optimization work your team would perform anyway.Then compare that baseline with cloud cost under the proposed service, before its fee:
Incremental cloud savings = cost without the vendor − cost with the vendor.
A comparison against public retail rates can describe a discount, but it can overstate the additional value for a business already paying less. Ask the vendor to separate existing benefits from improvements attributable to its service.
Keep the period, accounts, services, and currency consistent. For commitment optimization, compare the same usage under both purchasing approaches. For rightsizing or scheduling, assess equivalent business output and service requirements, since reducing resource consumption is part of the change.
When a proposal combines techniques, calculate their combined effect. Rightsizing can reduce the usage available for commitment discounts, so adding two standalone savings estimates can overstate the total. Ask for one reconciled outcome rather than summing overlapping recommendations.
Do not treat a lower invoice as proof of vendor impact. Falling demand, an unrelated migration, or a negotiated price change could also reduce the bill. Conversely, growth can increase total spend even while optimization improves costs.
Also distinguish avoided future expenditure from a reduction in current expenditure. Both can matter to Finance, but they answer different budget questions. This baseline gives the fee calculation a defensible starting point.
Keep the period, accounts, services, and currency consistent. For commitment optimization, compare the same usage under both purchasing approaches. For rightsizing or scheduling, assess equivalent business output and service requirements, since reducing resource consumption is part of the change.
When a proposal combines techniques, calculate their combined effect. Rightsizing can reduce the usage available for commitment discounts, so adding two standalone savings estimates can overstate the total. Ask for one reconciled outcome rather than summing overlapping recommendations.
Do not treat a lower invoice as proof of vendor impact. Falling demand, an unrelated migration, or a negotiated price change could also reduce the bill. Conversely, growth can increase total spend even while optimization improves costs.
Also distinguish avoided future expenditure from a reduction in current expenditure. Both can matter to Finance, but they answer different budget questions. This baseline gives the fee calculation a defensible starting point.
Check Which Savings Dollars the Fee Applies To
A fee percentage is incomplete without its denominator.
Vendor fee = agreed billable savings × fee percentage, subject to any minimums or additional charges.
The billable savings defined in the agreement may differ from the incremental savings in your investment case. Confirm whether the fee includes inherited commitment discounts, benefits generated by your team, or only improvements attributable to the vendor.
For commitments, ask whether the calculation nets unused costs against savings on utilized capacity. Charging for successful discounts while excluding related losses produces a different result from charging on the overall benefit. The proposal must make that treatment explicit.
Check for minimum monthly charges, separate implementation fees, tiers, and changes at renewal. A savings-based headline does not describe every commercial term.
Our guide to comparing savings-based pricing offers explores why the fee base can matter more than the advertised percentage.
Illustrative assumptions: The matched baseline is $1 million after existing rates and benefits. Cloud cost with the new optimization is $800,000, including the month’s allocated commitment costs, used and unused. The hypothetical vendor charges 20% of incremental savings. Other incremental costs total $10,000 for that month. No Cashback or other recovery is assumed.
These figures are a worked calculation, not a customer result, Usage.ai price quote, or forecast of achievable savings. Taxes and unrelated credits are excluded consistently from both cloud-cost figures.
For example, the assumed $10,000 could include $6,000 in one-time implementation expense and $4,000 in additional recurring reporting costs. That distinction matters when extending this month’s calculation into an annual business case: the implementation expense should not recur automatically.
For commitments, ask whether the calculation nets unused costs against savings on utilized capacity. Charging for successful discounts while excluding related losses produces a different result from charging on the overall benefit. The proposal must make that treatment explicit.
Check for minimum monthly charges, separate implementation fees, tiers, and changes at renewal. A savings-based headline does not describe every commercial term.
Our guide to comparing savings-based pricing offers explores why the fee base can matter more than the advertised percentage.
Worked Example: What You Keep From $200,000
Consider an enterprise evaluating additional Azure commitment management for a completed month. Azure savings plans for compute do not discount software, networking, or storage charges, so do not attribute savings on those charges to the plan.Illustrative assumptions: The matched baseline is $1 million after existing rates and benefits. Cloud cost with the new optimization is $800,000, including the month’s allocated commitment costs, used and unused. The hypothetical vendor charges 20% of incremental savings. Other incremental costs total $10,000 for that month. No Cashback or other recovery is assumed.
These figures are a worked calculation, not a customer result, Usage.ai price quote, or forecast of achievable savings. Taxes and unrelated credits are excluded consistently from both cloud-cost figures.
For example, the assumed $10,000 could include $6,000 in one-time implementation expense and $4,000 in additional recurring reporting costs. That distinction matters when extending this month’s calculation into an annual business case: the implementation expense should not recur automatically.
| Monthly measure | Calculation | Amount |
|---|---|---|
| Azure cost without the vendor | Matched baseline | $1,000,000 |
| Azure cost with optimization, before vendor fee | Includes used and unused commitment costs | $800,000 |
| Incremental cloud savings | $1,000,000 − $800,000 | $200,000 |
| Vendor fee | $200,000 × 20% | $40,000 |
| Savings retained after vendor fee | $200,000 − $40,000 | $160,000 |
| Other incremental costs | Assumed for this month | $10,000 |
| Net retained benefit | $160,000 − $10,000 | $150,000 |
The business retains 80% of incremental savings after the vendor fee, or 75% after other added costs. The fully loaded benefit is 15% of the $1 million baseline. These percentages use different denominators, so label them accordingly in the ROI review.
The fee reduces the benefit by $40,000, but does not erase it in this example. Combined cloud cost, vendor fee, and other costs total $850,000 against the $1 million counterfactual.
To see how fee negotiations affect the outcome, hold everything else constant:
The fee reduces the benefit by $40,000, but does not erase it in this example. Combined cloud cost, vendor fee, and other costs total $850,000 against the $1 million counterfactual.
To see how fee negotiations affect the outcome, hold everything else constant:
| Illustrative fee on the same $200,000 base | Vendor fee | Retained after fee, before other costs |
|---|---|---|
| 15% | $30,000 | $170,000 |
| 20% | $40,000 | $160,000 |
| 30% | $60,000 | $140,000 |
These rates are sensitivity assumptions, not market averages. Compare actual offers using their actual fee bases. A lower rate applied to a broader savings pool can still create a larger invoice.
Unused commitments: Microsoft’s EA savings-plan savings calculation subtracts unused savings-plan cost from savings on utilized usage. If unused cost is already included in your optimized cloud-cost figure, do not deduct it again.
Upfront payments: Azure’s actual and amortized cost views serve different purposes. Actual cost records purchase charges; amortized cost spreads commitment cost over its term and allocates used and unused portions.
Use amortization for period economics and a separate cash schedule for treasury. Subtracting an upfront purchase and its amortization in the same benefit calculation double-counts the cost.
Implementation and internal work: Include additional integration, reporting, and operating costs. Show staff capacity separately from cash savings unless the proposal identifies an expense the business will actually avoid.
Recovery and enterprise obligations: Keep accrued protection separate from received cash and count it once. If you have a Microsoft Azure Consumption Commitment, assess how lower eligible spend affects progress toward any milestones and the remaining obligation. A consumption reduction may not create an equal near-term cash benefit.
Our broader cloud cost optimization ROI framework connects these costs to payback and ongoing value.
The evidence should include:
Account for Costs Beyond the Vendor Fee
Use the after-fee amount for pricing discussions and the fully loaded amount for investment approval. Other costs and settlement timing can change the financial case.Unused commitments: Microsoft’s EA savings-plan savings calculation subtracts unused savings-plan cost from savings on utilized usage. If unused cost is already included in your optimized cloud-cost figure, do not deduct it again.
Upfront payments: Azure’s actual and amortized cost views serve different purposes. Actual cost records purchase charges; amortized cost spreads commitment cost over its term and allocates used and unused portions.
Use amortization for period economics and a separate cash schedule for treasury. Subtracting an upfront purchase and its amortization in the same benefit calculation double-counts the cost.
Implementation and internal work: Include additional integration, reporting, and operating costs. Show staff capacity separately from cash savings unless the proposal identifies an expense the business will actually avoid.
Recovery and enterprise obligations: Keep accrued protection separate from received cash and count it once. If you have a Microsoft Azure Consumption Commitment, assess how lower eligible spend affects progress toward any milestones and the remaining obligation. A consumption reduction may not create an equal near-term cash benefit.
Our broader cloud cost optimization ROI framework connects these costs to payback and ongoing value.
Verify the Proposal Before You Sign
Ask the vendor for a reconciliation you can reproduce, with one forecast for approval and a completed-period calculation to validate realized results.The evidence should include:
Baseline: Scope, period, currency, existing discounts, and assumptions about work your team would complete without the service.
Cloud cost: Source exports and treatment of commitment purchases, amortization, unused value, and billing adjustments.
Fee: Billable savings categories, percentage, minimums, additional charges, and a sample invoice calculation.
Protection: Eligibility, exclusions, settlement method, timing, and treatment in both savings reporting and billing.
Exit: Notice requirements, final charges, continuing Azure commitments, and what happens to protection after termination.
Microsoft’s Cost Management data guidance explains that current-period charges can remain estimated until invoicing. Confirm when data is considered final and how subsequent adjustments are reconciled.
Stress-test lower usage as well as the expected case. Recalculate both the no-vendor baseline and optimized cost for each scenario; subtracting unused commitments from an unchanged baseline can misrepresent the outcome. Include only recoveries supported by the applicable agreement.
Assign an internal owner to check the vendor’s monthly calculation. The purchasing decision should require positive incremental benefit, an acceptable downside, and reporting Finance can validate.
Set your approval threshold before negotiating. Positive savings may still be insufficient if the implementation burden, payback period, or remaining commitment obligations exceed what the business is willing to accept.
Through our read-only Savings Test, we evaluate existing commitments and uncovered eligible usage before you enable purchasing. We model potential savings for review rather than treating the forecast as money already saved.
With your authorization, we purchase and manage supported Azure commitments without changing workloads. We report savings, our fee, and accrued Cashback separately, giving your team the inputs to reconcile the financial result.
With our Flex Insured Commitments, teams can access up to 65% savings from an eligible three-year Azure compute Savings Plan with none of the commitment risk.
For an eligible Flex Commitment, we provide Cashback for the qualifying difference when its cost exceeds equivalent pay-as-you-go usage. We pay eligible Cashback 90 days after it accrues under program terms. Our Cashback does not cancel the Azure purchase, and we do not automatically protect existing customer-owned commitments as Flex Commitments.
We charge an agreed percentage of realized savings from Flex Commitments, billed monthly in arrears after Azure billing data is finalized. Our illustrative 20% example above is not a price quote.
To apply this calculation to your Azure spend, book a demo with our team to review your existing commitments, potential additional savings, and the estimated amount you could keep after our fee.
Stress-test lower usage as well as the expected case. Recalculate both the no-vendor baseline and optimized cost for each scenario; subtracting unused commitments from an unchanged baseline can misrepresent the outcome. Include only recoveries supported by the applicable agreement.
Assign an internal owner to check the vendor’s monthly calculation. The purchasing decision should require positive incremental benefit, an acceptable downside, and reporting Finance can validate.
Set your approval threshold before negotiating. Positive savings may still be insufficient if the implementation burden, payback period, or remaining commitment obligations exceed what the business is willing to accept.
How We Approach Savings-Based Pricing at Usage.ai
We help you assess potential Azure commitment savings against your existing discounts, so you can judge the additional value our service could leave after fees and other added costs.Through our read-only Savings Test, we evaluate existing commitments and uncovered eligible usage before you enable purchasing. We model potential savings for review rather than treating the forecast as money already saved.
With your authorization, we purchase and manage supported Azure commitments without changing workloads. We report savings, our fee, and accrued Cashback separately, giving your team the inputs to reconcile the financial result.
With our Flex Insured Commitments, teams can access up to 65% savings from an eligible three-year Azure compute Savings Plan with none of the commitment risk.
For an eligible Flex Commitment, we provide Cashback for the qualifying difference when its cost exceeds equivalent pay-as-you-go usage. We pay eligible Cashback 90 days after it accrues under program terms. Our Cashback does not cancel the Azure purchase, and we do not automatically protect existing customer-owned commitments as Flex Commitments.
We charge an agreed percentage of realized savings from Flex Commitments, billed monthly in arrears after Azure billing data is finalized. Our illustrative 20% example above is not a price quote.
Final Verdict: Decide on the Savings You Retain
Approve the proposal based on additional value after fees and costs, with obligations you understand and evidence you can reconcile. The worked example leaves $160,000 after the vendor fee and $150,000 after other added costs; your outcome depends on your baseline and agreement.To apply this calculation to your Azure spend, book a demo with our team to review your existing commitments, potential additional savings, and the estimated amount you could keep after our fee.
Frequently asked questions
Is there a standard Azure optimization success fee?
Use the provider’s quote and agreement. A 15% fee would leave 85% only if it applies to the same incremental savings you are measuring, with no other charges. This is a conditional calculation, not a universal benchmark.
Do free Azure tools let us keep 100% of savings?
Microsoft Cost Management for Azure and Azure Advisor have no additional tool charge. That removes a vendor fee, but implementation, engineering time, and commitment costs still belong in the business case.
Can we treat projected annual savings as money already saved?
No. Annualizing a month assumes its economics repeat. Keep forecasts separate from realized results, account for one-time costs separately, and reconcile each period before reporting retained benefits.
Share
Facebook
X
LinkedIn
Reddit
