Tooled FinOps audit
Where the money goes, what can be recovered, in what order: the whole bill quantified on your observed cost from read-only access, and a dated execution plan. First figures on Day 2 on Azure; on Google Cloud and AWS, as soon as the billing export covers 30 days.
This is your situation if
- The bill is rising and nobody can explain it
- Nobody is dedicated to the topic, or your FinOps is on their own
- A new manager wants a quantified baseline
- A reservation or Savings Plans renewal is coming
Format
Fixed scope: short format (one scope) or extended format (about six weeks, validation by entity).
What we ask for: a read-only role and one hour with a contact person; on Google Cloud and AWS, an active billing export.
People: a senior FinOps consultant and our app.
Figures you can defend
Net potential, lever by lever
Ranked by euro saved per day of effort, with its risk, its prerequisites and its status.
Variances explained
What moved from one month to the next, tied to a cause and to a resource.
A dated execution plan
Reduce before you reserve: commitments computed on the reduced base, never on the current estate.
Beyond virtual machines
Licenses in the cloud, first AI costs and, as an option, a first reading of Green IT indicators.
A verifiable workbook
In formulas, in French and in English: every figure can be recomputed and checked.
A self-service procedure
To replay the collection yourselves, without depending on us.
The same audit, at your scale
Extended format, by entity
One workbook per scope, a feedback register and validation by your application owners.
Large enterprisesShort format, one contact person
One scope, first figures within a few days, a two-hour readout.
SMEs and scale-upsAt your clients
In co-delivery on your clients' accounts, or under your brand.
IT service providersWhat this approach produced
Three anonymized cases, status shown for every figure.
An Azure bill already partly optimized
- Identified about 29% of the Azure bill in potential savings
- Validated 12 changes launched or ready four weeks after the start
A mature AWS foundation, potential quantified lever by lever
- Identified incremental potential of about 10% to 25% of the AWS bill
- Deliverable optimization plan of 18 levers, with owner and target quarter
SAP non-production: a sequenced Start & Stop
- Identified about 61% of non-production compute with a night and weekend shutdown, in simulation
All client results and the definition of the statuses.
Frequently asked questions
What access do you ask for?
A read-only role: Reader and Cost Management Reader on Azure, ReadOnlyAccess and CUR access on AWS, Viewer and Billing Viewer on Google Cloud. No write access, no administration rights.
Does our data leave our environment?
Yes if the analysis runs at KeeFinops: the collection archive (billing, inventory, metrics, resource names and tags; no application content) is sent to us and processed in a container without network access. No if you host that container in your own environment. See the privacy policy.
First figures on Day 2 on Azure
Thirty minutes to scope the perimeter, set the fixed fee and prepare the read-only access.