Who Actually Buys VA AI: TAC vs. SAC for SDVOSBs

Where do TAC and SAC sit in VA?

VA acquisition runs department-wide through the Office of Acquisition, Logistics, and Construction (OALC), which oversees four field activities through the Office of Procurement, Acquisition, and Logistics (OPAL): TAC (IT/technology), SAC (non-IT enterprise), the National Acquisition Center in Hines, IL (pharma, Med/Surg, Federal Supply Schedule), and the Logistics Support Service. Separately, the VHA runs its own contracting through 18 Network Contracting Offices aligned to the Veterans Integrated Service Networks (VISNs 1–23) under three Regional Procurement Offices — those handle local medical-center buys, which is where a VAMC-specific AI play would land. For enterprise AI, though, the two names that matter are TAC and SAC.

What is TAC, and why is it your primary target?

TAC is VA’s enterprise IT and technology buyer — roughly 200 acquisition professionals in Eatontown, NJ, an Austin, TX office, and remote staff across the country, providing contracting for VA’s major IT programs. Its industry philosophy, in its own words, is that a strong relationship with industry partners is key to success, and it favors “constructive and open dialogue with industry at the appropriate time.” The vehicles it owns are the ones VA AI actually flows through.

Most VA AI that’s been competitively contracted runs through these — VA.gov product teams on CEDAR/SPRUCE, identity and claims work, and the new Ambient Scribe Enterprise IDIQ scaling the AI-scribe rollout. TAC engages industry through the GSA Acquisition Gateway forecast, SAM.gov, the Virtual Office of Acquisition (voa.va.gov, where T4NG2 prime contacts and task-order announcements live), its APBI industry days, and VA Pathfinder for early innovation pitches. One leadership note worth knowing: Jeffrey Neill, who led TAC as Associate Executive Director from mid-2024, moved up to VA’s senior career procurement role (Executive Director of the Office of Acquisition and Logistics and Senior Procurement Executive) in March 2026; his TAC successor wasn’t publicly named at the time of writing.

What is SAC, and when does it matter for AI?

SAC is VA’s enterprise non-IT and mission buyer — life-cycle management of large, complex, non-IT solutions out of Fredericksburg, VA and Frederick, MD, organized into Acquisition Services directorates (AS-1 through AS-6) aligned to customer offices. Its big vehicles are enterprise services, not IT: the Community Care Network, the Medical/Surgical Prime Vendor program, VECTOR ($25B SDVOSB business-services IDIQ), VHA IHT 2.0 ($14B SDVOSB healthcare IDIQ, 9 primes awarded August 2025), and the Integrated Critical Staffing Program.

So why does an AI firm care about SAC? Two reasons, both recent and both real. First, clinical-AI pilots: in June 2025, SAC-Frederick executed the sole-source ambient-scribe contracts that came out of the VHA AI Tech Sprint — Abridge (a roughly $5.37M award) and Nuance — on behalf of VHA’s Digital Health Office, with a third Tech Sprint winner, Knowtex, announcing a $15M VA award later that year. Second, AI for SAC’s own acquisition work: in February 2025, SAC issued a sources-sought notice (AIAPT) for a commercial generative-AI/LLM tool to support its acquisition and contract-lifecycle functions — explicitly COTS-only, “not seeking custom-developed solutions,” with no public follow-on award identified as of spring 2026. The pattern to take away: SAC is where AI Tech Sprint follow-ons and enterprise-services-with-an-AI-component tend to land — a watchlist, not your first door.

TAC or SAC — which center for which work?

The decision rule for a brand-new AI/automation SDVOSB: TAC is your North Star because its OIT/digital-experience portfolio maps directly to document automation, RAG assistants, claims tooling, and predictive analytics. SAC is the watchlist for AI Tech Sprint–style sole-source pilots and enterprise-services task orders that pick up an AI component.

How does a new SDVOSB actually engage them?

Free, public, and well-trodden — there’s no paid gate. The sequence: confirm your registrations (SAM active, UEI, CAGE, NAICS 541512 primary, SBA VetCert SDVOSB — the gate for VA’s Veterans First program); monitor both forecasts (TAC on the GSA Acquisition Gateway, SAC on the VA Vendor Portal), tied to your forecasting workflow; set SAM.gov saved searches filtered to “Technology Acquisition Center” and “Strategic Acquisition Center” in your NAICS, and respond to every relevant Sources Sought even when you can’t prime, because that’s what feeds Rule-of-Two market research; use the Virtual Office of Acquisition for T4NG2 prime contacts; submit an innovation pitch through VA Pathfinder; attend a TAC APBI and an OSDBU Direct Access event; and send a tailored capability statement to the right contracting officer (CO) — by Procurement Service letter at TAC, by AS directorate number at SAC. It’s worth remembering who you’re courting: VA is the most SDVOSB-favorable agency in government, awarding about $10.2B — roughly 23% of prime dollars — to SDVOSBs in FY24, well above the statutory goal.

The 2026 wildcard: VA acquisition is reorganizing

Be honest about this, because an org map is only as good as its shelf life. VA reduced its contracting workforce by roughly 15% between April and November 2025, leaving about 2,658 contracting officials, and in November 2025 announced plans to realign procurement offices under a centralized department-level structure — a plan not finalized as of early 2026. A Senate bill (S. 1591, the Acquisition Reform and Cost Assessment Act) passed in December 2025 would, if enacted, create an Assistant Secretary for Acquisition and Innovation as VA’s chief acquisition officer, with the acquisition centers under that office. The names TAC and SAC are stable; their reporting lines may shift in 2026–2027. If S. 1591 becomes law, re-verify this org map.

What’s the honest play for Truvisory?

A brand-new SDVOSB with no TAC or SAC relationships — a solo combat-veteran founder, Cloudflare-native, 90-day fixed-scope delivery out of Denver — has a real position, but it imposes a sequence. TAC first, SAC second: the 541512 capability set maps to TAC’s OIT portfolio; SAC is the AI-Tech-Sprint watchlist. Sub before prime: with no past performance on the big vehicles, the realistic 6–18 month move is subbing on SPRUCE and T4NG2 task orders with primes who actively recruit SDVOSB subs for socioeconomic credit — pair this with the teaming spoke. Use the $5M sole-source bridge once there’s one VA past-performance and a program-office champion (sole-source spoke). And state the compliance posture plainly: Cloudflare for Government is FedRAMP Moderate (High in process), Truvisory is FedRAMP-aware and M-25-21-aligned, and intentionally not CMMC-certified, because CMMC is DoD-only and doesn’t apply to VA. Relationships take time here — source selections weight past performance heavily — so expect 12–24 months of forecasting, Sources Sought responses, and sub-tier delivery before priming looks possible.

Working with Truvisory

Truvisory is a brand-new SBA-verified SDVOSB founded by a combat veteran — with no TAC or SAC relationships yet, which is exactly why we map them before chasing them. Nothing here is a past-performance claim; it’s the buyer map we use ourselves.

If you’re a fellow SDVOSB, the move is to monitor both centers’ forecasts, sub on SPRUCE or T4NG2 first, and let past performance compound. When you’re ready, the capability statement guide and the forecasting workflow are the two tools that make these centers reachable; the vehicle spokes and teaming are how you get in. Start at the pillar for the full map, or get in touch.