Wise Forge Labs · FinOps reclaim estimator
Monthly cloud spend plus the maturity bucket that fits most closely — the calculator below returns a projected reclaim range (low and high percentages with an annualised USD band) and threads the result straight into the engagement inquiry so the advisory team can scope against it.
What the calculator reads
The first axis is the raw input — monthly cloud spend across AWS, GCP, and Azure combined, in USD. The second is an optimization-maturity bucket (Greenfield, Basic tagging, Active monitoring, Mature FinOps) that determines which end of the reclaim range the engagement tends to find. The calculator does the arithmetic; the engagement confirms the assumptions against your actual bills.
Pick the bucket that fits most closely. The number rounds — an honest “we don’t know” belongs in the bucket that best reflects what is missing, because the gap is what the engagement is supposed to find.
The estimator
The result updates as you type — no submit, no email round-trip. The CTA at the bottom of the result card threads your selected maturity through the engagement inquiry so the advisory team can read it against your notes.
Two inputs, in-page result
Enter your monthly cloud spend and pick the maturity bucket that fits most closely. The reclaim range updates as you type.
Optimization maturity
Awaiting inputs
Enter a monthly spend above and pick the maturity bucket that fits most closely.
The reclaim range is informational and does not store your spend. The engagement inquiry is what confirms the assumptions against your actual bills.
Reading the bands
The bucket you pick maps to a reclaim band — the wider the bucket’s band, the more leakage the engagement typically finds. The table below maps each tier to the band the calculator uses and the engagement that tends to fit it, so the result card is not a surprise.
No tagging discipline, no chargeback model, and the cloud bill is a quarterly surprise. The reclaim range sits at the top because the leakage is widest — the engagement instruments the data before the rate card is even visible.
Tagging is in place but inconsistent, and the cost conversation lives in a handful of spreadsheets. We tighten the schema, close the unattributed gap, and surface the first commitments so the rate-card conversation starts.
Anomaly alerts fire and the dashboards refresh, but the rate-card conversation and commitment discount cycle are still anchored on raw on-demand. The engagement overlays the FinOps commitments practice on top of the existing telemetry.
Commitments and showback are already negotiated annually; the residual reclaim tends to come from unit-economics and shadow-workload review. The briefing shifts to fractional advisory against the audited rate-card.
What the estimator is — and isn’t
If the reclaim range surfaced something you would rather not say out loud, the FinOps engagement is the next step. If the range confirmed posture, the briefing is still the cheap way to confirm it on paper.