Federal Teaming Agreements: What Primes Need to Know
Before a prime submits a proposal with a small business sub listed on their team, the relationship needs to be formalized. That formalization is a teaming agreement — a pre-award contract between the prime and one or more team members that defines each party's role, scope, and conditions for the relationship.
Teaming agreements are common across federal procurement. They're specifically authorized under FAR 9.601 and are a standard part of proposal preparation for any complex acquisition where no single entity has all the required capabilities. For prime contractors building teams that include cloud engineering and DevSecOps subs, understanding what these agreements require — and what they're designed to protect — matters before the proposal window opens.
What FAR 9.601 Actually Says
FAR Part 9.6 establishes the framework for contractor team arrangements. The regulation recognizes two types:
Type 1: Each team member is responsible for delivery of specific portions of the work. The prime manages the contract; each sub delivers its defined scope. This is the most common structure for IT programs where the sub owns a technical component.
Type 2: Team members share all aspects of performance, functioning as an integrated team under the prime's direction. This is more typical of large, multi-disciplinary programs where the work can't be cleanly partitioned.
For a cloud-native DevSecOps sub like Rutagon, Type 1 arrangements are the standard: Rutagon owns the infrastructure and pipeline delivery scope; the prime manages the program, customer relationship, and contract.
The FAR makes one critical point: teaming agreements are not contracts with the government. They're agreements between commercial entities about how they'll perform if they win the contract. The government's contract is with the prime. The prime's contract with the sub is a separate, private commercial agreement.
What Should Be in a Teaming Agreement
A federal teaming agreement establishes the pre-award relationship. It doesn't need to be a full subcontract — that comes after award. But it should cover:
Exclusivity and scope: Is the sub exclusive to this prime for this specific opportunity, or can the sub team with multiple primes bidding the same contract? Exclusivity is common in competitive situations and protects both parties — the prime knows the sub is committed to the team; the sub knows the prime isn't shopping alternatives.
Work allocation: What portion of the work will the sub perform if the team wins? For SBA small business subcontracting goals, the work actually performed by each party matters — simply listing a sub on the proposal without genuine work allocation can constitute fraud in government contracting.
Information sharing obligations: Teaming requires sharing sensitive information: pricing assumptions, proprietary technical approaches, sometimes labor rates. The agreement should include confidentiality provisions with defined scope and duration.
Proposal participation: Who prepares which sections? What technical content does the sub contribute? Cost/price data for the sub's scope? The agreement should define each party's proposal obligations and timelines.
Term and termination: Teaming agreements typically run from execution through contract award (or a defined period after the solicitation closes if award is delayed). They should address what happens if the opportunity is canceled, the team fails to win, or one party wishes to withdraw.
Award and subcontract: Does the prime commit to award a subcontract to the teaming partner if they win? This is one of the most negotiated points. Some primes want flexibility; small business subs want the commitment. The SBA has opined that a teaming agreement that doesn't result in an actual subcontract can constitute misrepresentation if the sub was listed solely for proposal credit.
Rutagon's Standard Teaming Structure
When Rutagon enters a teaming agreement with a prime, the structure Rutagon typically proposes:
Scope clarity first. Before signing, Rutagon documents the specific technical deliverables it expects to own: infrastructure design, CI/CD pipeline buildout, specific application modules, or compliance documentation. Vague scope creates disputes at proposal time and conflict during performance.
Rate transparency. Rutagon provides its labor category rates for the work scope at the teaming stage, enabling the prime to build an accurate proposal price. Government proposals that submit inflated sub rates as padding for post-award renegotiation create procurement integrity risk; Rutagon doesn't operate that way.
Exclusive on specific opportunity, not blanket. Rutagon can commit exclusivity to one prime for a specific solicitation without restricting its ability to work with other primes on other opportunities. The exclusivity is solicitation-specific, not a broad non-compete.
Post-award subcontract commitment. Rutagon requests a provision that if the team wins, the prime will award a subcontract to Rutagon consistent with the work scope in the teaming agreement. This protects both parties and keeps the SBA happy.
The Small Business Goal Dimension
A prime who lists Rutagon in a teaming agreement and then subcontracts work to Rutagon upon award can count that value toward their SB subcontracting plan goals. But the planning has to happen before proposal submission, not after award.
Subcontracting plans that list businesses to fill percentage goals without genuine work allocation are a compliance risk. The SBA and agency IGs actively review subcontracting plan execution — tracking what was promised vs. what was actually subcontracted. The safest plan is one where the work scope, dollar value, and sub capability are all credible and documented.
Rutagon's NAICS codes (541512 primary, 541511, 541519, 518210 secondaries), active SAM.gov registration (UEI: FB2FHEJHM493, CAGE: 19ZR7), and documented production delivery history make the subcontracting plan entry defensible, not just compliant.
When to Start the Teaming Conversation
The ideal time to approach a potential teaming partner is before the solicitation releases. Once a solicitation drops, the proposal timeline compresses quickly — often 30-45 days for a complex IT RFP. Negotiating and executing a teaming agreement, aligning on technical approach, and building the proposal sections a sub must contribute all take time.
Primes who wait until after solicitation release often end up with subs who sign boilerplate agreements without real alignment — which shows up in proposals and in performance.
Rutagon is open to teaming discussions for programs in cloud engineering, DevSecOps, software modernization, and government IT. Early-stage conversations are welcome even when a solicitation hasn't been released yet. For active opportunities, Rutagon maintains a standing capability brief at rutagon.com/government.
For context on what Rutagon delivers as a sub, see SBA Subcontracting Goals: What Primes Need and DevSecOps Subcontracting: What a Prime Gets.
Start a teaming conversation → rutagon.com/contact
Frequently Asked Questions
Is a federal teaming agreement legally binding?
A teaming agreement is a binding commercial contract between the prime and sub — it's enforceable under applicable state contract law. However, it is not a contract with the federal government. The government's contractual relationship is solely with the prime. The teaming agreement defines private commercial rights and obligations between the teaming parties.
What happens if the team doesn't win the contract?
Most teaming agreements include a termination provision tied to award — if the prime doesn't win, the agreement expires at a defined date after the solicitation outcome is known. Neither party has ongoing obligations. Any shared proprietary information remains subject to the confidentiality provisions for their stated duration.
Can a small business be on multiple teams competing for the same contract?
Yes, unless the teaming agreements include exclusivity provisions preventing it. Exclusivity is common when the prime has shared sensitive technical approaches with the sub. If the sub is teaming non-exclusively, the prime needs to evaluate whether shared technical approach content creates a conflict.
How does a teaming agreement support a prime's SBA subcontracting plan?
A teaming agreement doesn't by itself satisfy subcontracting plan requirements — but it documents the pre-award intent that supports the plan. When the prime submits a subcontracting plan listing Rutagon for a specific NAICS code and dollar value, the teaming agreement shows the government that the allocation is genuine and the relationship is formalized.
What is the difference between a teaming agreement and a subcontract?
A teaming agreement is a pre-award document that defines the relationship during proposal preparation and commits the parties to a specific arrangement if the team wins. A subcontract is the post-award contract that actually governs the sub's delivery of work. The subcontract typically incorporates the work scope from the teaming agreement and adds detailed terms: payment, deliverables, compliance flow-down, intellectual property, and dispute resolution.