What primes actually look for in a small-business teaming partner

What the prime is actually buying

Small firms tend to picture teaming as a relationship question. Capture managers experience it as a scoring question. Somewhere between the draft solicitation and the submission date, a capture manager reads the evaluation criteria, maps them against the people already on the bench, and finds two or three places where the bid will read thin. Adding a teammate is how those places get filled. Every question that follows, including the ones that feel like bureaucratic friction, traces back to whether the addition makes the score go up more than it makes the risk go up.

Three purchases are in play, and they are rarely equal on any given bid. The first is a capability gap. A prime that has instrumentation engineers and no one who has trained a model, or a systems integrator whose data engineering staff is fully booked on another program, has a hole in a technical volume that has to be written by somebody. The second is the small-business plan: on most large awards the prime must submit one, and on many it gets evaluated. The third is risk transfer on a scored weakness, which is the least discussed and often the strongest motive. If the customer has previously complained about a prime's slow analytics turnaround, naming a specialist teammate is a direct answer to a known criticism.

A fourth motive shows up on cost-sensitive bids: rate relief. A small firm without a large corporate overhead structure prices labor lower than a prime's fully burdened rate for the same skill. On a best-value tradeoff where price is a real discriminator, moving twenty percent of the hours to a lower wrap rate can be worth more than any technical narrative. Understanding which of these four the prime is buying, on this specific bid, is the difference between a useful first conversation and a generic one.

FAR 9.6 says less than most people expect

Teaming has a home in the regulation, and it is a short one. FAR 9.601 defines a contractor team arrangement two ways: companies forming a partnership or joint venture to act as a potential prime, or a potential prime agreeing with other companies that they will act as its subcontractors on a specified contract or acquisition program. FAR 9.602 says the government recognizes the integrity and validity of these arrangements as long as the relationships are disclosed in the offer, or before the arrangement becomes effective if it is formed later.

Then FAR 9.604 draws the boundary that matters. The government is not a party to the arrangement. It does not limit the prime's rights and obligations as the responsible party for the whole contract, and it does not shield the parties from antitrust law. FAR 9.603 adds that the contracting officer will normally neither require nor refuse to recognize a team arrangement. In practice this means nobody at the agency is going to enforce a work-share promise, adjudicate a dispute between a prime and a sub, or care very much how the team divided the labor as long as the prime performs.

One note on citations for 2026. The 2025 overhaul reissued large sections of the FAR through agency class deviations, and section text and numbering are moving in places. Verify the current deviation text your contracting activity is using. The substance described here, disclosure of the arrangement and the government's distance from it, has not changed.

A teaming agreement is not a subcontract

This is where small firms lose money and time. A teaming agreement is a pre-award document between two companies. It usually covers confidentiality, exclusivity for this pursuit, who writes which proposal sections, and an intended scope of work if the team wins. That last part is frequently written as an intention to negotiate a subcontract in good faith, which courts have treated as unenforceable. In Cyberlock Consulting, Inc. v. Information Experts, Inc. (E.D. Va. 2013, affirmed by the Fourth Circuit in 2014), a teaming agreement promising a 49 percent work share was held to be an unenforceable agreement to agree because the subcontract terms were left for future negotiation.

Dimension	Teaming agreement (pre-award)	Subcontract (post-award)
When it exists	Signed before proposal submission; commonly expires at award, at non-award, or on a stated date	Executed after the prime wins and the scope is funded
What it binds	Confidentiality, exclusivity, proposal support, an intended work share	Scope, price, schedule, deliverables, payment terms, remedies
Enforceability of work share	Often none; agreements to negotiate later have failed in court	The number in the subcontract is the number
Government role	None. FAR 9.604: the government is not a party	Still not a party, though consent to subcontract may apply under FAR 44.2
Clause flow-downs	A promise to accept flow-downs later	Real clauses: DFARS 252.204-7012, FAR 52.219-8, FAR 52.204-25, and others
Typical failure mode	Scope shrinks between bid and award, and the sub has no remedy	Slow definitization leaves the sub working at risk for months

Two practical protections. Ask that the intended statement of work and the labor categories with rates be attached as an exhibit to the teaming agreement, so the later subcontract is a fill-in rather than a fresh negotiation. And ask for a definitization deadline: a clause saying the parties will execute a subcontract within a stated number of days after award, with the exhibit as the default terms if they do not. Neither request is unusual, and a capture manager who has run this before will not be offended by either one.

