The one sentence that decides the deal
In most draft teaming agreements the exclusivity clause is a single sentence, it sits near the bottom, and it is the only term in the document that changes what a competition is worth to the smaller party. It usually reads something like: Subcontractor agrees to team exclusively with Prime with respect to this procurement and shall not participate on, or provide support to, any competing offeror. No consideration is attached. No workshare number appears anywhere near it. It costs the prime nothing to type and it is often the single most expensive thing the sub will give away that quarter.
The clause is not unreasonable. Primes have real reasons to want it, and we have signed it many times. The problem is that exclusivity is almost always negotiated as a yes-or-no question when it is really a scoping question. Exclusive to what? For how long? Across which technical scope? Bounded three ways, exclusivity is cheap for a sub to grant and still gives a prime everything it actually needs. Unbounded, it is a free option written by the party who holds it.
This piece walks the whole negotiation: what the FAR says and does not say, the arithmetic that drives a subcontractor's resistance, the give-get list that makes exclusivity fair, the enforceability trap that has cost small firms real money in federal court, and the small-business rules that quietly cap how much any exclusive partner can be handed in the first place.
What FAR Subpart 9.6 actually covers
FAR Subpart 9.6, Contractor Team Arrangements, is short and it is worth reading in full before any teaming negotiation. FAR 9.601 defines two forms of team arrangement: two or more companies forming a partnership or joint venture to act as a potential prime, and a potential prime agreeing with one or more other companies to have them act as its subcontractors under a specified government contract or acquisition program. Nearly every AI/ML teaming conversation is the second form.
FAR 9.603 states the government policy: agencies will recognize the integrity and validity of contractor team arrangements, provided the arrangements are fully disclosed in the offer, or, for arrangements entered into after submission of an offer, disclosed before the arrangement becomes effective. FAR 9.604 sets the limits. The arrangement must not prejudice the interests of the government, must not violate the antitrust statutes, must not obscure responsibility for contract performance, and must not be used to circumvent limitations that apply to the acquisition.
Now read what is absent. FAR 9.6 says nothing about exclusivity. It sets no workshare floor. It does not require a prime to issue a subcontract to a teammate it named in the proposal. It creates no privity between the sub and the government, which means the sub has no contractual relationship with the contracting officer and no direct remedy from the agency if the prime walks away after award. FAR 9.6 governs how the government treats the team. Everything that governs how the two companies treat each other is ordinary state contract law, and that distinction is where most of the pain lives.
Where teaming negotiations stall, by relative frequency of the sticking point
Editorial weighting from public sources and practitioner reading, illustrative rather than a measured statistic.
Why a prime asks for exclusivity
Solution protection. The technical approach that goes into a volume is co-authored. A capture manager who spends six weeks working an architecture with a specialist sub, then watches the same architecture show up as a competitor's discriminator, has funded the other team's win. This is the honest reason and it deserves respect.
Evaluation credibility. Key personnel commitments are checked. When a solicitation asks for letters of commitment and a named senior engineer appears on two proposals for the same requirement, that is a finding waiting to happen, and it lands on the prime. Primes ask for exclusivity partly so the commitment letter they submit is true.
Bid economics. Bid and proposal money is real money, and a mid-size prime may spend six figures pursuing a single recompete. Exclusivity is the prime's attempt to convert that spend into an asset it controls rather than an education it gave away.
Capacity math. If a specialist firm has three senior ML engineers and lands on the winning team of a competitor, the prime's staffing plan becomes fiction on award day. Primes have been burned by this, and they price it into how hard they push.
Sometimes, scarcity. On a bid where one small firm holds the only credible answer to a specific technical requirement, the prime is not protecting a solution so much as removing an option from three competitors. This is the version worth the most money to the prime and it should be the version that costs the most.
Why a sub resists: the portfolio math
The resistance is not stubbornness. It is arithmetic that any capture manager would recognize instantly if the roles were reversed.
Take a services recompete with five credible offerors. Absent inside information, a given prime's honest prior is somewhere near 20 percent, and even a well-positioned challenger rarely gets above 35. A specialist sub that can appear on three of those five teams has a strong chance of sitting on the winning team when the award comes out. Sign exclusivity with one of them and that chance collapses to the single prime's win probability. The sub has just converted a diversified position into one ticket, and it has done so before anyone wrote down what the ticket pays.
The cost is larger than one round. The sub contributes technical volume sections, resumes, a past-performance narrative, sometimes a live demonstration, and the calendar of the exact engineers it would otherwise be billing. Then it tells three other capture managers no, which is a relationship cost that outlives the competition. If the bid loses, the sub has spent the round and has nothing to show a board or a bank.
Then there is the option problem. A teaming agreement that contains exclusivity, no workshare floor, and a promise that the parties will negotiate a subcontract in good faith after award gives the prime a call option at zero strike price. If the prime wins and the market for that scope has softened, it can negotiate the subcontract down or issue it to someone else, and the sub's remedy is a good-faith clause that courts have repeatedly refused to enforce.
The three middles that actually get signed
Exclusive and non-exclusive are the endpoints, and most deals die there because both sides argue the endpoints. The productive move is to split exclusivity along three independent axes and grant it generously on each one, bounded.
Topic-scoped. Exclusivity attaches to one solicitation number and its amendments. Not the program. Not the customer. Not follow-on work. Not "related procurements." A draft that says the sub will not support any competing offeror "on this program or any successor effort" is asking a specialist firm to leave an entire mission area for years. Name the number, and if the prime wants the follow-on too, that is a second conversation with a second signature at the time it exists.
Time-boxed. Exclusivity begins at signature and ends automatically at the earliest of: award to another offeror, the prime's decision not to submit, a stated number of days after proposal submission with no subcontract negotiation opened, or a hard outside date. Without a sunset, a sub that teamed on a bid that slipped two fiscal quarters is still locked out of the recompete it slipped into.
Scope-scoped. Exclusivity covers the defined technical scope the sub is carrying, and nothing else. A firm that does AI/ML modeling, data engineering, and cloud migration can be exclusive on the AI/ML content for one bid while remaining free to support a different offeror on an unrelated scope in the same competition, if and only if the two do not touch. This one takes more drafting care than the other two, and it is often the term that lets a deal close when a sub already has a relationship on the other side of the same competition.
| Structure | What the prime gets | What it costs the sub |
|---|---|---|
| Unbounded exclusivity | Total lockout across program and follow-ons; no competitor can reach the specialist | Whole mission area, indefinite duration, often for no stated workshare |
| Topic-scoped | Lockout for the one bid the prime is actually funding | One round, one competition; other pursuits stay open |
| Time-boxed | Protection through submission and source selection | Bounded calendar; the clause dies on no-bid or non-award |
| Scope-scoped | Protection of the co-authored technical approach | Only the lane in play; adjacent capability stays sellable |
| Exclusive with workshare floor | Everything above, plus a teammate who staffs the bid seriously | Priced, not donated; the risk now runs both directions |
| Non-exclusive | Access to the capability and a named teammate in the volume | Nothing, and the prime knows it |
What exclusivity should buy the smaller party
Exclusivity is consideration flowing one direction. Something has to flow back, and the items below are ordinary, standard, and routinely accepted by primes who are serious about the bid. A prime that refuses all of them is telling you the teammate slot is decorative.
- A workshare floor. A stated minimum percentage of contract value or a dollar floor for the defined scope, with a written method for recalculating if the government changes the scope.
- A real statement of work. An Exhibit A that describes the tasks, deliverables, and periods, not the phrase "AI/ML support as required."
- A subcontract deadline. Execute within a stated number of days after prime award, failing which the exclusivity terminates and the sub is free to pursue the work independently.
- An attached price basis. Labor categories with rates or a rate ceiling with defined escalation, agreed at signature rather than left to a future negotiation.
- Background IP carve-out. Pre-existing tools, models, and code stay with the party that built them; only deliverables created under the subcontract are subject to the contract data clauses.
- Mutual non-solicitation. Named key personnel on both sides protected for the pursuit plus a stated tail, so exclusivity does not become a recruiting window.
Two additional items are worth asking for and are more often refused: a cap on unreimbursed proposal hours, and a most-favored-teammate clause promising the sub will not be given terms worse than another sub in the same tier. Ask anyway. What a prime refuses tells you how the subcontract negotiation will go.
The enforceability trap
The most expensive mistake in this area is assuming a signed teaming agreement guarantees the work. In Cyberlock Consulting, Inc. v. Information Experts, Inc., the Eastern District of Virginia held that a teaming agreement promising the subcontractor 49 percent of the work was an unenforceable agreement to agree, because the actual subcontract terms were left to future negotiation. The Fourth Circuit affirmed. Virginia is where a large share of federal teaming disputes are litigated, and the doctrine there is unforgiving: courts enforce terms that are definite and refuse to write the ones the parties left blank.
The practical lesson is a drafting lesson. Phrases that put a small firm at risk include "the parties shall negotiate in good faith a subcontract," "workshare is anticipated to be approximately," and "subject to mutual agreement on price and terms." Each one converts a promise into an intention. What survives is the opposite: an attached statement of work, an attached rate schedule, a numeric floor, a deadline, and a stated consequence if the deadline passes. A choice-of-law clause is not boilerplate either. Pick the jurisdiction deliberately and know what its courts do with these documents before signing.
A related point on remedies. Because there is no privity with the government, a sub dropped after award cannot protest its way back onto the team, and the Court of Federal Claims is not the forum. The remedy, if any, is a breach action in state or federal district court on the four corners of the teaming agreement. That is exactly why the four corners have to contain numbers.
Where exclusivity collides with small-business rules
Limitations on subcontracting. On a small-business set-aside, FAR 52.219-14 and 13 CFR 125.6 cap what the prime may pass to firms that are not similarly situated: 50 percent of the amount paid by the government for services, 50 percent for supplies excluding the cost of materials, 85 percent for general construction, and 75 percent for specialty trade construction. A sub demanding 60 percent of a services set-aside is asking a prime to violate a contract clause. Knowing the cap before the meeting saves a week.
The ostensible subcontractor rule. SBA's affiliation rules at 13 CFR 121.103(h) treat a prime and a sub as joint venturers, and therefore as affiliates for size, when the sub performs the primary and vital contract requirements or the prime is unusually reliant on the sub. Exclusivity plus a dominant workshare plus the sub supplying the program manager and the key technical staff is close to a textbook fact pattern. On a set-aside, the fix is deliberate structure: the prime holds the primary and vital requirements and the management, and the specialist holds a defined technical lane.
SBIR and STTR performance floors. Under the SBA SBIR/STTR Policy Directive, the small business must perform a minimum share of the research work: at least two thirds in Phase I and at least one half in Phase II for SBIR. STTR splits the work differently, with at least 40 percent performed by the small business and at least 30 percent by the partnering research institution. Eligibility itself sits at 13 CFR 121.702. Any exclusive partner on an SBIR bid is negotiating inside a ceiling set by regulation rather than by the parties, and saying so on the first call shortens the negotiation considerably.
Past performance contribution. FAR 15.305(a)(2)(ii) allows an agency to consider the past performance of subcontractors that will perform major or critical aspects of the requirement. When a sub's record is doing evaluation work inside the prime's volume, that is contribution, and it is a fair thing to price into workshare.
The conflict question that comes before the exclusivity question
FAR Subpart 9.5 governs organizational conflicts of interest, and it can decide the teaming question before anyone gets to the exclusivity clause. If a firm holds an advisory or assistance role touching the same program, unequal access to information or impaired objectivity can put the whole team at risk of exclusion. Contracting officers are required to identify and resolve these conflicts as early as possible. Ask the OCI question in the first conversation, in writing, both directions.
Two smaller mechanics matter as well. FAR 9.104-4 addresses the responsibility of prospective subcontractors and reminds everyone that the prime remains responsible for its team. And a growing number of solicitations require offerors to name subcontractors and describe workshare in the proposal itself, which removes the option of leaving the arrangement vague until after award. When the solicitation forces the disclosure, the exclusivity negotiation has to finish before the submission, not after.
Terms to have in writing before signing an exclusivity clause
- The solicitation number the exclusivity attaches to, and only that number
- A start date and an automatic termination event, both stated
- The technical scope covered, written narrowly enough to read as a boundary
- A workshare floor expressed as a percentage or a dollar minimum
- An Exhibit A statement of work and an Exhibit B rate schedule
- A deadline for executing the subcontract after prime award, with a consequence
- Background IP retained, deliverable rights defined by the flowed contract clauses
- Mutual non-solicitation, mutual confidentiality, and a chosen governing law
How we handle it
Our position is public because it saves everyone time. We sign topic-scoped exclusivity, and we sign it the same day. Exclusivity bounded to one solicitation number and its amendments, sunset at award or at a no-bid decision, tied to a defined technical scope with a workshare floor and a rate table attached. Our engineers work the bid seriously under those terms, including the technical volume sections, the architecture, and the evidence that makes a claim credible to an evaluator.
What we do not sign is program-wide or customer-wide exclusivity, indefinite duration, or an exclusivity clause with no scope and no floor attached. A prime that needs those terms usually has not decided whether it is bidding, and a small firm should not be the one carrying that uncertainty.
What we bring to a team: production AI, ML, data, and cloud engineering across defense, health, energy, transportation, and public-sector data, delivered by a bench of named engineers, licensed professional engineers, and domain specialists, led by a former professor in technology who ranks in the top 0.1 percent of a global machine-learning competition community and holds seven cloud certifications, with twenty years building production systems for federal agencies across five consulting firms, three of them federal. SAM.gov active, CAGE 1AYQ0, JCP and DD-2345 certified. Prime or subcontract, federal, state, or commercial.
Bottom line
Exclusivity is not the enemy. Unscoped exclusivity is. A prime that bounds the clause to one solicitation, sunsets it at award, ties it to a defined technical scope, and attaches a workshare floor gets everything it actually wanted: a protected solution, a truthful key-personnel commitment, and a teammate whose senior people are on the bid instead of hedging across three of them. A sub that gets those four things has been paid for what it gave up. Both sides can sign that document in a day, which matters, because the clock on a federal proposal is never generous.
Frequently asked questions
Yes. FAR 9.603 directs agencies to recognize the integrity and validity of contractor team arrangements when they are properly disclosed. FAR 9.604 sets the limits: the arrangement cannot violate the antitrust statutes, obscure responsibility for performance, or circumvent limitations that apply to the acquisition. Exclusivity between two companies is ordinarily a private commercial term.
No. Federal courts have held teaming agreements unenforceable where the subcontract terms were left to future negotiation, including the Cyberlock decision in the Eastern District of Virginia, which the Fourth Circuit affirmed. The agreement is only as strong as the definite terms inside it: attached scope, attached rates, a numeric workshare floor, a deadline, and a stated consequence.
FAR 52.219-14 and 13 CFR 125.6 limit the amount a small-business prime may pass to firms that are not similarly situated: 50 percent for services, 50 percent for supplies excluding materials, 85 percent for general construction, and 75 percent for specialty trade. On SBIR work the small business must also perform at least two thirds of the Phase I effort and at least half of Phase II.
SBA's affiliation rules at 13 CFR 121.103(h) treat the prime and sub as joint venturers, and therefore affiliates for size purposes, when the sub performs the primary and vital contract requirements or the prime is unusually reliant on the sub. An exclusive relationship combined with a dominant workshare and sub-supplied key personnel is the pattern protesters look for on set-asides.
A workshare floor stated as a number, an attached statement of work and rate schedule, a deadline for executing the subcontract after award with a consequence if it passes, a carve-out protecting pre-existing IP, mutual non-solicitation of named personnel, and an automatic sunset at award or no-bid. Those six terms turn a one-way clause into a trade.