Three line items inside the FY27 Defense IT request — PE 0303140K, PE 0305387D, and the consolidated JADC2 enterprise services pool — together direct $14.8B toward an integration pattern that effectively presumes a single-prime architecture. The trade press has covered the headline number ($170B, FPDS, FY25). It has almost entirely missed the structural consequence.
We have spent the better part of three months running the underlying obligations data against agency strategic plans and the FY26 President’s Budget Request. The result is less a story than a pattern — and the pattern is not what the trade press has been describing.
$14.8B
Redirected across three program elements
— DoD R-1, FY27 PBR
The 8(a) pattern hiding inside the consolidation
Read against the last six months of sole-source 8(a) awards above the simplified acquisition threshold, the picture sharpens further. Twelve awards, one prime, three contracting offices — a concentration ratio that has not been this tight at the program-element level since FY19.
“Everybody is reading the request like it’s a budget document. It is a sourcing document. The dollars are decided. What is being decided right now is who gets to compete.”— A contracting officer at a mid-tier civilian agency, speaking on background
What that means for an operator at $5M to $50M in annual federal revenue is unambiguous: the surface area you can reasonably cover is shrinking, and the cost of being wrong about which vehicles to chase has roughly doubled since FY23.
Contrarian
The conventional advice — add more NAICS codes, get on more schedules, hire a former agency PM — is exactly the wrong response to this cycle. Concentration, not coverage, is the only durable answer.
We will keep tracking this through the end of the fiscal year. If the pattern holds through Q4, the implications for the FY27 budget cycle are larger than anything we have written about in the past twelve months.
