Much of the government's technology work is bought through vehicles a small firm does not hold: GSA Multiple Award Schedule contracts, NASA SEWP, agency-specific IDIQs. The prime holds the vehicle; the work is done by whoever the prime brings. That arrangement works well when the subcontractor brings something specific and takes responsibility for a defined piece of the order, and badly when it brings bodies.
This note is about how to make it the first kind.
What a small firm should bring
A senior team with a track record in the specific work, not a bench. For us that means custom software and modernization, sensors and research systems, AI and voice agents, cloud and DevSecOps, and data engineering, delivered by the engineers who sit in the briefing. The prime gets a workstream it does not have to staff or manage day to day, and a partner whose name is on the outcome.
The other thing to bring is paperwork that is already done: an active SAM.gov registration with a UEI and CAGE, a capability statement, a service level agreement for supported systems, and a standard subcontract template that has been through legal before.
How to structure the workstream
- A defined scope with its own deliverables. The subcontractor owns something: the data pipeline, the portal, the sensor network, the landing zone. Not "engineering support".
- A definition of done and a schedule the prime can report against. Weekly burn and progress reports, written, in the format the prime already sends the government.
- Firm-fixed-price where the scope allows it. It aligns everyone: the government gets a price, the prime gets a margin it can plan, and the subcontractor is paid for the outcome. Time and materials where discovery is genuinely needed, with a cap.
- Direct access to the government's technical lead, with the prime present. Requirements that pass through two layers of account management arrive changed.
- Documentation as a deliverable. Runbooks, as-built records, and hand-off training, so the government is never dependent on the subcontractor for the system to keep running.
What the prime is responsible for
The vehicle, the contract, the compliance framework, invoicing, and the relationship with the contracting officer. The subcontractor should make those easier: clean flow-down acceptance, timely invoices with backup, and no surprises in the monthly report.
For agencies reading this
If you have a task order in flight and a piece of it is not moving, ask the prime who is doing that piece. Adding a specialist subcontractor with a defined scope is a modification the prime can propose, and it is often faster than any other route to getting the work done.
If you are shaping a requirement and want a small firm's view of what it should say, we will give it in writing, with no obligation.
Working with us
Vonar AI Inc. is an active SAM.gov registrant (UEI MU9YZL34ZB83, CAGE 13GP2) and works as a subcontractor on GSA MAS and NASA SEWP task orders, as well as under direct award and simplified acquisition. Teaming enquiries go to partnerships@vonar.ai, or start with a few lines about the order. The capability statement has the identifiers and the service areas.