The IT finance org chart: who owns what in a TBM model
In brief
A role-by-role map of IT finance and TBM: TBM office, IT finance, FP&A, FinOps, procurement and service owners, their reporting lines and model layers.
Steve Elliott · · 6 min read
On this page
In our view, most of the people who make a TBM model work don't sit in the TBM office. The TBM Council defines six roles inside the office, from executive sponsor to analyst, while IT finance, FP&A, FinOps, procurement, service owners and business relationship managers supply the data and act on the results.
The Council's guidance says who uses each layer of the taxonomy, not who owns it, and it doesn't prescribe reporting lines. In our view, that gap is where most ownership disputes start. Below is a role-by-role map: responsibilities and reporting lines from public sources where they exist, and our view of who should own cost pools, towers, solutions and consumers.
Who does what in IT finance and TBM?
Reporting lines marked "(source)" come from the sources listed below. Responsibilities paraphrase those sources where they exist and are otherwise our summary. Unmarked reporting lines and the last column are our view.
| Role | Core responsibilities | Typical reporting line | Owns in the model (our view) |
|---|---|---|---|
| CIO or CTO, as executive sponsor | Sponsors TBM, secures resources, uses the Technology View to defend and reshape the portfolio | CEO | Final call on how towers and solutions reflect the IT organization |
| CFO | Uses the Finance View for budgeting, planning, variance and chargeback | CEO | Policy behind cost pools: capitalization, depreciation, allocation principles |
| TBM office lead | Runs the practice, governs the taxonomy, accountable for outputs and executive adoption | CIO or technology CFO | Taxonomy, allocation rules and change control for the model |
| TBM analyst or modeler | Analysis and reporting; in small teams also data loads, mapping and administration | TBM office lead | Day-to-day mappings, fallout review, standard reports |
| IT finance business partner | IT budget, forecast and variance; advises IT leaders on spend decisions | Finance, with a dotted line to the CIO | Ledger-to-cost-pool mapping and reconciliation to the general ledger |
| FP&A counterpart | Runs the corporate budget process and consolidates business unit plans | Director or VP of FP&A, or CFO (source) | The corporate total and calendar the IT model must tie to |
| FinOps lead | Allocates and forecasts cloud and usage-based spend with engineering | CTO or CIO organization, dotted line to finance (source) | Cloud allocation feeding the Cloud Services cost pool and towers |
| IT procurement or vendor management | Sourcing, contracts, renewals, vendor performance | Chief procurement officer, or the CIO where IT runs its own vendor office | Contract and vendor data used to map spend to towers and solutions |
| Service and application owners | Accountable for a service's success, value, budget and cost recovery | IT delivery or product leaders | Solutions layer: service definitions, total cost of ownership, retire-or-invest decisions |
| Business relationship managers | Connect IT with business units on demand and priorities | CIO or IT strategy | Consumer layer: consumption drivers and the showback conversation |
What does the TBM Council say a TBM office needs?
The Council's TBM Office guidance lists six roles: executive sponsor, TBM practice lead, TBM solution owner, TBM change manager, TBM administrator and TBM analyst. The 2025 TBM Framework treats roles as one of five foundations, alongside data, tools, methods and change. The Council suggests a RACI matrix to set who is responsible, accountable, consulted and informed for each task.
- The sponsor should be senior. Effective sponsors are "typically the CIO, CTO, or Technology CFO," according to the Council, which warns that programs whose sponsorship is delegated to AVPs or senior directors often struggle for influence. GSA's federal TBM playbook lists CIO, CTO and CFO as typical sponsor backgrounds.
- The practice lead owns outcomes, not plumbing. The Council's practice lead guide says the lead does not configure the model's back end or run daily data ingestion, but is accountable for the model's strategic outputs. A separate Council article notes the role is often titled TBM director, program manager or technology CFO.
- Views split by audience. The CFO's Finance View focuses on cost pools and resource towers. The CIO's Technology View emphasizes the middle layers, towers and solutions. A third, the Business View, highlights solutions and consumers to show value delivery; mapping costs to consumers makes showback or chargeback defensible, the CFO guide says.
The Council's role pages don't say where the TBM office should report. Its "CFO of IT" competency model describes a role that works closely with CIOs, enterprise architects, TBM teams and finance leaders, without fixing a reporting line.
Who should own each layer of the TBM model?
This is our view. None of the TBM Council guides we read assign an owner to each layer, so write it down before the first allocation dispute.
- Cost pools: IT finance. The Council's CFO guide says cost pools map directly to the general ledger. The finance business partner for IT should sign off the mapping from ledger accounts to cost pools, with FP&A and the controller owning the ledger it maps from.
- Resource towers: the TBM office, validated by infrastructure leaders. The practice lead guide notes that assigning costs to towers is a separate mapping exercise, drawing on cost centers, contracts and vendor data. That puts IT vendor management in the chain. FinOps owns the cloud slice, since TBM Taxonomy 5.0 made Cloud Services a standalone cost pool.
- Solutions: service and application owners. Stanford's IT organization describes a service owner as the leader accountable for a service's overall success and value, including its budget and, where it applies, cost recovery. That is the person who should defend a solution's total cost and decide whether to retire it.
- Consumers: business relationship managers and business unit leaders. Taxonomy 5.0 renamed the Business layer the Consumer layer and added value streams, products, portfolios and digital services. BRM Institute describes the business relationship manager as the "strategic interface between a business function and one or more business partners." BRMs carry the consumer view to the people whose demand drives the cost.
The TBM analyst maintains mappings and reports across all four layers, so the role belongs to the office.
Where do these roles report?
Survey data on reporting lines is thin, with one exception. The FinOps Foundation's State of FinOps 2026 found 78% of FinOps practices report into the CTO or CIO organization and 8% to the CFO. It describes practices that sit in technology "with a dotted line to Finance."
For FP&A, AFP's published job descriptions show FP&A managers reporting to the CFO, a VP of finance or a director of finance or FP&A. For IT financial management, the FinOps Foundation's personas page describes ITFM as an allied persona "when it operates separately from Finance," which implies that in some organizations it sits inside Finance.
One workable arrangement, in our view and not from survey data, has two solid lines and a set of dotted ones. The CIO line runs down to the TBM office, FinOps, service and application owners, and BRMs. The CFO line runs down to FP&A and, in many companies, to the IT finance business partners, who carry a dotted line to the CIO. Procurement usually sits on the CFO side or under its own chief procurement officer, with a dotted line to IT for technology categories. The TBM office is the node with the most dotted lines, to IT finance, FinOps and procurement for data, and to service owners and BRMs for decisions.
In our view, the TBM office can work on either side. What matters is that the office lead has a standing seat with both the IT finance lead and the CIO's leadership team.
How does the org chart change with company size?
In our view, the roles stay the same as a company grows; the number of people per role changes.
- One to three people. The TBM Council says a team of one assumes all roles. With two, one person takes the practice lead and change manager work, and the other takes solution owner, administrator and analyst work. With three, the analyst and change manager roles combine. GSA's playbook recommends starting with at least two or three dedicated people from budget, capital planning and enterprise architecture.
- A small dedicated office. In our view, this is the stage where FinOps can sit inside the TBM office. The Council notes that many practice leads combine TBM and FinOps in one team. Our TBM vs FinOps post covers when that works.
- Large enterprises. Separate teams become more common. State of FinOps 2026 found that organizations with more than $100 million in annual cloud spend average 8 to 10 FinOps practitioners and 3 to 10 contractors, and that larger companies tend to run FinOps and asset management as separate, collaborating teams while smaller ones combine them. In our view, IT finance business partners at this scale usually cover one tower or business unit each, and the TBM office's job shifts from building the model to governing changes to it.
How do you assign ownership without a turf war?
Our suggested sequence:
- Name one accountable owner per layer. Use the RACI the TBM Council suggests, but add a row for each taxonomy layer, not only each task.
- Make IT finance accountable for the tie-out. The model total should match the ledger every month, and one named person should own the difference.
- Give service owners their numbers before budget season. A solution cost they first see in a budget review is likely to be disputed rather than used.
- Route consumption disputes through BRMs. Our post on why IT cost transparency projects stall argues that showback without a named business owner tends to go unread.
The same logic applies beyond TBM: when the people who own the plan, the money and the work sit in one operating model, each number has an owner when the decision is made.
Sources
- TBM Council, TBM Roles, TBM Framework foundations, published June 18, 2025, updated May 1, 2026
- TBM Council, The TBM Framework, published June 3, 2025
- TBM Council, TBM Practice Leadership: The Operational Engine of Value Realization, March 20, 2026
- TBM Council, Executive Sponsorship: The Critical Catalyst for TBM and Enterprise Transformation, March 6, 2026
- TBM Council, The TBM Practice Lead's Guide to the TBM Taxonomy, updated May 1, 2026
- TBM Council, The CFO's Guide to the TBM Taxonomy, May 8, 2026
- TBM Council, The CIO's Guide to the TBM Taxonomy, May 8, 2026
- TBM Council, Understanding the CFO of IT Role, July 17, 2025
- TBM Council, Update Your TBM Model with a New Taxonomy Version, July 16, 2025
- FinOps Foundation, FinOps Personas
- FinOps Foundation, State of FinOps 2026, 2026
- GSA, Technology Business Management Playbook
- AFP, Finance Job Descriptions: Titles, Roles and Responsibilities, August 14, 2026
- Stanford University IT, Service Owner Role
- BRM Institute, About Business Relationship Management
Frequently asked questions
Who should the TBM office report to?
No standard says. The TBM Council's role guidance describes six TBM office roles but sets no reporting line, and its executive sponsorship article names the CIO, CTO or technology CFO as typical sponsors. In our view, the office can sit under the CIO or inside IT finance, provided its lead has a standing seat with both the CIO's leadership team and the IT finance lead.
What is the difference between IT finance and FP&A in TBM?
FP&A runs the corporate budget process and consolidates business unit plans into corporate reporting, so it owns the total the IT model must tie to. IT finance works inside that total, owning the IT budget, forecast and variance. In our view, IT finance should also own the mapping from ledger accounts to TBM cost pools and the monthly reconciliation.
Does the FinOps team belong in the TBM office?
It can, depending on scale. The TBM Council notes that many TBM practice leads combine TBM and FinOps in one team. State of FinOps 2026 found 78% of FinOps practices report into the CTO or CIO organization. In our view, a combined team suits a modest cloud estate, while large cloud spenders usually need a separate FinOps team close to engineering.
How many people does a TBM office need?
It can start with one. The TBM Council describes how one person can cover all six TBM office roles, and how two or three people can split them. GSA's federal playbook recommends at least two or three dedicated people to start. In our view, larger organizations add analysts, administrators and change managers as the model and its audience grow.
Steve Elliott
Published November 22, 2026
More on TBM & IT Financial Management
Cost pools, towers, showback, unit cost.
Keep reading
TBM, ITFM or FP&A: who should own IT cost?
ITFM is the function, TBM the method, FP&A the enterprise planning team. How their remits differ, where they collide, and our view on who should own IT cost.
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.
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.
TBM vs FinOps: where one ends and the other begins
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.