Cloud cost visibility before cloud cost savings
There's an order of operations in cloud cost management. Trying to save before you can see is a waste of time.
The FinOps hierarchy
Level 1: You know your total cloud spend
Obvious, but 10% of teams don't. If anyone asks "how much did we spend on cloud last month," the answer shouldn't require a 3-day research project.
Level 2: You know where your cloud spend goes
Broken down by cloud, account, service. Still coarse, but visible. AWS Cost Explorer / Azure Cost Management / GCP Billing give you this for free.
Level 3: Cost is attributed to teams or applications
Via tags. Now you know which team's spend grew 20% this quarter. Most orgs plateau here.
Level 4: Cost is attributed to features or customers
"How much does feature X cost us per user?" Requires sophisticated labeling and allocation. Useful for pricing decisions.
Level 5: Unit economics
"What's our cost per 1,000 API calls?" Requires cost-per-request instrumentation. Rare outside SaaS companies with mature FinOps.
Where to start
If you don't have level 2, stop reading this and go enable cost alerts. If you don't have level 3, fix tagging. If you're at level 3, you probably have more signal than you're using — check whether team leads actually see their cost dashboard weekly.
Tools
- Cloud Tagging Compliance Tool for level 3 readiness.
- CIO Cost Dashboard Generator for level 2-3 exec reporting.