8(a) and HUB Contractors: Using AI to Compete on Large Federal Health Contracts

The Gap Between Small-Business Certs and Large-Contract Reality

The federal government has a statutory small-business goal: 23% of all prime contract dollars are supposed to go to small businesses, with sub-goals of 5% to 8(a) small disadvantaged businesses, 3% to HUBZone, 5% to WOSB, and 3% to SDVOSB. Agencies report against these goals every year. Some meet them; many fall short.

The structural problem is that small-business set-asides tend to cluster at the low end of the contract distribution. A $300 thousand BPA for on-site staffing, a $1.2 million task order for document scanning, a $2 million program-management support contract - plenty of those go to 8(a) and HUBZone firms. But the awards that carry the dollars and shape the agency's operations are overwhelmingly captured by the same large incumbents: GDIT, Leidos, Booz Allen, Deloitte, Accenture Federal, Maximus, SAIC, CACI, Peraton, GDIT again, and a handful of others.

Call-center work is a textbook case. A VA Veterans Experience Office contact center, a CMS 1-800-MEDICARE overflow task order, a CDC information line, a SAMHSA helpline, an IHS patient services contract - these are awarded in the $20M to $500M range. The implicit premise behind the RFP is: the prime has to be able to staff 200 to 1,500 agents, recruit in a tight labor market, handle surge, run a PMO, and clear high-trust personnel. Very few 8(a) firms can credibly represent that capability on paper. So contracting officers narrow the competition pool, and the work goes to the incumbent.

This is not a complaint. It's a description of the incentive structure. The contracting officer's job is to award to someone who can actually deliver, and the evaluation factors reflect that.

How AI Rewrites the Capability Equation

AI voice delivery is the first technology in a generation that meaningfully changes the cost and risk profile of call-center delivery. A prime that runs on AI voice does not need to stand up a 600-seat contact center to answer 600 seats' worth of call volume. The throughput of a well-designed AI voice deployment is constrained by telephony and integration capacity, not by how many chairs the prime can fill in how many floors of how many buildings in the next 45 days.

What this means operationally for a small-business prime:

• The FTE requirement is smaller and the composition is different. The contract's seat count doesn't translate directly to people hired. AI handles the volumetric work; humans handle supervision, exception cases, warm escalation, QA, program management, and compliance. A contract that would have required 500 traditional FTEs can be delivered with a radically smaller - but more skilled - human team.
• The limitations on subcontracting rule becomes achievable. FAR 52.219-14 requires the prime on a services set-aside to perform at least 50% of the cost of personnel. That's nearly impossible for a small prime on a traditional staffing model that relies on a large-business subcontractor for bulk agent labor. With AI-native delivery, the prime's own AI voice platform, supervision, and program management satisfy the 50% without needing a subcontractor to carry the labor.
• Surge and ramp are credible. AI voice scales horizontally. A small prime can proposal credibly on a contract whose SOW requires 2x surge during open enrollment or after a policy announcement, because the AI platform absorbs the surge without recruiting.
• Quality and consistency become differentiators. Call quality on a well-designed AI deployment is consistent - the same tone, the same accuracy, the same data capture on every call. Traditional staffed call centers have quality variance that tracks agent tenure, shift, and market wage pressure.
• Cost structure moves in the prime's favor. AI voice cost per handled call is typically 60-85% below fully-loaded human agent cost. That margin is what lets a small prime absorb past-performance risk and still deliver competitive price.

8(a), HUBZone, WOSB, SDVOSB: What Each Actually Unlocks

The small-business certifications are not interchangeable. Each has a different legal basis, a different eligibility path, and a different set-aside structure. The right cert - or combination of certs - depends on the firm's ownership, location, and target market.

