Three formats, from a half-day session to a two-day bootcamp, for engineers, tech leads, engineering managers and finance. In Paris or remote, built on your own bills when you want it to be.
Delivered in English or French. Each format draws on the modules below; the depth grows with the length.
€1,500 for up to 15 people
Everyone shares one vocabulary: how the bill is built, where cloud spend usually hides, and which levers exist.
None. Open to technical and non-technical roles.
€3,500 for up to 10 people, preparation included
The team reads its own bills and leaves with a prioritized list of savings it can act on.
Read access to a recent bill or cost export, and a few people who know the workloads behind it.
€7,000 for up to 8 people, preparation included
Practitioners can run the cost practice: analysis, commitments, allocation and unit economics, with cost in every design review.
Day-to-day work on AWS, Azure or Google Cloud, and access to billing exports for exercises.
Read a bill, size a service, and know what a design choice costs before it ships.
Put cost next to latency and availability in design reviews, and own the unit cost of a service.
Run a cost practice inside the team: tagging, showback, and a regular review that leads to action.
Understand what the line items mean, what commitments really commit to, and which questions to put to engineering.
Each format draws on these modules; the depth grows with the length. Cloud examples cover AWS, Azure and Google Cloud.
Meters, rates, usage types and the invoice they produce; why the same service shows up under several line items.
The AWS Cost and Usage Report, Azure cost exports and the Google Cloud billing export: what each row is and how to query it.
Matching instance and service sizes to the load you measured, and what to check before changing anything.
Savings Plans, Reserved Instances, Azure reservations and Google Cloud committed use discounts: how they work, what they lock in, and how to size them.
Tiers, retention and lifecycle rules for object and block storage, and the retrieval costs that surprise teams.
Where traffic is billed, why it is easy to miss, and which architectures avoid it.
Allocating spend to teams and products, and what to do with the share nobody owns.
Cost per customer, per request or per feature, so spend can be read against what the business gets for it.
Pricing a design before building it: an option-by-option monthly cost next to the other trade-offs.
Native cost tools, exports and calculators, and where a dedicated tool earns its place.
The published articles, the calculator and the book are the reference material: read them before, and keep them after.
Pick a slot and tell me the team, the clouds you use and the format you have in mind. Prices are per group, excl. VAT. Prefer writing? contact@mathieukerbel.com