Package Software as Fielded Hardware

This is why defense winners usually wrap software inside a thing the Pentagon can physically buy. The hard part is not whether the code works. The hard part is getting into a budget line, matching a requirement, and surviving a buying process built around equipment, custom programs, and multiyear funding cycles. Anduril’s playbook was to turn autonomy software into towers, drones, and other fielded systems, so the buyer is approving a deployable capability, not debating a stand alone subscription.

• The procurement system favors custom built programs over commercial software. Palantir had to challenge an Army solicitation on the grounds that the service was not giving proper weight to commercial products. That is a concrete example of how hard it is for software vendors to force their way into a process designed around bespoke development.
  5 gao 2 sacra
• Hardware maps more cleanly to how budgets are organized. In the interview, defense buyers are described as working through requirement documents, program offices, Congress, and two year funding cycles. That fits an aircraft, tower, vehicle kit, or drone more naturally than a recurring seat based software contract.
  3 sacra 4 sacra
• Anduril’s early border business shows the workaround. Boeing’s SBInet deployed surveillance technology along 53 miles of Arizona border after roughly $1 billion in spending, while Anduril used self funded software and cheaper sensors to sell a fielded tower system at fixed price. The software mattered, but it moved through procurement as a hardware capability.
  1 sacra 2 sacra 6 gao

The next phase is not software replacing hardware in defense. It is software becoming the brains inside products that can be bought fast, fielded quickly, and upgraded over time. The companies that win will keep turning code into systems, then use each deployed system as a foothold for more recurring software, maintenance, and adjacent programs.