FinOps · Cloud architecture · Paid on results

Your systems can be faster, for half the price.

I cut AWS, Azure and Google Cloud bills without slowing production down. The audit is free and takes 48 hours. My fee is 20% of what the bill actually loses.

For CFOs

A bill you can explain line by line, and a fee that exists only if it drops.

For CTOs

Savings that ship as engineering changes, checked against performance before production.

Fig. 01ComputeStorageNetwork
A cloud bill drawn as a planet, ordered dithering on an 8 × 8 Bayer matrix. An illustration.

Field notesAbout 35% of a cloud bill usually comes back without touching the architecture.In 48 hours there are always three levers, before Spot and reservations.An AI bill that explodes is mostly the wrong model per request, and a cache that writes without reading.The big mistake with reservations is not using all of what you reserved.Leaving the cloud only pays for steady, recurring loads.

EDF Power Solutions · 7 h 30 → under 30 s
01 · Use cases

Where the money goes.

Six situations behind a cloud bill that grows faster than it should. Each has its levers, and none of them needs a slower system.

AI · LLM

The AI bill grows faster than usage.

The right model for each request, and a cache that is actually read. Routing and prompt caching, tested on your own traffic.

Levers · routing · prompt caching · batch
Kubernetes

Clusters sized for the peak, all year.

Requests, autoscaling and node pools measured on real usage, and bare metal through Kubernetes where the load is steady.

Levers · rightsizing · autoscaling · bare metal
Batch · data · HPC

Jobs that run all night.

Profile first, then rewrite or move the slow part. At EDF, a 7 h 30 run came down to under 30 seconds.

Levers · profiling · parallel runs · ARM
Commitments

Reserved, paid for, half used.

Savings plans and reservations sized to what actually runs, so all of what you reserve gets used.

Levers · coverage · utilisation · term
Network · multi-cloud

A cheaper cloud that made the bill worse.

Transfer and NAT priced before anything moves. The cheaper answer often stays put, with storage tiers and free routes.

Levers · NAT · egress · tiering
Visibility

Nobody can say what each euro pays for.

Costs mapped to products and teams, with a unit cost finance can follow month after month.

Levers · tagging · allocation · unit cost

Not sure which one is yours? The bill diagnostic tells you in three minutes.

Run the bill diagnostic Live
02 · Why me

The usual worries about FinOps, answered.

“It will be too financial.”

Every saving comes as an engineering change: what to change, the effort, the risk for production. Your team approves each one.

“It won't be technical enough.”

I write Rust and design Kubernetes platforms and data pipelines. When a change needs code, I can write it with your engineers.

“They have never run production.”

Production is where I come from: a real-time IoT platform for over a million sensors, energy simulation at EDF, platform engineering at Pierre & Vacances Center Parcs.

Paid on results
20%

of the measured saving, for 12 months. If the bill does not go down, you owe nothing.

  • 01Changes, not a reportEach saving is priced with its effort and its risk, then applied with your team.
  • 02Performance stays firstA cheaper option that slows production down is not a saving. Latency is checked on every change.
  • 03Both sides of the billFigures finance can follow month by month, and changes engineers can review like any pull request.
  • 0448 hours to an answerA priced list of savings within 48 hours of the billing exports, shared after an NDA.
03 · Clients

They trusted me.

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

EnergyA real-time IoT platform, and a simulation engine moved from C# to Rust.

LeisurePlatform engineering: a developer plugin and a bug telemetry platform.

RailValidation on high-speed and intercity trains, in Europe, Egypt and the United States.

RetailThe run and evolution of an on-premises Hadoop data lab.

04 · About
Portrait of Mathieu Kerbel
FinOps consultant and cloud architect, Paris

I'm Mathieu Kerbel.

Cloud architect and FinOps engineer, self-taught, writing code for clients since 2019. I read every bill myself, and I treat cost as part of the design rather than a surprise after it.

  1. 2019First paid code, then freelance work while still at school.
  2. 2021–2023More than 50 freelance clients, from embedded systems to high-performance computing.
  3. 2024–2025EDF Power Solutions: a real-time IoT platform, then a C# to Rust migration on my own, from 7 h 30 to under 30 seconds, memory peak divided by 40.
  4. 2026FinOps paid on results, and a book: Something from Almost Nothing.
  • FinOps Foundation member
  • AWS · Azure · Google Cloud
  • Rust by choice
05 · Method

From a billing export to a lower bill.

Seven levels to work on, four steps to get there, and one optional step when the audit finds bigger work. Nothing changes in production without your team's approval.

Where I work on the bill

Seven levels, from cutting what serves no purpose to deciding where the money goes. 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.

How an audit runs

Five steps, from the first call to the bigger work. At step 3, the example bill goes through the seven levels above.

How an audit runsScroll to move through the steps

01 · Call and NDA

You

Book a call and bring the last bills, or just their totals and your main services.

Me

I tell you whether the offer fits, before any paperwork. If it does, we sign an NDA.

You get

A straight answer on fit, and an NDA before any data changes hands.

What I ask for after the NDA

Read-only access to billing is enough. No access to production at this stage.

AWS
Cost and Usage Report
Azure
Cost Management exports
Google Cloud
Billing export to BigQuery

02 · Free audit

You

Share the billing exports, read-only.

Me

I read the bill line by line across the seven levels, and price each lever with its effort, its risk and what it does to production.

You get

The lever table for engineering and a one-page summary for finance.

