The Pentagon stopped publishing out-year estimates. Reconciliation split the budget in two. Planning a multi-year defense business on this visibility is no longer realistic.
For the second time in recent memory, and only the second time, the military services submitted a President's Budget without out-year estimates in their justification books. The first was FY22. The second is FY26, which just landed in front of Congress with a structure that makes the visibility problem worse, not better.
The Department of Defense's FY26 request splits $961.6 billion across two instruments: an $848.3 billion discretionary budget and $113.3 billion of mandatory funding riding on the reconciliation bill. Two bills. One budget. No five-year outlook to tie it together.
For defense contractors trying to make workforce decisions, capital investments, or R&D commitments that pay back over three to seven years, this is the most opaque planning environment in at least a decade. And it may be the new normal.
The Senate Appropriations Committee said it plainly in its FY26 defense report: "the late and incomplete submission of the fiscal year 2026 President's budget request materially impacted the ability of Congress to provide for the Department of Defense's stated requirements."
That's a polite way of saying the Committee didn't get what it needed to legislate. Congress is working with the same fragmented picture contractors are. Nobody in the chain has the out-year visibility that the defense industrial base has been planning against for forty years.
During a Senate Armed Services Committee hearing, Senator Angus King pressed Secretary Hegseth directly on whether this is a one-time adjustment or a structural shift. "Are we playing reconciliation every year from now on? Why not give us an honest budget telling us what your priorities are?"
The answer, read between the lines, was that reconciliation is likely to stay. OMB has signaled flat defense budgets for the next four to five years. If the Department wants to fund modernization priorities beyond the flat topline, reconciliation is one of the few remaining instruments available. That makes it a recurring tool, not an exception.
The SAC-D report warned that splitting the budget "risks creating unnecessary funding cliffs, misalignments, and uncertainties for service and industry partners that could in turn hinder the Department's ability to sustain major procurement efforts and inhibit long-term investments in the production of major capabilities."
Translated into operator language, three things break.
Multi-year procurement planning. Any contract structure that depends on stable out-year funding becomes harder to underwrite when half the money rides on annual political negotiations. Primes and suppliers have to price more risk into proposals, and some programs that would have been multi-year locks become year-to-year gambles.
Capital investment decisions. A contractor deciding whether to expand a production line, stand up a new facility, or invest in specialized tooling needs a funding outlook that extends beyond the current fiscal year. When that outlook is opaque, the default answer becomes "wait." Waiting compounds across the industrial base into a real capacity problem.
Workforce planning. Hiring, training, and retaining cleared workforce requires multi-year program visibility. Reactive workforce planning is more expensive, and it produces worse outcomes than strategic workforce planning. The uncertainty tax on the labor side of defense contracting is already showing up in retention data.
The traditional answer to budget uncertainty has been to hire someone who worked in the building. An ex-OSD comptroller. A former HASC staffer. Someone with the institutional memory and relationship network to read the signals that aren't in the PB docs.
That model is hitting its limits. The information is more fragmented than any single expert can reconcile. The decision tempo is faster than a quarterly strategy review can support. And the staff bench of people with deep budget fluency is smaller than the number of companies that need the coverage.
What replaces it is analytical infrastructure. The data required to navigate FY26 and beyond exists, but it lives across a dozen systems that don't talk to each other.
Pulled together and run through predictive models, those inputs can forecast where funding is actually heading with far more precision than expert intuition alone. Pulled apart and left to individual analysts, they produce the same fragmented picture that has every defense CFO asking their strategy team the same questions quarter after quarter.
Predictive modeling in defense budget analysis isn't about forecasting the topline to the dollar. It's about answering the questions contractors actually have.
Which programs are most likely to see real funding growth under a reconciliation-dependent structure? Which ones are most exposed to cliff risk when the next reconciliation vehicle doesn't materialize? Which service priorities have the congressional support to survive markup, and which ones are quietly being pulled back? Where is committee language diverging from administration requests in ways that will matter in twelve months?
Those are modelable questions. They require a combined view of budget data, legislative activity, threat context, and historical program performance, but the data exists and the techniques to analyze it exist. What's been missing is the infrastructure to run the analysis at the speed that strategic decisions actually need.
Senator King's frustration during the hearing captured something larger than an individual exchange with the Secretary. "Why don't you give us a straight up budget for the defense department?"
The honest answer is that the Department may not be able to, at least not in the form industry has relied on for decades. The fiscal environment, the political dynamics around reconciliation, and the administration's signaled approach to defense topline all point toward a future where budget visibility is structurally lower than it used to be.
In that environment, the competitive advantage shifts decisively toward companies that can build their own visibility. Firms that have invested in modern market intelligence infrastructure can see through the fog. Firms that haven't are going to spend the next few years reacting to funding decisions after they've already been made.
The question isn't whether predictive modeling becomes essential in defense contracting. The FY26 budget just answered that question. The question is how quickly the companies that understand this can deploy it before their competitors do.
No cadence. No fluff. Original analysis on government demand, defense procurement, and federal capital movement, sent when we have something worth reading.
For PE, VC, sell-side, BD, capture, and strategy teams covering defense.