• 8(a) Business Development Program (SBA). Nine-year program for small businesses owned and controlled at least 51% by socially and economically disadvantaged individuals. Unlocks 8(a)-only set-asides, competitive 8(a) awards, sole-source awards up to $4.5M (services) and $7M (manufacturing), and Mentor-Protégé participation as protégé. The 8(a) program is the most powerful single cert for a small business pursuing federal work, and it is the one that transforms a vendor's trajectory fastest.
• HUBZone (SBA). For firms headquartered in a Historically Underutilized Business Zone with 35%+ of employees residing in a HUBZone. Provides HUBZone-specific set-asides and a 10% price evaluation preference in full and open competitions. Texas has its own state-level HUB certification through the Comptroller's office, separate from SBA HUBZone.
• WOSB / EDWOSB (SBA). Woman-Owned Small Business / Economically Disadvantaged Woman-Owned Small Business. WOSB set-asides are allowed in specific NAICS codes where women-owned firms are underrepresented.
• SDVOSB / VOSB (SBA and VA). Service-Disabled Veteran-Owned Small Business and Veteran-Owned Small Business. SDVOSB set-asides apply government-wide; VA has its own set-aside authority under the Vets First Contracting Program (38 USC §§ 8127-8128) which drives VA awards to verified SDVOSBs and VOSBs first.
• Native/Tribal 8(a) (ANC, Tribal, NHO). Alaska Native Corporations, federally recognized tribes, and Native Hawaiian Organizations can own 8(a) firms with special sole-source authority - notably, sole-source awards can exceed the $4.5M/$7M threshold without a justification and approval.
• State HUB programs (Texas, others). State-level HUB/MWBE programs drive state and local awards on state-funded work. Texas HUB is the most developed example - Texas state agencies have HUB goals and the Texas Comptroller runs the state HUB certification.
• Small Business (default). Every qualifying firm is "small" under SBA size standards for a specific NAICS code. Federal small-business set-asides are the broadest category.

BetaQuick's own status, for transparency: SAM.gov registration is active (UEI MDBYCN83MT69, CAGE 86Y32). 8(a) application is pending - not yet certified. GSA MAS application is pending. BetaQuick is not a veteran-owned firm and does not claim SDVOSB or VOSB status (BetaQuick does team with veteran-owned partners on relevant pursuits). NAICS footprint: 541511, 541512, 541519, 518210, 541330, 561422 (call center), and 611420.

Contract Vehicles That Matter

Winning a set-aside prime contract is a vehicle-and-agency problem as much as a capability problem. The relevant vehicles for AI voice and call-center scope:

• 8(a) STARS III (GSA). The premier 8(a)-only Government-Wide Acquisition Contract for IT services, with a $50 billion ceiling and active through 2029. STARS III on-ramps have historically been limited. Holders of STARS III get unique access to 8(a)-set-aside task orders across government. AI voice falls squarely in STARS III functional areas.
• GSA Multiple Award Schedule (MAS). The broadest small-business-accessible vehicle. Relevant SINs include 54151S (IT Professional Services) and 541611 (Management and Financial Consulting). Small business designations - 8(a), HUBZone, WOSB, SDVOSB - flow through MAS. Many agencies default to MAS for non-strategic IT services buys.
• CIO-SP4 (NIH NITAAC). Large IT services GWAC with small business reserves (8(a), HUBZone, WOSB, SDVOSB). Widely used by HHS agencies (CMS, NIH, CDC, HRSA).
• SEWP VI (NASA). IT products and supporting services; small-business categories.
• VA T4NG2 and VECTOR. VA's transformation-focused IT vehicle with strong SDVOSB set-aside orientation. Primary path for SDVOSB primes pursuing VA work.
• HHS Program Support Center (PSC) BPAs. Agency-specific BPAs for call-center, member services, and helpline scope - frequently set aside for small business or 8(a).
• Agency 8(a) BPAs. CMS, VA, SSA, CDC, HRSA, and IHS maintain their own 8(a) BPAs for recurring services. Entry point for 8(a) firms into repeat agency work.
• State cooperative purchasing. Texas DIR (Cooperative Contracts), NASPO ValuePoint, and state-level contracts. BetaQuick accesses Texas DIR work through partner Compass Solutions, LLC (DIR-CPO-6057, active through October 2030). Texas DIR carries HUB and minority-owned flags on its vendor roster.
• Direct sole-source 8(a) awards. Agencies can award up to $4.5M (services) or $7M (manufacturing) on 8(a) sole-source without competition. Tribal/ANC/NHO 8(a) firms can receive sole-source awards above those thresholds.