The diligence a prime runs before signing

Contracts and compliance staff at a prime run a standard check on any new teammate. Most of it is mechanical, most of it can be answered in a day, and being slow on it is one of the fastest ways to fall off a bid. The list below reflects what the checks are looking for.

• SAM.gov registration active, with the Unique Entity ID and CAGE code ready to paste into a teaming form. An expired registration is treated as a red flag about everything else.
• Size representation under the solicitation's NAICS code, not under a code the firm prefers. For 541512, Computer Systems Design Services, the SBA size standard is $34 million in average annual receipts, computed over five fiscal years under 13 CFR 121.104. SBA proposed a further inflation increase to receipts-based standards in August 2025 that was not final as of this writing.
• Exclusions and integrity records: the SAM exclusions list under FAR 9.404, plus whatever appears in FAPIIS and CPARS.
• Affiliation exposure under 13 CFR 121.103, which can change a size status through common ownership, management, or economic dependence.
• Socioeconomic certifications and whether they are certified or self-certified. SDVOSB and WOSB certification status determines whether the prime can count the dollars toward a specific goal.
• Cyber posture: a current NIST SP 800-171 assessment score posted in SPRS, a system security plan, a plan of action and milestones, and a stated CMMC level.
• Accounting capability matched to the subcontract type, including timekeeping adequate for a cost-reimbursement award and provisional indirect rates the prime can carry into its own cost volume.
• Organizational conflicts of interest screened under FAR 9.5 against the prime's other work on the same program, which is a live issue for firms doing advisory or test-and-evaluation work.
• Section 889 representations under FAR 52.204-24 and 52.204-26, plus insurance certificates and a W-9.
• Cash position sufficient to carry 30 to 60 day payment cycles, since a sub gets paid after the prime does.

Cyber posture is a gate now, not a conversation

For DoD work this changed materially in late 2025. The DFARS rule integrating CMMC into contracts was published on September 10, 2025 and took effect November 10, 2025, opening the first phase of a four-phase rollout in which solicitations begin carrying CMMC requirements through DFARS 252.204-7021 and the new 252.204-7025. Level 1 and self-assessed Level 2 requirements appear first, with third-party assessed Level 2 arriving in later phases.

The part that reaches subcontractors: DFARS 252.204-7012 already flows down to any subcontractor that will handle covered defense information, and it carries the NIST SP 800-171 control set plus 72-hour incident reporting to DIBNet. DFARS 252.204-7019 and 252.204-7020 require the self-assessment score in the Supplier Performance Risk System, and a prime can see whether a score is posted and how old it is. A small firm that says "we can get compliant after award" is asking the prime to accept schedule risk on a clause the prime cannot waive.

How the small-business plan gets scored

FAR 19.7 is the reason many teaming calls happen at all. Under FAR 19.702, an other-than-small prime must submit a subcontracting plan on an award expected to exceed the threshold when subcontracting opportunities exist. The 2025 inflation adjustment of acquisition-related thresholds raised that figure to $900,000, with $2 million for construction of a public facility. FAR 19.704 sets what the plan contains: separate percentage goals for small business, veteran-owned, service-disabled veteran-owned, HUBZone, small disadvantaged, and women-owned small business concerns, a description of the methods used to develop those goals, and a named individual responsible for administering the program.

Two things follow from this that small firms consistently underrate. First, the goals are numbers the prime has to report against through the electronic subcontracting reporting system, and failure to make a good faith effort to meet them carries liquidated damages under FAR 19.705-7. Primes do not enjoy writing goals they cannot hit. Second, many source selections evaluate small business participation as a separate factor, which means a named teammate with a real scope reads better than a percentage with no names attached. The government-wide statutory goal is 23 percent of prime contract dollars to small business under 15 U.S.C. 644(g), and recent SBA scorecards have reported the government exceeding it, with the small business prime share running near 28 percent and dollar totals above $170 billion.

When a capture manager asks for a firm's socioeconomic categories, this is the machinery behind the question. It is not idle curiosity, and a firm that answers precisely, naming which certifications are held, which are self-certified, and which are pending, is easier to fit into a plan than one that answers vaguely.

Work share, and what makes a percentage believable

Small firms frequently ask for a work-share percentage in the first meeting. Capture managers hear this as a request to commit before the bid is understood. A more effective approach is to propose the scope first and let the percentage fall out of it: name the specific CLINs, the specific tasks, or the specific proposal sections the firm would own, then price them.

