FinOps Team Charter: The Three Roles That Make a Program Work
Most FinOps programs are one engineer with a spreadsheet. The role split below is the difference between $100k and $5M of savings per year.
Why one person fails
One person can analyse and report; cannot also evangelise across teams and build automation. The work splits naturally into three distinct roles. Without the split, savings cap at what one person can negotiate per quarter.
- Analysis is full-time. Reading bills, finding savings, modelling reservations; one full-time job at any cloud bill above $1M/year.
- Evangelism is full-time. Partnering with engineering teams, coaching, surfacing wins; relationship work that does not scale alongside analysis.
- Automation is full-time. Building the tooling that makes savings durable; without it, savings reverse as soon as attention shifts.
- The cap. One person doing all three caps savings at $100k/year; the three-role split unlocks $5M+/year at scale.
The three roles
The role split is structural, not seniority-based. Each role demands different skills; each fills a gap the other two cannot. Below are the three roles and what each owns.
- Advocate. Partners with engineering teams; coaches on cost-aware design; surfaces wins to leadership; the relationship layer.
- Analyst. Sees the bills; finds the savings; models reservations and savings plans; the analytical layer.
- Automator. Builds the tooling that makes savings durable; right-sizing automation, anomaly detection; the engineering layer.
- The composition. Three FTEs; each role co-equal; together they produce the savings number that justifies the team.
Org placement
Report into engineering, not finance. Engineers respect engineers.
Quarterly readouts to finance for visibility; weekly work with engineering for execution.
Year-one scope
Year one: cut 15-25% of cloud spend. Year two: institutionalize so savings hold without heroics. Year three: cost-aware engineering culture.
Antipatterns
- FinOps as part-time finance role. Misses the engineering culture work.
- One person owns everything. Bus factor 1.
- Reporting to CFO. Engineering ignores.
What to do this week
Three moves. (1) Apply this lever to your highest-spend workload. (2) Measure the dollar impact for one month. (3) Roll the practice out to the next two services if the savings hold.