Forterra's performance-first autonomy playbook
Scott Sanders, chief growth officer at Forterra, on the defense tech startup playbook
This reveals Forterra is trying to win defense and industrial autonomy the hard way, by making one core stack cheap, interoperable, and good enough that customers keep choosing it without being trapped. The company sells a fixed price kit, then adds integration, testing, and mission specific work around it, instead of carving the product into premium tiers or hiding the system behind proprietary lockups. That only works if the same stack can ship across many vehicle types and markets at scale.
-
Forterra frames its product like a commercial item, with the same base system sold into defense and commercial use cases. That matters because cost plus contractors grow by adding labor, while a product company grows by reusing the same hardware and software on more vehicles with lower unit costs over time.
-
The stickiness comes from field performance and integration into real workflows. On the DoD side that means autonomy on missile launchers, logistics vehicles, and future platforms, plus links into battlefield C2. In yards it means tying autonomous tractors into ERP systems, weak networks, and constantly changing container movements.
-
This is also a direct contrast with both primes and narrow autonomy startups. Primes tend to monetize custom work and headcount, while vertical specific autonomy companies are exposed to one market's budget and timing. Forterra argues a horizontal stack lets it shift between defense demand today and commercial demand as those markets mature.
Going forward, the winners in defense robotics are likely to look less like closed software vendors and more like scaled product manufacturers with strong integration layers. If Forterra keeps proving the same autonomy stack on more vehicle classes and programs, performance itself becomes the moat, and the installed base becomes easier to expand without forcing customers into black box dependence.