Make it stick
You found $200,000 in savings last quarter. Congratulations. Now ask yourself: what prevents the same waste from accumulating again next quarter? The Operate phase answers that question. It is about embedding FinOps practices into the daily rhythm of the organization so that cost efficiency is not a periodic cleanup project but a continuous operational discipline.
Key Activities in the Operate Phase:
1. Automation and Governance as Code
Manual cost reviews do not scale. The Operate phase implements policies that enforce cost hygiene automatically:
- Scheduled shutdown scripts that stop non-production environments outside business hours.
- Cloud Custodian or AWS Config rules that flag or terminate resources missing required tags.
- Budget alerts that trigger Lambda functions to notify teams or even throttle resource creation when spend thresholds are breached.
- Infrastructure as Code (IaC) guardrails that prevent engineers from deploying instance types above a certain size without an approval workflow.
2. Unit Economics and Continuous Improvement
Rather than tracking raw dollar spend (which grows as the business grows), mature FinOps teams track unit economics — the cost per meaningful business outcome:
- Cost per active user per month
- Cost per 1,000 API calls
- Cost per GB of video transcoded
- Cost per order processed
Unit economics decouple cost from growth. If revenue doubles and cloud spend doubles, that might be perfectly acceptable. If revenue doubles but cost per transaction also doubles, that is a problem.
3. Cloud Center of Excellence (CCoE) and Cadence
The Operate phase institutionalizes a regular meeting cadence — typically weekly or bi-weekly — where representatives from Engineering, Finance, and Product review cost anomalies, track optimization commitments, and assign ownership of new findings. This is the organizational heartbeat of FinOps.
Goal of the Operate Phase: Execute the processes that achieve the goals of technology, finance, and business teams simultaneously — not sequentially, not in conflict.
A common interview question is: "How do you prevent FinOps from being a Finance team problem that engineers ignore?" The answer is the Operate phase: you make cost a first-class engineering metric by embedding it in dashboards engineers already use (Grafana, Datadog), alerting in channels engineers already monitor (Slack, PagerDuty), and tying it to OKRs engineers are already measured on. Cost awareness must live where engineering work lives.