Skip to main content
Savings Tracking measures the actual dollar impact of every implemented recommendation — recording the baseline, monitoring cost changes post-implementation, and surfacing variance against the original projection.

​
KPIs

​
How savings are tracked

When Alex implements a recommendation, CloudThinker records the implementation date, stores the projected savings, and begins monitoring actual cost changes. For recommendations you implement manually:
  1. Open the recommendation and mark it Implemented.
  2. Enter the actual monthly savings amount.
  3. Add implementation notes and any supporting documentation.

​
Savings attribution

​
Projections

Alex forecasts future savings from your active recommendation backlog:

​
Validation

Actual cost changes are tracked automatically against each implementation:
  1. Baseline cost is recorded on the implementation date.
  2. Actual costs are monitored at 30, 60, and 90 days post-implementation.
  3. Variance from the original projection is calculated and surfaced.
Common causes of variance: workload changes after optimization, new resources created in the same category, provider pricing changes, and seasonal usage patterns.

​
Example prompts

Cost Analytics

Explore spending patterns and anomalies before and after optimization

Recommendations

Review and implement AI-generated cost-saving recommendations

Artifacts

Generate executive savings reports and schedule recurring delivery

CloudKeepers

Surface waste as continuous findings that feed the savings pipeline