TBM vs FinOps: where one ends and the other begins
In brief
TBM models the full cost of technology from the ledger; FinOps brings usage data and accountability to spend as it happens. How they differ and overlap now.
Steve Elliott · · 5 min read
On this page
TBM models what all of technology costs and what it delivers, from staffing and data centers to software and cloud, starting from the general ledger. FinOps brings usage data and shared accountability to technology spend as it happens, putting cost in front of the engineers, finance teams, product owners and leaders who drive it. In our view most large organizations need both, working from one set of cost data.
The line used to be easy to draw: FinOps did cloud, TBM did everything else. Since mid-2025 both disciplines have moved toward each other, so that rule of thumb no longer holds.
How do TBM and FinOps differ?
| TBM | FinOps | |
|---|---|---|
| Core question | What does technology cost, and what does it deliver? | How do we get the most business value from technology spend, with timely, data-driven decisions? |
| Scope | All technology spend: staffing, hardware, software, cloud, facilities, outside services | Started in public cloud; now also SaaS, data center, data cloud platforms and AI |
| Standard | TBM Taxonomy 5.x: cost pools, resource towers, solutions, consumers | FinOps Framework, plus the FOCUS specification for billing data |
| Steward | TBM Council | FinOps Foundation, part of the Linux Foundation |
| Data starts from | The general ledger and chart of accounts | Provider billing and usage data |
| Main audience | CFO, CIO, IT finance and business leaders | Practitioners, engineering, finance, product, procurement and leadership |
The FinOps Foundation defines FinOps as "an operational framework and cultural practice which maximizes the business value of technology, enables timely data-driven decision making, and creates financial accountability through collaboration between engineering, finance, and business teams." Its earlier framework guidance described the overlap this way: TBM provides a total cost of ownership view that includes cloud-related labor, SaaS and licenses, while FinOps provides granular insight into cloud provider spend and how to get more value from it.
What has changed since mid-2025?
TBM moved toward cloud and AI. TBM Taxonomy 5.0, released in June 2025 and updated to 5.0.1 in July, made Cloud Services a standalone top-level cost pool, merged internal and external labor into a single Staffing pool, and added a Data tower and AI sub-towers.
The data got easier to connect. FOCUS 1.3, released in December 2025, added columns that show how providers split shared costs across workloads, and a separate dataset for contract commitments. In our view, both should make cloud bills easier to carry into a TBM model without rebuilding allocations by hand.
FinOps moved up and out. The FinOps Framework 2026, presented in March 2026, added a capability called Executive Strategy Alignment. It covers tying spend to strategic initiatives, multi-year investment planning with IT finance data, product prioritization and strategic decision support. The framework now names technology categories beyond public cloud: SaaS, data center, data cloud platforms and AI. It lists IT financial management among several disciplines, alongside asset management, sustainability, security and enterprise architecture, that are "allied, adjacent, and increasingly converged" with FinOps, and says this is not about FinOps absorbing them.
The TBM Council claimed the broader frame. In November 2026 the TBM Council repositioned TBM as the business operating system for the AI era. Its strategy series, which began in September with the paper Beyond Tokenomics, puts the split this way: FinOps helps you make the right tactical decisions, while TBM helps you decide whether to run the workload at all. The paper says FinOps "is wonderful at optimizing cloud, but with its limited scope, it does not address business value."
So the two stewards describe the relationship differently. The FinOps Foundation talks about adjacent disciplines converging. The TBM Council positions TBM as the wider frame, with FinOps covering cloud and tactical decisions.
Where they overlap, and how we would split ownership
Four areas cause most of the friction. This is our view of where the line should sit.
- Cloud cost allocation. FinOps owns tagging and allocation of provider bills to workloads and teams. TBM uses those allocations and carries them through towers to solutions and consumers. One allocation, two views.
- Chargeback and showback. TBM owns the policy and the bill of IT, because it covers every cost pool. FinOps supplies the consumption detail for usage-based lines.
- AI cost. FinOps owns token and compute spend, where usage changes daily. TBM owns the fully burdened cost of an AI initiative, including the staffing, data work and licenses around it.
- Multi-year planning. This has long been TBM and IT finance territory. The overlap is new because FinOps moved into it with Executive Strategy Alignment. Whoever owns the annual technology plan should own it, with FinOps forecasts feeding the usage-based lines.
How does cloud data flow into a TBM model?
In earlier framework guidance, written against TBM Taxonomy 4.0, the FinOps Foundation described a mature state where cloud costs map to all four TBM layers and both teams share terminology and processes such as chargeback. In Taxonomy 5.0 the last of those layers is called the Consumer layer. The flow runs roughly like this:
- Where providers support it, billing data arrives in FOCUS format, with tags and allocation columns for shared resources.
- FinOps allocates it to workloads, teams and products.
- Those lines map to the Cloud Services cost pool, then to resource towers such as compute, storage and data.
- Towers roll up to solutions and consumers, where cloud sits beside the staffing, software and other costs of the same service.
That same guidance suggested measuring progress by the share of cloud provider costs mapped to TBM towers, solutions and business capabilities, plus tagging compliance.
How should the two teams be organized?
The FinOps Foundation's guidance says the teams can be centralized or separate, depending on the organization. Three patterns we think work, depending on how much of your spend is cloud:
- FinOps inside the TBM office. Cloud is a modest share of spend and one finance-led team can carry both.
- Side by side, with shared data. A large cloud estate where FinOps needs to sit close to engineering. The test is whether both teams report the same cloud number.
- FinOps-led, with TBM reporting. A cloud-native company with little on-premises infrastructure, where most technology spend is already in FinOps.
Whichever you choose, agree on one allocation of cloud spend. If FinOps and TBM report different cloud totals, the CFO will trust neither.
If you only have one, where do you start?
Start where most of your spend and most of your questions are. If the CFO is asking what technology costs and what it delivers across the whole estate, start with TBM and a cost-pool and tower view. If the pressure is a fast-growing cloud or AI bill, start with FinOps and build toward a TBM model as the practice matures.
Sources
- FinOps Foundation, What is FinOps?
- FinOps Foundation, FinOps Framework 2026: Executive Strategy, Technology Categories, and Converging Disciplines, March 19, 2026
- FinOps Foundation, Intersection of FinOps & ITFM/TBM (earlier framework version)
- Linux Foundation, FinOps Foundation Launches FOCUS 1.3, December 11, 2025
- TBM Council, Update Your TBM Model with a New Taxonomy Version
- TBM Council, Beyond Tokenomics, published September 2, 2026
- TBM Council press release, TBM Council Establishes TBM as The Business Operating System for AI, November 17, 2026
Frequently asked questions
Is FinOps part of TBM?
No. They are separate disciplines with separate stewards: the TBM Council for TBM and its taxonomy, and the FinOps Foundation for FinOps and the FOCUS specification. The FinOps Foundation describes IT financial management as adjacent and converging, not absorbed. The TBM Council positions TBM as the broader frame, with FinOps covering cloud and tactical decisions.
Can FinOps replace TBM?
FinOps has expanded beyond public cloud to SaaS, data center and AI, and now covers executive strategy. Its published scope still centers on technology spend and usage data rather than modeling the full general ledger, including staffing and facilities, through to the solutions and consumers that use it. In our view most large organizations need both.
How does cloud spend fit into the TBM Taxonomy?
TBM Taxonomy 5.0 has a standalone Cloud Services cost pool. Cloud costs, ideally allocated by FinOps first, map into that pool, then to resource towers such as compute, storage and data, and finally to the solutions and consumers they support, alongside the staffing and software costs of the same service.
What is FOCUS in FinOps?
FOCUS, the FinOps Open Cost and Usage Specification, is a common format for billing data across cloud, SaaS and other providers. Version 1.3, released in December 2025, added columns showing how shared costs are split across workloads and a separate dataset for contract commitments.
Steve Elliott
Published November 22, 2026
More on TBM & IT Financial Management
Cost pools, towers, showback, unit cost.
Keep reading
Cost center or product P&L: where technology cost should land
Should technology run as a cost center, a shared-services recharge or inside product P&Ls? What each model does to behavior, plus a worked margin example.
How business relationship managers should use TBM data
BRMs sit closest to business demand, so they should do more than receive TBM reports. How BRMs can use the bill of IT, intake and value reviews instead.
How to present IT cost to a CFO on one page
What a CFO wants to know about technology spend, the TBM views that answer each question, the language to use, and a sample one-page structure to copy.
TBM in health systems: technology cost on margins this thin
About 43% of hospitals in Kaufman Hall's sample run at a loss. How TBM helps health systems cost the EHR, defend cyber spend and price IT into service lines.