FinOps is the practice through which engineering, finance and leadership decide about technology spend together, and this chapter explains where its vocabulary comes from and how it works in a company that has no FinOps function of its own. It opens the handbook: the terms introduced here, principles, phases, personas, domains, capabilities, maturity levels and scopes, return in every later chapter. A reader who understands the cloud bill but not who owns it finds the frame here; a reader who knows the frame but not the mechanics of billing finds those in the chapters that follow.

What this chapter covers

The Foundations section follows the FinOps Foundation's Framework, which is licensed CC BY 4.0, and answers seven questions in turn. What FinOps is and what it is not: not a tool, not a cost-cutting project, not a job for finance alone. Which six principles the Foundation names and what each of them means for a team with a handful of accounts. How the three phases Inform, Optimize and Operate fit together and why they form a loop rather than project stages. Which personas the Framework distinguishes and why they describe perspectives, not positions. How the four domains group their capabilities and which of those a small company actually needs. What the maturity levels Crawl, Walk and Run mean and why Run is not the goal everywhere. And how technology categories name the kinds of spend (Public Cloud, SaaS, Data Cloud Platforms, Data Center, AI) and how a scope cuts a business segment across them.

The Practice section answers the two questions that remain after the foundations. How a company of 10 to 200 people spreads the capabilities across the roles it already has, an engineering lead, the person who pays the bill and management, and which artefacts carry that practice from month to month. And how the terms cloud cost management, FinOps and cloud financial management relate to each other, terms that tenders, job advertisements and product descriptions use interchangeably although they do not mean the same thing.

The Foundation most recently added the capability Executive Strategy Alignment to the Framework and deepened its guidance on scopes and technology categories; what of that matters to a small team is set out in FinOps Framework 2026: what small teams should actually change. The chapter itself stays with the terms and what they mean; it is reference, not a guide.

Key terms

  • FinOps: the framework and cultural practice the whole chapter is about; the name stands for the collaboration of finance and engineering, not for a department.
  • Cost allocation: the capability Allocation in the domain Understand Usage & Cost; the chapter treats it as the first artefact a practice needs.
  • Cost report: the output of the capability Reporting & Analytics; in this chapter, the form in which cost reaches an owner.
  • Budget: the capability Budgeting in the domain Quantify Business Value; here, the line against which a scope is measured.
  • Anomaly: the subject of the capability Anomaly Management; the chapter uses the term for the unexpected rise someone has to explain.
  • Savings opportunity: the starting point of the Optimize phase; a documented proposal with an estimate, not yet a realised saving.
  • Showback and chargeback: the two ways the capability Invoicing & Chargeback brings allocated cost back to those who caused it, by showing it or by charging it.

Neighbouring chapters

This chapter opens the handbook, and it is deliberately the only one that starts from the framework rather than from the invoice. The chapter How cloud billing works follows immediately with the invoice itself: the billing account, line items, the billing period and the question of why the total keeps moving after month end. The chapters Billing data and standards, Pricing models and commitments and What cloud services cost then supply the material the Inform phase works with in the first place.

The practice itself lives in chapters 6 to 10. Allocation and ownership, Reporting and analysis, Budgets, forecasts and finance, Optimisation and savings and Governance and the operating model each take one or two domains of the Framework apart and show how the capabilities become concrete in reports, budgets and rules. A reader who wants to know, after this chapter, how an allocation covers the whole bill or what a budget per scope looks like reads on there. FinOps for AI, Europe: currency, tax and sovereignty and Tooling close the handbook with the three subjects the Framework only touches on, as a technology category, as a regional particularity and as the capability Automation, Tools & Services.