I came across the paper behind this post through Azeem Azhar's Exponential View newsletter, in a short item noting that AI-native startups start smaller and stay smaller than non-AI-native startups. Reading the actual research behind it sent me somewhere Azhar didn't go: straight into the relationship between this pattern and the organizational dynamics lean manufacturing and lean startup have been arguing for, in their own domains, for decades.
A startup called FazeShift has ten employees. It handles the entire accounts receivable lifecycle for its enterprise customers: invoicing, collections, cash application, matching payments to invoices, chasing down the exceptions that used to require an analyst staring at a spreadsheet. A traditional AR software vendor selling the same outcome would need a much bigger team, not because FazeShift's customers are easier to please, but because someone still has to build the firm-specific exception handling and someone still has to staff the operations that resolve what the software can't. FazeShift's AI agents do both jobs. The company just never built the department.
That example comes from a working paper out of Harvard Business School and INSEAD, "AI-Native Firms," by Hyunjin Kim and Rembrand Koning. They pulled workforce data across five years of Y Combinator batches and a broader pool of U.S. venture-backed startups, comparing firms that qualify as AI-native to otherwise similar firms in the same industry and funding cohort. The AI-native firms are 25% smaller. Their hierarchies run about a seniority level flatter. They employ more engineers and fewer of basically everyone else: sales, operations, finance, admin. And despite being smaller, they raise comparable funding and hit comparable valuations, which rules out the easy explanation that they're just under-resourced or low-quality entrants. They're doing more with less, on purpose, by design.
Plenty of people have already made the case that giving your team access to AI makes them faster. Kim and Koning actually tested that directly, coding which firms' job postings mention specific AI tools, and found it barely predicts anything about firm size or hierarchy. What predicts the shrinkage is something else: whether the firm builds AI directly into what it sells, so the product does the work that used to require a department.
The gap lean spent seventy years trying to close
Traditional lean manufacturing, the Toyota Production System and everything that descended from it, was never really about cutting headcount for its own sake. It was about creating flow and value from the perspective of the customer, in part by closing the distance between the person doing the work and the person with the authority to fix it. Every layer of hierarchy you add between the assembly line and the decision is a layer where information degrades, where problems get filtered into reports instead of fixed on the spot. Ohno's obsession with andon cords and quality built in at the source, rather than inspected afterward by a separate department, enabled an attack on the coordination tax that hierarchy imposes.
Lean startup, the Eric Ries and Steve Blank flavor that showed up a couple decades later, took a related but distinct idea and pointed it at company formation instead of factory floors. The unit of work wasn't supposed to be a department handing a project down a chain of approvals. It was supposed to be a small cross-functional team that owned a hypothesis end to end: build, measure, learn, repeat, without anyone outside the loop. The team stayed small because speed of learning was the entire point. You didn't want a layer of managers translating between the people building the thing and the people who understood the customer.
What Kim and Koning are documenting looks like the lean startup team that never had to graduate. In a normal company, that small cross-functional unit eventually hits a wall. The product works, customers show up, and now someone has to build a sales function, a support function, an operations team to handle the volume. Headcount becomes the price of growth. What the AI-native firms in this data seem to have figured out is that you can keep paying that price in compute instead of people, at least for the parts of the business where the "team" doing the work was always knowledge work to begin with.
Gamma, the AI presentation startup the paper uses as a case study, makes this concrete. A traditional firm offering "we'll build your deck for you" scales by hiring: someone scopes the request, someone designs it, someone reviews it before it goes out. Gamma turned that into a product interaction instead of a workflow. Thirty employees, millions of users, $50 million in annual revenue within two years. The deck still gets made. Nobody had to build the department that used to make it.
Where this differs from automation as we've known it
It's worth being precise about why this isn't just the next chapter in "software eats jobs." Giving a worker a tool that makes them 30% faster at an existing task is the process channel, and Kim and Koning's data says that channel alone doesn't predict smaller, flatter firms. What predicts it is moving the judgment itself into the product, so the customer interacts with the AI directly rather than with a person using AI. Legion Health, an AI psychiatry platform built on language models, has 28 employees. Intellect, a non-AI mental health company built on a network of human therapists, has 446. Same market, same underlying service. One scales with people, one scales with compute. That gap is the entire argument in a single comparison.
Lean and lean startup were both, in their own domains, arguments against unnecessary coordination. Lean said: don't make a worker wait for an inspector to tell them what they already know. Lean startup said: don't make a founder wait for a department to validate what a small team could learn directly. AI-native firms are running a third version of the same argument, except now the thing closing the gap between work and judgment isn't a flatter org chart. It's the product itself.
The open question is whether that's a permanent shift in how firms get built, or a feature of right now, when the underlying models are improving fast enough that betting your headcount on them looks smart. Lean took decades to prove it wasn't a fad. This one's had a couple years.
Either way, it puts a different question in front of two different audiences. If you're running an existing company and your AI strategy is a tool rollout, Copilot here, a Claude agent there, ask whether you've actually moved any judgment into the product itself, or just made the existing company a bit faster at being the existing company. And if you're starting something new, the harder discipline isn't proving you can build small. It's resisting the old instinct to hire the department once the product starts working, when the entire point was never needing one.