Mentor-Protégé and Joint Ventures

The single most underused tool in the small-business federal playbook is the SBA Mentor-Protégé Program. A formally approved mentor-protégé joint venture can compete for small-business set-aside awards (8(a), HUBZone, WOSB, SDVOSB, or general small-business set-asides) where the small business is the prime JV member and the large-business mentor contributes past performance, subject matter expertise, and capacity.

• Eligibility. Any small business can enroll as a protégé. The mentor can be any other business (including a large business). SBA approves the mentor-protégé agreement before any JV is submitted on a solicitation.
• Approved JV can compete for set-asides. Once the agreement is approved, the protégé and mentor can form a joint venture to bid a set-aside work even though the mentor itself is not small. This is the legal mechanism by which a large incumbent can back a small-business prime on a small-business set-aside without violating set-aside rules.
• Protégé must do at least 40% of the JV work. The protégé is the lead technical member of the JV and must perform at least 40% of the work - no paper-prime arrangements.
• Past performance of the mentor counts for the JV. The evaluation can consider the mentor's past performance as if it were the JV's, which closes the single biggest gap a new small prime faces.
• Limit per protégé. A protégé can have up to two mentors concurrently. A firm can serve as protégé for up to two mentor-protégé agreements in its life as a small business.
• Limit on mentor-protégé JV set-asides. Specific NAICS-based rules apply; SBA's final rule on affiliation and size exceptions covers the detail.

Mentor-protégé is how a small-business prime credibly competes for the $50M-to-$500M range of set-aside work that would otherwise be out of reach. The protégé brings the set-aside status and lead technical role; the mentor brings past performance and scale back-stop. On AI-voice-delivered contracts, the protégé's AI platform is often the actual source of the delivered scale, which reverses the classic dependence.

Teaming With Incumbents Without Getting Absorbed

Many 8(a) and HUBZone firms teaming with large primes end up as pass-through subs, never building independent past performance and never graduating to primary primes. That is avoidable with a few disciplines.

• Sub on strategic work only. Subcontract roles where the small business is the technical owner of a discrete, nameable scope - "AI voice platform," "member-services contact operations," "multilingual outreach" - not a pool of pass-through labor.
• Build independent past performance references. Insist on being identified to the customer as the owner of the delivered scope. Get the CPARS citation to include the small business by name.
• Structure contracts with scope boundaries. The sub-prime contract should describe the scope the small business independently controls, not vague "task order support."
• Use teaming on pursuits, mentor-protégé on delivery. A teaming agreement on a single pursuit is fine. For multi-year delivery, a mentor-protégé agreement is better - the small firm graduates with past performance tied to a specific customer, not just a prime.
• Protect IP and data. The small business's AI platform, scripts, voice models, and deployment tooling are the firm's own IP. Teaming agreements should be clear that the prime does not acquire rights to the small business's platform.
• Graduate deliberately. Plan the transition from sub to prime from day one. By the third year of any teaming relationship, the small business should be able to cite its own past performance at meaningful volume.

Past Performance Strategy for Small Primes

Past performance is the single most common reason a technically sound small-business proposal loses. Agencies want to see that the prime has delivered the specific scope, at similar magnitude, in a similar environment, within the past three to five years.

