IT cost transparency – a decision-making capability

IT cost transparency enables organisations to link technology spend to business value, argues Chris Good.

When organisations talk about reducing technology costs, the conversation often starts in the wrong place… it starts with budgets.

• “How much are we spending?”
• “Where can we cut?”
• “Can we reduce run costs by 10%?”

Reasonable questions. But often the wrong ones. Because the more important question is:

• What does it actually cost to deliver the IT services the business depends on?

And surprisingly few organisations can answer that with confidence.

That is where IT cost transparency – often enabled through Technology Business Management (TBM) – becomes valuable. Not as a finance reporting exercise. But as a decision-making capability.

Most organisations can tell you what they spend on:

• Infrastructure
• Software licences
• Cloud consumption
• Suppliers
• People costs

But ask:

• What does our Collaboration Service cost to run?
• What is the unit cost of our End User Compute service?
• What does our Customer Portal cost per transaction?

…and the answers often become much less clear.

Costs are usually managed in silos. Budgets often sit with technology towers. And spend is visible, but service economics are not.

That creates a problem. Because businesses make strategic decisions about services and capabilities. Not about server clusters or software contracts.

The shift from cost centres to services

This is where IT cost transparency changes the conversation. Rather than viewing spend through technology components, it aligns costs to the services the business consumes. For example, instead of saying:

• £2m hosting spend
• £800k licensing spend
• £1.5m support labour.

You can say:

• Email and collaboration service costs £X per user
• Customer portal costs £Y per transaction
• End-user compute costs £Z per employee.

That is a fundamentally different level of insight. And much more useful.

What sits underneath it?

This is often where people assume TBM is complicated. It doesn’t have to be. At its core, it is simply about linking cost → service → value.

Typically, this starts by bringing together common technology cost categories such as:

• Labour (internal and third parties)
• Software and SaaS subscriptions
• Hardware and infrastructure
• Cloud consumption
• Facilities and data centre costs
• Shared support functions and tooling.

And then aligning those costs to services using defensible allocation methods.

Common methods often include:

• Consumption-based allocation – using measurable usage data:
  • Cloud spend by tagged workloadsStorage allocated by consumption
  • Licensing allocated by active users
• Utilisation-based allocation – allocating shared costs according to usage or workload:
  • Infrastructure by capacity consumed
  • Service Desk costs by ticket volumes
• Activity-based allocation – using effort or activities as cost drivers:
  • Support effort by service
  • Labour time aligned to service ownership
• Percentage or weighted allocations:
  • Using % of headcount in each business unit or location, used pragmatically where direct consumption measures are unavailable. Not perfect, but often good enough to support better decisions.

And that is usually the point. Perfection is not the goal. Decision usefulness is.

Why this matters commercially

Done well, this enables materially better decisions.

• Invest where value is clear. If a digital customer service costs £1m annually and supports £15m revenue… that is a stronger investment conversation. Not a cost-cutting discussion. A value conversation.
• Divest where value is weak. Legacy platforms often survive because their costs are hidden. Once service costs are visible, rationalisation decisions become easier. And usually less political.
• Optimise rather than blindly reduce. This is where mature organisations differentiate. They stop asking: “How do we cut costs?” and ask: “How do we improve the cost-performance ratio?” That is a very different mindset, and a better one.
• Support better business trade-offs. This is often overlooked. Good cost transparency does not just help IT decisions. It helps businesses invest, divest, consolidate, pivot and prioritise. Because the impact of those decisions becomes visible.

Where many organisations struggle

There are some common traps.

• Chasing perfect data
  • Trying to get 100% cost precision usually stalls progress.
  • Most organisations can derive significant value at 70–80% maturity.
• Over-engineering the model
  • A model nobody trusts or understands has little value.
  • Simplicity matters.
• Weak service definitions
  • If your Service Catalogue is poor, your cost model usually will be too.
  • This is often the hidden dependency.
• Treating it as a finance-only exercise
  • This rarely works.
  • Effective TBM is usually a shared capability spanning IT, finance and the business, not an isolated reporting function.
• Unclear TBM roles
  • Providing cost transparency is not a one-off activity.
  • Effective TBM requires ongoing sponsorship and management. Clear roles are required, including ownership of each data point that underpins the model.

What good looks like

In my experience, the most effective organisations:

• Start simple
• Build around business decisions, not reporting outputs
• Align to a clear service model
• Use pragmatic allocation drivers
• Iterate maturity over time
• Focus on unit economics, not just total spend
• Use transparency to drive conversations, not just dashboards.

And importantly, they use the outputs. Because visibility alone does not create value. Better decisions do.

A practical example

Consider a service costing materially above benchmark.

Without cost transparency: “IT is expensive.”

With cost transparency: “This service costs 40% above peer benchmarks due to support model and licence choices.”

Now you can act. Different conversation, different outcome.

Final thoughts

IT cost transparency is often mistaken for a financial control exercise. It is much more than that. At its best, it enables technology to be managed less like a cost centre, and more like a portfolio of business services.

And once you can connect £ → service → value, better decisions tend to follow.

That is where TBM becomes powerful.  Not in the model. In the conversations it enables.