What the VA enterprise AI support services contract buys, and when the solicitation lands
VA enterprise AI support services is a planned contract for one services contractor to handle the work around an AI product, not the product itself. This is new-business capture with no incumbent. VA buys the commercial AI suite separately. The winner integrates it, supports it, trains users on it, secures it, and extends it. RFI 36C10B26Q0834 posted September 22, 2026. Responses are due October 7 at 10:00 a.m. Eastern. VA expects to release the solicitation in October 2026 or early in the first quarter of fiscal 2027. It says those dates are for planning only.
For a BD lead or capture lead at a systems integrator or mid-market VA IT-services firm, October 7 is the last scheduled chance to shape the draft Performance Work Statement. For a service-disabled veteran-owned small business (SDVOSB) on NASA SEWP, the nearer buy is the product. Decide which lane you’re in before either solicitation drops.
| Field | Answer |
|---|---|
| Signal | RFI 36C10B26Q0834, third of three enterprise AI RFIs, with a draft Performance Work Statement attached |
| BD implication | A dated shaping window on a new, no-incumbent services contract tied to a 540,000-user rollout |
| Customer | VA Office of Information and Technology, Chief AI Office |
| Buyer | VA Technology Acquisition Center, Eatontown, New Jersey |
| Funding | Not identified. No ceiling, estimate, or funded amount is disclosed |
| Vehicle / path | Services: no acquisition vehicle stated. Product: SDVOSB set-aside through NASA SEWP (stated intent) |
| Incumbents / ecosystem | No incumbent. SDVOSB SEWP holders on the product lane (stated intent); VA IT integrators on services |
| Access strategy | Prime or subcontractor on services; reseller or product partner on the product lane |
| Timing | RFI due October 7, 2026. Solicitation anticipated October 2026 to early fiscal 2027 |
| Confidence | High on scope, structure, and dates; low on funding and services vehicle |
| Pursuit posture | SHAPE |
| Upgrade triggers | Services solicitation posted; services set-aside or vehicle announced |
| Downgrade triggers | Product award slips or is protested; VA cancels the services effort |
What the RFI and draft Performance Work Statement describe, and what they exclude:
- One services contractor (the RFI refers to “the Contractor”), expected to be priced firm-fixed-price against outcomes or deliverables.
- In the draft Performance Work Statement: a 12-month base period and two 12-month options, capped at 36 months.
- No product subscriptions, user licenses, model or API consumption, cloud consumption, or standard vendor support. Those sit in the product buy.
The product buy comes first, and VA intends it as an SDVOSB set-aside
VA split its enterprise AI strategy into two acquisitions and announced the sequence. The first two RFIs covered the product. An August 17, 2026 update to the first RFI states VA intends to buy it as an SDVOSB set-aside through NASA SEWP. SEWP is the Solutions for Enterprise-Wide Procurement contract NASA runs for governmentwide IT buys. The third RFI says VA intends to procure the services “immediately following the first-party acquisition.”
The product award will likely determine which vendor’s suite the services contractor supports first. VA’s own examples are Anthropic, Google, and OpenAI. The RFI refers to “supplier(s)” and “product(s)” and includes migration support. VA has left room for more than one product.
| Product lane | Services lane | |
|---|---|---|
| What VA buys | Enterprise AI product, native vendor services, training curricula, adoption playbooks | Integration, Tier 1-3 support, adoption, security and authorization support, applied development |
| Set-aside | SDVOSB, stated intent | Not stated |
| Vehicle | NASA SEWP | Not stated |
| Timing | First | Immediately following the first-party acquisition (VA’s wording) |
| Stage | Two RFIs issued | Third RFI open until October 7 |
No product-lane solicitation or award is public yet. A SEWP order is competed among SEWP contract holders and typically becomes public only at award. So that absence doesn’t mean the product buy has slipped.
About one in five provisioned users would chat monthly by the final wave. A firm-fixed-price bid gets priced against that assumption. The draft Performance Work Statement makes the contractor track it against actual use.
The conflict-of-interest flag could limit which contract you can win
The RFI states that the relationship between the product acquisition and the services acquisition “raises potential organizational conflict of interest considerations.” VA’s illustrative example task shows why. Before any build, the services contractor would deliver a solution mode recommendation. It would state whether to configure the commercial product or build custom. That artifact would include a capability matrix “independent of the Contractor’s own commercial relationships.” It would also disclose any commercial, contractual, or corporate tie between the contractor, its subcontractors, and the product vendor.
Under the draft Performance Work Statement and example task, the services contractor would evaluate the product before every build and recommend what gets built on top of it. VA’s Chief AI Office and the contracting officer’s representative would approve that recommendation before each build. The contractor would report adoption and cost monthly and support a product-to-product migration if VA chooses one. A firm that also resells the product has a stake in each of those calls.
Mitigation plans, disclosure-and-evaluate approaches, and outright bars are the standard organizational conflict of interest remedies. What is new here is that VA flagged the conflict at the RFI stage and wrote disclosure into the example task. I expect the solicitation to pick one remedy. VA hasn’t said which.
Because VA intends to buy the product first, firms will likely commit to a product team before VA says how it will handle the conflict on services. Treat the two lanes as separate bets. A SEWP SDVOSB that carries a winning product may be the firm VA doesn’t want running the services. An integrator that signs an exclusive with one product vendor carries a disclosure problem if that vendor wins. If that vendor loses, the integrator may be shut out of supporting a rival product.
Competitive Landscape: who is positioned in each lane
RFI respondents are not public at this stage. Three categories of firm are positioned:
- Product lane. SDVOSBs holding NASA SEWP contracts, carrying frontier-lab or hyperscaler AI suites. A large product vendor needs one to quote it. That reseller will need to show how the order meets small-business set-aside rules, such as limitations on subcontracting.
- Services lane. VA IT-services integrators with service desk, identity and endpoint, and authorization to operate past performance. The draft ties Tier 1 through Tier 3 support to the VA Enterprise Service Desk.
- Applied development. AI engineering firms with Model Context Protocol connector, agent, and evaluation work. VA frames this as a “small team to start.” That reads as a subcontract role under a services prime.
Service desk contractors are a fourth group to watch. VA posted a separate Enterprise Service Desk Tier One Support RFI in July 2026. If that effort reaches award, its contractor would run the Tier 1 intake the AI support scope plugs into. That makes service desk firms natural services-lane competitors or teammates.
The same contracting center awarded the Ambient Scribe Enterprise IDIQ to Carahsoft Technology Corporation and Knowtex Inc. on September 18, 2026. That is a multiple-award contract with a five-year ordering period and a $775.72 million shared ceiling, not obligated spend. It was a clinical documentation buy on a standalone IDIQ with no set-aside. The enterprise AI product lane differs: VA’s August 17 notice points to an SDVOSB set-aside order on NASA SEWP.
The RFI’s example task signals the technical bar
For firms building an AI in government practice, VA’s illustrative example task favors portable, standards-based engineering over one-vendor practices. Integrations would use the Model Context Protocol or an equivalent open protocol, so a connector works across VA surfaces. Reusable capabilities go in an open Skills format or equivalent. Monitoring uses OpenTelemetry or equivalent. VA makes portability an acceptance criterion.
The safety terms are concrete:
- Connectors to VA systems of record are read-only by default. Any write path needs separate approval and human sign-off for consequential actions.
- Custom code goes to VA’s source code repository continuously, under the SHARE IT Act. That 2024 law requires agencies to share custom code.
- Evaluation, bias testing where rights-impacting, and regression testing come before any production release.
If your AI practice is built around one vendor’s proprietary tooling, the portability criterion works against it. VA asks directly for barriers to competition, so name it in your response.
How to answer RFI 36C10B26Q0834 by October 7
VA says generic capability statements will not be reviewed. Responses are capped at 20 pages in Word format, excluding cover page and appendices.
- Map your capability to each task in the draft Performance Work Statement. Cite federal or regulated-enterprise generative AI work.
- Answer the technical challenge question. VA intends to use one in evaluation. It asks what “show-me-don’t-tell-me” approach it should use.
- Propose a payment milestone structure for firm-fixed-price. Say whether the draft gives enough detail to price.
- Give rough order-of-magnitude pricing for Tasks 5.1 through 5.5, with labor types, mix, and hours.
- Name the cost drivers: user population, ticket volume, rollout waves, integrations and connections, agents, and evaluation cycles.
- State business size, VetCert status for veteran-owned firms, existing vehicles, and your ability to meet VA’s limitations on subcontracting clause, 852.219-75.
The RFI carries no set-aside, yet it asks for VetCert proof, veteran-owned partners, and subcontracting-limit compliance. That mix suggests VA is testing whether enough veteran-owned firms can do the services work to justify a set-aside under its Veterans First rules. That is an inference from the questions, not a decision VA has announced.
- Systems integrator or mid-market VA IT firm: respond by October 7 and answer the technical challenge and milestone questions. Line up a VetCert-verified SDVOSB or VOSB partner now.
- SDVOSB on NASA SEWP: team with a named AI vendor. Be ready to quote when VA issues the product-lane request to SEWP holders. Get a conflict-of-interest read before joining a services team.
- AI engineering firm: position as the applied development subcontractor. Lead with connector portability and evaluation evidence.
- AI product vendor without a SEWP SDVOSB partner: secure one before the product-lane order is competed.
- Any firm: list every commercial tie to Anthropic, Google, OpenAI, or another AI vendor. VA’s illustrative example task makes each tie a disclosure item.
What would move this from shaping to a pursuit
VA enterprise AI support services is a shaping target today. The buyer, scope, and rollout are documented. A solicitation, a dollar figure, and a services set-aside or vehicle are still missing.
Two events would make it a pursuit. One is the services solicitation, which VA expects as early as October. The other is a services set-aside or vehicle decision, which tells you whether you can prime. Watch for the product award too. VA sequences services after it.
Two events would push it back. A delayed or protested product award would likely delay the services buy. VA could also revise or cancel the services effort, which the RFI expressly reserves. For now, respond by October 7, choose your lane, and build the team that lane requires.
FAQ
Is VA’s enterprise AI support services contract funded?
No funding figure is disclosed for either lane. VA says the RFI is market research only. It doesn’t commit VA to a solicitation or award.
Can the company that resells the AI product also win the services contract?
VA hasn’t decided. It has flagged the risk and written vendor-tie disclosure into its illustrative example task. Expect mitigation or restriction language in the solicitation.
Which AI products could VA buy?
VA names Anthropic, Google, and OpenAI as examples, along with “another vendor’s suite.” The list is illustrative, not a shortlist. The product award will likely set which suite the services contractor supports first.
Will the services contract be set aside for veteran-owned firms?
VA hasn’t said. The RFI’s VetCert and subcontracting-limit questions point to VA testing whether a set-aside is viable.
What does the services contractor staff at the start?
At least one customer success lead per VA business unit, up to 50, plus program management set up during a base-period mobilization. Applied development starts small and grows as VA approves use cases.
