The gap between what you own and what you use and why it’s blowing up your cloud spend
Many organisations still talk about ITAM and FinOps like they’re separate projects. In reality if you’re serious about cloud in 2026, they’re the same conversation – how do we line up what we planned to spend with actual consumption, without unnecessary vendor cost or surprise audits.
What are we really talking about?
If we strip the buzzwords out, ITAM is everything to do with what you own and what you are entitled to use – licences, contracts, SaaS, hardware and more and whether you remain compliant and pay a sensible price. FinOps is everything to do with how you consume cloud and the value you receive in return, including which teams are driving spend, how efficient they are, and whether anyone is actively steering that consumption.
Same money, different angles. ITAM grew up around true‑ups and licence audits and FinOps grew up around variable cloud bills and teams shipping features at speed.
In most organisations, those two worlds barely talk ,which in our experience is where waste creeps in.
Where ITAM and FinOps overlap and why it matters
FinOps focuses on the cloud cost profile – instance sizes, reservations, storage choices, autoscaling, anomaly detection. But a big chunk of that spend is really software cost delivered via cloud services, such as databases, operating system licences, middleware and security tools.
This is where ITAM becomes critical – when FinOps enables Azure “Hybrid Use Benefit” to secure 10–44% discounts, ITAM must validate that the required Windows and SQL licences are in place, and when FinOps rightsizes or decommissions workloads, ITAM must record those changes so the organisation stops paying for licences it no longer needs and avoids creating noncompliance elsewhere.
Real Insight becomes real world, bankable reductions
In SCC engagements, this is exactly how we connect the dots – FinOps Services surface where the cloud estate is inefficient; SAM & Licence Review and 365/SaaS Optimisation turn those insights into real, bankable reductions in licence and SaaS spend as well.
Licence management and true‑up
True‑ups used to be mostly an on‑prem story. Now the same entitlement might be:
- Partially on physical kit
- Partially in IaaS/PaaS
- Partially delivered as SaaS
If you don’t connect the dots, you pay three times – in cash or in risk. SCC is often called in when a vendor drops a six‑ or seven‑figure claim on a customer’s desk, based on a shaky view of what’s actually deployed.
ITAM’s job is to build the Effective Licence Position and fight back where the numbers don’t stack up; FinOps’ job is to plug in actual cloud consumption, so that position reflects reality rather than guesswork. SCC’s Audit Defence, Critical Application Licence Review and ITAM health checks are designed to do that quickly before renewal or audit deadlines bite.
Chargeback, showback and unit economics
Most of us have seen cloud spend by subscription dashboards that tell you nothing politically useful. FinOps tries to fix that with showback/chargeback carving costs up by product, app or environment.
ITAM adds the other half of the picture:
- Which licences and SaaS contracts sit behind those services
- When they renew
- Where you’ve over‑ or under‑bought
Once you join that up, you can talk proper unit economics – £1 of platform X equals Y customer actions, and here’s the mix of cloud + licence cost behind it. That’s the level CFOs and product owners actually understand.
SCC’s FinOps Services focus hard on that unit view, while Enterprise Service Management and ITAM Maturity work ensure the data and processes underneath aren’t made of spreadsheets and hope.
Where they diverge and why you still need both
Even with all that overlap, ITAM and FinOps are not the same job.
ITAM is risk and controloriented, focusing on license compliance, audit defense, vendor terms and conditions and shadow IT from a licensing and security perspective, working to contract cycles, hardware refreshes and software lifecycles, whereas FinOps is behavior and efficiencyoriented, influencing engineering and product teams to design and operate services in a costconscious way, working to agile sprints and continuous optimisation cycles.
You don’t want to mash those into one overloaded, generic role. The pattern we have seen across many organisation is – the on‑prem ITAM person is now also the FinOps person – this can be high‑risk for exactly that reason.
Bridging strategy and spend is about creating deliberate hand‑offs:
- FinOps spots a cluster that’s massively over‑provisioned; ITAM translates that into concrete licence changes and a negotiation stance at renewal.
- ITAM sees a big Oracle, Microsoft or Adobe renewal coming; FinOps models what moving pieces of that footprint to cloud, SaaS or alternative services would actually do to run‑rate and unit economics.
SCC’s model builds those hand‑offs into how services are delivered: ITAM, FinOps and Managed Services working off the same data and playbook rather than lobbying the customer separately.
What are their roles in your cloud migration journey?
If we walk a typical cloud migration from left to right, there are a few obvious points where ITAM and FinOps should be joined at the hip.
1. Before you move anything – baseline and plan
Most organisations bring help in when something’s already gone wrong – an ugly audit, a runaway Azure bill, or a renewal that’s jumped from £3m to £5m with no clear “why”.
A better pattern is:
- ITAM baseline: what do we actually own, what do we use, what’s critical, and what licence rights can we carry into cloud or trade away? (SCC uses ITAM Maturity assessments, SAM & Licence Review and Critical Application Licence Review here.)
- FinOps baseline: what’s our cost and value model for the target state – budgets, tags, guardrails, KPIs like cost per user or cost per transaction. (SCC’s FinOps Services design and implement that.)
Put that together and cloud migration planning stops being lift‑and‑shift plus hope, and becomes a portfolio exercise – this app moves as‑is, this one gets modernised, this one gets killed, here’s the cost/licence story in each case.
2. During migration: control shadow IT and sprawl
As you move, you’ll uncover three uncomfortable truths:
- You have more SaaS than anyone realised.
- Not all of it is sanctioned.
- A fair chunk is under‑used or duplicated.
ITAM’s job is to shine a light on that – discover shadow IT, clean up 365 entitlements, rationalise overlapping tools. FinOps’ job is to surface the cost of those decisions in the cloud and SaaS bills, and challenge the “we must be using it if we’re paying for it” assumption.
SCC’s 365/SaaS Optimisation and health check style advisory pieces are designed as quick, low‑friction door‑openers at this point – small engagements (often sub‑£10k) that land tangible savings and build trust before you get into bigger managed services conversations.
3. After migration: run, optimise, defend
Once you’re firmly in the cloud, two things tend to happen:
- Cloud costs creep up; people shrug and call it “the new normal”.
- Vendors quietly tighten licensing rules and increase audit activity, especially around blended on‑prem/cloud rights.
This is where an ongoing, joined ITAM/FinOps practice pays for itself:
- FinOps keeps tuning – anomaly detection, right‑sizing, commitment management, chargeback/showback, unit economics.
- ITAM keeps you out of trouble – tracking rights, defending audits, leveraging renewals, keeping the configuration and entitlement data clean.
On SCC side, that’s typically wrapped as Managed Services across ITAM and FinOps, with Enterprise Service Management underneath to keep process and data flows sane rather than spreadsheet‑driven.
Why bring SCC into this?
If you and I were having this conversation in a meeting room, the honest summary would be:
- If you’re not taking ITAM and FinOps seriously, and not joining them up, you’re almost certainly wasting serious money and carrying avoidable risk.
- Internal “side of desk” effort and a tool alone won’t fix it; both disciplines are now too specialised, and the cloud/licensing mix too messy.
SCC’s value here is pretty straightforward:
- Deep ITAM and FinOps expertise: people who live in licence terms and cloud bills all day, and know where the traps and quick wins are.
- A joined‑up service catalogue: Enterprise Service Management, Audit Defence, SAM & Licence Review, ITAM Maturity, 365/SaaS Optimisation, FinOps Services and Managed Services designed to interlock, not compete.
- The ability to execute: not just advice, but hands on keyboard – configuring tools, cleaning data, negotiating with vendors, and sitting with your teams as they change how they design and run services.
Bridging strategy and spend isn’t a slide; it’s a discipline. If your cloud story is growing faster than your control story, now is the moment to get ITAM and FinOps in the same room – and, ideally, backed by a partner that knows how to run both.