Savings Estimates

CostOps reports Potential monthly savings, not realized savings. The number helps you size the open opportunity for one connection before you decide what to implement.

​

What the estimate includes

CostOps sums the monthly estimates on open, actionable findings: The headline uses every matching open finding for the connection. It does not depend on how many cards the current page has loaded.

​

Why it is an upper bound

Two findings can overlap. For example, a right-sizing 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 CostOps forecast;
• review resource overlap before adding estimates to a plan;
• use the finding’s confidence, reversibility, effort, and risk to prioritize work.

CostOps keeps the forecast and potential savings separate because they answer different questions. The forecast estimates where the bill is heading; potential savings estimates the value of open actions.

​

How filters affect the findings total

The headline Potential monthly savings remains the full actionable estimate for the selected connection. Filters change the recoverable total in the What Keeper found panel subtitle, not the headline. That line appears only when the filtered total is above zero, and scan progress or a scan-error notice replaces it while a scan runs or after one fails. The top service rows show the potential savings attributed to each service. The dashboard headline always remains connection-scoped.

​

Potential is not realized

CostOps does not currently calculate realized savings, return on investment, capture rate, or 30/60/90-day post-implementation variance. Promote a finding to Plan to govern the work, but keep external billing validation for realized-savings reporting. This distinction prevents an estimate from being presented as financial proof.

​

Related