Most cloud waste isn't technical — it's organisational. When the cloud bill lands on one central team, no one else feels it, and no one optimises. The fix isn't another dashboard; it's ownership. Done right, chargeback turns cloud cost from a monthly surprise into a shared responsibility.
Start with tags, not spreadsheets
You can't charge back what you can't attribute. The foundation is a consistent tagging policy — every resource tagged to a team, environment and cost-centre. In practice, coverage is the battle: our FinOps work (with Aquila Clouds) uses tag-policy scans to surface untagged and non-compliant resources, then bulk-remediate them.
Showback before chargeback
Don't start by billing teams — start by showing them. Showback (visibility without invoicing) builds the habit and the trust. Once teams see their own spend and trends, chargeback becomes a formality, not a fight.
Guardrails, not gates
Set per-team budgets with anomaly detection and alerts. The goal isn't to slow teams down — it's to catch a runaway spend on day one, not on the invoice. Add forecasting so budgets are set from reality, not guesswork.
Close the loop with ROI
The best FinOps programmes connect cost to value — tying spend to revenue or unit economics, so a "high" bill in a high-margin product reads very differently from waste. That's how cost governance earns a seat at the strategy table.
Takeaway: Chargeback isn't an accounting exercise — it's how you make optimisation everyone's job.