FinOps: how to control cloud spend

February 5, 2026 · Baoss
The cloud FinOps approach joins finance, technology and business together to manage cloud spend responsibly. Its goal is not just to cut the bill, but to maximise the value of every euro invested in the cloud, giving visibility and accountability to the teams that consume the resources. Done well, it cuts spend by between 20% and 30% without slowing innovation.

What is cloud FinOps and why does it matter?

In the cloud, spending is variable and decentralised: any team can deploy resources, and the bill grows without anyone having the full picture. FinOps introduces a culture and a set of practices so that cost becomes a shared responsibility and one more variable in engineering decisions. It is not “spend less”, it is “spend better”.

What are the phases of the FinOps model?

The framework is based on a three-phase cycle that repeats continuously:
  1. Inform (visibility): knowing who spends, on what and why. It requires tagging, cost allocation and dashboards.
  2. Optimise: eliminate waste and right-size resources: switch off what is unused, rightsizing, reserved instances or savings plans, and more efficient architectures.
  3. Operate (govern): establish policies, budgets, alerts and responsibilities to keep control over time.

Where does cloud waste hide?

The most common spend leaks:
  • Oversized resources (instances larger than needed).
  • Orphaned resources: disks, IPs or test environments nobody switched off.
  • Non-production environments running 24/7 when they are only used during working hours.
  • Missing discounts: paying everything on demand without reserved instances or savings plans.
  • Poorly optimised data transfer and storage.

How to get started with FinOps in your company?

A practical roadmap:
  • Gain visibility: switch on tagging and a cost dashboard by team and project.
  • Spot quick wins: switch off idle resources and right-size; this usually delivers immediate savings.
  • Apply discounts: analyse steady usage and contract reservations or savings plans.
  • Automate: shutdown policies, budget alerts and anomaly detection.
  • Build culture: make engineering teams co-responsible for the cost they generate.

FAQ

Is FinOps only for large companies? No. Any organisation with a recurring cloud bill benefits; the earlier it is adopted, the more accumulated overspend is avoided. Do I need a specific tool? It helps, but you can start with the provider’s native tools (AWS, Azure, Google Cloud) and good tagging practices. How much can be saved? It depends on the starting point, but cutting cloud spend by 20-30% in the first months is common.
Is your cloud bill growing out of control? At BAOSS we implement cloud FinOps to give you visibility and real savings. Let’s talk.
 

Prefer to talk to us directly? Contact the BAOSS team and tell us about your challenge.