Typical subcontractor shares on services work range widely, and anything from 10 to 40 percent is common depending on the gap being filled. Two structural facts constrain the number. On a set-aside, the limitations on subcontracting at 13 CFR 125.6 and FAR 52.219-14 cap what a small prime may pass to firms that are not similarly situated, which is 50 percent of the amount paid by the government for services other than construction. On full-and-open work the constraint is different: the prime wants to keep the work that builds its own past performance, so the durable subcontract positions are the ones the prime does not want to staff itself.

Expect the number to move at award. Funding gets cut, the customer descopes an option, or the technical approach shifts during negotiations. A sub whose entire business case depends on the pre-award percentage holding exactly is a sub that will end up disappointed. Build the case on getting into the contract and performing well enough to grow inside it.

Key personnel is the promise broken most often

Named key personnel with committed availability is worth more to a bid than almost any other contribution, and it is the commitment small firms most often fail to keep. The pattern is familiar to every capture manager: a resume goes into the proposal, the award lands eight months later, and the person has moved on or been billed to other work.

Handle this directly. Say who is available, at what percentage, and what happens if the award slips two quarters. If the person is the founder and the founder cannot be at 100 percent, say so and propose the substitution path in writing. A prime can plan around a stated constraint. It cannot plan around an optimistic resume, and a key-personnel substitution request in the first month of performance is a memorable way to damage a relationship that took a year to build.

The capture sequence, and where a small firm has to fit

Teaming decisions run on the prime's calendar, not the sub's. The rough shape below is typical for a mid-size services or systems bid. The exact durations vary, but the ordering is stable, and a firm that shows up at week three before submission is arriving after the team is closed.

The mistakes that end first conversations

Opening with the firm's story. A capture manager under deadline pressure is scanning for one thing: does this firm solve the problem on the current pursuit. Company history, founding narrative, and a slide about the mission belong later, if at all.

Asking "how can we work together" with no opportunity attached. This puts the work of finding a fit on the person who has the least time for it. Naming a specific solicitation, a specific agency program, or a specific recurring recompete makes the conversation concrete.

A capability statement that lists technologies instead of outcomes. A page listing every framework and cloud service the firm has touched signals breadth without depth. Two or three areas of genuine depth, with the evidence a technical evaluator would accept, beats fifteen logos.

Not knowing the firm's own size status under the solicitation's NAICS code. This gets asked in nearly every first call, and hesitating on it costs credibility that is hard to recover.

Overstating clearance or facility status. Personnel clearances, a facility clearance, and an export certification are three separate things, and a prime will verify all of them. Saying "we can get cleared" when the firm has no facility clearance sponsorship is caught immediately.

Asking for exclusivity on the first call. Exclusivity is something a prime grants after it decides the firm is worth protecting. Requesting it early reads as a firm managing its own risk before it has contributed anything.

Being slow. A prime that asks for a rate sheet on Tuesday needs it before the Friday pricing review. Firms that answer diligence questions in hours, with complete documents, get invited back regardless of size.

What a useful first email contains

Short, specific, and structured for a reader who will spend forty seconds on it. The opportunity or program by name. One sentence on the gap the firm fills, written in the customer's language rather than the vendor's. Two or three sentences of technical substance that show the work has been thought about. The compliance line: UEI, CAGE, primary NAICS codes, size status, socioeconomic categories, SAM status, and cyber posture in one block. Named availability of the one or two people who would do the work. Then a single ask.

What to leave out: adjectives about the firm, a pitch deck attachment, a request for a call before any written exchange, and any claim that cannot be verified in a document. The tone that works with capture staff is the tone of an engineer reporting a status, and the firms that get repeat invitations are usually the ones that make the capture manager's job easier rather than the ones that describe themselves most impressively.

Bottom line

Teaming is a scoring decision wearing the clothes of a relationship. The prime is closing a gap, defending a subcontracting plan, and reducing risk on an evaluated weakness, and everything it asks for is instrumentation on those three purposes. A small firm that shows up with clean registrations, a stated cyber posture, a scope proposal instead of a percentage demand, honest availability for named people, and same-day responsiveness has removed most of the reasons to say no. That is the whole method. The regulation is short, the diligence is mechanical, and the differentiator is being easy to put on a bid.

Frequently asked questions