Savings you can actually book
After an action executes, GetFinOps re-measures the resource’s state and books state-verified × list-price savings — with a verifier sweep that re-checks over time. Unlocks %-of-proven-savings pricing.
"Potential savings" is a vanity metric. Finance can’t reconcile a dashboard estimate against the invoice, so nobody trusts the ROI number — and the FinOps program can’t prove its own value.
Built to do the work, not just show it
State-verified savings
The saving is booked from the resource’s confirmed post-execution state, not a pre-action guess.
Verifier sweep
A scheduled sweep re-checks due rows and confirms the change stuck (or flags a revert).
Per-account verification
The verifier assumes the remediated account’s own cross-account role, so non-primary accounts verify correctly.
Pricing-grade evidence
A durable ledger of proven savings underpins %-of-proven-savings and AI-margin pricing.
From signal to result
Execute
A remediation runs and records its before/after state.
Verify
The ledger books state-verified × list-price; the sweep re-confirms on a schedule.
Report
Realized savings roll up per account and across the portfolio.
- A revert at T+7 is caught and demotes the action type’s autonomy automatically.
- Savings are attributed to the account that was actually remediated.
- The ledger is the basis for outcome-based pricing.
Questions
How is a saving "verified"?
From the resource’s confirmed post-execution state times list price — not a pre-action estimate.
What if the change is undone later?
The verifier sweep detects the revert and adjusts the ledger, and the action type’s autonomy is demoted.