Ask an ITAM lead and a FinOps lead what they are responsible for, and the answers are starting to overlap. Industry surveys over the past year point the same way: asset managers are increasingly pulled into cloud cost decisions, and cloud cost teams are increasingly pulled into licensing ones. SaaS sprawl and hybrid licensing have made it hard to draw a clean line between the two disciplines.
That overlap is not a problem in itself. The problem is that in most organisations it has no owner. Two teams have drifted into shared territory without anyone deciding how that territory should be governed.
The same estate, seen from two sides
An ITAM function is built to answer questions about entitlement: what do we own, what are we using, and are those two numbers consistent. A FinOps function is built to answer questions about consumption: what are we spending, where, and could we spend less. Both are valid lenses. Neither shows the whole estate.
Consider a workload that can run on licences the organisation already holds, or on licences bundled into a cloud rate. Choose the cloud rate when owned licences were available and the bill is higher than it needed to be. Choose the owned licences when the entitlement doesn't actually extend to that environment and the organisation is exposed at its next audit. The decision sits exactly on the boundary between the two teams, and each of them holds only half the information needed to make it. Separate tools, separate registers and separate review cycles make sure it stays that way.
Two sets of strengths, no shared framework
What makes this worth solving is that the two functions have exactly what the other one is missing.
ITAM brings process. Years of audit pressure have produced documented workflows, clear accountability models, evidence standards and a steady rhythm of reviews and policy updates. Cloud teams, which grew up moving fast, have rarely had to build any of that. FinOps brings numbers. Consumption data, allocation logic, anomaly detection and unit economics give a level of financial precision that traditional asset management has never had.
Put together, that is a complete governance capability. Kept apart, it is two partial ones, each with its own operating model, its own KPIs and its own version of the truth when finance asks what the technology estate actually costs.
One estate, one program
This is the premise SofClo is built on. Software, hardware, cloud and AI are one technology estate, and governing it is one problem. So we run ITAM, FinOps and AI governance as a single Tech Value Program rather than as parallel initiatives.
In practice that means four phases that both disciplines move through together.
In Program & Plan, the program gets one vision, one set of SMART goals and KPIs, and one roadmap. Maturity is assessed against the SAM, HAM and FinOps frameworks side by side (ISO 19770, IAITAM and the FinOps Foundation Framework), so a Crawl-Walk-Run rating in licence compliance sits next to the equivalent rating in cloud allocation or rate optimisation. You can see, in one view, where the estate is strong and where it is exposed.
In Operating Model, the team structure, stakeholder tiers and service catalogues for SAM, HAM and FinOps are defined once. The ITAM manager, the cloud platform owner, procurement and finance appear in the same stakeholder matrix, not in two org charts that never meet.
In Optimization, Policy & Process, the governance muscle ITAM already has becomes shared infrastructure. A single RACI Matrix assigns who is responsible and accountable for licence reconciliation, contract renewals, cloud cost allocation and anomaly response. The Document Builder and Workflow Builder produce the policies, playbooks and processes for both disciplines from the same library. And the Cost Optimization Tracker records every saving, hard or avoided, in one ledger regardless of whether it came from a rightsized instance or a renegotiated ELA.
In Commercial, Compliance & Risk, the two registers finally sit next to each other. Software vendors and agreements, cloud vendors and commitment inventory, sub-account ledgers, cost anomaly workflows, and audit risk and ELP exposure all live in one place, on one Annual Wheel of renewals and commitments. That is where the licensing-versus-cloud-rate question stops being a hand-off between two teams and becomes a single decision with a single owner and a single piece of evidence behind it.
What changes when you run it this way
The immediate change is visibility: the same underlying data serves the analyst, the program lead and the executive, without duplication. The deeper change is accountability. When every agreement, commitment and cost line has an owner, and every process has a RACI behind it, the question “who decided this?” always has an answer. That is what audit-ready looks like, and it is also what negotiating from data rather than instinct looks like.
The overlap between ITAM and FinOps is only going to grow. The organisations that will benefit are the ones treating them as one program with one governance model, one value ledger and one set of accountabilities.
That is what a Tech Value Program is for.