• Stack past performance by scope, not size. Demonstrate delivery on the functions the RFP requires - multilingual member services, crisis routing, scheduling, benefit intake, surge handling - at any dollar level. Functional match matters more than dollar match for evaluation.
• Commercial past performance is valid. Commercial call-center and AI voice work (BetaQuick's past performance includes SSA DCPS from 2016-2021, NIH RTL Code System from 2022-2024, General Dynamics IT from 2015-2016, Capital One from 2021-2022, and Under Armour from 2016) is evaluated alongside federal past performance. Federal evaluators look for execution discipline and outcome, not only a federal contract number.
• Use mentor-protégé past performance. The JV's past performance is counted for set-aside awards, which lets a small prime get past the experience threshold.
• Leverage state government past performance. State Medicaid, state unemployment, state child support, and state health department deployments count as public-sector past performance for federal proposals.
• Document the delivered metrics, not just the work. Past performance write-ups should include specific performance data - service level achieved, call volume handled, abandonment rate, CSAT, cost savings versus baseline. Evaluators reward specifics.
• Build CPARS discipline. Every federal contract closeout is a CPARS opportunity. Small primes that actively manage CPARS through the life of the contract (not just at the end) build a past performance record that evaluators trust.

Compliance Posture Agencies Expect

Small businesses pursuing federal health and VA work need to clear a compliance bar that used to be only a large-business burden. AI voice delivery specifically adds a layer of data-protection, model-governance, and auditability obligations.

• SAM.gov active registration. Non-negotiable. UEI and CAGE assigned. BetaQuick: active, UEI MDBYCN83MT69, CAGE 86Y32.
• FedRAMP. Moderate or High authorization on the AI platform. Federal health agencies increasingly require FedRAMP High for PHI-touching workloads. BetaQuick's stack runs on FedRAMP-authorized components (Amazon Connect FedRAMP High, Azure OpenAI FedRAMP High, AWS Transcribe FedRAMP, Azure Speech Services FedRAMP).
• HIPAA Business Associate Agreement. For any health agency contract, BAA with covered entity. 42 CFR Part 2 QSOA where SUD records are in scope.
• NIST 800-53 and 800-171. 800-53 for federal systems, 800-171 for controlled unclassified information. CMMC for DoD-adjacent work.
• Section 508. Accessibility of any public-facing system.
• CJIS where routing touches law enforcement. Relevant if the contract involves VA police, VA OIG, or cross-agency law enforcement.
• Personnel clearance. Public Trust (MBI, BI) for most federal health agency contact-center work; Secret for some DoD-adjacent. Small primes partner with cleared-personnel firms where in-scope.
• Executive Order on AI (2025) and NIST AI RMF. Federal agencies apply the NIST AI Risk Management Framework to AI deployments, with additional guidance from OMB. Model governance documentation is an expected proposal artifact.
• Supply chain security. SBOM (Software Bill of Materials) delivery, signed artifacts, and secure development lifecycle documentation per EO 14028.
• StateRAMP for state work. Increasingly required by state health, Medicaid, and behavioral health agencies.

The Playbook: Turning a Cert Into a Federal Prime Win

Consolidating the above into a sequenced plan:

1. Get the cert. 8(a) application, HUBZone (if geographically eligible), WOSB (if applicable), SDVOSB (if applicable). Apex Accelerators (formerly PTAC) provide free application support.
2. Complete SAM, UEI, CAGE. Non-negotiable prereq for every subsequent step.
3. Pick the vehicle. 8(a) STARS III if available; GSA MAS as the broad baseline; CIO-SP4 for HHS-heavy pursuits; T4NG2 / VECTOR for VA-heavy pursuits.
4. Identify a mentor and apply for mentor-protégé. The mentor should have complementary past performance - ideally a large federal health integrator with call-center track record who will not compete against the protégé on the same opportunities.
5. Build a narrow target list. 8 to 15 specific upcoming solicitations over the next 24 months. Stop chasing every RFI. Depth beats breadth.
6. Invest in past performance on state and commercial work. Every state Medicaid, state BH, state child support, or commercial health deployment builds the proposal dataset.
7. Stand up FedRAMP posture early. Inheriting controls from FedRAMP-authorized cloud providers (AWS, Azure Gov) is faster than authorizing the platform end-to-end, but documentation is still required.
8. Engage the contracting officer early. Pre-solicitation Industry Day attendance, RFI responses, and capability statement distribution through the agency's small-business specialist. Make the firm known before the solicitation drops.
9. Propose with AI as the delivery story, not a feature. The proposal narrative should make AI-native delivery the center of the technical approach, with FTE, scale, and surge explained in that framework.
10. Graduate deliberately. Start as protégé/sub; plan the transition to independent prime by year three.

Frequently Asked Questions