Scale Through Software and Hardware Integration
Scott Sanders, Chief Growth Officer at Forterra, on autonomy for every vehicle
In defense and industrial autonomy, the hard part is not writing the autonomy model, it is turning that model into a product that can be manufactured, certified, serviced, upgraded, and bought repeatedly. Forterra is making the point that software only margins do not matter if the software cannot survive bad networks, rugged vehicles, factory line integration, and multi year procurement. The winning stack is the one that closes operationally and commercially, not the one that sits highest in the architecture.
-
Forterra sells one core autonomy kit across defense vehicles and commercial yard trucks, which lets it reuse the same sensors, compute, and software while buying parts in higher volumes and integrating directly with OEM production. That is how hardware becomes margin accretive instead of a drag.
-
The real bottleneck is downstream of the demo. Sanders describes tracking exactly what was shipped, supporting systems in the field, managing change logs, forecasting production, and avoiding early contract terms or SBIR pricing that block long term scale. That is why a pilot is only a small fraction of the work.
-
The closest comparables show two different answers to the same problem. Anduril bundles Lattice with its own systems and third party integrations, while Applied Intuition proves there is demand for a more modular software layer. But even Applied is winning by getting software onto real military vehicles fast, not by staying purely abstract.
The market is heading toward fewer pure software autonomy vendors and more companies that own the messy middle between code and deployment. That favors teams that can pair edge software with OEM integration, supply chain discipline, and programmatic contracting. In autonomy, scale will belong to the companies that can ship thousands of working systems, not just impressive demos.