On the TBM Council's numbers, tokens are 4.5–15% of AI cost. What that means for your budget
The TBM Council puts labor at 50–70% of AI project cost. On its numbers, tokens are 4.5–15% of the total. What the figures show and what to budget for.
Dotwork Blog
Strategy, operating models, planning and AI, from the people building Dotwork.
The TBM Council puts labor at 50–70% of AI project cost. On its numbers, tokens are 4.5–15% of the total. What the figures show and what to budget for.
When a fixed annual IT budget works, when a rolling forecast is better, and how to run both: plan headcount and contracts, forecast cloud and AI by driver.
ASU 2025-06 drops the stage model for internal-use software. What it changes for IT finance: when capitalization starts, the evidence, and the cost model.
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.
Which FOCUS columns feed which TBM Taxonomy 5.0 cost pools, towers, solutions and consumers, and how to handle amortization, commitments and untagged spend.
Usage-based cloud and AI spend outruns a TBM model rebuilt each year. What a living cost model means, what stays hard, and where AI agents help and don't.
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.
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.
Banks, payment firms and insurers must map technology and suppliers to critical services. Why that changes IT cost transparency, and how a TBM model helps.
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.
Many TBM programs publish dozens of unit costs that rarely change a decision. Why that happens, what makes a unit cost useful, and a test to prune the list.
Moving from project to product funding changes the cost object, allocation, capex evidence, budget cadence and how success is measured. What to change.
Run, grow, transform is a useful board shorthand and a weak cost model. Where the split breaks down, what the federal DME and O&M split adds, and what to do.
Chargeback changes behavior only where consumers control demand and cost falls when they cut it. A worked example, failure modes and a readiness checklist.
Why the same engineering labor is capitalized under ASC 350-40 but deducted or amortized under Sections 174A and 174, and the time records IT finance needs.
The 2025 State of TBM finds high-maturity orgs 2–3x more likely to report significant impact. A close read and how to cite it in a business case.
After a deal, two IT cost models rarely add up. Map both to one TBM taxonomy, conform capitalization, and baseline run cost per tower before synergy targets.
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.
How TBM and IT cost recovery work in state agencies and public universities: funds, rates, federated campuses, legislative reporting and what models need.
Moving from TBM Taxonomy 4.x to 5.0.1 means remapping every layer. A practitioner change log: what each change breaks, a before/after table and a sequence.
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.
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.
What a TBM analyst does each month, from loading the ledger to chasing unmapped cost, plus the skills, the certifications that exist and where the role leads.
Many IT cost transparency projects don't fail outright. They publish a model and little changes. Why that happens, and how to restart around one decision.