Cost Findings

A CostOps scan asks the provider’s cost keeper to investigate one connection with read-only cloud commands. The keeper writes verified opportunities as draft recommendations, which CostOps presents as findings.

​

Finding classes

No action findings appear in All. CostOps does not expose them as a separate filter because they do not require work.

​

What a finding contains

Each finding card shows: Effort and Risk appear when you open the finding’s detail dialog, not on the card. CostOps uses the finding’s billing service to drive the service filter; it is not displayed as a field. The scan verifies a candidate with a fresh provider read before it creates, updates, or closes a finding. Detection output alone is not proof.

​

Quick wins band

Quick wins · ready to review sits above the findings list when the scan found at least one quick win. It shows the top 2 quick wins with their combined monthly estimate. Selecting one opens its Actions dialog directly, rather than the read-only detail view.

​

Filter findings

Findings appear in the What Keeper found panel. Use the CostOps dashboard to narrow the same connection-scoped finding pool:

• Select All, Quick wins, or Needs review.
• Select a row under Top services last month to show findings attributed to that billing service. This also rescopes the Quick wins and Needs review counts on the tabs to that service.
• Select the same service again to clear the filter.
• Switch the cloud connection at the top of the page to load that connection’s spend and findings.

The default view shows the top 5 findings, marks the highest-value one Start here, and collapses the rest behind Show N more actions. A filtered or paginated view renders a flat ranked list with no priority badge. Findings paginate 20 per page, ranked by estimated monthly savings. Account-wide findings, such as commitment coverage or cross-service tagging, have no single billing service. They appear in All and do not appear under a service filter.

​

Recover from scan errors

CostOps shows progress while a scan runs and keeps that state across navigation. If one service fails, use its retry control under Top services last month without restarting completed work. The findings error summary also offers Re-scan to start a new full-connection analysis. Scan and retry controls require CostOps management permission.

​

From finding to Plan

A CostOps finding is a draft recommendation. Saving it changes that recommendation to active so it can appear in Plan; it does not create a second object. The control is a bookmark icon labelled Save recommendation. Use Plan for assignment, approval, scheduling, and execution tracking. CostOps remains the source view for billing context, scan state, and the current savings classification.

​

Related