Showback — IT definition

Showback (cost transparency) is the FinOps practice of showing business units what they consume in IT and cloud cost, without proceeding to effective recharge. Unlike chargeback which transfers the financial charge, showback limits itself to pedagogy and transparency.

It is generally the first step of a mature FinOps program: make business teams aware of what they actually consume, before considering effective recharge that creates more political friction.

How showback works

Showback uses the same mechanics as chargeback:

• •Disciplined tagging: of cloud resources and SaaS subscriptions.
• •Continuous consumption measurement: .
• •Unit pricing model: per resource type.

The difference: no accounting entry is generated, no invoice is sent. Costs are published in a shared dashboard, monthly report, Slack channel — visible, without direct budget impact.

Showback vs [Chargeback](/en/glossary/chargeback) vs central allocation

The three cost-allocation models:

| Model | Effective recharge? | Transparency | Political friction | FinOps maturity | |---|---|---|---|---| | Central allocation | No | Low | Low | Low | | Showback | No | High | Low-medium | Medium | | Chargeback | Yes | High | High | High |

The FinOps Foundation explicitly recommends going through showback (6 to 18 months) before flipping to chargeback.

Why showback is powerful

Showback is often underestimated. Its power comes from several mechanisms:

• •Mirror effect: seeing costs is enough to change behavior. A team discovering it consumes €50,000 per month on a forgotten GPU cluster spontaneously turns it off.
• •Data-driven conversations: CIO and business discuss actual costs, not impressions.
• •Cultural preparation: teams get used to seeing their costs before having to pay them.
• •Anomaly detection: spikes, drifts, duplicates become visible.
• •FinOps champion identification: the most engaged teams emerge naturally.

Implementation

Typical 3 to 6 month roadmap:

1. Define perimeter: cloud first, then SaaS, then global application.
2. Implement mandatory tagging (cost center, team, project, environment, owner).
3. Build dashboards: per team, per product, per project — with drill-down.
4. Define cadence: monthly reporting published to executive committee and directions.
5. Launch a FinOps cadence: monthly cost review per direction.
6. Identify first quick wins: forgotten resources, duplicates, over-provisioning.
7. Measure impact: savings generated without recharge, simply by mirror effect.

SaaS showback

Showback naturally extends to SaaS, often one of the most dispersed spend categories:

• •Cost per active user (not per assigned license).
• •Cost per consuming direction.
• •Cost per supported business capability.
• •Comparison between tiers and features actually used.

Kabeen produces these SaaS showbacks automatically by cross-referencing licenses, seats, and real usage measured by agents and SSO.

AI showback

New 2025-2026 perimeter: showing teams their generative AI costs.

• •Costs per direction of LLM use.
• •Tokens consumed per use case.
• •API calls to Anthropic, OpenAI, Google.
• •AI agent inference costs.

Without AI showback, the cost becomes invisible and uncontrollable.

When to switch from showback to chargeback

A few switch criteria:

• •Tagging is mature (coverage rate > 95 %).
• •Dashboards have been stable and reliable for 6+ months.
• •Teams are used to discussing their costs.
• •The executive committee explicitly sponsors the program.
• •Internal accounting flows are ready (cost-center reference, recharge process).
• •First showback gains are measured and published.

Skipping directly to chargeback without a showback phase is one of the most common mistakes — and often leads to political failure.