The lever table
Every lever with its level, its saving a month, its effort, its risk and what it does to production.
Your cloud bill goes down, or you pay nothing.
I audit your bills, find the savings and help your team apply them. I'm paid 20% of the measured savings for 12 months. The audit is free, delivered within 48 hours of receiving your billing exports.
20% of the measured saving, every month for 12 months. No flat fee and no licence. After that, every euro saved stays with you.
An order of magnitude, not a quote. The audit gives the real figure, lever by lever.
Over the first 12 months: €567,000 saved, €113,400 of fee, €453,600 kept.
A call first, then an NDA, then the billing exports. Read-only access to billing is enough for the audit.
A first look at the bill together. If the offer fits, an NDA, then the billing exports.
Every lever priced with its effort, its risk and what it does to production. Your team picks what to apply.
I write or drive each change with your teams. Your engineers review and deploy it.
A monthly statement against the baseline, at comparable usage. After 12 months, all of the saving is yours.
When a lever needs a redesign or a migration, I scope it as a separate project.
Tools and checklists cover the first three. The savings that last sit further down, in architecture, code and steering.
| Workstream | Levers | Effort | Timeline |
|---|---|---|---|
| 1HygieneCut what serves no purpose | Orphaned volumes and IPs, old snapshots, non-production off at night and at weekends, tags. | Low | Hours to days |
| 2RightsizingFit to real usage | Oversized instances and databases, gp2 to gp3 disks, a move to ARM (Graviton). | Medium | Days to weeks |
| 3CommitmentsPay less for what remains | Savings Plans, reserved instances, Spot for workloads that can take an interruption. | Low | Days |
| 4NegotiationCloud and vendor contracts | Multi-year commitments (EDP, MACC), private pricing, migration credits, licences and SaaS contracts. | Medium | Weeks to months |
| 5ArchitectureChange what generates the bill | Managed or serverless services, autoscaling, caching, outbound traffic, storage lifecycle. | High | Weeks to months |
| 6Code and runtimeRewrite what runs the most | Profile the hot paths, change language where it pays. A C# batch moved to Rust went from 7 h 30 to under 30 s. | High | Months |
| 7CTO steeringDecide where the money goes | Cost per customer or per transaction, the cloud's share of revenue, build or buy, repatriation where it is justified. | High | Quarters |
| Each level works on what the levels above it left. | |||
The same figures for engineering and for finance, so nobody has to translate.
Every lever with its level, its saving a month, its effort, its risk and what it does to production.
The bill, the savings found, the fee if they are applied, and what you keep in year one.
We walk through both documents together, and your team picks what to apply.
The saving measured against the baseline, at comparable usage, and the fee that goes with it.
€1.3M saved on client bills in total. No amount is attributed to a single client.
Runs went from about 7 h 30 to under 30 seconds, and cloud costs fell by about half.



Exercises built on what each company published, priced at AWS list prices. Not client work: I have no relationship with these companies. The percentage is the base scenario of each case page and covers every lever of the exercise; the levers named here are the level 5 ones.
Describe your use case and the agent turns it into billing lines on AWS, Google Cloud and Azure. Set the priority, see the security baseline you'll need and the savings already in sight.
Up to 20 days a month, in Paris or remote. Daily rate on request.
A FinOps engineer on your team: bill audits, approved changes applied with your engineers, and cost estimates at the design stage.
Every component priced before it is built. The cheaper option is kept when it does the job, and the monthly bill is estimated while the design is still on paper.
The architecture written as specifications your engineers, or their coding agents, can build from: decisions and their reasons, constraints, interfaces and acceptance criteria.
Paid on results suits an existing bill you want lower. The daily rate suits a team that wants a FinOps engineer inside it.
Nothing without your team's approval. The audit only needs billing exports, shared after an NDA. Access comes later, only for the changes your team approves.
Against a baseline set from recent bills, at comparable usage. The usage measure is agreed at the start: requests, users or data processed.
They sit in the baseline, so the fee only covers what changed.
Then you owe nothing.
The offer is built for bills of €30,000 to €300,000 a month.
AWS, Google Cloud and Azure, separately or combined, with Kubernetes and data platforms on top.
Free audit · NDA first · nothing changes without your approval