Teaming Agreement vs. Subcontract: What to Sign Before the RFP Drops

The teaming agreement is a bridge, not the destination

FAR Subpart 9.6 recognizes contractor team arrangements because the government benefits when companies combine complementary capabilities. That does not make every private teaming promise enforceable, and it does not turn a pre-award agreement into a funded subcontract. The government awards one prime contract. Your commercial relationship with that prime still needs its own terms.

The clean distinction is operational. A teaming agreement governs how the parties pursue a named opportunity: who leads, what each party contributes, how proprietary information is handled, whether either party may join another team, and what work each expects if the team wins. A subcontract governs performance: statement of work, price, funding, invoicing, flow-down clauses, intellectual property, data rights, changes, acceptance, disputes, and termination.

If the prime says, "The teaming agreement covers us," ask where the labor categories, ceiling rates, payment terms, CDRLs, flow-downs, and data-rights allocation live. If those answers are not written, you do not have a subcontract. You have an expectation. Expectations are not a staffing plan.

Use a three-document sequence

Small contractors often jump from a nondisclosure agreement straight to a ten-page teaming agreement because the capture clock is running. A better sequence separates information protection, bid behavior, and funded execution.

• 1. Mutual NDA. Sign this before exchanging proprietary technical approaches, rates, resumes, customer intelligence, or incumbent data. Keep it mutual unless only one party will disclose.
• 2. Opportunity-specific teaming agreement. Sign once both parties have made a real bid decision. Name the solicitation, agency, vehicle, anticipated scope, proposal responsibilities, expected workshare, exclusivity boundary, and termination events.
• 3. Negotiated subcontract. Build the framework during capture, finish it after award details are known, and sign it before funded performance begins. Do not let employees charge "at risk" while the commercial terms remain open.

A letter of intent can sit between steps two and three if award timing forces it, but it should be narrow: a not-to-exceed amount, authorized period, named work, approved rates, invoice process, and a hard stop. An LOI is not permission to begin an unlimited transition on hope.

The practical schedule is short. NDA review should take one to three business days. A focused teaming agreement can usually be resolved in five to ten business days if the scope is real. Start the subcontract term sheet before proposal submission, then target a near-final subcontract within ten business days after the prime receives award. Long legal cycles are sometimes unavoidable. Undefined cycles are not.

Seven terms that matter before the proposal leaves the building

You do not need to negotiate every post-award clause before the RFP drops. You do need to remove the ambiguity that lets one party harvest the other's capture value without a credible path to work.

• Named opportunity. Identify the agency, program, solicitation or forecast number, vehicle, and anticipated procurement. "All opportunities with Customer X" is too broad.
• Proposal responsibilities. State who owns the solution, pricing, past performance, resumes, compliance matrix, color reviews, and final submission. Add due dates or a proposal calendar by reference.
• Workshare and scope. Use an estimated percentage plus identified work packages, CLINs, labor categories, or technical functions. State the assumptions that can legitimately change the allocation.
• Exclusivity. Limit it to the named pursuit, the defined role, and a finite period. Include automatic release if the prime no-bids, removes your scope, misses submission, or stops communicating.
• Customer access and communications. Define who may attend meetings, who leads, how contacts are coordinated, and whether the subcontractor may preserve its pre-existing customer relationships.
• Path to subcontract. Attach a term sheet or identify the required terms, negotiation deadline, and conditions precedent. "The parties may negotiate" is not a path; it is permission to walk away.
• Exit and survival. Cover termination, return of data, continued confidentiality, proposal-cost responsibility, use of contributed material, and what happens if the acquisition is delayed or recompeted.

Have counsel review the final language, especially governing law, remedies, exclusivity, and enforceability. The business team still owns the deal. Counsel cannot invent the workshare, customer strategy, or walk-away line after the capture team has already given away its leverage.

Workshare must connect percentage to actual work

"Subcontractor will receive 20%" sounds specific. It is not specific if nobody can identify 20% of what. Is it contract value, funded value, labor dollars, hours, headcount, or a subset of technical scope? Does it include ODCs and travel? Is the denominator the full IDIQ ceiling, the awarded task order, or only work actually ordered?

Build a one-page workshare map with four columns: scope element, proposed owner, pricing basis, and condition. A useful entry looks like: "Cybersecurity engineering; subcontractor lead; six named labor categories and associated ODCs; subject to customer approval of key personnel and award of CLIN 0003." That is far stronger than "approximately 20% based on best efforts."

Use a range when the RFP is still moving, but make it a real range. For example, 15% to 20% of labor dollars tied to two work packages is decision-grade. "A substantial portion" is not. If the prime refuses any measurable commitment while asking for unique past performance, named key personnel, or customer introductions, price the pursuit as high risk.

Also separate promised workshare from small-business subcontracting-plan goals. A prime's plan may describe categories and targets across the contract; it does not automatically reserve your company a specific piece of work. Likewise, limitations on subcontracting may affect how the prime structures performance, but they do not create your entitlement. Your protection has to be in your agreement.

Exclusivity and customer access are where leverage disappears

Exclusivity can be reasonable. A prime cannot build a differentiated team if a critical partner takes the same solution, resumes, and pricing to every competitor. The problem is scope creep: a clause written for one bid quietly blocks you from other work across an agency, vehicle, mission area, or multi-year recompete cycle.

