The self-driving company: six levels of operational autonomy
The car industry agreed on what autonomy means before it built it. Companies are automating without that vocabulary — so here's ours.
PostHog recently shipped something they describe as putting your product into self-driving mode. The shape of it is worth studying: signals come in from errors and session replays, agents cluster them into reports, reports become pull requests, and nothing reaches production until a human clicks merge. Every change ships with the instrumentation to measure whether it worked — and if the metric doesn't move, that becomes a new signal.
That last part is the bit most people skim, and it's the whole thing. The loop closes.
It's also not unique to product engineering. The same shape is already running in places most companies don't think of as autonomous:
- Dependency management. Tools like Dependabot and Renovate watch for updates, open the pull request, run your tests, and wait for a human. Nobody calls this AI any more. It's just how repositories work.
- Ad platforms. Google and Meta's automated bidding has been setting budgets and creative allocation against an outcome signal for years. Most marketers now describe their own performance targets rather than their bids.
- Fraud and risk. Payment fraud systems score, decide, and retrain on the outcome of their own decisions, at a volume no review team could touch.
- Infrastructure. Autoscaling and automated rollback have been closing the observe-decide-act loop in production for a decade.
In each case the pattern is identical: a signal, a decision, an action, and — critically — a measurement that feeds back. What's new is that the same loop is now affordable for the messy, language-shaped work that used to need a person: support, operations, finance admin, reporting, coordination.
The levels
Automotive engineering got something right early: before building autonomy, the industry agreed a shared vocabulary for what each degree of it meant. Companies are automating without that, which is why "we're doing AI" tells you nothing. Here's the scale we use internally.
Two observations from doing this in live businesses.
Most companies are at Level 1 and think they're at Level 3. Rolling out a chat assistant to everyone feels transformative — usage is up, people are pleased — but nothing changed structurally. Remove the tool and the company runs exactly as before, slightly slower. That's a productivity feature, not autonomy. A useful test: if a person has to remember to start it, you're at Level 2 at best.
The hard jump is 3 to 4, not 0 to 1. Getting an agent to act is now easy. Getting it to know whether it did the right thing means you need a definition of the right thing, instrumentation on the outcome, and somewhere durable to keep what was learned. That's not a model problem. That's an operating-system problem, and it's why most deployments plateau at "impressive demo, unclear impact".
Humans in charge, not humans in the loop
One deliberate word choice. "Human in the loop" positions the person as a step in a pipeline — a checkpoint, and eventually a bottleneck to be removed. That framing quietly makes your best operators into approval clicks.
We build for humans in charge. The person sets intent, defines the boundary, and reviews exceptions. The system does the volume and reports what it did. Nobody's job is to rubber-stamp; the job is to decide what good looks like and to notice when reality disagrees.
That distinction isn't sentimentality. Level 4 only works if someone with judgement is watching the measurements and willing to say the loop is optimising for the wrong thing. Take that person out and you don't get a self-driving company — you get one confidently accelerating in a direction nobody chose.
← All posts