Then a call

We walk through both with your CTO and your CFO on the same call, and your team picks what to apply.

Lever tableFor engineering · Illustration
Example of the audit's lever table
LevelLeverSaving a monthEffortRiskProduction
1Schedule test environments€7,4001 dayLowNo production change
1Delete old snapshots and orphaned volumes€4,9001 dayLowNo production change
2Rightsize the main compute group on ARM€12,6001 weekMediumTested on staging first
3Three-year commitments on the stable compute€18,9002 daysLowThree-year commitment, stable floor only
4Negotiate a multi-year discount (EDP)€9,9501 weekMediumNo production change
5Prompt caching and model routing€6,5002 weeksMediumQuality and latency measured
5Gateway endpoint for S3, not the NAT€3,0001 dayLowTested on staging first
6Incremental export, smaller database€6,8001 weekMediumTested on staging first
7Retire the reporting stack nobody opens€4,2002 daysLowData archived first
Total€74,25032 days55.0% of the bill
One-page summary, per monthFor finance
Bill€135,000
Savings found€74,250
Fee if applied€14,850
You keep in year one€59,400

03 · Changes

You

Pick the levers to apply. Your engineers review and deploy each change.

Me

I write or drive each change with your teams: the pull request or the configuration, its test, and a way back.

You get

A lower bill without a slower system. The fee starts only once a saving shows on the bill.

In this example, the €135,000 monthly bill goes down to €60,750 once the seven levels are applied: €74,250 a month saved, and a fee of €14,850 a month.

Example bill, one monthIllustration
Compute
−€41,100€16,900
Databases
−€9,350€12,650
Storage
−€6,200€9,800
AI models
−€8,000€5,000
Analytics
−€5,250€3,750
Network
−€3,900€4,100
Licences
€5,000
Support and other
−€450€3,550
Total a month€60,750
−55.0%
Saved a month €74,250Fee, 20% of the saving €14,850
The seven levels, in order

04 · Follow-up

You

Keep shipping. Growth in usage is taken into account, not held against you.

Me

Each month I measure the saving against the baseline, at comparable usage, and send the statement.

You get

A monthly statement you can check line by line. After 12 months, every euro saved is yours.

How the saving is measured

The baseline comes from recent bills. Discounts and commitments you already had stay in it, so the fee only covers what changed.

The usage measure is agreed at the start: requests, users or data processed.

Monthly statement · month 3Illustration
Baseline, from recent bills
€135,000
Usage compared with the baseline
8.0% more
Baseline at this month's usage
€145,800
Actual bill
€71,550
Saving
€74,250
Fee, 20% of the saving
€14,850

+ · Bigger work

You

Decide whether the bigger work is worth it, with the figures in hand.

Me

When the audit finds a redesign or a migration worth doing, I scope it as a separate project: goal, cost, expected saving and plan.

You get

A fixed scope you can accept or not. The levers already found stay paid on results.

When it happens

Levels 5 to 7, when a lever needs more than a setting: a batch rewritten and run in parallel, a platform moved to bare metal through Kubernetes, an AI feature rebuilt around caching and routing.

Client work · EDF Power Solutions · level 6A simulation engine rewritten from C# to Rust.7 h 30 → under 30 scloud cost about halved
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's and covers every lever of the exercise; the levers named here are the level 5 ones.

  • 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.
Start with the free auditA call first, then an NDA, then the billing exports.
Architecture by the day · from January 2027

Architecture that costs what it should, from the first diagram.

An architect on your team, up to 20 days a month, in Paris or remote. Daily rate on request.

01

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.

  • A priced design, per component and per month
  • Options compared on cost, performance and run effort
  • The estimate checked against the first real bills
02

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, before the first line of code.

  • Decision records, with the options left aside
  • Interfaces and acceptance criteria you can test
  • Specs written to be read by people and by agents
06 · Articles

Every line of the bill, explained.

Twenty articles so far, one cloud service at a time, each with its prices and its levers.

07 · Trainings

Trainings for tech teams and the people who fund them.

Worked on your own cases, in small groups or one to one.

Open

CTO Sparring

Decisions, applying them, and the budget of a tech team, worked on your real cases.

10 hours · €2,400 · first hour free
Draft

Cloud for managers

Cloud services, what they cost and who builds them, explained to the people who sign the budget.

Duration and price to set
Open

FinOps for engineering teams

Read the bill, find the levers, and ship the change without hurting production.

Half a day to two days · from €1,500
Draft

Rust for speed and cost

Moving the hot path from C# or Python to Rust, the way the EDF engine went from 7 h 30 to under 30 seconds.

Duration and price to set
08 · Questions

What CFOs and CTOs ask first.

Do you need access to production?

Not for the audit: it only needs billing exports, shared after an NDA. Access comes later, only for the changes your team approves, under your own rules.

What if the bill does not go down?

Then you owe nothing. The fee is 20% of the measured saving, for 12 months, and only once the saving shows on the bill.

How is the saving measured?

Against a baseline set from recent bills, at comparable usage. Discounts and commitments you already have are part of that baseline.

Will it slow production down?

Performance is part of every review. A cheaper option that hurts latency or reliability is not counted as a saving.

Which clouds do you cover?

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

Can we hire you by the day instead?

Yes, from January 2027: FinOps or architecture by the day, up to 20 days a month, in Paris or remote.

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

Free audit · NDA first · nothing changes without your approval