What Survived and What Died in the FY26 NDAA Conference Agreement

The fiscal year 2026 National Defense Authorization Act has cleared both chambers of Congress and is heading to the President's desk. The total authorization landed at $900.5 billion. The more consequential story, as always, is in the conference report language.

Several of the ambitious commercial contracting reforms that came out of the Senate survived conference. Others did not. For defense contractors, venture investors, and commercial technology companies evaluating federal exposure, the specific pattern of what made it and what didn't tells you where the House and Senate could agree, and where the structural friction against commercial acquisition reform is still sitting.

This is a clear read on both sides of the ledger.

What survived

Portfolio Acquisition Executives (Section 1802). The final bill formally establishes Portfolio Acquisition Executives, shifting from the traditional Program Executive Officer structure to portfolio-based management of related capabilities. PAEs carry substantial authority, including the power to modify, discontinue, or terminate programs with cost growth, performance deficiencies, or schedule delays. They are statutorily required to prioritize Other Transaction Agreements for prototypes and commercial procurement, run iterative development cycles, and maintain direct liaison with operational users. Program managers report to PAEs. PAEs report to service or component acquisition executives.

The engagement model this creates is materially different from today. Contractors will interact with portfolio-level leadership making decisions across related programs, rather than navigating multiple program offices individually. That accelerates technology insertion on successful products and accelerates termination on unsuccessful ones. The mandate to prioritize OTAs and commercial procurement should favor companies that have built around those pathways.

Combatant Command Experimentation Authority (Section 873). COCOMs gain direct authority to conduct experimentation, prototyping, and technology demonstrations against operational needs they identify. This moves innovation authority closer to the warfighter and creates a new buyer inside the Department that most commercial vendors have not historically sold to. Companies building COCOM-facing capture strategies now will have a real customer to sell into in FY26.

BOOST Program (Section 1833). The Director of the Defense Innovation Unit is now required to establish the Bridging Operational Objectives and Support for Transition program to move technologies from successful prototypes into established capability development and procurement. This is a direct attempt to close the valley of death, and it complements Section 913, which authorizes DIU to establish regional outreach centers domestically and internationally.

For companies already working inside the DIU ecosystem, BOOST provides a structured path from pilot into larger-scale procurement. It does not, however, replace the competitive prototype requirement under OTAs. More on that below.

SOCOM Urgent Innovative Technologies Initiative (Section 863). A new pilot program lets U.S. Special Operations Command accelerate research, development, testing, procurement, and initial sustainment of innovative technologies against emerging mission requirements. The inclusion of "initial sustainment" authority matters. It allows SOCOM to procure and maintain innovative technologies without immediately transitioning to traditional contracts, which directly addresses the common failure pattern where prototypes lack the support infrastructure to stay operational after fielding.

For companies working in advanced communications, autonomous systems, low-observable technologies, advanced materials, or specialized equipment, this creates a dedicated fast-track channel.

Nontraditional Defense Contractor Exemptions (Section 1826). The final bill exempts nontraditional defense contractors (entities that have not performed defense contracts subject to full cost accounting standards for at least a year, per Section 3014 of Title 10) from certain business system requirements. This lowers the compliance load that has historically discouraged commercial technology companies from engaging with the Pentagon.

Commercial Product Preference Reforms (Sections 1822-1824). Three related provisions strengthen the Department's preference for commercial solutions.

Section 1822 establishes a formal non-availability process. Contracting officers and program managers must submit written memoranda explaining any decision to use non-commercial solicitation procedures, grounded in market research and requirements analysis. Compliance expands to consultants and advisors supporting requirements development.

Section 1823 expands the purposes for which Commercial Solutions Openings procedures can be used and creates authority for sole-source follow-on procurements, provided the procedures of Section 4022 or 3204 are followed.

Section 1824 limits the flowdown of contract clauses to subcontracts and supply agreements for commercial products or services, reducing compliance burden on commercial suppliers in the defense industrial base.

Consumption-Based Solutions (Section 1825). The procedures for consumption-based solutions (metered and billed based on actual usage with predetermined pricing) are now permanent. This matters specifically for cloud computing and SaaS providers, and it creates a stable framework for recurring-revenue commercial models inside the Department.

Contested Logistics Prototyping Expansion (Section 871). The demonstration and prototyping program for contested logistics expands in scope, with a new requirement for the Secretary of Defense to establish best practices for reducing the time needed to return repaired equipment to service through additive manufacturing closer to the point of use. Companies working on distributed manufacturing, 3D printing, and forward-deployed production capabilities are the direct beneficiaries. The original Senate version would have made the program permanent by removing its three-year sunset. The final version expands scope but the permanency question appears to have been modified.

