Skip to main content
Optimize reports Potential monthly savings, not realized savings. Use the number to size the open opportunity for one connection before deciding what to implement.

​
What the estimate includes

Optimize sums the monthly estimates on open, actionable findings: The headline uses every matching finding for the selected connection. It does not depend on the board column or filter currently on screen.

​
Why it is an upper bound

Two findings can overlap. For example, a rightsizing finding and a commitment coverage finding can both estimate savings against the same compute spend. For that reason:
  • do not treat the total as a guaranteed bill reduction;
  • do not subtract it from the current-month forecast;
  • review resource overlap before adding estimates together;
  • use confidence, reversibility, effort, and risk to prioritize work.
The forecast estimates where the bill is heading. Potential savings estimates the value of open actions. They answer different questions.

​
How settlement changes the total

A finding leaves the actionable total when your team settles it through status or disposition. Expected and snoozed findings are hidden from the board by default, but you can reveal them to review the decision. The top service and Overview totals remain connection-scoped. Service and class filters narrow the visible cards without converting the headline into a realized-savings measure.

​
Potential is not realized

Optimize does not present the estimate as return on investment, capture rate, or verified post-implementation savings. Validate the next provider bill after implementation if you need financial proof. This distinction keeps an estimated opportunity separate from an observed billing result.

Findings

Review the findings included in the estimate

Cost Explorer

Compare the estimate with completed-month spend

Anomalies

Inspect unusual cost changes separately from savings

Reports

Generate an evidence-grounded savings report