VA IT official to contractors: Bring your AI game or get axed

TL;DR

The Department of Veterans Affairs is signaling a major shift in contractor retention strategy: incumbents who fail to demonstrate AI and modernization capabilities risk losing their contracts. Zack Schwartz, a VA IT official, made clear in a recent interview that the agency expects contractors to proactively bring AI solutions and modernization expertise to the table. This represents a departure from traditional contract renewal patterns, where incumbents enjoyed significant advantage. Contractors currently holding VA IT contracts—or pursuing new awards—must now treat AI integration and modernization as table-stakes capabilities, not optional enhancements. The warning applies across the VA's IT portfolio, though specific contract vehicles and timelines remain pending source review. Firms without demonstrable AI competencies face heightened recompete risk, while those who can showcase modernization track records may find new capture opportunities as the VA reshuffles its vendor base.

Key Points

• What happened: A VA IT official publicly challenged incumbent contractors to demonstrate AI and modernization capabilities or face contract termination, marking a shift in the agency's vendor retention posture.
• Who is affected: Current and prospective VA IT contractors across the agency's portfolio; specific NAICS codes, contract vehicles, and program offices pending source review.
• Timeline: Timeline TBD pending source review; the statement suggests ongoing evaluation of incumbent performance rather than a single deadline.
• What contractors should do NOW: Audit current VA contracts for AI/modernization language, inventory demonstrable AI capabilities and case studies, engage VA program offices to surface modernization opportunities, and prepare capability statements that position AI as core competency rather than add-on service.

Who Is Affected

This event affects contractors currently holding or pursuing Department of Veterans Affairs IT contracts. The scope includes incumbents across the VA's technology portfolio who may face heightened recompete risk if they cannot demonstrate AI integration and modernization expertise. Prospective bidders with strong AI capabilities may find new capture opportunities as the VA evaluates its vendor base. Specific NAICS codes, contract vehicles (e.g., T4NG, VECTOR, VETS 2), program offices, and compliance regimes pending source review. Contractors should assume broad applicability across VA IT services until the agency publishes more granular guidance.

Frequently Asked Questions

Q: Does this apply to all VA IT contracts or only specific vehicles?

The official's statement suggests broad applicability across the VA's IT portfolio, but specific contract vehicles, program offices, and dollar thresholds have not been detailed in the available source material. Contractors should treat this as a portfolio-wide signal until the VA publishes clarifying guidance. Pending source review: whether this applies equally to small-dollar task orders, large IDIQ (Indefinite Delivery/Indefinite Quantity) vehicles, or specific modernization programs.

Q: What qualifies as "bringing your AI game" in the VA's view?

The source material does not define specific AI capabilities, maturity models, or technical requirements the VA expects contractors to demonstrate. Pending source review: whether the VA will publish AI competency frameworks, preferred use cases (e.g., claims processing automation, clinical decision support), or certification requirements. Contractors should engage their VA contracting officers and program managers directly to understand program-specific expectations.

Q: How should incumbents respond if their current contract scope doesn't include AI work?

The official's statement implies that contractors should proactively propose AI and modernization enhancements rather than waiting for the VA to modify contract scope. Pending source review: whether the VA will issue formal modification solicitations, establish innovation challenge mechanisms, or expect contractors to self-fund capability demonstrations. Incumbents should document any AI pilots or modernization initiatives already underway and prepare unsolicited proposals that align with VA strategic priorities.

Definitions

• Incumbent contractor: A vendor currently holding an active contract with an agency, typically enjoying informational and relationship advantages during recompete.
• Modernization: In federal IT context, the process of replacing legacy systems with cloud-native, API-driven, and user-centered architectures; often tied to the Technology Modernization Fund and agency-specific transformation roadmaps.

Intelligence Response

Cabrillo Signals War Room has already detected this policy shift and delivered this briefing, demonstrating the platform's ability to surface strategic signals that don't appear in traditional SAM.gov (System for Award Management) feeds. The Match Engine should be configured to rescore all active VA IT opportunities, flagging those where AI capabilities or modernization experience now carry heightened weight. Teams should update scoring rubrics to reflect the VA's new emphasis on proactive innovation rather than reactive compliance.

The Intelligence Hub should establish saved searches for VA IT solicitations containing keywords: "artificial intelligence," "machine learning," "modernization," "legacy system replacement," and "innovation." Set alerts for amendments to existing VA IDIQ vehicles (T4NG, VECTOR, VETS 2) that may introduce AI evaluation criteria. Track VA Office of Information Technology press releases and leadership interviews for follow-on guidance.

Proposal Studio users should immediately update the VA win theme library to emphasize AI case studies, modernization track records, and proactive innovation narratives. The compliance matrix module should flag any existing VA proposals that position AI as optional or future-state rather than current capability. The bid/no-bid decision engine should incorporate a new risk factor: "Does our team have demonstrable AI delivery on comparable VA or federal health programs?"

Workflow Tracker should route this briefing to capture managers with active VA pursuits, triggering a 48-hour sprint to assess AI positioning in pending proposals. Gate 3 (solution development) and Gate 6 (proposal production) reviews should now include mandatory AI capability validation.

Who to notify:

• Capture Managers (VA portfolio) — Immediate reassessment of incumbent risk and competitive positioning required.
• Proposal Directors — Update VA-specific win themes, past performance narratives, and technical approach templates to foreground AI capabilities.
• BD/Pipeline Analysts — Rescore VA opportunities; deprioritize pursuits where the team lacks AI credentials.
• Technical Fellows / AI Practice Leads — Prepare capability statements, case studies, and teaming partner assessments for rapid insertion into VA proposals.
• Contracts/Compliance — Review existing VA contracts for modification opportunities or innovation clauses that permit unsolicited AI pilots.

First 48-Hour Playbook:

• Hour 0–4: Inventory all active VA IT contracts and pending proposals. Flag those lacking explicit AI scope or past performance. Distribute this briefing to capture teams and technical leads.
• Hour 4–12: Convene rapid assessment meetings for each flagged contract/opportunity. Answer: (1) Do we have AI case studies relevant to this program? (2) Can we propose an AI pilot within existing scope? (3) Should we initiate teaming discussions with AI-specialized firms?
• Hour 12–24: Update Proposal Studio win theme library with VA-specific AI narratives. Draft capability statements positioning AI as core competency. Identify 2–3 VA program offices for proactive engagement (e.g., unsolicited white papers on AI use cases).
• Hour 24–48: Route updated positioning to proposal teams with VA deadlines in the next 90 days. Schedule calls with VA contracting officers and program managers to surface modernization priorities. Configure Intelligence Hub alerts for VA AI-related solicitations and amendments.

For contractors handling Controlled Unclassified Information (CUI (Controlled Unclassified Information)) in VA systems, ensure AI tooling and data pipelines comply with NIST 800-171 (NIST Special Publication 800-171) and emerging CMMC (Cybersecurity Maturity Model Certification) requirements. Reference the CMMC Compliance Guide (/insights/cmmc-compliance-guide) for AI/ML workload security controls and the CUI-Safe CRM Guide (/insights/cui-safe-crm-guide) for managing VA opportunity data. The Secure Operations Guide (/insights/secure-operations-guide) provides end-to-end playbooks for maintaining compliance while accelerating proposal cycles.

---