Calculator

Cloud Savings Opportunity Estimator

Estimate cloud run-rate savings from rightsizing, commitment discounts, storage optimization, and network and egress controls. Use conservative inputs and validate with billing trend after controls are installed.

Educational only. Validate with your billing system and engineering owners before committing to savings.

Processed in-browser. Nothing is stored.

Inputs

Required

Formatting only.

$

Required

Spend split

%

Estimated percent of cloud spend that is compute.

%

Estimated percent of cloud spend that is storage.

%

Estimated percent of cloud spend that is network and egress.

Commitment discounts

%

Percent of compute spend eligible to be covered by commitment discounts.

%

Average discount percent achieved on the covered compute spend.

Rightsizing and idle cleanup

%

Percent savings achievable on compute spend via rightsizing and idle cleanup.

Storage optimization

%

Percent savings on storage spend from cleanup and tiering.

Network and egress

%

Percent savings on network spend from routing, caching, and egress controls.

$

Cost to implement controls. Used for payback.

Used in memo output.

Optional context for stakeholders.

Assumptions

  • This is an estimate. Use conservative inputs and validate by cloud billing trend after controls are installed.
  • Savings levers can overlap. Keep assumptions conservative to avoid double counting.
  • Commitment savings depends on stable workloads and disciplined coverage management.
  • Rightsizing savings depends on tagging and ownership to sustain changes.

Fix validation errors to generate results.

Results

Enter inputs and click Generate.

How to use

1) Enter annual cloud spend and a simple spend split (compute, storage, network).

2) Enter conservative savings assumptions for each lever.

3) Generate results to view savings breakdown and payback.

4) Copy or download the memo and export a one-row CSV for Finance.

What results mean

- Rightsizing savings: savings from downsizing overprovisioned compute and removing idle instances.

- Commitment savings: savings from applying commitment discounts to the stable portion of compute.

- Storage savings: savings from cleanup and tiering.

- Network and egress savings: savings from routing, caching, and egress controls.

- Payback: implementation cost divided by ongoing monthly savings (if implementation cost is provided).

Common pitfalls

- Double counting: rightsizing and commitments can overlap; keep assumptions conservative.

- Bad spend splits: compute + storage + network cannot exceed 100 percent.

- Over-committing: commitment savings assumes stable workloads and disciplined coverage management.

- No ownership: savings do not stick without tagging and cost ownership.

Definitions

- Rightsizing: reducing overprovisioned resources to match actual usage.

- Commitment coverage: the percent of compute spend you can safely discount via commitments.

- Egress: data leaving the cloud provider network that often drives unexpected cost.

Change log

v1.0 (2026-01): Latest release