Teaming for VA AI: How an SDVOSB Gets Onto T4NG2 and SPRUCE Work
If you’re a brand-new SDVOSB AI shop, you missed the prime on-ramp onto T4NG2 and SPRUCE — both rosters are closed. But you have three doors onto the work that flows through them: subcontract to a prime, sign a teaming agreement for a specific bid, or form an SBA-approved joint venture and prime the set-aside yourself. And there’s one piece of math that makes a verified SDVOSB AI specialist the most valuable partner a prime can name on a VA set-aside: under the “similarly situated entity” rule, your workshare doesn’t count against the prime’s subcontracting limit. That single carve-out is the entire conversion engine of this page.
This is a spoke under the VA AI modernization pillar, written for a prime BD or capture lead who needs verified SDVOSB AI depth to satisfy set-aside math, and for an SDVOSB deciding whether to sub, team, or joint-venture onto VA AI work.
Why is a VetCert SDVOSB AI sub the most valuable partner a prime can name?
Because of one number: 50%. On an SDVOSB set-aside services contract — which is most VA AI work — the limitations-on-subcontracting rule at 13 CFR 125.6 and FAR 52.219-14 says the prime can pay no more than 50% of what the government pays it to firms that are not similarly situated. Put the other way: the prime, plus any similarly-situated subs, must self-perform at least half the contract revenue.
The carve-out is what creates the leverage. A similarly situated entity is a first-tier subcontractor that has the same small-business program status that qualified the prime — a verified SDVOSB sub on an SDVOSB set-aside — and is small for the NAICS the prime assigned to the work. Work that a similarly-situated sub performs with its own employees is excluded from the prime’s 50% cap. So when a large T4NG2 prime competes for an SDVOSB-set-aside task order, it needs a verified SDVOSB on the team to capture the work at all; and when a small SDVOSB prime competes, it can hand AI, cloud, and automation scope to a VetCert SDVOSB sub without burning any of its own self-performance budget. Either way, a verified SDVOSB AI shop is mathematically more valuable on the bid than an equivalent large or non-SDVOSB small partner.
There’s teeth behind it now: under a 2023 SBA rule, a contracting officer (CO) is barred from giving a satisfactory past-performance rating to a small-business prime that violates the limitation, absent specific mitigating circumstances. Missing the math is no longer a paperwork problem — it’s a past-performance risk.
What does “similarly situated” actually mean at the VA?
It means VetCert, full stop. The governmentwide definition (FAR 19.001, 13 CFR 125.1) requires the same status plus small size — but the VA adds a hard requirement that trips up teams built for other agencies. VAAR 852.219-73 states that for limitations-on-subcontracting purposes, only VIP-listed/VetCert SDVOSBs count as similarly situated. A sub that’s “self-certified SDVOSB” — which may count at another agency — does not count at the VA, and a sub whose VetCert lapses mid-performance retroactively destroys the prime’s math. The takeaway for a prime: confirm a sub’s VetCert status in the SBA certification database before naming them in a proposal. The takeaway for an SDVOSB: your active VetCert is the asset, and keeping it current is non-negotiable. The certification gate itself is covered in the Veterans First guide.
Subcontract, teaming agreement, or joint venture — which one?
Three structures, escalating in commitment and in upside.
A simple subcontract under FAR Subpart 9.6 is the fastest door: you sign on to a specific task order, the prime stays solely responsible to the government, and you start building past performance. The catch is that the CPARS record accrues to the prime, not to you. A teaming arrangement (a bid-specific contractor team arrangement, also FAR 9.6) is more formal — you’re named in the proposal, sometimes with exclusivity — and the government recognizes the arrangement, though the prime remains the sole contracting party. The highest-leverage door is an SBA-approved joint venture under 13 CFR 125.18: a separate LLC, registered in SAM.gov with its own UEI and CAGE, with a verified SDVOSB managing venturer owning at least 51% and a named responsible manager who is the SDVOSB’s employee. A JV can prime an SDVOSB set-aside — and a Mentor-Protégé JV under 13 CFR 125.9 lets a brand-new SDVOSB do it while borrowing an established mentor’s past performance and capacity, with an explicit exception from affiliation, provided the mentor-protégé agreement is SBA-approved before the offer goes in.
| Structure | Best when | Setup | Past-performance leverage | Upside |
|---|---|---|---|---|
| Subcontract | Building CPARS on existing primes’ task orders | Low | None — accrues to the prime | Speed, minimal risk |
| Teaming agreement | Jointly pursuing a known bid | Medium | Some — named in the proposal | Better economics, exclusivity |
| SBA small-business JV | You have an SDVOSB peer; want to prime set-asides | Medium-high | Each partner’s record considered | You become the prime |
| Mentor-Protégé JV | You’re new and need a mentor’s resume | High | Maximum — bid as SDVOSB with mentor’s record | Prime set-asides at scale; affiliation excluded |
How does the JV math work — the 40% rule and the 50% rule?
There are two stacked workshare problems on every SDVOSB JV award, and they’re easy to confuse.
The 40% rule lives inside the JV: the SDVOSB partner (the managing venturer, or the protégé in a Mentor-Protégé JV) must perform at least 40% of the work the JV itself performs, and it has to be substantive work, not administrative filler, so the SDVOSB gains real experience. The 50% rule lives outside the JV: the JV as a whole, treated as the prime, must still satisfy the limitations on subcontracting against any non-similarly-situated subs it hires. So on, say, a $20M SDVOSB SPRUCE task order, the JV must keep at least half the revenue with itself plus similarly-situated subs, and within the JV’s own share the SDVOSB partner must do at least 40%. Compliance documentation has to trace both lines, and a status protest will check both.
How does a new SDVOSB actually get onto T4NG2 and SPRUCE?
The honest answer differs by vehicle, because they’re structured differently.
T4NG2 is a mixed pool — roughly 33 awardees after the 2026 protest litigation settled, a blend of large primes (Accenture Federal, Booz Allen, CGI Federal, Deloitte, ManTech, SAIC) and reserved small-business and SDVOSB seats, several of which are themselves joint ventures. There’s no on-ramp, so a new SDVOSB’s only paths onto T4NG2 work are to subcontract or team with one of the holders on a specific task order, to form a JV with a holder, or — occasionally — to make the Rule-of-Two case that the requirement should come off T4NG2 to a VA standalone SDVOSB set-aside. SPRUCE is a 100% SDVOSB set-aside with ten primes, four of them SDVOSB joint ventures. Because every SPRUCE prime needs SDVOSB workshare and any non-VetCert sub counts against the 50% cap, a verified SDVOSB AI shop is especially valuable on SPRUCE task orders.
The proof the JV path works is in the recent award record: the Oddcore JV (Oddball/Wilcore) won a ~$15M AI-enabled VA.gov chatbot task on SPRUCE; Aquia Nava II (Aquia/Nava) won a ~$43M disability-benefits task with an AI claim-classification component; the SGL360 JV (Sentinel/DocMe360/Diligent) won a ~$3.28M AI clinical-documentation summarization award; and Olympus Alpha (MBL/Atlas) won a ~$4.98M Trustworthy AI program-management award. The Tech Sprint follow-on pattern, where these JVs often surface, is in the AI Tech Sprint guide, and the sole-source path several of them used is in the $5M sole-source guide.
What are the traps?
Four, and they’re the ones that bust SDVOSB eligibility or the prime’s math.
The ostensible subcontractor rule (13 CFR 121.103(h)) treats a prime as affiliated with a sub it’s “unusually reliant” on — but recent SBA decisions confirm a workable safe harbor for services: if the prime plus similarly-situated subs meet the 50% limitation, there’s no separate “primary and vital” problem. The two-year rule generally bars a specific JV from being awarded new contracts beyond two years from its first award without the partners being deemed affiliated (orders under an existing IDIQ are fine; new vehicles aren’t). In a Mentor-Protégé JV, the mentor-protégé agreement must be SBA-approved before the offer is submitted, or the affiliation exception doesn’t apply. And the one specific to the VA: a lapsed VetCert retroactively turns a similarly-situated sub into a non-SSE, blowing up the prime’s 50% calculation after the fact.
What security posture do I need to bring?
The same FedRAMP-and-ATO posture the rest of the cluster describes — not CMMC. VA AI work runs in the VA Enterprise Cloud (VAEC) on AWS GovCloud or Azure Government at FedRAMP High, under the VA ATO process and VA Handbook 6500/6517, with Section 508, HIPAA where clinical data is involved, and NIST 800-53 controls inherited from the platform; VA’s M-25-21 plan describes an accelerated path that can issue an initial AI ATO in about 60 days. For a sub or JV partner, the realistic and honest posture is FedRAMP-aware — able to build on FedRAMP High services within the VA’s boundary and inherit its controls — not “FedRAMP-certified,” and not CMMC-anything. CMMC is a DoD framework and isn’t a VA requirement; claiming it is reads as a credibility flag to a VA contracting officer. The full framing is in FedRAMP-aware, not CMMC-certified.
Frequently asked
Do I have to be on T4NG2 to win VA AI work?
What's the difference between a teaming agreement and a joint venture?
Can I count as a similarly-situated sub if I'm only self-certified SDVOSB?
What past performance does a JV inherit?
What happens to my SDVOSB status when I JV with a large mentor?
Working with Truvisory
Truvisory is an SBA-verified SDVOSB founded by a combat veteran, building working AI and automation on a Cloudflare-native, FedRAMP-aware architecture — fixed-scope, in 90 days.
If you’re a T4NG2 or SPRUCE prime who needs verified SDVOSB AI depth to satisfy the 50% similarly-situated math and fill an AI capability gap on a task-order bid, a VetCert SDVOSB AI sub is mathematically the most efficient partner you can name — book a capture call. If you’re an SDVOSB weighing a teaming or JV arrangement, start with the VA AI modernization pillar and the Veterans First guide.