The Self-Driving Company

**Nathaniel Whittemore** (0:00)
Today on The AI Daily Brief, what it means for AI to create self-driving companies. The AI Daily Brief is a daily podcast and video about the most important news and discussions in AI.
All right, friends, quick announcements before we dive in. First of all, thank you to today's sponsors, Robots and Pencils, Blitzi, Section and Airtable. To get an ad-free version of the show, go to patreon.com/aidailybrief, or you can subscribe on Apple Podcasts. To learn more about sponsoring the show, send us a note at sponsors at aidailybrief.ai.
This is, of course, a weekend episode, a big thing slash long reads episode, and the CEO of Replit just dropped a great big think piece. So let's dive in.
One of the things that is happening, and really has been happening all year, is that AI has advanced in such a way that it's no longer just making us rethink how we do work on an individual level or even a team level, but is starting to implicate the entire design of the company itself. Some of the experiments that people have been really excited about this year are things like PULSIA, which started as a framework for entirely no-human companies, and that has evolved a bit to be a new AI-native company operating system that dramatically minimizes the base activation energy needed to build and maintain a company, even if it doesn't require there being no humans at all. But it's not just totally new efforts that are seeing the impact of new agentic ways of working. In fact, as cool as some of these brand new startup style experiments are, ultimately their examples can be a little bit hard to see how they apply to today's existing companies, which is why it's really interesting to see when companies that are at least slightly larger, even if one might still consider them startups, are sharing their totally new ways of working that are, well, working. We got a great example of this last week when Replit CEO Amjad Massad published a new post called The Self-Driving Company. I'm going to read that blog post from X and then we'll come back and talk about some of the implications.
The Self-Driving Company We're beginning to see what happens when a company learns to operate itself. In the past six months, engineers at Replit have nearly tripled code output. Review times held steady. Reversions and product incidents have stayed flat. Quality metrics improved and releases have accelerated. All the typical trade-offs you might expect have not occurred. While the code is the visible part, what's happening under the surface is much more interesting. Agents now investigate production incidents, review pull requests, answer questions, analyze business data, triage support tickets, research sales accounts, and improve the systems that power Replit agent itself. It feels like a single master intelligence threaded through every employee even though it is not. It is an expanding system of agents operating across the company, taking goals from people, gathering context, performing work, checking the results, and escalating when human judgment is needed. We think this represents the beginning of a new kind of organization, the self-driving company. A self-driving company is not one without people. People still choose the destination. They decide which problems matter, make difficult trade-offs, exercise taste, and take responsibility for the outcome.
But increasingly, they do not perform every step required to get there.
The shift began late last year. Like many people working in AI, we returned from the Christmas break feeling that something fundamental had changed. Models could sustain work over much longer horizons. Tasks that had repeatedly failed, like alert triage and root cause investigation, began working. AI started solving some of our most stubborn bugs. We stopped treating agents as tools that lived inside an editor or chat window. We wove them carefully into the fabric of the company itself.
Once engineering proved the value, adoption took on a life of its own. Team after team started offloading their most tedious work, reclaiming time for the strategic and creative thinking that actually moves the business. People don't feel like they've been automated. They feel like they've been promoted. This is the story of how AI has completely changed the way that we work at Replit. Engineering saw the impact first. In late January, we turned up infrastructure to experiment with internal agent use cases quickly. We leveraged our agent harness, micro VMs and remote file systems infrastructure, so any engineer could orchestrate swarms of agents in parallel. Then we locked the whole thing behind access policies, token proxies, audit logging, and our zero trust network.
At that point, we felt safe giving the agent access to all the things we use to get our jobs done. GitHub, GCP, Linear, Notion, Slack, Zendesk, and more. With context across systems, we saw a leap forward in productivity. Experiments that previously failed became easy. The most immediate impact was in coding stats. We were in a sprint week leading up to Agent 4 release in March, where we typically see a big spike. Meetings disappear, scope is known, and engineering shifts into pure execution mode, often for up to 16 hours per day. But this time was different. Our productivity curve bent upward in a way none of us had seen before, which can be traced to the adoption of our new internal agentic system. From early January to late June, there was a 5.8x increase in the lines of code contributed. Part of this increase can be attributed to hiring well. Our new agent accelerates time to productivity, which is great, but we can remove the hiring effect for cleaner data. Keeping a consistent cohort of authors, we see 2.9x as much code as before. Traditionally, it's considered excellent if you keep output per engineer flat as you scale a team. We just tripled per engineer rate while doubling the team. Now you might wonder who is reviewing all this new code and whether we've created a new bottleneck in the review process.