May Mobility is going public in a SPAC transaction that values the autonomous vehicle company at approximately $1.4 billion. The obvious story is the valuation. The more important logistics story is the operating model.
May Mobility is attempting to separate autonomous intelligence from transportation assets. Its partners can own the vehicles, operate the depots, maintain the fleets and provide the customer interface, while May provides the autonomous driving system, software, remote assistance and continuing technology services. May is not just asking whether autonomous vehicles can work. It is asking whether autonomous transportation can scale as a technology layer without the autonomy company owning the transportation network beneath it.
That is a much bigger question.
The $1.4 Billion Bet
May Mobility announced a definitive agreement to combine with ACP Holdings Acquisition Corp. The transaction implies a pro forma enterprise value of approximately $1.4 billion and could provide up to $337 million in gross proceeds, including a $120 million PIPE and as much as $217 million held in the SPAC’s trust account. The company expects to trade on Nasdaq under the ticker MAY if the transaction closes.
The current business is still relatively small. May generated approximately $10 million in revenue in 2025, produced a 27 percent gross margin and burned approximately $93 million in cash. It says it has completed more than 550,000 commercial autonomous rides covering roughly 1.1 million miles. So the valuation is clearly not about the company May Mobility is today; it is about what investors believe the operating model might become.
Autonomy Without Owning the Transportation Network
May Mobility calls its model Autonomy-as-a-Service. The architecture is straightforward: fleet partners can own and operate the vehicles, OEMs provide the underlying vehicle platforms, transportation platforms bring demand, and May supplies the autonomous driving system and supporting software layer.
That is a fundamentally different proposition from building a vertically integrated autonomous transportation company, but it also looks familiar. Transportation management systems influence enormous freight networks without owning trucks. 3PLs orchestrate transportation and warehousing without owning every asset involved. Digital freight platforms connect capacity and demand without becoming traditional carriers.
The logistics industry has spent decades separating orchestration from asset ownership. May Mobility is applying the same logic to autonomy.
Toyota is its primary OEM partner, while May also has relationships with Uber, Lyft, Grab and CaoCao. Instead of rebuilding the transportation ecosystem around its technology, May is attempting to insert its autonomous intelligence into networks that already exist. That is the real bet.
Capital Efficiency May Matter as Much as Autonomy
Autonomous transportation has always had two scaling problems. The first is technical: can the vehicle operate safely without a human driver? The second is economic: can thousands, and eventually millions, of autonomous vehicles be deployed without requiring equally extraordinary amounts of capital?
That second problem is becoming more important. Vehicles still have to be purchased. Sensors still cost money. Compute platforms must be installed. Depots still need to operate. Tires still wear out. Vehicles still require maintenance, cleaning, charging or fueling, while remote operations still require people, systems and infrastructure.
Removing the driver does not remove the transportation operation.
May’s strategy pushes much of that operational burden toward organizations already designed to manage physical fleets, allowing May to concentrate more heavily on the intelligence layer. The company says this model could eventually support gross margins of up to 70 percent and EBIT margins of as much as 30 percent. Those are management targets, not current results; its 2025 gross margin was 27 percent.
But those numbers show exactly what May is trying to become. It does not want the economics of a transportation fleet. It wants the economics of a technology platform embedded inside transportation fleets.
Asset-Light Does Not Mean Operations-Light
There is a catch. Separating autonomy from fleet ownership may improve capital efficiency, but it also creates more interfaces. Vehicle uptime matters. Maintenance quality matters. Software releases matter. Depot execution matters. Communications between the vehicle, fleet operator, autonomy provider and customer platform matter.
And somebody still needs to own the exception when something goes wrong.
This is where logistics executives should recognize the architecture immediately. Outsourcing an asset does not outsource the need to orchestrate it. Usually, it makes orchestration more important.
Autonomous transportation will not simply be a vehicle plus an AI model. It will be a system of OEMs, fleet owners, maintenance providers, telecommunications networks, customer platforms, remote operations centers and software providers.
The vehicle is one node. The network is the product.
Autonomy Is Becoming an Industrialization Problem
One of the most revealing details in May Mobility’s announcement has relatively little to do with artificial intelligence. The company says it plans to invest part of the proceeds in its supply chain to reduce bill-of-materials costs, while also funding R&D and industrialization.
That is what happens when a technology begins moving from demonstration toward deployment. A lidar unit that works but costs too much becomes a supply chain problem. A compute platform that cannot be sourced economically becomes a supply chain problem. A redundant braking architecture that is difficult to manufacture becomes a supply chain problem. A sensor package with too many custom components becomes a supply chain problem.
At that point, procurement, supplier development, component standardization, manufacturing engineering and lifecycle cost begin to matter as much as another improvement in the driving algorithm. The question is no longer simply, Can we make it work? It becomes, Can we manufacture it, deploy it, maintain it and operate it economically at scale?
That is a very different stage of the market, and it is much closer to logistics.
The Freight Analogy Is Hard to Ignore
May Mobility is focused on passenger transportation, not freight, but the operating model translates surprisingly well. Consider autonomous trucking: an OEM builds the truck, an autonomy provider supplies the driving system, a carrier owns the equipment, a digital freight network brings loads, a third party operates autonomous truck terminals, maintenance providers service the vehicles, and remote operations centers manage exceptions.
No single company has to own the entire stack. The competitive advantage shifts toward orchestration.
The same logic can apply in middle-mile transportation, yards, ports and closed industrial environments. The autonomy provider does not necessarily need to become the transportation company. It may become the intelligence layer used by transportation companies.
That is a much more scalable proposition if the economics work.
The Real Test Starts Now
May already has deployments in the United States and Japan and relationships with several major transportation platforms. The company is also targeting additional commercial expansion, including operations with Uber in Arlington, Texas. Those deployments will tell us far more than the SPAC valuation.
Can the company reproduce deployments across markets? Can partners operate the vehicles efficiently? Can the hardware cost curve come down? Can May maintain software performance across fleets it does not own? Can the partner ecosystem deliver consistent uptime? Those are no longer simply autonomy questions. They are systems questions, industrialization questions and network-design questions.
Increasingly, they are supply chain questions.
The $1.4 billion valuation will get the headline. The more consequential experiment is whether autonomous transportation can be separated into specialized layers—vehicle, fleet, demand, maintenance and intelligence—and then recombined into a scalable operating system.
If May Mobility proves that architecture works, autonomy will have crossed an important threshold. It will no longer be primarily an AI problem.
It will be an industrialization, orchestration and unit-economics problem.
That is where logistics executives should start paying attention.
The post May Mobility’s $1.4B SPAC Tests Asset-Light Autonomy appeared first on Logistics Viewpoints.