A contract is not a line. Nearly every one of them is subject to the availability of appropriations.
Most emerging defense companies have a contract and no line. An OTA, a framework agreement, an IDIQ seat — real instruments that obligate nothing until an appropriations account names the work.
The gap between a prototype that works and a program that pays is not technical. It is written in two bills, by two sets of committees, on a schedule nobody sends you.
The NDAA authorizes. It sets policy, creates authorities, imposes certification and reporting requirements, and establishes ceilings. Appropriations bills provide the money. A company can be authorized and unfunded, funded and unauthorized, or — most often — named in neither. The two bills are written by different committees on different tracks, and they routinely disagree about the same program in the same summer.
FY2027 is a clean illustration. In the House-passed NDAA, H.R. 8800, the Family of Affordable Mass Missiles research line is cut $52.5 million below the request. In the House appropriations bill, the same program's procurement line is increased by $300 million. One committee is pulling the development money down while the other pushes the production money up. Neither outcome is settled, because the Senate has not passed its authorization bill and has not marked up a defense appropriations bill at all.
That is the condition most emerging defense companies are actually in: multiple live, contradictory positions on their own program, in documents they have never read, decided by staff they have never met.
For defense contractors and emerging technology companies, the work divides cleanly — and each front has its own committee, its own document, and its own deadline.
Authorities, certification gates, technical data rights, multiyear procurement, acquisition pathways. A provision in one chamber's bill with no counterpart in the other lives or dies in conference. Getting one drafted, sponsored, and carried is a different job from getting money — and usually the one that decides whether the money is usable.
Defense Production Act Title III, Industrial Base Analysis and Sustainment, and the Office of Strategic Capital carry over $2.9 billion combined in the House FY2027 defense bill. These accounts pay for capacity — a second source, a facility, a qualification run — and they are general-purpose by design. Report language, not the topline, decides who they reach.
The House bill funds the Defense Autonomous Warfare Group at $1 billion, then bars obligating any of it — or the counter-small-UAS funds alongside it — until the Secretary delivers a detailed execution plan to the congressional defense committees. The bill sets the amount. The execution plan decides the vendors, and it reaches four committees before anyone spends a dollar.
Prototypes are paid out of research and development. Production needs a procurement line, a rate, and often multiyear authority. Under the current continuing resolution, a program with no FY2026 production appropriation cannot start production at all, and one that has an appropriation cannot go faster. Technical readiness is not the binding constraint.
The FY2027 House defense appropriations bill creates a procurement line for companies that have never had one: $836 million for new-entrant low-cost munition systems — $355 million for the Family of Affordable Mass Missiles and $481 million for low-cost hypersonic strike — with multiyear procurement authority attached.
Then the two bills disagree about what that authority is. H.R. 9495, Sec. 8010(c) authorizes multiyear contracts for those systems for a period of not more than three years, and adds that no such contract may be initiated unless the Secretary certifies to the Appropriations Committees, thirty days in advance, that qualification and operational test and evaluation are complete. The committee explained why in H. Rept. 119-715: the request departed from historical practice by covering families of systems rather than specific weapon systems, and by including programs entering procurement that had not yet demonstrated mature, stable production.
H.R. 8800, Sec. 1839, as passed by the House, authorizes seven program years for the same list of systems, with no test-completion gate.
Three years or seven, gated or not, is the difference between a production line a lender will finance and a pilot program. The appropriators and the authorizers will not reconcile it on their own, and neither chamber has finished. That is a room somebody needs to be in.
The largest open question in defense software is whether command and control consolidates onto a single vendor. It will be answered in text rather than in a competition.
The House Appropriations Committee cut the JADC2 development and experimentation line from a $2.11 billion request to $1.0 billion — a $1.109 billion reduction itemized as an unjustified request. The House appropriations bill separately requires any software developed, procured, or operated with Department funds to use a modular open systems approach, with a government-owned interface layer kept separate from vendor-specific application logic. The Senate authorization bill goes further, requiring multi-vendor technology and explicit protections against vendor lock-in.
The phrase "multi-vendor" appears three times in the Senate bill and not once in the House bill. There is no conference. Which text survives will set the market structure for years — and it comes down to a sentence that has not been written yet.
Send a short note describing the program, the provision or account it depends on, and the date you are working against. If there is no vehicle, we will tell you that instead.
justin@kpgpolicy.com