Understanding the decisions behind the bill
A bill tells you how much a service costs. To decide what to do with it, you also need to understand how it is used, the constraints it creates and what it brings to the business. These are the questions I focus on.
How I approach FinOps
I start with usage and the available data. Who consumes the resources? Which project do they belong to? Which commitments limit the options? What would an architecture change mean?
These questions give technical teams and budget owners a common basis for discussing costs. They also help distinguish a potential saving from an action that can actually be implemented.
For AI, I pay particular attention to the cost of a validated task. Token pricing matters, but output quality, retries and review time also affect the cost of using a model.
Why this site
I share my analysis of FinOps, Cloud and the value of AI investment on LinkedIn. This site gives me room to develop topics that need more context: the conditions for an optimisation, the limits of a vendor announcement or the consequences of a technical choice.
Articles are available in French and English.