Skip to main content
Potential monthly savings adds up the monthly estimates on every open finding (one savings opportunity a scan found) for one cloud account. Use it to size the work in front of you, not as a promise of a smaller bill.

Where the number appears

Every Optimize page shows one account at a time. To switch, open the account menu next to the page title (it shows the current account’s name) and pick another. Totals use the account’s billing currency: USD on AWS and GCP, and the billing scope’s currency on Azure. There’s no savings total across accounts. To see them side by side, generate a Savings opportunities report with All accounts scope on Reports. On Findings, the summary follows the Service filter, so picking one service shows that service’s share. The Quick wins and Needs review cards, search, the effort and risk filters, and paging don’t change the summary, so the header stays stable while you browse. Each summary card on Findings also compares the current total with the total recorded when the last scan completed. In this line, “actions” means counted findings: The delta moves for any reason the total moves: new findings, findings you moved or marked, edited estimates, and lapsed snoozes. Run a new scan after your team ships changes, or after you dispute findings, since the agent re-checks disputed findings then. Re-scan on Overview and on Findings start the same account scan, and the comparison then measures against the total it records. See Refresh findings.

How estimates are calculated

During a scan, CloudThinker reads the account’s billed spend for each service and inspects the resources behind it with read-only commands. The permissions it uses are listed per provider: AWS, GCP, Azure. Each estimate comes from those measurements, not from a fixed rate card, and each finding’s write-up shows the arithmetic. For example, two idle NAT gateways billed at $33/mo each give a $66/mo estimate, with the gateway IDs and the measured traffic as evidence. The figures are illustrative. Check a finding’s evidence badge before you quote its number to finance. Verified is the one to quote; Inferred and Assumed leave something the scan didn’t read, so confirm that part yourself. See how to read a finding.

Which findings count

A finding counts toward the total only when all three conditions hold. See how to read a finding for how a scan picks a class and an evidence badge.
Disputed findings stay visible and flagged, but their savings leave the total. CloudThinker re-checks them first on the next scan. If your dispute was right, the agent archives the finding: it leaves the board and the total for good, without moving to a status column. Otherwise the evidence is refreshed and the Disputed mark stays until you select Clear mark.

Why it is an upper bound

Two findings can estimate savings against the same spend. Say a rightsizing finding saves $200/mo and a Savings Plan finding on the same compute saves $150/mo. After you rightsize, the plan covers a smaller footprint, so doing both saves less than $350. Optimize doesn’t flag overlapping findings for you. In practice:
  • Don’t subtract the total from the month-end forecast on the <Month> spend card on Overview (for example October spend). The forecast says where the bill is heading; the savings total says what open work might be worth.
  • Don’t report the total as realized savings or ROI. Optimize doesn’t measure savings after a change.
  • Before adding two estimates together, open both findings and check whether they touch the same resources.
  • Prioritize by class, effort, and risk, not by the dollar amount alone.

Keep the total accurate

Work findings off the total as your team decides on them. Each change updates the total for everyone, so the number is only as honest as the board. Findings covers how to move, mark, and edit a finding, and what each mark asks you for. Moving and editing need the workspace Developer role or higher, and marking a finding as expected, snoozed, or disputed needs Admin. Organization Owners and Admins hold workspace Admin in every workspace.
Optimize keeps no record of realized savings. Before you move a finding to Implemented, note its estimate in your ticket or select Download PDF on Findings. Then confirm the real reduction as shown in Prove savings after a change.

Send findings to your workflow

For a file to attach to a review, select Download PDF on Findings or on Cost Health. For a written report now or on a schedule, use Reports. For a recurring summary, use one of the two Optimize digests. Turn email, Slack, Microsoft Teams, or Google Chat on or off per digest on Notifications. Optimize has no built-in button that opens a ticket or a pull request from a finding, and no CSV export of findings.

Prove savings after a change

Optimize reports potential savings only. To show a real reduction:
  1. Wait for a complete billing month after the change. A partial month understates the result, and provider billing data can lag (AWS Cost Explorer by 24 to 48 hours).
  2. In Optimize → Cost Explorer, compare the last full month before the change with the first full month after it. Group by takes one dimension at a time: start with Service to find the service that dropped, then switch to Region to see where it landed.
Optimize’s Cost Explorer doesn’t break spend down by resource or tag. To isolate one resource, use your provider’s own tools: resource-level AWS Cost Explorer or the Cost and Usage Report, the BigQuery billing export on GCP, or Azure Cost Management.

Troubleshooting

Optimize troubleshooting lists every savings-total symptom with its cause, check, and fix. These two need more detail.
Cause: the total is shared across the workspace, so anyone’s decision moves it. It goes up when a snooze date passes, a teammate clears a mark, a teammate moves a finding from Implemented or Ignored back to Pending or In Progress, or a teammate raises an edited estimate. It goes down when a teammate moves a finding to Implemented or Ignored, marks it, or lowers its estimate, and when a scan upholds a dispute.Check: open the finding. Its Activity tab lists status changes and edits, and a marked finding shows who set the mark and when. Select the hidden toggle in the Findings toolbar to see marked findings.Fix: move, edit, or clear the mark again if the change was a mistake.
Cause: at $0, no finding meets all three conditions in Which findings count, so the board is probably all No action, marked, or already Implemented or Ignored. A total that looks too high usually has findings estimating savings against the same spend. A Findings total below Overview means a Service filter is set.Check: the Quick wins and Needs review cards, the status columns, and the filter bar above the board.Fix: clear the Service filter so the two totals match, and compare the resources on large findings before you add them up. See Why it is an upper bound.

Next steps

Work the findings

Triage findings by class and evidence, and move them through the board.

Check spend in Cost Explorer

Compare completed months to confirm a change lowered the bill.

Review anomalies

Investigate unexpected cost changes separately from savings.

Optimize troubleshooting

Every Optimize problem in one place, with cause, check, and fix.