A complete framework for implementing FinOps across AWS and Azure environments — from team design to CI/CD integration.
Most enterprises have cost dashboards. Few have cost culture. The gap between seeing cloud spend and acting on it is organisational, not technical — and closing it requires a structured operating model, not more tooling.
This blueprint documents the FinOps operating model we've implemented across four multi-cloud enterprises, achieving average cloud cost reductions of 35–45% within 18 months without sacrificing engineering velocity.
Authors: CELESDEV Solutions — FinOps Practice.
Applicable contexts: Multi-cloud enterprises on AWS + Azure; engineering organisations of 50–5,000 engineers; organisations targeting FinOps Foundation maturity levels Crawl → Walk → Run.
Full document includes Terraform modules for tagging enforcement, Grafana dashboard templates, Jira story templates, and a detailed 90-day FinOps adoption roadmap. Available on request.
Expected outcome: Organisations completing all three phases typically achieve 15-25% cloud cost reduction within the 90-day window. The remaining 20-30% reduction comes in months 4-18 as Reserved Instance coverage and engineering culture changes compound.
| CAPABILITY | CRAWL | WALK | RUN |
|---|---|---|---|
| Tagging coverage | < 50% | 50-85% | > 95% |
| Team attribution | Account-level | Team-level | Service-level |
| CI cost gates | None | Informational | Blocking |
| RI/SP coverage | < 20% | 20-60% | > 70% |
| Rightsizing | Manual, ad hoc | Monthly reviews | Automated |
| Cost culture | Finance-owned | Shared with eng. | Eng. accountable |
Score each capability from 0-3 (Crawl=1, Walk=2, Run=3). A total score below 10 indicates Crawl overall maturity. 10-15 is Walk. 16+ is Run. Reassess every 90 days and publish scores to engineering leadership.