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 analyze and report; cannot also evangelize and automate. The work splits naturally into three roles.
Without the split, savings cap at what one person can negotiate per quarter.
The three roles
- Advocate, partners with engineering teams; coaches; surfaces wins.
- Analyst, sees the bills; finds the savings.
- Automator, builds the tooling that makes savings durable.
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.