What didn't survive

Four reforms from the Senate version were dropped or meaningfully weakened in conference. Each is worth reading closely, because the pattern points to where the institutional resistance to commercial acquisition reform still lives.

OTA Follow-On Production Without Competitive Prototype. This was potentially the most consequential OTA reform in the Senate bill. It would have allowed follow-on production under Other Transaction Agreements without requiring a separate competitive prototype, provided the capability had been demonstrated in a relevant environment and the acquisition executive issued a written determination.

Its absence from the final bill is the single biggest disappointment for defense tech investors and vendors operating inside the OTA ecosystem. The competitive prototype requirement for production transitions has been one of the structural weaknesses of OTAs for years. Removing it would have compressed the path from successful prototype to production contract significantly. That path still has a competition gate in FY26, and companies planning around OTA-to-production transitions need to keep planning accordingly.

Nontraditional Contractors Treated as Commercial. The Senate version would have required contracting officers to treat nontraditional defense contractors at any tier as commercial products and commercial services unless a written determination was approved by the head of the contracting activity. That presumption of commercial status did not survive conference.

Section 1826 provides real exemptions for nontraditional contractors, but the final bill stops short of the automatic commercial treatment the Senate wanted. Vendors still need to pay attention to which requirements can be waived and which can't, on a procurement-by-procurement basis.

Modified Definition of Nontraditional Defense Contractor. The Senate wanted to expand the definition of nontraditional defense contractor to include business entities that don't qualify as a covered segment under DFARS 231.205-18. That definitional change would have broadened the pool of companies eligible for streamlined procedures. It was not included.

Cloud Computing Competition Review. The Senate committee report directed the DoD Inspector General to review sole-source awards in cloud computing contracting over the past three years, assessing justification quality, market research, and systemic competition concerns. That review was not included as a formal requirement in the final bill. The conference agreement does include IG audit language on cloud contracts, but it focuses on national security risks from foreign personnel access rather than the competition and vendor concentration questions the Senate was pursuing.

For any company competing in defense cloud, this matters. The Senate was pointed at vendor concentration. The final bill is pointed at personnel access. Both are real issues, but they lead to different findings and different policy responses.

Portfolio Acquisition Executive Capstone Requirements. The Senate version contained capstone requirements for three or more portfolio acquisition executives, developed in consultation with the Joint Requirements Oversight Council, to set strategic guidance for portfolio-level decision-making. Those capstone requirements did not make it into the final bill. PAEs are formally established under Section 1802, but they will not have the additional layer of statutory strategic direction the Senate wanted.

What this means for the market

The final FY26 NDAA is a mixed outcome for commercial acquisition reform. The reforms that survived are substantive. The ones that were cut were some of the most aggressive, and the pattern of which ones fell out tells a clear story: Congress is willing to lower compliance barriers and expand commercial preferences, but it is not yet willing to remove competition gates or grant automatic commercial status to nontraditional vendors.

For commercial technology companies. The nontraditional contractor exemptions and commercial product preference reforms provide real regulatory relief. The automatic presumption of commercial status isn't there, so understanding which specific requirements can be waived and which must be met is still a per-procurement question. The shift to Portfolio Acquisition Executives means offerings need to be positioned against capability portfolios, not individual programs. PAEs are required to prioritize commercial procurement and OTAs, which helps.

For companies working on prototypes. BOOST is a formal pathway to bridge successful prototypes into production programs. Engage early with DIU on transition requirements. The PAE mandate to prioritize OTAs reinforces the pathway. But because OTA follow-on production authority without competitive prototype did not survive conference, plan for the probability of a separate production competition even on prototypes that perform.

For operational innovation vendors. The COCOM experimentation authority, the contested logistics prototyping expansion, and the SOCOM Urgent Innovative Technologies Initiative open three new direct channels to operational commands. Companies with solutions aimed at forward-deployed scenarios now have concrete pathways that didn't exist in FY25.

For cloud and software providers. The permanent authorization of consumption-based contracting is a real win for recurring-revenue commercial models. But the increased scrutiny on foreign personnel access signals that cloud vendors should prepare for enhanced vetting, and the cloud competition review may come back in a future NDAA even though it didn't survive this one.

The FY26 NDAA doesn't rewrite defense acquisition. It moves a handful of the right things forward, it leaves a handful of others on the table, and it sets up the next two NDAA cycles as the place where the remaining reforms get fought out. Contractors positioning against what's actually in the final bill, rather than what was proposed, will be the ones who capture the opportunities this legislation creates.