Forterra on repeatable autonomy deployments
Scott Sanders, chief growth officer at Forterra, on the defense tech startup playbook
Negative pilot economics usually mean the company has not built a repeatable deployment machine yet. In commercial autonomy, a five vehicle test can look like traction, but the vendor is often staffing remote operators, field engineers, safety support, and custom integration work that costs more than the pilot revenue. Forterra is positioning around concentrated yard environments, OEM integration with Kalmar, and long term contract structure so each added deployment requires less babysitting and can scale into real product revenue.
-
Forterra picked terminal tractors partly because ports and yards have many vehicles in one place. That concentration keeps supervision and service costs lower than trucking or earthmoving, where fleets are fragmented and every new site adds expensive support overhead.
-
The core failure mode in autonomy pilots is selling a custom demo before solving factory integration, safety case, pricing, and serviceability. Forterra argues that if those pieces are not lined up early, a pilot may prove the tech works but still cannot turn into a scaled contract.
-
The better analogs in defense autonomy are companies moving from hardware sales into repeatable software or multi year system contracts. Shield AI is layering Hivemind software on top of drone sales, and Quantum Systems is pushing toward software subscriptions, both aimed at improving margins beyond one off deployments.
The market is moving toward autonomy vendors that can ship standardized systems, not staffed science projects. As OEM partnerships, recurring software layers, and multi year procurement models mature, the winners will be the companies that turn each deployment into a cheaper repeatable rollout instead of a new custom pilot.