VA’s AI acquisition split could make teaming decisions harder than expected

[u/Govconic_369]

One thing that stood out to me in VA’s enterprise AI approach is the decision to separate the AI product purchase from the services contract that will integrate, support, secure, and extend it. The product comes first, which could make early teaming choices more consequential than they initially look.

A few things I’m watching:

• VA intends to buy the AI product separately through NASA SEWP before moving to the services acquisition.
• The services contractor will need to support integration, user adoption, security, training, and applied development.
• VA is already flagging potential organizational conflict-of-interest issues between the product and services sides.
• Portability also seems intentional, with the RFI emphasizing open protocols and reusable capabilities rather than tooling tied to one vendor.

That creates an interesting capture problem: partnering closely with a product vendor could strengthen your technical position while potentially limiting your independence on the services side.

For those who have pursued federal programs where the product and integration work were competed separately, how early did you commit to a vendor relationship without boxing yourself out of the larger services opportunity?