Subcontracting to an SDVOSB — how primes close small-business goals with a bounded work package

Every prime with a subcontracting plan under FAR 52.219-9 reports against small-business categories, and service-disabled veteran-owned small business is one of them. The statutory government-wide SDVOSB goal is 3 percent under 15 U.S.C. § 644(g); agency and prime targets are often set higher, and the reporting is public. Most primes do not miss the goal for lack of will. They miss it because the work offered to small firms is shaped as staffing rather than as scope.

Why staffing requests underperform

A request for “two developers at these labor categories” asks a small firm to become a temp agency. The firm carries the recruiting risk, the prime carries the management burden, and neither gets a deliverable it can point to. When the contract is a services set-aside with FAR 52.219-14, the workshare math gets harder as well.

A bounded work package fixes that. It gives the small firm a deliverable with acceptance criteria, gives the prime a fixed interface, and gives the government a traceable outcome.

Anatomy of a work package

A work package that a prime can award and a subcontractor can own has six parts:

1. Scope statement. What is being built or delivered, for which users, in what environment.
2. Interfaces. The systems, data, and platforms the package touches, and who owns each side of the boundary.
3. Deliverables. Named artifacts: source, documentation, test evidence, training, handoff inventory.
4. Acceptance evidence. What the prime and the government will see to accept the work.
5. Retained authority. What stays with the prime: platform, security authorization, hosting, program management, enterprise operations.
6. Schedule and price basis. Milestones tied to deliverables, with labor detail that supports the prime’s own pricing.

Examples inside a modernization program: a public-facing portal with intake and routing; a content inventory, information architecture, and migration scope for a website consolidation; an accessibility assessment and remediation backlog; a reporting layer over the prime’s data platform; a bounded AI prototype on synthetic data with an evaluation record; or the documentation, testing, and training package for a system that has none.

Workshare and limitations on subcontracting

On a small-business services set-aside, FAR 52.219-14 requires that the awardee not pay more than 50 percent of the amount paid by the government to firms that are not similarly situated. Where the prime is itself a small business and the subcontractor is an SDVOSB, the arrangement can count toward compliance; where the prime is large, the limitation does not apply to the prime but the SDVOSB’s work still counts toward the subcontracting plan. Structure the package so the SDVOSB performs the package with its own people, and document that in the teaming agreement.

What the prime should ask the SDVOSB for

• SBA VetCert record and SAM registration that match.
• A capability statement mapped to the package, not a general brochure.
• The names and experience of the people who will perform.
• A candid statement of what the firm does not have, including clearances, authorizations, or federal past performance, so there are no surprises in the compliance matrix.

How Be Chosen Agency works with primes

BCA pursues defined subcontract work packages with explicit interfaces, deliverables, and acceptance evidence, and leaves platform authority, security authorization, hosting, and program management with the prime. It is an SBA-certified SDVOSB in NAICS 541511, based in Peoria, Arizona, with owned-system engineering evidence a technical evaluator can inspect and no federal past performance yet. Send the section of the statement of work you are trying to place to Teton Wilson and BCA will return a work-package proposal you can put in front of your program manager.