Projected savings are not proven savings
CloudCostIQ treats projected savings as a claim that needs review, owner accountability, and measurement before leadership counts it.
Savings proof before automation
How CloudCostIQ proves cloud savings.
Savings claims are useful only when finance and engineering can trust them. CloudCostIQ separates projected savings from realized savings, preserves evidence, assigns reviewers, and keeps slipped-back or rolled-back claims out of executive totals.
Every claim needs evidence
Evidence can include billing-period comparisons, cost snapshots, tickets, review notes, approvals, external links, and manual reviewer notes.
Proof is human-reviewed
Reviewer roles distinguish finance and engineering review. The system assists the workflow; it does not declare financial outcomes by magic.
Savings must hold
Follow-up checks watch for weakening, rollback, and expiration so one-time reductions do not become permanent executive claims.
Financial trust model
Savings Proof is the source of truth.
Recommendations remain workflow objects. Savings proof records are financial claims with reviewer assignment, projected and realized savings, confidence, evidence strength, follow-up confidence, rollback probability, slipped-back savings risk, and savings confidence.
Projected savings
Estimated monthly savings before financial validation.
Realized savings
Measured monthly savings observed after implementation.
Savings needing proof
Completed or pending savings work that has not been financially proven.
Savings confidence
Composite score based on confidence, evidence strength, completeness, follow-up confidence, rollback risk, and slipped-back savings risk.
Savings slipped back
A previously claimed saving weakens or costs return after implementation.
Rollback
The action was reverted, excepted, or undone for operational reasons.
Billing evidence quality
Whether the savings claim is backed by recurring native proof, review-ready uploaded evidence, stale data, or missing proof.