VA's AI Ultimatum: What It Means for Challengers

When a federal agency's IT leadership goes on record telling incumbent contractors to modernize or get cut, that's not a press release. That's a recompete signal disguised as a management speech.

That's exactly what happened at the VA. According to FedScoop's coverage, the agency's IT leadership has explicitly challenged incumbent contractors to keep pace with AI and modernization initiatives — or risk losing work. For challengers sitting on the sideline, that kind of statement is worth more than six months of pipeline scouting.

What the VA Is Actually Telling the Market

Federal agencies almost never publicly undercut their own incumbent contractors. When they do, it means one of two things: the incumbent has already lost internally and the agency is managing the transition narrative, or leadership is genuinely frustrated and using public pressure to accelerate change it can't drive through contract vehicles fast enough.

Either way, the message to the market is the same: there's a crack in the wall.

The VA's IT portfolio is massive — the department consistently ranks among the largest federal IT spenders, with multi-billion dollar modernization efforts across EHR systems, benefits processing infrastructure, and enterprise support services. When IT leadership signals dissatisfaction with incumbent pace, the ripple effect touches dozens of task orders across multiple IDIQ vehicles.

Why Incumbents Are Vulnerable Here Specifically

AI modernization creates a specific type of incumbent vulnerability that's different from ordinary performance risk. Here's the dynamic: most large IT incumbents won their VA positions on the strength of integration depth, cleared personnel, and institutional knowledge. Those are real advantages. But they're largely irrelevant when the evaluation criteria shift toward demonstrated AI capability.

An incumbent that built its value proposition on "we know your legacy systems" is now being evaluated against challengers who can say "we have deployed agentic workflow automation in analogous civilian agency environments." That's a different competitive axis — and one where many incumbents haven't invested.

The VA scenario playing out now mirrors what has happened historically when agencies go through significant technology shifts. The incumbents who survive are the ones who saw the shift coming and rebuilt their teaming structures and technical approaches before the recompete. The ones who get displaced are the ones who assumed continuity of evaluation criteria.

That staffing pressure matters for challengers, too. A leaner agency IT staff means contracting officers are more dependent on contractor-led program management and technical direction — which raises the stakes on who's actually running the work, not just who holds the contract.

How to Position Against a Vulnerable Incumbent

The strategic move here isn't to draft a generic AI capability statement and attach it to your next proposal. That's what everyone is doing, and it won't differentiate you. The move is to build a specific counter-positioning around the incumbent's known weaknesses.

Step one: Identify the incumbent's technical debt narrative. What systems or platforms are they locked into? If [Incumbent Vendor] has spent five years embedding their team in a legacy ticketing infrastructure, their AI pitch will likely involve bolting something onto that infrastructure. Your pitch should be about what a clean-sheet approach enables.

Step two: Build teaming around the agency's stated priorities, not your existing bench. The VA has been explicit about AI being a priority. That means your teaming structure needs an AI-native subcontractor or a demonstrable internal practice — not a partner you recruited two weeks before proposal submission. Evaluators have seen paper teams. They're not impressed.

Step three: Run the recompete timeline backward from contract expiration. Pull the current contract award from USASpending and work backward. If the incumbent's IDIQ task order expires in 18 months, the RFP is probably 6-9 months out, which means your capture window is now. Map the solicitation timeline, identify the source selection officials if you can, and start positioning for industry days and RFI responses.

Plug your own numbers in before committing capture resources to any of these opportunities — the math on expected value changes fast when proposal costs run high on competitive VA IT work.

The Trap Challengers Need to Avoid

Here's the uncomfortable truth about "incumbent is vulnerable" signals: they attract a lot of noise. Every BD lead in the market reads the same FedScoop headline. The result is a recompete that draws 8 offerors instead of 3, all claiming AI capability, most of it thin.

The challengers who win these situations aren't the ones with the best AI marketing language. They're the ones who invested in the relationship infrastructure before the RFP dropped — who showed up at VA industry days, submitted substantive RFI responses, and had conversations with program offices about actual technical problems the incumbent wasn't solving.

This is a core principle across federal BD tactics: access precedes award. In a contested recompete, your probability of win at RFP release is largely determined by what you did in the 18 months before it.

The VA's AI ultimatum is a gift to challengers who are paying attention. It's irrelevant to challengers who treat it as a marketing prompt.

Reading This Signal Across Your Pipeline

The VA is not the only agency signaling this. EPA's CIO has publicly described piloting AI across low-stakes workflows while protecting higher-level decisions — which is a different posture, but still a signal that AI integration is becoming a contract evaluation criterion rather than a nice-to-have.

When you're scanning your pipeline for wired RFPs versus genuine competition, the inverse signal matters too: agencies explicitly saying they want competitive AI capability are often the same agencies where incumbent complacency has created real displacement opportunity. That's a different market than a shop where the CIO has been quietly renewing the same vendor for eight years.

The practical filter: when agency IT leadership makes public statements challenging incumbents, add that agency to your active capture list. When the same agency's leadership says nothing about modernization while quietly extending existing vehicles, add it to your wired-RFP watch list instead.

Those are two completely different BD strategies for two completely different competitive environments.

The VA just told the market something valuable. Whether you do anything with it before the RFP drops — or after — will tell you a lot about whether your BD process is actually a BD process or just a solicitation-response machine.

Frequently Asked Questions

How much lead time do you realistically need to compete on a VA IT recompete?

Eighteen to twenty-four months is the functional minimum for meaningful capture on a competitive VA IT recompete. That includes time to build teaming, engage program offices through RFIs and industry days, and develop a differentiated technical approach. Showing up at RFP release without prior engagement is a proposal exercise, not a capture strategy.

Does the VA's AI push mean they'll evaluate AI capability as a formal evaluation criterion?

Not necessarily in every solicitation, but directionally yes. Agency leadership statements about technology priorities tend to propagate into PWS language and evaluation criteria within 1-2 procurement cycles. Even before it's explicit, evaluators reward offerors who demonstrate they understand the agency's modernization direction — which is effectively an informal weighting.

If the incumbent has poor AI capability, why haven't they already lost work?

Contract vehicles and task order ceilings create inertia. Agencies can't simply fire an incumbent mid-performance without triggering termination costs, transition risk, and contracting officer workload. What they can do is signal market intent, reduce follow-on task orders, and run a more genuinely competitive recompete at the natural transition point. The signal comes before the action.

Should small businesses go after VA IT work directly or through subcontracting?

Both paths have merit, but they require different positioning. Prime opportunities exist on set-aside vehicles like SDVOSB-reserved task orders, where small businesses compete head-to-head. Subcontracting paths work when a large business prime needs credentialed AI capability or specific veteran-owned teaming to meet participation requirements. Know which lane you're in before you start building your capture plan.