The technology for Ford's production line existed forty years before Ford used it.
Edison had commercialised electricity in New York by 1881, and his dynamo was already efficient enough. Every factory owner in America could have built Ford's factory in 1881. Almost none did. What they did instead was leave the building exactly as it was - four floors, central shafts, belts running off a single drive - and swap the coal engine for an electric one.
That got them about 6% better.
The 3x came from something nobody wanted to do: demolish the factory. Move it out of Manhattan. Build it flat and long on cheap land in New Jersey, and redesign the entire floor around small dynamos placed wherever the work happened, because electricity - unlike a steam shaft - can go anywhere. Ford did that. The productivity gain powered the American century.
Alejandro Maza, who runs product and AI at the Latin American used-car marketplace Kavak, tells this story to his team constantly, because he thinks it is happening again right now, and that most companies are once again buying the 6%.
Here is what the other version looks like.
At Kavak today, 96% of all customer interactions are handled by agents with no human involved. 95% of transactions are fully agent-run. You meet a person when you collect your keys; that is roughly it. Between 100,000 and 200,000 agents are instantiated every single day, each one in its own virtual machine. They wake up, work for three minutes or eight hours or three days, set an alarm for their next task, and go back to sleep.
This is a company that sells used cars and underwrites car loans. Not a software product. Physical inventory, regulated lending, emerging markets, an average ticket most people take three months to decide on.
The results are not marginal. NPS tripled. The agents initially converted 50% better than the human sales team, and now convert 2.1x better. Loan approvals that take two months elsewhere in Mexico take under three minutes. Warranty claims fell 26%.
Maza is clear that none of this came from adoption. It came from three decisions most companies will not make.
The first: they rebuilt the company, not the workflow. "The first instinct is you leave your structure as it is and just give ChatGPT to your team, and then there's no efficiencies, your customers have the same problems, and nothing happens." Kavak rewrote its APIs and its internal systems so that agents - not people - could operate them. The question they asked was not "where can AI help?" It was "how would we build this company in 2035, with 2035-level intelligence?" Then they built that.
The second: an agent per customer, not per task. This is the architectural bet, and it is the opposite of what almost everyone is doing. Most agentic systems are workflows - graphs, functions, handoffs between specialist agents. Kavak had built exactly that: tens of thousands of multi-agent systems, running the business, profitable, growing. Then a more capable model shipped and Maza concluded the harness itself had become the constraint. So they destroyed two years of working architecture and started again.
What replaced it is one long-running agent per customer, with its own machine, its own memory of every interaction going back years, and a single long-term goal: maximise that customer's lifetime value. The company stopped being transactional and became relational. Ten million customers in the database, most with an agent permanently assigned to them. Activating 1% of that base is worth hundreds of millions of dollars.
The third: evals are the brakes, and brakes are what let you go fast. Kavak spends roughly as much engineering time, money and compute on evaluation as on building the agents themselves. Maza's framing is that companies moving slowly on AI are moving slowly because they cannot see what is happening - and the answer to that is not more caution, it is better instrumentation. And the thing they measure is not calls handled or minutes saved. It is: did the customer convert, did they get value, did they come back. "That's where most things break. I see companies measuring number of calls or minutes during the call - superficial KPIs that give you some information but don't really work."
Two details are worth sitting with.
The first is what happened to the org chart. In most deployments, when an agent gets stuck it escalates to a human queue and the trail goes cold - which means the failure never becomes training data. Kavak inverted it. The agent hits a wall and calls an API asking for help, and on the other end of that API is a person. Map it and you get human teams that have an agent, not the other way round. Sometimes the agent is the boss.
The second is the AI CEO. They carved out one Mexican city, Cuernavaca, and put an agent in charge of it. Target for month one was to double profit. It missed - it only delivered 50% more. It reads every number, forecasts, and messages physical staff each morning with their plan, asking for voice notes back. Inventory, financing penetration, satisfaction all improved. "That was the last job AI was supposed to take."
Everyone at Kavak, from the CEO to the mechanics, goes through a six-week internal programme they call the Jedi Academy. They ship a production agent at the end of it. The point is not to turn mechanics into AI engineers. It is that there is no version of this company where you do not know how to work alongside the thing.
And here is the part that should interest anyone building rather than defending: Maza does not think incumbents will do this. Not because they are stupid, but because Schumpeter was right. It is nearly impossible for the CEO of a large public company to stand up and say they are demolishing forty years of accumulated structure to rebuild around a technology that is two years old. They will adopt superficially, book their 6%, and report it as progress.
Which leaves the rebuild to whoever is willing to do it from scratch.
Source: Kavak's Playbook for Rebuilding a Company Around AI - a16z