FinOps paid on results: cut your AWS, Azure or Google Cloud bill

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.

Fee
20% of the measured saving
Duration
12 months, then the saving is all yours
Audit
Free, within 48 hours
Bills
€30,000 to €300,000 a month
The bill going through the seven levels, ordered dithering on an 8 × 8 Bayer matrix. An illustration.
AWS · Azure · Google Cloud, with Kubernetes and data platforms on top
01 · Your fee

What you pay, and when.

20% of the measured saving, every month for 12 months. No flat fee and no licence. After that, every euro saved stays with you.

€135,000
Saving the audit finds

An order of magnitude, not a quote. The audit gives the real figure, lever by lever.

Saving a month
€47,250
My fee a month
€9,450
You keep, year one
€37,800
You keep, from year two
€47,250
Your current bill, split in year one
New bill €87,750You keep €37,800Fee €9,450

Over the first 12 months: €567,000 saved, €113,400 of fee, €453,600 kept.

Guarantees

  • Nothing is payable until the bill goes down.
  • Nothing changes without your team's approval.
  • The audit commits you to nothing.
  • Discounts you already have sit in the baseline.
02 · How it runs

Four steps, and one more if the audit finds bigger work.

A call first, then an NDA, then the billing exports. Read-only access to billing is enough for the audit.

  1. 01 · Call and NDADay 0

    A first look at the bill together. If the offer fits, an NDA, then the billing exports.

  2. 02 · Free audit48 hours

    Every lever priced with its effort, its risk and what it does to production. Your team picks what to apply.

  3. 03 · ChangesPaid on results

    I write or drive each change with your teams. Your engineers review and deploy it.

  4. 04 · Follow-up12 months

    A monthly statement against the baseline, at comparable usage. After 12 months, all of the saving is yours.

  5. + · Bigger workOptional, scoped and paid

    When a lever needs a redesign or a migration, I scope it as a separate project.

03 · Where I work

Seven levels, from clean-up to steering.

Tools and checklists cover the first three. The savings that last sit further down, in architecture, code and steering.

Your billWhat is leftSaved
The seven levels I work at, with their levers, effort and timeline
WorkstreamLeversEffortTimeline
1HygieneCut what serves no purposeOrphaned volumes and IPs, old snapshots, non-production off at night and at weekends, tags.LowHours to days
2RightsizingFit to real usageOversized instances and databases, gp2 to gp3 disks, a move to ARM (Graviton).MediumDays to weeks
3CommitmentsPay less for what remainsSavings Plans, reserved instances, Spot for workloads that can take an interruption.LowDays
4NegotiationCloud and vendor contractsMulti-year commitments (EDP, MACC), private pricing, migration credits, licences and SaaS contracts.MediumWeeks to months
5ArchitectureChange what generates the billManaged or serverless services, autoscaling, caching, outbound traffic, storage lifecycle.HighWeeks to months
6Code and runtimeRewrite what runs the mostProfile the hot paths, change language where it pays. A C# batch moved to Rust went from 7 h 30 to under 30 s.HighMonths
7CTO steeringDecide where the money goesCost per customer or per transaction, the cloud's share of revenue, build or buy, repatriation where it is justified.HighQuarters
Each level works on what the levels above it left.
The bill narrows level by level, and what falls away is the saving. Widths and dots are an illustration.
04 · What you get

Two documents, one call, then a statement each month.

The same figures for engineering and for finance, so nobody has to translate.

For engineering

The lever table

Every lever with its level, its saving a month, its effort, its risk and what it does to production.

For finance

The one-page summary

The bill, the savings found, the fee if they are applied, and what you keep in year one.

With your CTO and CFO

One call

We walk through both documents together, and your team picks what to apply.

Every month

The statement

The saving measured against the baseline, at comparable usage, and the fee that goes with it.

05 · Proof

Measured on client bills, and on public ones.

€1.3M saved on client bills in total. No amount is attributed to a single client.

Client work · EDF Power Solutions · Energy

A simulation engine rewritten from C# to Rust.

Runs went from about 7 h 30 to under 30 seconds, and cloud costs fell by about half.

7 h 30 → under 30 scloud cost about halved
  • EDF
  • Groupe Pierre & Vacances Center Parcs
  • Televic
  • Nature & Découvertes

If I were FinOps at…

Exercises · level 5 levers

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.

Calculator

Price an architecture before you build it.

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.

Example · multi-cloud SaaSEUR / month
Monthly cost
€10,812
Savings found
€2,529
Security baseline
€414
By the day · from January 2027Jan 2027

The same work, inside your team.

Up to 20 days a month, in Paris or remote. Daily rate on request.

01

FinOps by the day

A FinOps engineer on your team: bill audits, approved changes applied with your engineers, and cost estimates at the design stage.

02

Cost-by-design

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.

03

Spec-by-design

The architecture written as specifications your engineers, or their coding agents, can build from: decisions and their reasons, constraints, interfaces and acceptance criteria.

06 · Questions

Before you send the export.

Which format fits?

Paid on results suits an existing bill you want lower. The daily rate suits a team that wants a FinOps engineer inside it.

What do you touch?

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.

How is the saving measured?

Against a baseline set from recent bills, at comparable usage. The usage measure is agreed at the start: requests, users or data processed.

Do the discounts I already have count?

They sit in the baseline, so the fee only covers what changed.

What if the bill does not go down?

Then you owe nothing.

What size of bill is this for?

The offer is built for bills of €30,000 to €300,000 a month.

Which clouds do you cover?

AWS, Google Cloud and Azure, separately or combined, with Kubernetes and data platforms on top.

Send the billing export. Get the levers in 48 hours.

Free audit · NDA first · nothing changes without your approval

FinOps assistant· replies in seconds
Give me your monthly cloud bill or describe your architecture. I'll tell you where it can go down and how the free audit works.
Press Enter to send

Automated assistant. The figures it gives are orders of magnitude, not a quote.