PHASE 03 // IMPLEMENT

recfo@implement:~/runbooks/s8-05
S8-05 · Manage the FinOps Practice · FinOps Practice Operations

Establish a Dedicated FinOps Function

Why

FinOps without a named owner stalls. A dedicated function provides the sustained focus required to maintain governance, drive optimisation, and evolve the practice. Side-of-desk responsibility absorbed by an existing team without formal time allocation produces sporadic results that fade within weeks.

What

Establish a dedicated FinOps team or named practitioner with a defined mandate, reporting line, and allocated capacity. Define the scope of the role, the skills required, and the operating model.

How

Define the FinOps Mandate

Document what the FinOps function is responsible for. A clear mandate prevents scope creep and sets expectations with stakeholders.

Responsibility AreaActivities
Cost visibilityBilling pipeline, dashboards, showback reports
Cost allocationTagging strategy, shared cost rules, chargeback
OptimisationRecommendation pipeline, savings tracking, triage
PlanningDemand intake, forecasting, budgeting, variance
GovernancePolicies, guardrails, maturity assessment
EnablementTraining, awareness, stakeholder engagement

Right-Size the Team

Cloud Estate SizeRecommended Staffing
<$1M/year1 named practitioner (can be part-time 50%+)
$1M–$10M/year1–2 dedicated practitioners
$10M–$50M/year3–5 practitioners + tooling support
>$50M/yearDedicated team with specialisations

The risk is under-staffing — a team too small for the scope burns out. Honest assessment of the estate size and the number of BUs drives the right sizing.

Define Reporting Line and Operating Model

The FinOps function should report to a leader who bridges Finance and Technology — typically CTO, VP Infrastructure, or CFO. Avoid burying it three levels deep in one department.

Operating model: hub-and-spoke works best. Central FinOps team sets standards, builds tooling, and runs governance. Embedded champions in each BU drive adoption and relay feedback.

Hire or Assign and Onboard

Key skills: cloud billing mechanics, data analysis (SQL), stakeholder communication, financial modelling basics. FinOps Foundation certification (FinOps Certified Practitioner) is a useful baseline.

Deliverable Checklist

  • FinOps mandate documented and approved
  • Team size determined based on estate assessment
  • Reporting line and operating model defined
  • Named practitioner(s) assigned or hired
  • Onboarding completed (access to billing data, dashboards, ITSM)