Migrating to the cloud promises flexibility and speed on day one. After the first year, however, the topic that lands on the CFO's agenda is almost always the same question: "Why is our bill so high?" FinOps (Cloud Financial Operations) was born to answer it. It is not a tool but a working model where technology and finance teams sit at the same table.
The Three Phases of FinOps
According to the FinOps Foundation reference model, every organisation progresses through three phases:
- Inform: who spends what? Tagging discipline, cost dashboards and detailed invoice analysis.
- Optimize: right-size over-provisioned resources, buy Reserved Instances or Saving Plans, move cold data to cheaper tiers via lifecycle policies.
- Operate: cost per unit of value (cost per customer, per transaction) is reported and engineers make decisions against it.
Most teams get stuck in "Inform". The real value emerges in the third phase.
The Biggest Cloud Cost Leaks
Common leaks seen across Turkish enterprises:
- Test environments stay up at night: roughly 60% of dev/staging environments run through weekends and nights. Auto-shutdown can save 40% a month.
- Over-provisioned databases: a 16-vCPU RDS instance running at 15% utilisation is not unusual. Right-sizing saves millions annually.
- Egress (data-transfer) charges: five-figure monthly dollar line items that appear in cross-region traffic without anyone noticing.
- Untagged resources: resources without tags or clear ownership can consume 15-25% of the budget.
A Proper Tagging Strategy
Tagging is the foundation of FinOps. Minimum mandatory tag set: environment (prod/staging/dev), cost-center, owner-team, application. Azure Policy, AWS Config or GCP Tag Constraints should prevent the creation of untagged resources.
Reserved Instance / Saving Plan Decision
1-3 year commitments on stable workloads yield 40-70% discounts. But unused committed capacity becomes sunk cost. General rule: commit the baseline that runs >60% consistently; keep bursts on-demand.
The Organisational Side of FinOps
FinOps is not only finance — it is a culture built jointly by finance, engineering and product. A monthly FinOps review, showback/chargeback tracking per team, and tying cost savings to engineer KPIs are hallmarks of successful programmes.
