---
title: "FinOps Fundamentals"
description: "The FinOps framework: Inform→Optimise→Operate cycle, FinOps maturity model, and the three core teams that jointly manage cloud economics."
sidebar:
  order: 1
  label: "FinOps Fundamentals"
source_url: "https://framework.stackit.cloud/advisory/cloud-finance-management/finops-fundamentals/"
source_file: "docs/advisory/cloud-finance-management/finops-fundamentals.mdx"
---

## What is FinOps?

FinOps (Financial Operations) is a practice and culture that brings finance, technology and business teams together to jointly understand, manage and optimise cloud spend.

FinOps is not software. It is not a dashboard. It is an organisational operating model with three participating groups:

| Group                       | Responsibility                                       | Typical people                   |
| --------------------------- | ---------------------------------------------------- | -------------------------------- |
| **Finance & Controlling**   | Budget governance, reporting, chargeback             | CFO office, IT Controlling       |
| **Technology (CCoE/Teams)** | Technical optimisation, tagging, rightsizing         | CCoE, engineering teams          |
| **Business (departments)**  | Cost accountability, prioritisation of optimisations | Product owners, IT budget owners |

FinOps only works when all three groups actively participate — not when it is a purely IT task.

## The Inform→Optimise→Operate cycle

FinOps is not a one-time project, but a continuous cycle.

The cycle consists of three phases, continuously repeated: **Inform** creates visibility — make costs visible, implement tagging, create showback reports. Without visibility there is no basis for decisions. **Optimise** actively reduces costs — eliminate idle resources, perform rightsizing, purchase reserved instances. This phase requires concrete action, not just observation. **Operate** steers permanently — budget alerts and anomaly detection, activate chargeback, teams take ownership of costs for their workloads. Then the cycle begins again.

Most organisations start in Inform and remain there. That is a mistake — Inform alone without Optimise and Operate produces attractive reports, but no cost reduction.

## FinOps maturity model

| Maturity level      | Characteristics                                                 | Typical savings potential |
| ------------------- | --------------------------------------------------------------- | ------------------------- |
| **Crawl** (Inform)  | Costs visible, tagging partial, no active optimisation          | 5–10 %                    |
| **Walk** (Optimise) | Regular rightsizing reviews, reserved instances, budget alerts  | 15–25 %                   |
| **Run** (Operate)   | Chargeback active, teams own costs, automated anomaly detection | 25–35 %                   |

**Realistic expectation:** After 6 months an organisation should have reached Walk level. Run level after 12–18 months. An organisation still in Crawl mode after 24 months has an organisational problem, not a technical one.

## FinOps maturity signals: where do you stand?

**Crawl signals (Inform):**

- You can report cloud spend by provider, but not by team or application
- Tagging compliance is below 80 %
- There are no budget alerts

**Walk signals (Optimise):**

- Monthly rightsizing reviews take place
- Reserved instances or committed use cover >30 % of baseline spend
- Budget alerts are configured and acted upon

**Run signals (Operate):**

- Every team sees their own cloud spend in real time
- Chargeback is active — teams pay from their own budget
- Anomaly detection is automated; CCoE is automatically notified at >20 % deviation

## The FinOps culture: who is responsible?

FinOps fails when "cloud costs" are treated as an IT problem. They are a business problem.

**The decisive cultural change:** Teams that use cloud resources must see the costs of those resources and be accountable for them.

A developer who deploys a Kubernetes cluster with 10 nodes for a test workload and then forgets it costs EUR 800/month. If the developer does not see this cost contribution — or is not responsible for it — there is no incentive to decommission it. If they see the costs and must pay from their team budget, the incentive is maximised.

## Practical steps

1. **Conduct a FinOps maturity assessment**: where does your organisation stand today?
2. **Nominate a FinOps team**: all three groups (Finance, Tech, Business) represented
3. **Define target maturity** for 6 and 12 months
4. **Evaluate FinOps tooling**: STACKIT Billing Dashboard as a starting point