Essay
Everyone Is Climbing Toward AI-Native. Few Have Asked What's at the Top.
The maturity ladder tops out at total dependency — and it can't tell the difference between capability you own and capability you rent.
Everyone is climbing toward AI-native. Very few people have asked what is at the top.
The usual maturity ladder runs Equipped, Assisted, Augmented, Native, and the test for each is simple. Take the AI away. What breaks?
At Equipped, nothing. You bought software.
At Assisted, work reverts to manual pace.
At Augmented, teams drown in backlog.
At Native, operations stop. There is no manual fallback, because the work was rebuilt around the capability.
That last line should give you pause. We are treating total dependency as an achievement.
The electrification bargain — and why AI breaks it
The usual defence is that this is the price of a step change in economics, and that is roughly what happened with electrification. Factories became dependent on power and it was worth it.
But factories owned their generators. Once the capital was spent, the marginal cost of electricity fell and stayed down.
Today AI capability mostly arrives through an API contract. Pricing, model weights and access terms can change overnight, and several enterprises found that out this year. So the deeper your dependency, the less leverage you have with the party you depend on. That is the opposite of the electrification bargain.
Same tier, very different position
Which makes the ladder incomplete, because it cannot tell these two apart.
An organisation running its own models on its own infrastructure, operating at Native, has accepted operational exposure.
An organisation at Native on a hosted frontier model has handed a supplier structural leverage over whether it can function.
Same tier. Very different position.
So the honest question is not how do you get to Native. It is which parts of the business should be Native, and whether that rests on capability you control or capability you rent.
For a lot of enterprises, Augmented on rented capability and Native on what you own is a more defensible target than Native everywhere.
Nobody actually decides this
And that is the real problem. You automate a process because it is cheaper. Two years later the people who did it manually have moved on, and the fallback quietly stopped existing. No one accepted that exposure. It accumulated.
We ran the removal test on ourselves and landed at Assisted, moving toward Augmented. The useful part was not the score. It was realising we had never asked which tier we actually wanted.
Run it on your own stack. Then ask the harder question. For the processes that would stop, do you own that capability, or rent it?
Opinions are my own.