2 min lesson
Showback vs. chargeback and why cloud FinOps breaks here
Think through this situation: "In the domain round you're asked to design cost attribution for inference. Why might you recommend starting with showback rather than chargeback?" Give the practical answer in plain words.
Step 1 of 2
Showback vs. chargeback and why cloud FinOps breaks here
- Showback reports each team's cost without billing them - it builds awareness and surfaces waste with low political friction. Chargeback actually allocates the cost to a team's budget, which changes behavior but invites fights over the allocation rules.
- Traditional cloud FinOps assumes stable, taggable resources. AI workloads are dynamic and experimental: training and eval runs spike, a single agent request fans out across many model calls and shared model endpoints make per-team attribution genuinely hard.
- R&D spend (training, experimentation) is an investment that shouldn't be charged like production COGS. Separating R&D from production inference is half the battle in any honest attribution model.
When they ask you to design attribution live, start with showback and a clear unit metric (cost per inference, cost per active user) before reaching for chargeback. Say why: showback gets you trustworthy data and behavior change with far less political cost and you can graduate to chargeback once the allocation rules are battle-tested. Sequencing the rollout is the senior move.
These rounds are run by people who serve models for a living. If you don't know a number, reason from first principles out loud and say what you'd measure to confirm. A confident wrong figure is worse than “I'd validate utilization against the dashboard before committing - but if it's near 25%, here's the implication.”