What this tier actually looks like.
The CFO has a cloud-cost dashboard. The CIO presents trend slides quarterly. Per-team cost is visible somewhere — but nobody on the engineering team looks at it before designing the next service. Anomalies get flagged a week after they happen.
You probably have:
- A FinOps function (sometimes one person, sometimes embedded in finance).
- Tags applied to most resources (some, somewhere — consistency varies).
- A cost dashboard visible to engineering leadership.
- Some commitment coverage (Savings Plans, Reservations, CUDs) — set long ago, not reviewed.
- Lifecycle policies on storage if you’re lucky; default-hot if you’re not.
- Annual cost reviews where the answer is “we’ll do better next year.”
Why most teams get stuck here.
Aware-tier orgs typically stall because they treat cost as a finance problem. Three patterns that keep teams here:
- Cost dashboards no engineer opens. Visibility without point-of-decision visibility doesn’t change architecture.
- Commitment coverage set-and-forget. A 3-year commit made 2 years ago at a different scale is now over- or under-coverage. Both leak money.
- Idle waste invisible. Unattached disks, orphaned snapshots, dev environments running 24×7 add up to 5-15% of cloud bill and require zero architectural change to fix.
The substrate move is changing where the cost signal lives: out of finance’s monthly report, into the engineer’s daily flow.
The three substrate moves to the next tier.
1. Per-service cost in the developer’s daily view.
Wire per-service cost into Backstage / Cortex / Slack / wherever engineers already look. OpenCost, Kubecost, CloudHealth, Vantage all do this.
2. Commitment coverage on a quarterly review cadence, target 70-90%.
FinOps Foundation guidance. Coverage above 70% buys 15-25% off on covered usage. Below 50%, you’re leaving real money on the table. Above 90%, you’re locked into the current spend shape; risky for orgs anticipating growth or divestiture.
3. Named owner per service spend. Cost regressions become incidents.
Every service has an owner attached to its monthly spend. Cost spike > 30%? Owner-alert, expected-response SLA, postmortem if not resolved within 48 hours. Cost becomes a reliability metric, not a finance ask.
What changes when you cross.
- Architecture choices change at design time. Engineers see cost-of-this-design before they ship.
- Commitment portfolio breathes with growth. Quarterly review replaces annual forgetting.
- Idle waste drops to noise level. Auto-quarantine after grace period eliminates 5-15% of bill.
- You move from 5-12% YoY savings to 20-35% from baseline. This is the Controlled tier.
The Cloud Commitment Optimiser calculator is the tool for tuning the second move. The GenAI Cost-Per-Outcome calculator is the one to add when AI inference becomes >5% of cloud spend.
Run the diagnostic.
To find out whether your team scores at this tier or another, run Cloud Cost. It takes 2–4 minutes and surfaces both your overall tier and the capability breakdown that shows you where the move starts.
For the bigger picture: the compound diagnostic takes results from all six diagnostics and shows you the substrate gap that bounds your overall delivery, not the per-discipline symptom.