IT showback
IT showback is the gentlest form of cost allocation. It shows business units what they consume without moving the bill. The goal is transparency and behavior change, not budget transfer.
How showback works
Every month, each team receives a report: their cloud spend, broken down by service, project, and environment. The central IT budget still pays the provider, but the team now sees its footprint. Over time, this creates the cultural conditions for optimization.
When showback is the right choice
- Early FinOps maturity. Your organization is just starting to think about cloud cost accountability.
- Untrusted data. Tagging and attribution are new; you need time to clean them.
- Shared services. Some costs are genuinely hard to assign precisely.
- High political sensitivity. Charging teams directly would create friction before the value is proven.
How to implement showback
- Tag every resource with team, project, and environment.
- Build a dashboard or report that allocates spend by tag.
- Distribute the report monthly at first, then weekly as maturity grows.
- Pair the report with education: explain what drives the numbers and how teams can influence them.
From showback to chargeback
Showback is usually a stepping stone. Once teams trust the data and have learned to act on it, the most controllable services can move to chargeback. For the full comparison, see showback vs chargeback.
What belongs in a showback report?
A report that only shows a number gets ignored. A report teams act on contains four things:
- Spend with a comparison — this month against last month and against budget. An absolute number carries no signal.
- A unit metric — cost per request, per customer, or per deploy. Teams that ship more should spend more; unit cost is what tells you whether that is happening efficiently.
- The top three drivers — the specific services or workloads behind the change, not a full inventory.
- One action — a named, concrete thing the team can do this month. Without it, the report is trivia.
How long should showback run before chargeback?
Long enough that teams stop disputing the data, typically two to three reporting cycles. The signal to move is behavioral: when teams start asking for their numbers before you send them, and when challenges shift from "this allocation is wrong" to "this allocation is right and we want to reduce it," the data has earned enough trust to carry money.
Does showback actually change behavior?
Only when it reaches the person who can act. A report addressed to a director who does not choose instance types or model tiers produces agreement and no change. Send it to the engineering team that owns the service, and copy the budget holder — visibility works through the owner, not the org chart.
Want this applied to your own LLM spend? FinOps LLM runs a free audit of your AI costs and shows where the savings are. Book free audit →
FAQ
What is IT showback?
IT showback is a cost allocation model that reports technology spending to business units without actually charging them. It creates visibility while keeping the central IT budget intact.
When should you use showback?
Use showback when you want to build cost awareness and accountability before moving to chargeback. It is ideal for early FinOps journeys and shared services.
How do you move from showback to chargeback?
Move to chargeback once tagging is trusted, teams understand their spend, and leadership is ready to transfer budget ownership for controllable services.