Originally published on rikuq.com. Republished here for Dev.to's readers.
I get this question from Indian CFOs about once a month: "my procurement team wants ITAM, my CTO wants FinOps, my finance lead is reading about ITFM. Which one do we actually invest in?" The answer is none of them, because the framing is wrong. These three disciplines aren't competing for the same slot — they cover different scopes, run on different cadences, and produce different outputs. The 2026 industry consensus is convergence, not selection.
But mid-market entities still have to sequence the investment. You can't stand up all three operating models simultaneously without under-resourcing each. This post explains what each discipline actually does, where each is strongest, and how to sequence the build at Indian mid-market scale.
I'm Ravi. I run three production AI SaaS solo (Prism, Citare, BatchWise) and do advisory work on this exact problem via rikuq services. The framework below is what I take into every CFO conversation that starts with "we need to get a handle on our IT spend."
TL;DR
| FinOps | ITFM | ITAM | |
|---|---|---|---|
| What it manages | Cloud + AI consumption + SaaS | All IT spend (broader) | All IT assets (lifecycle) |
| Primary purpose | Maximise value per dollar of cloud/AI spend | Financial governance + budgeting + TCO | Asset + licence lifecycle management |
| Time horizon | Real-time / daily / weekly | Monthly / quarterly / annual | Multi-year asset lifecycle |
| Who runs it | Engineering + Finance collaboration | Finance-led with IT input | IT operations / procurement |
| Granularity | Service / resource / per-API-call | Cost-centre / aggregate IT lines | Asset-level inventory |
| Output | Showback, chargeback, unit economics | Budget, forecast, TCO, controls | Asset register, contract repository, renewal calendar |
The side-by-side framework
Three disciplines, three scopes, three operating cadences.
| Dimension | FinOps | ITFM | ITAM |
|---|---|---|---|
| Scope | Cloud + AI consumption + SaaS (2026 expanded definition) | All IT spend — hardware, software, licensing, labour, on-prem, cloud | All IT assets — hardware, software licences, SaaS subscriptions |
| Primary purpose | Maximise business value of technology investment via data-driven consumption decisions | Financial governance + budgeting + forecasting + TCO for all IT spend | Lifecycle management of IT assets from procurement through retirement |
| Time horizon | Operational + real-time | Strategic + budgetary | Asset lifecycle |
| Ownership | Engineering + Finance collaboration | Finance-led with IT input | IT operations / procurement |
| Granularity | Service / resource / per-API-call | Cost-centre / aggregate IT lines | Asset-level inventory |
| Output | Chargeback / showback / unit economics / optimisation recommendations | Budget / forecast / TCO / financial controls / chargeback framework | Asset register / contract repository / licence compliance / renewal calendar |
| Practitioner certifications | FinOps Certified Practitioner (FOCP) + FinOps Certified Engineer (FOCE) | TBM Council Certified Practitioner; CIPS for procurement | IAITAM CHAMP / CSAM / CITAM |
| Underlying framework | FinOps Foundation Framework (2026 update) | TBM Council Taxonomy; ITFM body of practice | ISO/IEC 19770; ITIL ITAM module |
These overlap in places (SaaS sits in all three to some extent) but they're genuinely distinct disciplines. Treating them as substitutes is the most common mistake.
Where each is actually strongest
The right way to think about which discipline to lean on for a specific decision is to match the decision shape to the discipline's strength.
FinOps is strongest at:
- Real-time or near-real-time consumption visibility — engineering teams making cloud and AI procurement decisions today based on yesterday's cost data
- Unit economics — cost per API call, cost per inference, cost per active user, cost per transaction
- Engineering accountability — making consumption decisions visible to the engineers driving them
- Cloud and AI vendor consolidation analysis — identifying redundant providers, underutilised reserved capacity, over-provisioned workloads
- Forecasting near-term consumption trajectory (next 30-90 days) based on engineering roadmap
ITFM is strongest at:
- Multi-year budget cycles and annual financial planning
- Total Cost of Ownership including labour and indirect costs
- Defensible cost allocation for chargeback to business units at finance-team granularity
- Integration with the general ledger, ERP, and corporate financial reporting
- Hybrid environments where on-premises infrastructure, cloud, and SaaS combine
ITAM is strongest at:
- Licence compliance and audit defensibility — particularly relevant for entities subject to Microsoft, Oracle, or IBM licence audits
- SaaS subscription rationalisation — surfacing duplicate or unused subscriptions across business units
- Contract renewal calendar — preventing auto-renewals at sub-optimal terms
- Asset lifecycle — knowing what hardware is in service and when it needs refresh
- Hybrid licensing complexity — where cloud and on-premises licences interact
The overlap zones are real (SaaS subscriptions sit in both ITAM and FinOps, for example) but the primary strength of each discipline is distinct enough that matching decision to discipline produces materially better outcomes than treating them interchangeably.
The 2026 convergence thesis
Per the State of FinOps 2026 from the FinOps Foundation, the dominant industry trend is convergence rather than competition. FinOps practice needs the planning discipline, financial controls, and allocation logic that ITFM provides. ITFM practice needs the timely usage signals, operational feedback loops, and unit economics that FinOps provides. Both need the contract and lifecycle visibility that ITAM provides. Collaboration between FinOps and ITAM teams alone is up 20% year over year per the 2026 survey.
The practical implication: a mature 2026 organisation does not pick one of the three. It runs all three with shared data infrastructure (typically a unified observability and cost data lake), shared dashboards for executive consumption, and coordinated operating cadence. The job titles stay distinct; the tooling and data layers increasingly merge.
You can see this in the vendor landscape. Apptio (now IBM-owned) acquired Cloudability and now positions itself as covering FinOps + ITFM + TBM in a single product surface. CloudKeeper has expanded from pure cloud cost optimisation into broader IT spend governance. The category lines that existed in 2022 are blurring in 2026.
India context — how to actually sequence the build
Most Indian mid-market entities (₹50-2,000 crore revenue) currently have none of these three practices in mature form. Some have nascent versions — usually a FinOps Inform-phase exercise that one engineer ran for two months before getting pulled onto something else, or an ITAM spreadsheet of software licences that hasn't been updated since 2024. None of those count as "established practice."
The pragmatic sequencing for an entity starting from ground zero:
1. Start with FinOps Inform phase. Get visibility into cloud and AI consumption at the service level. This is the highest-immediate-ROI starting point because cloud and AI spend have the most variability and the largest optimisation lift. The FinOps Foundation framework is free; hyperscaler-native tooling (AWS Cost Explorer + CUR, Azure Cost Management, GCP Billing Reports) is sufficient for the first six months. The output is consumption visibility per service, per team, per environment.
2. Layer in ITFM discipline for the broader IT spend base. Once cloud and AI are visible, extend the financial discipline to the rest of IT — software licensing, on-premises infrastructure, IT labour. Annual budget cycles and TCO modelling come into scope. This stage is finance-led but requires engineering and procurement input. The output is budgets that reflect reality, forecasts that hold for two quarters, and TCO models that survive contact with the audit committee.
3. Add ITAM as the asset-and-contract layer. Particularly relevant for entities with material Microsoft, Oracle, Adobe, or SAP licensing, or with SaaS sprawl across business units. ITAM at this stage isn't a spreadsheet — it's a SaaS Management Platform (SMP) or equivalent, integrated with the FinOps consumption layer and the ITFM financial layer. The output is licence compliance, renewal calendar discipline, and asset rationalisation savings.
For Indian listed entities preparing for the FY 2026-27 audit cycle, the combined FinOps + ITFM + ITAM data set is precisely what audit committees and statutory auditors are increasingly expecting on AI-augmented finance work. The framing is evolving under ICAI voluntary practitioner guidance on AI assurance, DPDP Act 2023 obligations, and the directional signal from SEBI's June 2025 AI/ML consultation paper (applicable today to MIIs, intermediaries and mutual funds; still in consultation for the broader market). Starting the sequencing in mid-2026 is the difference between a clean FY 2026-27 audit and a scramble in March 2027.
Where the three overlap (and how to handle it)
The overlap zones aren't a bug — they're where coordinated tooling and data pay off.
SaaS subscriptions sit in all three:
- ITAM tracks the contract, licence terms, and renewal date
- FinOps tracks consumption (which seats are actually active, which features get used)
- ITFM allocates the cost to the right business unit and rolls it into budget
For a mid-market entity with 80-150 active SaaS subscriptions (typical), the value of integrating all three views is substantial. You can identify the 20 subscriptions where licence count exceeds active users (ITAM + FinOps overlap), the 15 where the cost allocation is going to the wrong BU (ITAM + ITFM), and the 10 where the renewal is in the next 60 days and the team is underutilising the platform (all three).
Reserved capacity / commitments sit between FinOps and ITFM:
- FinOps optimises the commitment level and term
- ITFM allocates the discount across consuming teams and records the commitment as a contractual liability for forecasting
Vendor consolidation analysis crosses all three:
- ITAM tells you what contracts exist
- FinOps tells you what's actually being used
- ITFM tells you the financial impact of consolidation scenarios
The point isn't that you need three separate teams — small mid-market entities often have one person wearing all three hats. The point is that the underlying data layers of all three disciplines should be coordinated so the decisions you make in any one of them aren't blind to the others.
Common confusions worth resolving
"Is FinOps just cloud cost cutting?" No. FinOps is decision-quality work — the practitioner often increases aggregate spend in order to maximise per-unit business value. The goal is value, not cost reduction. A team that doubled its Claude API spend because the capability was generating 3x the revenue per unit cost is doing FinOps right.
"Is ITFM just finance-team-led IT accounting?" No. ITFM is broader — financial governance, budgeting, forecasting, TCO modelling, financial controls. The finance team owns it but engineering, procurement, and IT operations contribute substantially. Treating it as a finance back-office function is what produces budgets that engineering doesn't believe in.
"Is ITAM just spreadsheets of licences?" It was, historically. Modern ITAM (post-2023) is dynamic — integrating with SaaS Management Platforms, licence-usage telemetry, and contract repositories. ISO/IEC 19770 and the ITIL ITAM module are the reference frameworks. An ITAM practice that hasn't moved beyond a spreadsheet hasn't actually started.
"Which framework matters most for Indian AI-controls expectations?" All three contribute. ICAI voluntary practitioner guidance on AI assurance and audit-committee scrutiny of AI-augmented finance work expects model documentation, log-trail sufficiency, version control, and reproducibility — produced by FinOps (consumption data) plus ITFM (financial allocation) plus ITAM (asset and contract context). Audit-readiness on AI-augmented financial reporting effectively requires the combined data set.
"Do we need separate tools for each?" Not necessarily. Vendor consolidation in the cost-management tooling space itself is a 2026 trend — platforms like Apptio (which acquired Cloudability) now span FinOps + ITFM + TBM in a single product. Whether to consolidate tooling is itself a FinOps Optimize-phase decision and should be made after the underlying practice is established, not before.
Where to start tomorrow
If you're at a mid-market Indian entity reading this with material cloud or AI spend and none of the three disciplines in mature form:
- Pick FinOps Inform phase as the first investment. Two-week exercise. Hyperscaler-native tooling. Output: consumption visibility by service / team / environment. No platform purchase yet.
- If the FinOps exercise surfaces vendor-consolidation opportunities, quantify the Indian tax overlay — Section 195 TDS classification, GST RCM exposure, Ind AS 38 implications — before negotiating consolidations. Tax recovery often funds the entire FinOps exercise.
- Defer ITFM and ITAM investments by 6-12 months. Once FinOps Inform is established, ITFM and ITAM build on top of it more efficiently than trying to do all three at once.
If you want a written scope proposal for the diagnostic side of this work — what an engagement on FinOps Inform setup plus tax-recovery quantification would look like for your specific situation — the services page has both a Cal.com booking link and a Tally intake form. Free 30-min discovery, written scope before any commitment.
What's next
This post is the framework. The adjacent posts that go deeper on specific dimensions:
- What is LLM FinOps? — the AI-specific version of the FinOps discipline
- AI / Cloud FinOps Providers in India — who fits what at the provider-selection layer
- LLM gateway attribution is harder than cloud FinOps ever was — why the attribution layer is the hardest part
Top comments (0)