The cloud bill arrives and an uncomfortable silence falls over the meeting. Nobody can quite explain why it went up again. The cloud promised to pay only for what you use — but without discipline, "what you use" grows on its own, month after month. FinOps is the answer: a practice that brings financial accountability to cloud spending, and that usually cuts a significant slice of the bill without losing capacity.
Why the cloud bill spirals
The "pay for what you use" model is a double-edged sword. Because it is easy to turn on resources and nobody pays out of their own pocket, machines are spun up "just to test" and stay on for months, data nobody looks at again is kept, things are oversized out of caution. Each decision seems small, but added up they make a bill nobody can explain line by line.
What FinOps is
FinOps (from "Financial Operations") is the practice of managing cloud cost the way you manage any important expense: with visibility, accountability and continuous optimization. It is not cutting blindly — it is ensuring every euro spent delivers value, and that those who consume see and own the cost of what they consume. It brings finance, engineering and business around the same bill.
The three steps: see, optimize, operate
- See: make cost visible and attributable — who spends what, and why. Without visibility there is no management.
- Optimize: turn off what is not used, resize the oversized, tier old data into cheaper storage.
- Operate: make this a continuous habit with budgets, alerts and reviews — not a one-off cleanup.
The savings that are waiting
Most cloud bills have obvious fat: resources on 24 hours that are only used in working hours, forgotten test environments, premium-priced storage for data nobody has queried in months, reserved capacity "just in case" that is never reached. Just catching this waste usually yields cuts of 20 to 30% — without touching anything the business actually uses.
A concrete case
A company with a monthly cloud bill of about 20 thousand euros started by making cost visible by team. That alone already changed behaviors — when each team saw its own bill, it started turning off what it did not need. Then, they resized chronically underused machines and moved old data to cold storage. In three months, the bill dropped to ~14 thousand, with no loss of capacity. The annual saving paid for the effort several times over.
It is not an event, it is a culture
The mistake is doing one big cleanup and going back to old habits. Without a culture of accountability — each team seeing and owning its cost — the fat piles up again. Effective FinOps is continuous: small constant gestures, budgets with alerts, and the norm of asking "is this worth what it costs?" before turning on anything.
In practice
If your cloud bill rises without anyone quite knowing why, start with the simplest and most powerful thing: make it visible by team. Visibility alone changes behaviors. Do you know today how much each team in your company spends on cloud — and how much of that is pure waste?
