Skip to content
Back to Architecture Decisions

FinOps Practice

The organizational practice of making cloud cost everyone's responsibility, not just finance's.

Why

When cloud cost is 'finance's problem', engineers have no incentive to be economical — they provision xlarge because it's easy and never see the bill. FinOps is the practice of giving engineers cost visibility and accountability: per-team cost dashboards, cost-as-a-metric in PR reviews, and budgets that trigger alerts. Teams with a FinOps practice spend 20-40% less at the same output because the people making the spending decisions are the people seeing the cost. It's a culture change, not a tool, but the tools make the culture possible.

When

Once monthly cloud spend > $5k and growing. Setup takes 1-2 weeks. Skip for small static deployments.

How

1. Tag every resource with team + env + project (enforce via policy)
2. Build per-team cost dashboards (Cloud Billing → BigQuery → Looker)
3. Set per-team monthly budgets with 80% → warning, 100% → page the team lead
4. Add a cost-delta check to PRs that touch infra (Terraform plan cost estimate)
5. Hold a monthly cost review with each team lead — they own their spend
6. Share a company-wide cost summary so teams see their relative spend
7. Celebrate teams that hit cost-reduction targets, not just feature targets

Example

Team cost dashboard (monthly):
  payments-team:   $4,200 (budget $5k)  ✓ 84%
  growth-team:     $7,800 (budget $6k)  ⚠ 130% → page lead
  platform-team:   $3,100 (budget $4k)  ✓ 78%

PR cost check (Terraform):
  "This plan adds 2x r5.2xlarge → +$620/mo. Approve? [y/n]"

Monthly review: growth-team explains spike (new A/B test infra),
  agrees to right-size or raise budget with justification.

Common Problems

  • ⚠Dashboards that nobody looks at — visibility without accountability changes nothing; pair every dashboard with a review meeting.

Best Practices

  • ✓Make the cost dashboard one click from the team's main Slack channel — friction kills visibility.
  • ✓Tie a portion of team OKRs to cost-efficiency (output per dollar), not absolute spend — absolute budgets punish growth.

Related Resources