All essays
§028 · Architecture

Federal autonomy budgets are moving while allied tech firms watch from the wrong window

Last week's appropriations data shows NASA obligating funds for Orion crew capsule development, the Air Force Research Laboratory contracting through BlueStaq, and Kratos securing SBIR Phase III work—all against a backdrop of accelerating unmanned systems procurement across allied navies. The pattern is familiar: by the time these obligations appear in public records, the commercial architecture decisions are already locked.

3 min · Published 2026-10-19 · By Bridger

The collision between crewed deep-space missions and autonomous maritime swarms is not a metaphor. It is this week's federal spending portrait. NASA's Orion obligation sits in the same dataset as Air Force Research Laboratory tasking and a second Chinese UUV mothership entering service. The simultaneity is not coincidental. Federal buyers are allocating budget authority across human-in-the-loop and machine-only architectures in parallel, and the firms positioned to shape those architectures were inside the tent 18 to 36 months before the obligation notices went public.

BlueStaq and Kratos are instructive cases. Both appear in this week's appropriations actions—BlueStaq supporting AFRL and Space Systems Command requirements, Kratos executing under an SBIR Phase III vehicle tied to COSMIC AES. Neither contract represents a cold start. SBIR Phase III awards, in particular, are a post-prototype commercialisation path: the technical risk conversation happened in Phase II; by Phase III, the government is buying at scale under an OTA-style authority that bypasses full and open competition. The allied tech firm that learns about the opportunity at the Phase III stage has already lost.

The pre-RFP window is where architecture gets set

Federal procurement rewards early positioning because the Request for Proposal is not where requirements are written—it is where requirements are formalised. The substantive decisions—whether a capability will be crewed or autonomous, cloud-native or on-premise, open-architecture or proprietary—are made in working groups, prototype evaluations, and informal technical exchanges that begin years before contract award. This week's intelligence assessments confirm the pattern: the U.S., Taiwan, Australia, and European allies are simultaneously advancing unmanned surface and underwater vehicle procurement, corroborated by imagery of China's second UUV mothership. The allied firms that will win those contracts are already embedded in the technical dialogue.

The allied tech firm that learns about the opportunity at the Phase III stage has already lost.

The Department of Energy obligations in this week's data—Honeywell managing the National Security Campus, UChicago Argonne operating Argonne National Laboratory, Sandia LLC running Sandia—represent the opposite end of the spectrum: multi-decade, sole-source management and operations contracts where the incumbent advantage is structural. But even here, the architecture decisions that determine which technologies get integrated into the lab mission are made in pre-competitive forums: technical working groups, federally funded R&D centres, and university-affiliated research centres. The allied firm that waits for a teaming invitation is negotiating from a position of dependency, not partnership.

What allied tech firms miss by staying outside

The asymmetry is not that allied firms lack capability—it is that they lack visibility into the pre-RFP window where capability gets translated into requirements language. When Booz Allen Hamilton wins a CDC Data Modernization Accelerator task order, it is executing under a pre-existing IDIQ vehicle where the scope, ceiling, and evaluation criteria were set years prior. The allied firm that approaches the program office after the task order drops is offering a capability the government has already decided how to buy.

This week's budget execution cluster shows no coordinated anomaly—just dispersed, routine FY25-26 spending except for sustained DHS immigration enforcement obligations of approximately $585 million. That exception is itself revealing: when a policy priority is clear and stable, budget execution becomes predictable, and the firms positioned in the relevant contract vehicles enjoy sustained demand. Allied tech firms entering the US federal market often assume the challenge is winning a single contract. The actual challenge is positioning in the multi-year pipeline where sustained demand flows through pre-competed vehicles.

The solution is not to mimic incumbent behaviour—allied firms bring differentiated technology and, often, sovereign-backed R&D momentum that US primes cannot replicate. The solution is to enter the federal market at the correct altitude: not at RFP release, but at the requirements-formation stage where architecture is still negotiable. That requires treating federal business development as an intelligence problem—tracking program office priorities, identifying technical working groups, and understanding which contract vehicles are being shaped for future competitions—rather than a sales problem. Bridger exists to collapse that asymmetry. The firms that use it are not waiting for the RFP. They are shaping the requirement.

Built on this thesis

See how it shows up in the product.

Request access