The Real FY27 Defense Picture: Base Budget, Reconciliation, and Supplemental Funding
Harvey Morrison: Co-Founder/CEO, Marion Square
If your public sector sales team is building its revenue forecasts on headline figures from the FY 2027 White House budget request, you are likely looking at a mirage.
The Administration’s fiscal year 2027 budget proposes an extraordinary $1.5 trillion in total defense resources. But that figure consists of two very different and far from equally certain funding streams:
Approximately $1.15 trillion in base discretionary funding; and
Approximately $350 billion in proposed mandatory funding expected to move through budget reconciliation.
That distinction is not budget-process trivia. It could determine which programs scale, when contract opportunities materialize, and whether some of the Department of War’s most ambitious technology priorities receive anything close to the funding shown in the President’s request.
The reconciliation assumption is already under significant pressure. The House’s emerging reconciliation framework has contemplated roughly $60 billion for defense far below the Administration’s $350 billion request and its prospects in the Senate remain uncertain. At the same time, Congress is considering how to cover the cost of the conflict with Iran, replenish expended weapons, restore readiness, and fund requirements that did not exist when the FY27 budget was assembled.
For companies selling artificial intelligence, autonomous systems, cybersecurity, data infrastructure, communications, logistics technology, space capabilities, and advanced manufacturing, the operative question is therefore not simply, “How large is the defense budget?”
The more useful questions are:
Which legislative vehicle is expected to fund the requirement?
How secure is that vehicle?
Is the money annual or multiyear?
Can the Department obligate it under a continuing resolution?
If one funding stream falls short, which programs will be protected and which will become bill payers?
Four Numbers, Four Different Meanings
The FY27 defense debate is easier to understand when its major figures are separated.
1. The $1.15 trillion base request
The Administration requested approximately $1.15 trillion for base defense discretionary programs. This is the portion intended to move through the regular annual appropriations process.
Authorization is not the same as funding, however. The House-passed FY27 National Defense Authorization Act supports approximately the requested topline, but an authorization establishes policy and permits spending; an appropriations act provides the actual budget authority.
The House Appropriations Committee’s defense bill provides approximately $1.072 trillion about $78 billion below the Administration’s $1.15 trillion base request. That gap alone means that even before reconciliation is considered, Congress may force choices among readiness, personnel, procurement, research and development, and modernization.
2. The proposed $350 billion reconciliation package
The Administration’s budget assumes approximately $350 billion in new mandatory defense funding. According to the Department’s budget materials, this funding would support major investments in areas such as:
Drone Dominance and autonomous systems;
Critical munitions and multiyear procurement;
Artificial intelligence and data infrastructure;
Golden Dome and advanced missile defense;
Shipbuilding and the supporting industrial base;
Critical minerals and supply-chain resiliency; and
Working-capital and production-capacity initiatives.
The Department proposes, among other investments, $53.6 billion for Drone Dominance, $52.9 billion for critical munitions, and $46 billion for a multiyear “AI Arsenal.” These figures help explain why the $1.15 trillion base should not be read as independently financing the entire modernization agenda.
This is the central vulnerability in the request: several signature priorities rely heavily on a separate legislative vehicle that Congress has not yet provided at the requested level.
3. The approximately $60 billion reconciliation alternative
The House reconciliation framework has contemplated roughly $60 billion for defense. That is not merely a smaller version of the $350 billion request. It is a fundamentally different funding scenario.
A $60 billion package would be nearly $290 billion below the Administration’s assumption. Moreover, much of that smaller package may be needed to address immediate Iran-related costs and depleted inventories rather than finance the full slate of planned FY27 modernization investments.
Under that outcome, Congress and the Department would have to decide whether to:
Concentrate the money on a handful of urgent priorities;
Move selected reconciliation dependent programs into regular appropriations;
Reduce quantities or delay schedules;
Restructure multiyear procurements;
Reprogram money from lower-priority accounts; or
Defer programs into later fiscal years.
This is where program level tracking becomes indispensable. A vendor can be aligned with a stated priority and still be pursuing funding that never reaches the relevant account.
4. The Iran supplemental
In June, the White House submitted an approximately $87.6 billion emergency supplemental request, much of it associated with Operation Epic Fury and the Department’s Iran related requirements. The package included substantial amounts for munitions replenishment, operational costs, classified activities, and other government requirements.
That request was already considerably below an earlier reported Pentagon proposal of approximately $200 billion. Defense Secretary Pete Hegseth subsequently estimated that the conflict had cost approximately $37.5 billion as of late July.
A supplemental and reconciliation funding are not interchangeable in either purpose or timing. A supplemental is generally designed to cover emergency or unforeseen needs. Reconciliation can provide multiyear mandatory resources for broader investment priorities. If Congress uses a smaller reconciliation package primarily to cover the Iran conflict, less capacity remains for the long-term modernization initiatives originally placed in the $350 billion request.
The Most Important Distinction: Priorities Versus Funded Programs
The Department’s priorities appear relatively durable. Congress and the Administration continue to emphasize munitions, air and missile defense, drones and counter-drone systems, AI, shipbuilding, resilient communications, industrial capacity, and supply-chain security.
What remains uncertain is the scale, pace, and contracting path for those priorities.
This distinction is particularly important because reconciliation funding has previously been used to support activities that would normally be considered enduring defense requirements. The Congressional Budget Office found that, in the FY26 request, reconciliation resources did not always sit cleanly “on top of” the base. In some acquisition accounts especially within the Navy and Air Force they partly offset base budget funding that was lower than earlier plans anticipated.
That precedent should caution vendors against assuming that the base budget is the cake and reconciliation is simply the icing. In some portfolios, the two funding sources are structurally intertwined.
What Happens Under Each Scenario?
Scenario 1: Congress provides most or all of the $350 billion
This is the maximum-growth scenario.
Multiyear funding would give the Department greater ability to place large orders, expand production capacity, support new suppliers, and provide industry with predictable demand. The strongest opportunities would likely include:
Autonomous systems and counter-UAS
AI infrastructure, applications, and mission integration
Munitions and missile interceptors
Golden Dome sensors, command-and-control, communications, and defensive systems
Shipbuilding and maritime industrial base capacity
Critical minerals and domestic manufacturing
Logistics, sustainment, and contested-distribution technologies.
For nontraditional vendors, this scenario could accelerate demonstrations and production contracts but it would also increase competition. Large, visible funding pools will attract incumbents, venture-backed entrants, integrators, and commercial technology companies simultaneously.
Scenario 2: Congress provides approximately $60 billion
This would create a triage environment.
Immediate operational needs particularly munitions replenishment, air and missile defense, readiness, and Iran related costs would compete directly with longer-term transformation programs. Initiatives dependent on very large multiyear commitments would be most exposed.
Munitions demand would remain strong, but some multiyear agreements could be reduced or delayed. Drone and counter-drone investments would likely be protected because recent conflicts have reinforced their operational relevance, although the scale could fall significantly below the request. AI programs tied to defined missions and measurable near-term outcomes would likely fare better than expansive enterprise initiatives without a clear acquisition pathway.
This scenario rewards vendors that can connect their capabilities to a funded mission gap, an existing program office, and a specific appropriation not merely to a high-level strategic priority.
Scenario 3: Reconciliation fails
If reconciliation does not pass, the Department would face a gap of as much as $350 billion relative to the President’s FY27 plan.
Congress could attempt to migrate some priorities into regular appropriations, but the House committee’s $1.072 trillion allocation does not currently provide room to absorb the entire reconciliation portfolio. Moving programs into the base would therefore require a larger topline, offsets elsewhere, or both.
Programs with the strongest operational constituencies would be best positioned: readiness, personnel, nuclear modernization, critical munitions, air and missile defense, and select shipbuilding requirements. Large new initiatives without mature requirements, established acquisition offices, or congressional champions would face greater risk.
The Department could also look to legacy platforms, delayed programs, excess balances, and underperforming accounts as sources of offsets. Technology priorities might remain intact rhetorically while their funding profiles stretch over more years.
Scenario 4: The Iran supplemental is delayed or underfunded
This is the scenario most likely to produce hidden consequences across the portfolio.
Military operations do not stop generating costs while Congress deliberates. Without timely supplemental funding, the Department may need to rely temporarily on existing operation and maintenance resources, inventories, transfer authority, or reprogramming actions.
That can create downstream pressure on:
Training and readiness
Depot maintenance
Facility sustainment
Planned exercises
Software and service contracts funded through operation and maintenance accounts
Equipment upgrades
Lower-priority research and development activities.
The greatest near term risk for many technology companies may therefore be indirect. A product does not need to be connected to Iran to be affected by the conflict. If its customer must redirect flexible resources toward operations, replenishment, or force protection, the vendor’s program can slow even while remaining an official priority.
If supplemental funding eventually arrives, the opposite dynamic may follow: agencies could face compressed obligation timelines and urgent acquisition activity, favoring vendors that already have contract access, validated requirements, security credentials, pricing, and teaming relationships in place.
Continuing Resolutions Add Another Layer
The possibility of a continuing resolution further complicates FY27 planning.
Under a CR, agencies generally operate at prior year rates and face restrictions on starting new programs, increasing production quantities, or changing program direction. Existing contracts and mature programs usually have an advantage. New starts, major scale-ups, and initiatives that depend on FY27-specific authorities can be delayed even when Congress broadly supports them.
A CR does not eliminate demand. It changes the timing and accessibility of that demand.
For vendors, a delayed appropriation can create two very different periods:
A slower opening to the fiscal year, as customers preserve funds and wait for authority; and
A compressed execution period after enactment, when program offices must obligate significant funding before September 30.
Companies that wait for the final budget to begin market development are likely to arrive too late for the second phase.
What Technology Vendors Should do Now
FY27 go-to-market strategies should be built around funding confidence, not just total addressable market.
First, map each target opportunity to its actual funding source. Determine whether it depends on base appropriations, reconciliation, the Iran supplemental, prior-year balances, or a combination of vehicles.
Second, classify opportunities by legislative risk:
Higher confidence: established programs supported in both the request and congressional marks;
Moderate confidence: supported priorities whose scale or account structure differs across proposals; and
Higher risk: new or dramatically expanded programs dependent on the full reconciliation request.
Third, identify the executable portion of each opportunity. A $50 billion initiative does not translate into a $50 billion immediately addressable market. Vendors need to know which program office controls the requirement, which contract vehicles can be used, what acquisition authority exists, and how quickly the customer can obligate funding.
Fourth, prepare for multiple scenarios. Messaging, teaming, pipeline forecasts, and hiring plans should not depend on a single $1.5 trillion outcome. Companies should establish a base case, an upside reconciliation case, and a downside CR or underfunded-supplemental case.
Finally, begin customer engagement now. Budget uncertainty is not a reason to postpone go-to-market activity. It is a reason to make that activity more informed.
The Real Competitive Advantage is Budget Intelligence
The FY27 defense request points unmistakably toward greater investment in autonomous systems, AI, munitions, missile defense, resilient networks, shipbuilding, and industrial capacity.
But direction is not the same as appropriation, and appropriation is not the same as an executable contract opportunity.
Between the President’s request and an awarded contract lies authorization bills, appropriations measures, reconciliation instructions, supplemental requests, continuing resolutions, congressional program changes, transfers, reprogramming actions, acquisition strategies, and obligation deadlines.
Technology vendors do not need to predict every congressional vote. They do need a system for detecting when assumptions change and for translating those changes into account-level and program-level business decisions.
That is where Marion Square helps clients compete: tracking the legislative plumbing behind the topline, identifying which priorities have durable funding, and converting fast-moving budget intelligence into practical go-to-market action.
Budget and legislative status current as of August 19, 2026.