The timing problem, stated plainly
A system integrator reads a draft statement of work and finds three paragraphs of ordinary systems engineering and one paragraph that is not. Anomaly detection on telemetry. Document extraction from forty years of scanned records. Retrieval over a corpus the customer cannot move to a commercial cloud. The integrator can build the pipes, the interfaces, the hosting, the security package. The model is the gap. Proposals are due in five weeks. Hiring a senior machine-learning engineer with a federal background takes four to seven months from posting to first productive sprint, and that clock does not start until a contract exists to fund the seat.
So the honest question is not whether to build an internal AI practice. Many integrators should, eventually. The question is what to do about the bid in front of you, on the calendar in front of you, without putting a capability claim in the proposal that nobody on the payroll can execute. Evaluators are good at spotting that gap. A technical volume that describes a model in the passive voice, with no named engineer and no prior artifact, reads as risk in the source-selection narrative even when the rest of the response is strong.
The fix is a bench you attach to the bid rather than a team you build for it. We are that bench. Our people write the AI and ML portion of the technical volume, sit on the resume matrix as named personnel, and then perform the work as a subcontractor under your prime contract. You keep the customer, the vehicle, the architecture, and the record.
Where an external AI bench fits an integrator's bid
Editorial weighting from public sources and practitioner reading — illustrative, not a measured statistic.
Four engagement shapes
Almost every integrator request we get resolves into one of four structures. The differences matter because each one prices differently, carries a different flowdown burden, and produces a different kind of evidence for the next bid.
| Shape | When it fits | Contract form | What you get back |
|---|---|---|---|
| Named sub on the bid | Solicitation is open, AI work is a defined portion of the SOW | Teaming agreement now, subcontract on award | Resumes, work share percentage, technical volume sections, letter of intent |
| Task-order surge | You already hold the IDIQ or BPA and a task order landed with ML in it | Subcontract under the existing prime contract, consent per FAR 52.244-2 | Named engineers against your labor categories within days of award |
| Fixed-scope module | The AI piece has a clean interface and a testable acceptance criterion | Firm-fixed-price subcontract CLIN with defined deliverables | A working component, its test suite, and the runbook to operate it |
| Bench on call | Recurring, unpredictable AI demand across several programs | Master subcontract agreement with priced labor categories | Pre-negotiated rates and a standing team you can task in a week |
Named sub on the bid. This is the most common and the most valuable to both sides. We come in before submission, read the full solicitation rather than the excerpt, and write the AI and ML portions of the technical approach against your architecture. Our named engineers appear in the personnel section with real resumes. The teaming agreement is a contractor team arrangement in the sense of FAR 9.601(2), and FAR 9.603 states the government's policy of recognizing the integrity and validity of those arrangements, which means an evaluator has no basis for penalizing a properly documented team.
Task-order surge. You already won the vehicle. A task order arrives with a machine-learning requirement inside a period of performance that does not allow for recruiting. Under FAR 52.244-2 the contracting officer's consent to subcontract is often required for cost-reimbursement work and for subcontracts above the stated threshold, so the sequence is predictable and worth starting early. Where an approved purchasing system exists, consent requirements narrow considerably. Firms expecting more than $25 million in government sales over the next twelve months face a purchasing-system review under FAR 44.302(a).
Fixed-scope module. When the AI component has a real boundary, the cleanest structure is a firm-fixed-price subcontract for that boundary. An interface contract, a data sample, an acceptance test, a delivery date. You carry no labor risk and no model risk. We carry both. Integrators choose this shape when a program manager wants a single line item rather than a rate card, and it produces the crispest evidence for the next proposal, because the deliverable either passed the acceptance test or it did not.
Bench on call. Integrators with three or four programs that each need six weeks of ML work a year do better with a master subcontract agreement and pre-negotiated labor categories. Rates are settled once. Each new call becomes a task authorization rather than a procurement. The lead time from "we need someone" to "someone is working" drops from months to about a week.
How to describe the capability in the proposal
The most common mistake is describing the AI work in the abstract while describing the systems work in specifics. Evaluators read the contrast. If your integration section names the message bus, the interface control document, and the accreditation boundary, and the AI section says the team will "apply advanced machine learning," the technical volume has told the evaluator which half you actually control.
Write the AI section the way you write the rest. Name the model class and why it fits the data, not the trend. State the training and evaluation data by source and volume. Give a measurable target with a baseline attached: extraction accuracy against a hand-labeled sample of a stated size, false-positive rate at a fixed operating point, latency per document at a stated batch size. Name the person doing it. Name the subcontractor performing that work share. Every specific claim helps; every vague claim invites a weakness.
On past performance, the rule is friendlier than most integrators assume. FAR 15.305(a)(2)(iii) directs the evaluation to take into account past performance information regarding predecessor companies, key personnel with relevant experience, and subcontractors that will perform major or critical aspects of the requirement. A prime may cite a subcontractor's relevant record when that subcontractor is performing a major or critical portion. That is a legitimate, checkable path to covering an AI past-performance requirement you cannot cover on your own record. It does not run the other direction, and no small firm should promise you that it does.
One more piece of language matters: the key-personnel clause. Whatever Section H says about substituting key personnel binds you after award. Do not name a subcontractor engineer as key personnel unless the subcontract commits that engineer at the same level of firmness. We write our subcontract commitments to match the prime's key-personnel obligations exactly, because a mismatch there is where teaming relationships go bad in month four.
The regulatory math that decides the work share
Work share is not a negotiation over pride. Several rules cap or shape it, and the number in the teaming agreement should be derived from them rather than guessed.
- Set-aside limitations. For a services set-aside, 13 CFR 125.6 limits the prime to paying no more than 50 percent of the amount received from the government to firms that are not similarly situated entities. If the prime is small and the sub is small under the same NAICS code, the similarly-situated exception changes the arithmetic.
- Pass-through charges. FAR 52.215-23 addresses excessive pass-through charges, and the associated solicitation provision applies where an offeror intends to subcontract more than 70 percent of the total cost of work. Indirect costs and profit on subcontracted effort for which the prime adds no or negligible value can be disallowed.
- Subcontracting plans. Under FAR 19.702 and the clause at FAR 52.219-9, a large prime needs an accepted small-business subcontracting plan for contracts expected to exceed $750,000. An AI subcontract is frequently the cleanest way to move a goal line.
- SBIR and STTR performance of work. On an SBIR, the small business must perform at least two-thirds of the effort in Phase I and at least half in Phase II. On an STTR, the small business performs at least 40 percent and the research institution at least 30 percent. These are floors on the awardee, and they decide who can prime.
- Cost realism. On cost-reimbursement bids, FAR 15.404-1(d) means the evaluator will test whether your proposed labor mix can actually do the work. A thin AI staffing line with an ambitious AI promise is exactly what cost realism analysis is designed to catch.
In practice, most AI modules inside integration programs land between 8 and 25 percent of total contract value. That range keeps the prime comfortably clear of the pass-through provision, satisfies set-aside limitations in most structures, and is large enough that the sub qualifies as performing a major or critical aspect for past-performance purposes.
What the integrator keeps
This is the question every capture manager asks second, right after price. The answer should be written into the subcontract rather than assumed.
The customer relationship. We do not contact the government customer outside the channel you define. Technical exchanges happen with you in the room or with your written consent. No parallel business development against your account, ever.
The prime position and the record. The contract is yours. The CPARS entry is yours. The transition path into the follow-on is yours. If the program grows into a larger AI scope and you want to hire for it, we hand over the code, the training pipeline, the evaluation suite, and the documentation, and we brief your new hires.
The deliverable rights. Software and technical data delivered to the government carry the rights the prime contract assigns. On DoD work that is DFARS 252.227-7013 for noncommercial technical data and 252.227-7014 for noncommercial computer software, with restrictions identified and asserted under 252.227-7017 before award rather than after. We assert our pre-existing background tooling in that pre-award list and license it to you for the program. Everything developed under the effort is delivered with the rights your prime contract requires. On SBIR-derived components the SBIR data rights clause at DFARS 252.227-7018 governs, with a protection period of twenty years from award under the SBA policy directive, and that posture gets settled in writing before any code is written.
The architecture. You own the system design. We fit the model to your interfaces and your accreditation boundary rather than proposing a platform that reshapes the program around our preferences. That discipline is the difference between a subcontractor and a vendor trying to land a footprint inside your account.
Flowdowns that ride along
An AI subcontract on federal work carries the same compliance freight as any other subcontract, and the integrator's contracts office will want the answers before the teaming agreement is signed. DFARS 252.204-7012 flows down where covered defense information is involved, which pulls NIST SP 800-171 into the sub's environment along with the 72-hour cyber incident reporting obligation. The CMMC program rule at 32 CFR part 170 sets the assessment level tied to the information handled, and the clause at DFARS 252.204-7021 carries it into the subcontract chain at the level appropriate to what the sub touches.
Export-controlled technical data adds a second gate. A subcontractor receiving militarily critical technical data through DoD channels needs to be certified under the Joint Certification Program via DD Form 2345. We hold that certification, with CAGE code 1AYQ0, so export-controlled drawings and data can move without a two-month detour. If the delivered component has a user interface reaching government employees or the public, Section 508 of the Rehabilitation Act (29 U.S.C. 794d) and the standards at 36 CFR part 1194 apply to the interface, and that is a design constraint from day one rather than a remediation project at delivery.
From requirement to signed teaming agreement
Who is actually on the bench
Precision Federal is an SBIR and STTR shop that builds production AI, ML, data, and cloud systems for federal, state, and commercial customers, as prime or as subcontractor. Our practice is led by a former professor in technology who ranks in the top 200 of more than 200,000 competitors on Kaggle, the top 0.1 percent, and holds seven cloud certifications, with twenty years building production systems for federal agencies across five consulting firms, three of them federal. Behind that sits a standing bench of named engineers, licensed professional engineers, and domain specialists across defense, health, energy, transportation, and public-sector data.
What that means for a bid is specific. When you send a requirement, you get back names and resumes, not a capability brochure. The engineer described in the technical volume is the engineer who performs the work. Our registration is active in SAM.gov, our CAGE code is 1AYQ0, and our Joint Certification Program status is current, so the contracts side of the file is already assembled when your subcontracts officer asks for it.
When you should not add a sub
Three cases where the answer is no, and we will say so. First, when the AI paragraph is decorative and the customer does not actually want a model. Adding a sub to satisfy a buzzword adds cost and reporting for nothing, and a good evaluator sees through it. Second, when the work is a permanent, full-time function of your business rather than a program-scoped need; at that point hiring is correct and we will tell you so. Third, when the scope is genuinely undefined. "AI somewhere in the program" cannot be priced, cannot be tested, and turns into a dispute in month five. Define the boundary first, then attach the bench.
Bottom line
Integrators lose AI-adjacent work for a reason that has nothing to do with engineering talent and everything to do with calendar arithmetic. The requirement arrives on a proposal clock, and hiring runs on a hiring clock. Attaching a named, credentialed bench to the bid resolves the mismatch in days rather than quarters, satisfies the past-performance and personnel sections with real evidence, and leaves the customer, the contract, the architecture, and the record exactly where they belong: with you.
What to send
- The requirement paragraph or the topic text, verbatim
- The close date and the period of performance
- Contract type and vehicle, if one is already in place
- Ceiling or target value, if you have one
- Data sensitivity: CUI, export-controlled, classified, or none
- The work share you want the AI portion to carry
Frequently asked questions
Yes, where the subcontractor will perform a major or critical aspect of the requirement. FAR 15.305(a)(2)(iii) directs evaluators to consider past performance of predecessor companies, key personnel with relevant experience, and such subcontractors. The reverse does not hold, so a sub cannot claim the prime's record as its own.
Most AI modules inside a larger integration program land between 8 and 25 percent of total contract value. That range keeps a prime clear of the excessive pass-through provision at FAR 52.215-23, works inside the set-aside limitations at 13 CFR 125.6 in most structures, and is substantial enough to support a past-performance citation.
The engineering side moves in about a week once scope is defined. The pacing item is usually contractual: consent to subcontract under FAR 52.244-2 where it applies, and the flowdown package. Starting the consent conversation with the contracting officer at the same time as the technical scoping compresses the whole sequence.
Deliverables carry the rights the prime contract assigns, which on DoD work usually means DFARS 252.227-7013 and 252.227-7014, with pre-existing background material identified and asserted under 252.227-7017 before award. Settle the assertion list before code is written rather than at delivery.
Where covered defense information is involved, DFARS 252.204-7012 flows down with NIST SP 800-171 and 72-hour incident reporting. CMMC obligations follow the program rule at 32 CFR part 170 and the clause at DFARS 252.204-7021. Export-controlled technical data requires Joint Certification Program status through DD Form 2345.