VA's FY2026 systems-design spending: where the account research starts

VA reported $3.97 billion in FY2026 net contract obligations for computer systems design services through September 12, 2026. Ten recipients account for 88.3% of that amount. Oracle Health Government Services alone accounts for 40.8%.

For a company planning its FY2027 VA business, that concentration narrows the field of portfolios worth understanding. It does not identify an opportunity by itself. The next question is which awards involve work the company can deliver, and whether there is a documented way to participate.

A concentrated market still contains different kinds of work

The chart uses NAICS 541512, Computer Systems Design Services, with VA as the awarding agency. The population contains 122 reported recipients and $3,972,009,269.43 in net obligation actions from October 1, 2025 through September 12, 2026. The data was obtained directly from USAspending.

The ten largest recipient rows total $3.51 billion. Smaller positive amounts and net reductions appear separately so the displayed total retains the full population; zero-balance recipients remain in the downloadable source data.

A portfolio at this scale may contain implementation, integration and continuing support for several programs. A company providing interface testing or training needs to find the orders that cover those responsibilities. A broad industry classification does not establish that every award involves the same program, or that every recipient needs the same kind of partner.

September's EHR hearing changes the questions worth asking

The September 2 House Veterans' Affairs hearing put VA's electronic health record modernization back into the account-planning conversation. In its testimony, GAO reported that 14 of its 18 recommendations were not fully implemented as of August 2026. Its concerns included cost and schedule information, user adoption, operational testing and the management of system problems.

For a specialist firm, those issues suggest more precise research than a general pitch about digital transformation. Operational testing raises questions about which contract covers testing and who owns the work. User adoption raises questions about training responsibilities and the evidence of readiness at deployment sites.

That is our interpretation of the account-research implications, not a claim that the hearing created new contract opportunities. An oversight finding does not establish available funding or a prime contractor's interest in teaming. The award scope and current acquisition documents must support the connection.

The spending classification requires the same care. NAICS 541512 covers VA work beyond EHR modernization. The hearing adds context to relevant awards; it does not turn the entire $3.97 billion population into EHR spending.

The recipient identifier matters when the names repeat

Oracle Health Government Services, UEI DT2KS3HH5FP5, accounts for $1.62 billion in this defined population. Keeping that identifier with the finding makes it possible to trace the total back to the right recipient and awards.

The chart also contains two rows called BOOZ ALLEN HAMILTON INC, under different UEIs. A corporate view may reasonably combine related entities, but that is a separate calculation with its own scope. Our contractor identity analysis examines the two rows and their reported parent. The individual award still belongs to the recipient identified on it.

For a business development team, that distinction affects who it researches and what it can claim about a relationship. A familiar corporate name is useful for orientation. The specific entity and contract determine the evidence behind a potential fit.

From the spending chart to an account decision

The productive next step is to examine the awards behind a plausible recipient, then connect the relevant work to a current notice, an accessible vehicle or a documented subcontracting route. G2X's documentation on company research and vehicle access explains that investigation.

You can begin with a free-forever G2X account, research contractors and buyers, and organize the companies and contacts relevant to your account plan. Lumen, the GovCon Growth Agent, can help assemble a sourced brief around a recipient and your capability. The Lumen documentation covers the conversation; the agent section below keeps the exact research steps available separately.

Before FY2027 begins October 1, the goal is a small number of account decisions backed by specific work. The spending concentration tells you where to look. The contract descriptions, access route and current program context tell you whether an account deserves your team's time.