// Definition
A FinOps team is the function responsible for cloud financial management — cost visibility, allocation, optimization strategy, committed purchase management, and the governance framework that sustains these practices. It bridges engineering and finance, translating cloud billing data into decisions that both teams can act on.
// Why It Matters
Structure varies by organization size and cloud spend. At Crawl stage: one person, part-time, typically a cloud architect or engineering manager. At Walk: 2–4 dedicated practitioners with a mix of technical and financial backgrounds, reporting to a VP of Engineering or CTO. At Run: a central FinOps function plus embedded FinOps practitioners in major engineering domains.
The FinOps Foundation defines three core personas: FinOps Practitioner (owns the practice), Engineering/Operations (implements optimizations), and Finance/Business (owns budget accountability). A functional FinOps team requires representation from all three, even if the "team" is one person wearing multiple hats early on. See our full FinOps team structure guide.
// In Practice
Example: A company at $3M/year cloud spend builds a three-person FinOps team: a FinOps lead (ex-cloud architect, owns technical optimization and tooling), a cloud financial analyst (owns reporting, forecasting, and finance liaison), and a platform engineer (implements tagging enforcement, pipeline cost gates, and automation). The team reports to the VP of Engineering and meets monthly with the CFO.