FinOps Certified Practitioner cheat sheet

FinOps is an operating model and cultural practice that brings financial accountability to variable technology spend and enables trade-offs among cost, quality, and speed.

The six FinOps principles are: teams need to collaborate; business value drives technology decisions; everyone takes ownership for their usage; FinOps data should be accessible, timely, and accurate; FinOps should be enabled centrally; take advantage of the variable cost model.

The FinOps Framework components include Principles, Personas, Phases, Maturity, Domains, Capabilities, Scopes, and Technology Categories.

The FinOps lifecycle phases are Inform, Optimize, and Operate; the cycle is continuous rather than a one-time linear sequence.

Crawl, Walk, and Run describe capability maturity, not team seniority or organization size.

Unit cost = total technology cost / business metric; examples include cost per transaction and cost per active user.

Decision rule: establish visibility, allocation, and forecasting in Inform before attempting optimization, because unallocated cost data can drive incorrect actions.

Central FinOps enablement means a central team builds standards, tooling, and coaching while accountable teams make usage and cost decisions.

Personas are the roles that interact with FinOps; each persona needs different cost views, decisions, and levels of detail.

Core persona groups include FinOps practitioners, engineering, finance, procurement, product, and executive leadership.

A RACI mapping assigns each capability or decision to responsible, accountable, consulted, and informed personas.

The FinOps practitioner enables the practice by defining data standards, facilitating reviews, and coaching teams; the role does not solely own all spending decisions.

Engineering personas select and operate resources, so they need granular usage and cost data to rightsize, remove waste, and evaluate architecture trade-offs.

Finance personas own budgeting, forecasting, accounting treatment, and variance analysis, and need reconciled cost data aligned to financial plans.

Procurement personas manage vendor contracts, discounts, commitments, and renewals, and need usage forecasts to negotiate terms that match expected consumption.

Product and leadership personas use unit economics, portfolio cost views, and business-value measures to prioritize investments and set risk appetite.

Inform provides visibility: accurate, timely, allocated cost and usage data plus forecasts and budgets.

Optimize improves cost through usage changes and rate changes while preserving required performance and business value.

Operate sustains results through governance, automation, accountability reviews, and continuous improvement.

Crawl maturity is typically manual, reactive, and limited to basic visibility.

Walk maturity is repeatable, with allocation, regular reviews, and some automation.

Run maturity is automated, proactive, and embeds unit economics and business value into decisions.

Rate optimization lowers the price paid per unit through commitments, reserved capacity, negotiated discounts, and vendor terms.

Usage optimization changes consumption through rightsizing, idle-resource removal, scheduling, architecture changes, and storage tiering.

Maturity is assessed per capability and per scope, not as a single organization-wide score.

The four FinOps domains are Understand Usage & Cost, Quantify Business Value, Optimize Usage & Cost, and Manage the FinOps Practice.

Understand Usage & Cost includes capabilities such as data ingestion, allocation, reporting and analytics, anomaly management, forecasting, and budgeting.

Quantify Business Value includes capabilities such as planning and estimating, unit economics, and benchmarking that connect cost to business outcomes.

Optimize Usage & Cost includes usage optimization, rate optimization, licensing and SaaS management, and sustainability-related capabilities.

Manage the FinOps Practice includes practice operations, education and enablement, assessment, policy and governance, chargeback and showback, and automation.

A capability is a repeatable FinOps activity; each capability can be assessed for maturity independently.

Allocation assigns direct and shared costs to owners using tags, accounts, projects, or split rules; it is a prerequisite for showback, chargeback, and unit economics.

Showback reports costs to teams without billing them; chargeback actually bills or transfers costs to responsible budgets.

Unit economics compares total cost to a business metric so teams can evaluate cost efficiency rather than only total spend.

A FinOps scope defines the boundary of technology spend being managed, such as public cloud, SaaS, data center, or licensed software.

Each scope has different cost drivers, data sources, and optimization levers, but the same FinOps principles apply.

Public cloud spend is variable and usage-based; cost drivers include compute hours, storage volume, network egress, and commitment coverage.

SaaS spend is often subscription-based; cost drivers include seats, tiers, usage limits, and renewals, with focus on license utilization and contract terms.

Data center or on-premises spend includes depreciation, power, cooling, space, and support contracts, requiring asset and facilities data.

Licensed software scope focuses on contract entitlements, true-ups, renewal timing, and reconciliation of installed versus entitled usage.

Technology categories include compute, storage, network, databases, containers, serverless, analytics, and AI/ML; each has distinct cost metrics and optimization levers.

For containers and serverless, allocate shared platform costs to namespaces, workloads, or teams using metrics such as CPU, memory, requests, or execution time.

Decision rule: select allocation and optimization methods by scope and technology category rather than applying one cloud-centric method everywhere.