FinOps meets ITSM: from service management data to cloud and AI cost control

Cloud and AI application consumption costs represent one of the primary concerns for an organisation’s leadership. FinOps, which manages the cost and value of technology spending, appears with increasing frequency in conversations about ITSM. This convergence — the coming together of those who manage technology costs and those who manage IT services — remains, however, little explored from a service management perspective.

Most organisations treat cost control as a separate financial exercise, conducted through billing statements and spreadsheets. Yet the data that would allow spending to be linked to business services and their owners already exists within service management systems.

In this article, we explain how CMDB, asset inventory, service catalogue, and request and change logs can become the foundation of credible cost governance. And we demonstrate why collaboration between FinOps and ITSM is beneficial in both domains.

Why FinOps and ITSM are converging

FinOps was born as a public cloud cost management practice, but its scope has expanded rapidly. According to the ITSM.tools analysis dedicated to the FinOps Foundation’s State of FinOps 2026 report, 98% of surveyed organisations now manage artificial intelligence spending, compared to 31% just two years ago, while 90% manage or plan to manage SaaS spending within the year. A growing number of companies also oversee licences, private cloud, and data centres.

For those working in service management, however, the most relevant point in the report is a different one: ITSM is explicitly identified among the operational domains with which FinOps teams collaborate, alongside IT financial management and asset management. Collaboration is increasingly oriented, among other things, towards automation and the implementation of remediation actions.

FinOps and ITSM are drawing closer because they address the same problem from different angles: the former quantifies spending, the latter possesses the processes and contextual data. FinOps needs operational processes to act, while ITSM rarely connects its processes and data to the economic dimension.

The problem: growing spending, unclear attribution

Cloud and AI spending is growing in absolute terms, but in most organisations no one can say precisely which service, project, or organisational unit generated each cost item. Consumption attribution remains approximate, and even weaker is the link between the spending incurred and the value produced by the services to which that spending is directed.

The State of FinOps 2026 report highlights a dynamic that makes the problem particularly urgent: many organisations are asking their teams to fund AI investments through savings achieved via spending optimisation, precisely as the most significant savings opportunities are being exhausted. When asked whether AI investments are generating value, the report observes, almost no organisation today is able to answer.

Without reliable attribution of costs to different services and their owners, spending governance is reduced to a continuous negotiation over budgets, conducted without shared data. With reliable attribution, every discussion can start from a factual basis: which service generates a given consumption, for what amount, for the benefit of which organisational unit, and with what return.

The data IT already possesses

The data needed to attribute cloud and artificial intelligence costs to the services and organisational units that generate them already exists, and resides in the service management systems that IT uses every day.

CMDB and asset inventory: linking spending to services

The CMDB — the database that describes the components of the IT environment and their relationships — contains the map that does not appear in cloud provider billing reports: for each technology resource, the service it supports is indicated; for each service, the responsible owner is identified.

Linking cloud and AI consumption data to CMDB entries means transforming an undifferentiated list of costs into a distribution of spending by service and by organisational unit. The asset inventory adds to this information data on licences, contracts, and expiry dates, which make it possible to identify paid but unused resources, overlaps between tools, and renegotiation opportunities.

For the link between consumption data and the CMDB to work, the database must be kept up to date and cloud resources must be tagged according to uniform naming rules established at the organisational level. This is an organisational requirement before it is a technical one, and compliance can be ensured by ITSM change management processes: every new resource introduced into the environment is registered and correctly tagged as part of the process itself.

Service catalogue and request workflows: governing provisioning

When the activation of new cloud resources or new AI services passes through the service catalogue and the related request and approval workflows, every future consumption is authorised, justified by a documented need, and traceable to a service.

Provisioning — that is, the allocation of resources — ceases to occur through direct purchases by individual teams on provider consoles, outside of central control, and becomes a governed process: with spending thresholds that require additional approvals, predefined durations beyond which the resource is reviewed, and the automatic recording of the requester and the justification for each activation.

The same workflows can manage the reverse cycle, namely the decommissioning of resources that FinOps analyses identify as underutilised: the savings recommendation becomes a tracked change request, with an owner and a deadline.

ITSM as the system of record for operationalising FinOps

In essence, ITSM can be the system of record that operationalises FinOps recommendations. FinOps teams excel at identifying what should change (resources to decommission, infrastructure to right-size, tagging rules to enforce), but implementing these changes requires structured operational processes — and this is precisely what service management does: open a request, assign it, approve it, execute it, verify it, and document it.

The benefit is mutual. FinOps teams gain assurance that their recommendations are actually put into practice: every action identified by the analyses is entrusted to service management processes, which ensure its execution, verification, and documentation, and prevent savings recommendations from going unactioned.

When the cost per service is visible and up to date, value demonstration and spending control reinforce each other: every budget conversation becomes a conversation about services, with data that both parties recognise. The State of FinOps 2026 report offers a telling organisational indication in this regard: 78% of FinOps teams now report to the CTO or CIO, and teams that engage with senior leadership exert two to four times greater influence over technology purchasing decisions.

Cost management as a shared responsibility

The convergence concerns organisational culture before it concerns tools. As long as cloud and AI spending control remains confined to a financial function and consumption is observed from the outside, resource attribution will remain approximate and corrective actions will arrive late. When, on the other hand, service management data feeds cost analysis, and service management processes promptly implement corrections, cost management becomes a shared responsibility of service management. For IT leaders, the starting point is immediate: a well-maintained CMDB, a comprehensive service catalogue, well-designed request workflows. Technology spending governance is made of the same data and the same processes that service management produces every day.

FAQs

1. What is FinOps and why does it concern ITSM?
The term “FinOps” refers to the set of practices through which an organisation manages the cost and value of its technology spending: born for the cloud, it has extended to AI, SaaS, and licences. It concerns ITSM because service management is among the primary areas of collaboration, particularly for the operational implementation of remediation actions.

2. How does the CMDB support cloud and AI cost control?
The CMDB links resources, services, and owners: by combining this data with billed consumption, generic spending becomes a distribution by service and by organisational unit, on which to base decisions and accountability.

3. How is provisioning controlled through ITSM workflows?
By requiring that the activation of cloud resources and AI services occurs exclusively through the service catalogue, with mandatory approvals, spending thresholds, and predefined durations. Every consumption is thus born authorised, justified, and traceable to a service.

4. What benefits does ITSM gain from collaboration with FinOps?
The ability to demonstrate the economic value of managed services, thanks to visibility into the cost per service, and greater relevance with senior organisational leadership.