Narrow exclusivity on four dimensions:

• Opportunity: one identified procurement, including specified task orders only if they are genuinely part of the pursuit.
• Role: the capability or scope you are providing to this team, not everything your company sells.
• Time: through submission and award, with an outside date if the acquisition slips.
• Performance by the prime: exclusivity ends if the prime no-bids, excludes your material, materially reduces agreed scope, or fails to submit.

Customer access needs equal discipline. Coordinate communications; do not accept a blanket gag order. If you brought an existing relationship, record it as pre-existing. If the prime wants you in a meeting because your subject-matter expert creates credibility, ensure your company and role are visible in the agenda, slides, or meeting record. Otherwise the prime learns your customer position while the customer forgets you were ever there.

Never share another company's procurement-sensitive information, and do not freelance around the prime's capture lead. The point is not uncontrolled access. It is preventing "coordination" from becoming erasure.

Draft the subcontract skeleton before award

The worst time to discover a flow-down, IP, or payment dispute is the week employees are supposed to start. Build a subcontract issues list during proposal development. You may not know the final prime-contract clauses, funding, or period of performance, but you can identify the business positions that determine whether the work is executable.

• Scope and deliverables: draft SOW, acceptance criteria, CDRLs, reporting cadence, and dependencies.
• Pricing: contract type, labor categories, rates, escalation, fee, ODC treatment, travel rules, and ceilings.
• Cash: invoice timing, payment timing, rejection process, retainage if any, and whether pay-when-paid language exists.
• Compliance: anticipated FAR/DFARS flow-downs, CMMC and CUI boundaries, cybersecurity incident duties, timekeeping, and audit support.
• Data and people: background IP, deliverable rights, inventions, key-person approvals, nonsolicitation, and employee-transition rules.
• Change and exit: written change authority, stop-work process, funding notices, termination, disputes, and records retention.

Compare that list with the flow-down clauses the prime sends. The subcontract should not simply say every prime-contract term applies "as appropriate." Build a clause matrix: mandatory, applicable to your scope, modified for the relationship, or not applicable. That review is cheaper before performance than after the first rejected invoice.

Know the red flags and set a walk-away line

Every capture team says the final subcontract will be worked out after award. Sometimes that is normal sequencing. Sometimes it is a warning that the prime wants your value in the proposal while preserving complete freedom later.

Escalate or walk when you see a combination of these:

• Broad exclusivity with no outside date or prime-performance condition.
• No measurable workshare despite requests for your past performance, key people, rates, or customer relationships.
• Unilateral right for the prime to use your proposal material after terminating the team.
• "Good-faith negotiation" language with no scope anchor, term sheet, deadline, or remedy.
• Pressure to begin transition or recruiting before written authorization and funding.
• Refusal to identify expected flow-downs, CUI boundaries, data rights, or payment structure.

Use a simple bid-risk score before signing: workshare clarity, exclusivity burden, strategic customer value, proposal cost, probability of win, and probability of actually receiving the subcontract. Score each one from 1 to 5. If the team only looks attractive because the prime's win probability is high, you are measuring the wrong outcome. Your expected value is probability of prime win multiplied by probability of subcontract, expected gross profit, and the strategic value that survives even if the bid loses.

This is a business framework, not legal advice. State law and exact wording matter, and courts have treated vague agreements to negotiate differently. The operator's job is to give counsel concrete terms worth protecting instead of asking them to rescue an undefined handshake.

Need a hand?

If a prime has sent a teaming agreement and the capture clock is running, we offer free 30-minute teardown calls for small Defense contractors. Bring the draft, the opportunity map, and the work you expect to own. We will pressure-test the workshare, exclusivity, customer-access rules, and path to subcontract so you know which business points need resolution before the proposal consumes your team.

Book a teardown ↗

FAQ

Is a teaming agreement the same as a subcontract?

No. A teaming agreement normally governs capture and proposal activity before award and sets the intended path to a subcontract. The subcontract governs funded performance after award: scope, price, invoicing, flow-downs, data rights, changes, termination, and delivery obligations. Treating the first document as a substitute for the second leaves major execution terms unresolved.

Should a teaming agreement state an exact workshare percentage?

Usually yes, if the opportunity is mature enough to support it. Tie the percentage to identified scope, labor categories, CLINs, or work packages and state the assumptions that could change it. A percentage with no scope map can be hollow, while vague language such as "substantial work" gives the prime too much room after award.

How long should exclusivity last in a government contractor teaming agreement?

Limit exclusivity to the named opportunity and end it at a defined event: a no-bid decision, elimination from the competition, award to another team, failure to submit, termination of the agreement, or a fixed outside date. Broad customer-wide or agency-wide exclusivity can block unrelated pursuits without giving the subcontractor anything in return.

When should the parties negotiate the actual subcontract?

Start the subcontract framework before proposal submission and resolve the full document before performance begins. At minimum, agree before the bid on scope, pricing assumptions, key flow-downs, data rights, payment timing, and the schedule for final negotiation. A practical target is a near-final subcontract within 10 business days after prime-contract award.

Can a small business rely on an email promise of workshare?

Do not build a hiring plan around it. Capture emails can explain intent, but they rarely settle scope, conditions, or post-award remedies. Put the workshare, assumptions, customer-access rules, proposal responsibilities, and path to subcontract in the signed agreement, then confirm any material change in writing.