If you work in ITAM, FinOps is less of a leap than it looks. Both disciplines share the same core goals: visibility, cost control, and business value; just applied to different environments. This article walks through our See, Save, Plan, Run framework for cloud cost management and shows how your existing ITAM instincts translate directly into FinOps practice.
If you work in IT Asset Management, you already know this feeling. A new technology wave arrives, there’s a new framework for it, and suddenly there is pressure to learn an entirely different discipline. Just when you have ITAM running well, the conversation shifts to FinOps, and it can feel like starting from scratch.
Here is the thing: you’re not starting from scratch! Not even close.
FinOps and ITAM share the same foundation. Both are about knowing what you have, understanding what it costs, eliminating waste, and making sure the business gets real value from its technology investment. Only the context is different: cloud instead of on-premise hardware and software. But the instincts that make a good ITAM professional are exactly the instincts FinOps requires.
This article is not about convincing you to abandon what you know. It is about showing you how much of it already applies.
FinOps, short for Financial Operations, is the practice of bringing financial accountability to cloud spending. It connects the teams who consume cloud resources with the teams who manage budgets, so that everyone is working from the same picture and making informed decisions together.
The FinOps Foundation, the industry body that defines and certifies the practice, frames it as a cultural shift as much as a process change. You are not installing a tool. You are building a discipline, one that helps your organisation get genuine business value from every euro it spends in the cloud.
If that sounds familiar, it should. ITAM professionals have been doing exactly this for years: tracking assets, attributing costs, enforcing governance, and bridging the gap between IT consumption and business value. FinOps applies that same logic to a billing model that charges by the second instead of by the license or device.
Traditional IT infrastructure had a certain predictability to it. You bought hardware, depreciated it over several years, and knew roughly what your costs would look like. Software licenses were procured, tracked, and renewed on a defined schedule. ITAM existed precisely to bring order and visibility to that cycle.
Cloud changed the rules. Billing now happens by the second, across hundreds of service types, consumed by dozens of teams, without purchase order, without delivery note. Environments can scale up instantly. And just as easily forget to scale back down. Resources can be created by an engineer at 11pm on a Friday and forgotten by Monday morning, still running, still billing.
The pain points that emerge are ones ITAM professionals will recognise immediately:
These are not new problems. They are the same problems ITAM was built to solve, showing up in a new environment. FinOps is the framework that addresses them in the cloud context.
To make FinOps practical and actionable, we organise cloud cost management into four core capabilities. As you read through them, notice how closely each one mirrors established ITAM practice.
In ITAM, the discovery and inventory phase always comes first. You can’t manage assets you can’t see, and you can’t report on costs you can’t attribute. FinOps starts from exactly the same principle.
Visibility in FinOps means attributing cloud costs to specific teams, products, projects, and environments. The primary mechanism is tagging: adding metadata to cloud resources so that spend can be mapped back to the business unit or workload generating it. Think of it as the cloud equivalent of asset registers and cost centre allocation: the same logic, but applied to infrastructure that bills dynamically.
We have seen organisations skip this step and go straight to cost-cutting. It almost always creates friction. Teams resist optimisation they don’t understand, and finance can’t validate savings they can’t trace. Start with See, and everything downstream becomes easier.
In practice, this means:
Any ITAM professional who has run a license reconciliation knows what happens when visibility improves: waste surfaces quickly. Shelfware, duplicate tools, unused installations — they appear the moment you look carefully enough. Cloud is no different.
Once you have visibility into cloud consumption, idle resources, oversized instances, forgotten storage volumes, and services running at a fraction of their capacity become obvious. Common optimisation levers include rightsizing compute resources to match actual usage, cleaning up resources attached to nothing, and shifting stable workloads from on-demand to reserved pricing.
The goal here is not to spend as little as possible. It is to spend appropriately: matching cloud resources to real demand, and eliminating the costs that deliver no business value. ITAM calls this optimisation. FinOps calls it Save. The outcome is the same.
Bottom line: visibility without optimisation is just reporting. Optimisation without visibility is guesswork. You need both, in that order.
ITAM teams are no strangers to forward planning. True-up cycles, renewal calendars, volume licensing negotiations — all of it requires a clear picture of current consumption and confidence in future demand. FinOps operates on the same logic.
Cloud providers including AWS and Azure offer sizeable discounts in exchange for usage commitments over one or three years. To take advantage of these responsibly, you need reliable data about your baseline consumption, the same kind of data a mature ITAM function produces.
Planning in FinOps also feeds directly into broader business processes: annual budgeting, product cost modelling, capacity planning, and building the business case for new cloud investments. When FinOps data is mature enough to inform these conversations, finance and engineering stop reconciling surprises after the fact and start aligning on expectations before the year begins.
Pro tip: Reserved and committed-use discounts can be a large source of cloud savings available to mid-market organisations. But they require trust in your consumption data. Plan only after See and Save are in place.
In ITAM, the work does not stop after the first discovery exercise or the first license reconciliation. Assets change. Contracts renew. New tools get adopted. Maintaining governance means making it a continuous practice, not a project you complete and close.
FinOps works the same way. Cloud environments are not static: new services launch, teams grow, architectures change, and workloads migrate. Costs that were optimised in Q1 can drift upward by Q3 if no one is actively monitoring them.
Running FinOps well means embedding cost discipline into day-to-day operations: regular reviews, clear ownership, and feedback loops between engineering decisions and financial outcomes. In the organisations where we have seen this done well, it often starts with a small cross-functional group from IT, finance, and engineering, meeting monthly to review spend, identify anomalies, and agree on next steps. The tooling matters less than the habit.
It is worth being direct about something. ITAM and FinOps are increasingly treated not as competing disciplines but as mutually reinforcing ones. Both frameworks share the same ultimate goals: maximise business value, control costs, and ensure compliance. They approach those goals from slightly different angles, but the overlap is significant.
ITAM provides the governance foundations - structured lifecycle management, cost attribution, vendor relationship oversight, and audit readiness - that FinOps depends on to function well. FinOps, in turn, extends that discipline into cloud environments where traditional ITAM tooling often does not reach. Together, they give organisations a complete picture of technology spend across on-premise and cloud.
If your organisation is being asked to take on FinOps responsibilities, or if FinOps conversations are happening around you, the most important thing to know is this: your ITAM experience is an asset, not a liability. The instincts you have developed around visibility, attribution, lifecycle management, and governance translate directly.
The FinOps Foundation defines a three-stage maturity model: Crawl, Walk, and Run. Most organisations land somewhere in the Crawl stage when they start: partial tagging, limited visibility, no formal governance, and FinOps responsibilities sitting informally with whoever cares most about the cloud bill.
Progressing through the stages is not about deploying a specific platform. It is about building the right processes, the right stakeholder alignment, and the right habits. A professional assessment, conducted against the FinOps Foundation's criteria by experienced consultants rather than a self-scoring online checklist, gives you an honest view of where you stand today and a concrete roadmap for what comes next.
The path forward follows a logic any ITAM professional will find intuitive. Here is how we recommend approaching it.
Step 1: Align your stakeholders Bring IT Asset Management, engineering leads, finance, and business leadership into the same conversation. Agree on why cloud cost management matters, who owns it, and what good governance looks like in your organisation. Nothing else works without this.
Step 2: Audit your current tagging Review what tagging is already in place across your cloud environments. Identify gaps where resources can’t be attributed to a team, product, or cost centre. This is your starting inventory, the cloud equivalent of a first asset discovery scan.
Step 3: Establish a tagging policy Define a consistent tagging standard and apply it across all cloud resources. Prioritise the attributes that matter most to your business: cost centre, product, environment, and owner. Enforce it for all new resources going forward.
Step 4: Build visibility dashboards Give teams self-serve access to their own cloud consumption data. The goal is to make spend visible and attributable before any optimisation work begins. You can’t manage what you can’t see.
Step 5: Identify and eliminate waste With visibility in place, waste surfaces quickly. Start with the obvious: idle resources, oversized instances, unattached storage. Apply the same instincts you use in a license reconciliation, and act on what you find.
Step 6: Review commitment and discount opportunities Once consumption patterns are stable, assess where reserved or committed-use pricing could reduce costs. Treat this like a software renewal negotiation: know your baseline, understand your terms, and commit only where the data supports it.
Step 7: Embed ongoing governance Set up a regular review cadence with a small cross-functional group. Review spend, track optimisation progress, and catch anomalies before they become budget surprises. Make it a habit, not a project.
FinOps is not a whole new world. It is a familiar discipline, applied to a new environment. And if you have been doing ITAM well, you are already most of the way there.
Curious about where your organisation stands on the FinOps maturity curve? A structured assessment conducted by experienced consultants gives you the clarity and roadmap to move forward with confidence. Contact us for a short call - just to find out if our FinOps Assessment is the right fit for you.