The News
The Linux Foundation’s Technology Value (LFTV) umbrella hosted an analyst briefing covering the state of its four constituent foundations: FinOps Foundation, ITAM Forum, Tokenomics Foundation, and the Focus specification project. General Manager JR Stormer presented findings from a 472-respondent State of Tokenomics survey (median respondent revenue: $1.8B), introduced the concept of Total Cost of AI (TCA), and outlined the Tokenomics Foundation’s early frameworks for connecting AI infrastructure spend to measurable business value. The session also covered Focus 1.5, a forthcoming release of the Open Costing Usage Specification that adds AI-specific billing dimensions including model identity, token direction, and cache status.
Analyst Take
The TCA Framing Is the Right Fight
The most consequential idea from this briefing is not a product or a standard. It is a reframing. The Tokenomics Foundation is making a direct argument that token costs represent only 10–25% of total AI spend once energy, capital, infrastructure, software, labor, and process costs are included. That is the kind of assertion CFOs will either immediately validate or immediately challenge, and the fact that the foundation has CFOs from JPMorgan Chase and BNY on its governing board suggests it will get a fast reality check. For ITDMs, the practical implication is straightforward: any AI business case built primarily on token pricing is almost certainly undercosting the initiative and overestimating the return.
The survey data reinforces this. Respondents were broadly confident in their visibility to AI spend, but most could not demonstrate value to a CFO in terms the CFO would accept. That gap, between spend visibility and value defensibility, is exactly the gap that FinOps failed to close at the executive level over six years of practitioner adoption. The Tokenomics Foundation is trying to jump that gap faster by pulling CFOs into the conversation earlier. Whether that works depends on whether the value claim framework, currently described as a “walk stage” output, matures into something an auditor would accept.
Developer Productivity Economics Are Still Unresolved
One of the more candid admissions in the briefing was around developer productivity. Stormer acknowledged that the biggest challenges in this domain are the lack of formal frameworks for measuring productivity when AI is involved, and that most organizations are defaulting to spend caps rather than value measurement. This is a structural problem. Spending limits are a blunt instrument that tells you nothing about whether a $500/month Cursor seat is generating $5,000 in engineering output or $50. For developers, the relevant question is whether AI tooling time is being tracked against shipping outcomes. Right now, most organizations are not doing that.
This matters because the purchasing decisions being made today are largely faith-based. According to ECI Research’s Google GovTech Survey, 47.2% of respondents identified “Developer velocity and ease of integration” as the factor carrying the greatest weight in their final technical selection process, once baseline compliance requirements are met. That is a velocity-first buying posture, but without measurement infrastructure, organizations cannot confirm whether they got the velocity they paid for. The Tokenomics Foundation’s value claim framework is attempting to create that measurement infrastructure, but the foundation’s own team described it as still in a “top-down” phase with significant allocation and attribution work remaining.
Where Focus 1.5 Actually Moves the Needle
For technical practitioners, Focus 1.5 is the most concrete near-term deliverable. Adding model name, model family, model version, token direction, and caching status as normalized dimensions is genuinely useful work. Right now, a team running workloads across Anthropic, AWS Bedrock, and Azure OpenAI is reconciling three different billing schemas to answer questions that should be trivially answerable: Which model am I using most? What percentage of my token spend is cache hits versus new inference? Which team or agent is responsible for this charge? Focus 1.5 makes those questions answerable from a single dataset.
The limitation is scope. As Focus working group chair Matt Calvert acknowledged directly, Focus 1.5 does not yet cover inference processing tiers, reasoning tokens, cache storage, input modality, or provisioned throughput. It also does not address the broader TCA components, such as energy, capital, or labor, that Stormer’s framework argues are the majority of actual AI cost. The short answer to whether Focus covers TCA is, in Calvert’s own words, “no, not yet.” For ITDMs evaluating whether to build cost attribution tooling now or wait for a more complete standard, that “not yet” is an important caveat. ECI Research’s Google GovTech Survey found that 55.4% of respondents reported spending 26–50% of their application development budget on maintaining legacy technical debt, which suggests that organizations already carrying heavy structural cost burdens need robust attribution frameworks before adding AI spend to the ledger, not after.
Looking Ahead
The Tokenomics Foundation is two months old. Judging it against the maturity of FinOps after six years would be unfair, but the direction is clear and the organizational design is smarter than the early FinOps playbook. By recruiting Fortune 100 CFOs to the governing board at formation rather than after the practitioner community has already defined the discipline, the foundation is trying to ensure that value measurement frameworks are CFO-legible from the start. The December 8 CFO forum will be an early test of whether that strategy is generating useful signal or just executive buy-in theater.
The bigger structural question is whether the convergence of FinOps, ITAM, ITFM, and Tokenomics into a single “technology value” umbrella produces genuine integration or just organizational proximity. Right now, the disciplines are described as overlapping and blurred, which is accurate, but the foundation has not yet produced a unified framework that tells a practitioner which team does what. The FinOps Framework 2027 update, slated for March, is the first real test of whether the convergence narrative becomes operational guidance. If it does, the LFTV umbrella could become the dominant standards body for enterprise AI economics. If it does not, organizations will continue solving this problem with fragmented tooling, siloed teams, and spend caps, which is precisely where they are today.
Stay Ahead of Application Development Trends
Get weekly analyst insights, research notes, event coverage, and AppDevANGLE updates delivered directly to your inbox.
Subscribe for Weekly Insights
Join technology leaders, practitioners, and GTM teams following the trends shaping modern software delivery.
Looking for deeper research access?
Explore ECI Research reports, survey insights, and market analysis through the ECI Research Portal.
