The invitation arrives late, and that is the first fact about it
A teaming invitation almost never shows up at the start of a capture. It shows up after the prime has read the evaluation criteria, mapped them against the people already on its bench, and found a hole. By then the solicitation is public, the close date is fixed, and somebody needs a resume and a rate sheet by Friday. The email reads like recognition. It is closer to a purchase order for four things you own: your company name on another firm's proposal, the names of specific engineers, technical writing that came out of your head, and a block of calendar you would otherwise have spent on your own pipeline. Deciding whether to hand those over is a pricing exercise, not a relationship exercise.
The default answer inside most technical firms is yes, and the reason is understandable. A named position on a large bid looks like the thing you have been working toward. Sometimes it is exactly that. Often it is a coverage bid the prime is running because a customer expects to see its name, and your contribution is a resume that makes one paragraph read better. The cost of being wrong is not catastrophic in any single instance. It compounds. Three of these in a year is a month of engineering time spent on other companies' lottery tickets, and it is a month you did not spend building the thing that would have made the next offer come with a scope attached.
So the useful question is not whether the bid could win. Almost any bid could win. The question is whether your name on it is the cheapest way for you to find out, and whether the version of yes you are being offered is one you can actually perform.
What the offer is actually asking you to give
Your company name, disclosed to the customer. FAR Subpart 9.6 covers contractor team arrangements, and it is short. FAR 9.601 defines the 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. FAR 9.603 states the policy: the government recognizes the integrity and validity of these arrangements provided they are identified and the company relationships are fully disclosed in an offer, or before the arrangement becomes effective if it forms later. Disclosure is the point. Once you are in that offer, the customer sees you as part of that team, which is worth something when the team wins and is a plain fact when the team loses badly.
Your people's names, as representations the government relies on. This is the asset firms hand over most casually and can least afford to. GAO's standard for an impermissible personnel substitution has three parts: that the offeror knowingly or negligently represented it would rely on specific personnel it had no reasonable basis to expect to furnish, that the agency relied on the representation, and that the reliance had a material effect on the evaluation. In ASRC Federal Data Solutions, B-421008 (December 2, 2022), GAO sustained a protest where a proposed key person had withdrawn her acceptance of a contingent employment offer. When a proposed key person becomes unavailable before award, the offeror is expected to tell the agency. If you cannot say plainly that a named engineer will be available at the stated percentage on a schedule you do not control, the honest options are to name someone else or to decline.
Technical content that is yours. Proposal writing is engineering time with the outputs pointed at a document instead of a system. FAR 31.205-18 makes bid and proposal costs allowable as indirect expenses to the extent they are allocable and reasonable, which matters at year end and does nothing for the week you spend writing. Cash out is cash out, and the sections a prime asks a specialist sub to draft are usually the hardest ones.
A window on your calendar. The last three weeks before a close are the weeks a prime needs most, and they are the same weeks you would need for your own submissions. That collision is the real cost on most teaming offers, and it is the one that never appears in the teaming agreement.
Weighing the signals, in the order they matter
The block below is how we weight the signals that push a teaming offer toward no. It is an editorial ranking of decision drivers, not a measured statistic, and the numbers exist to show relative weight rather than to be quoted as data. What it captures is that the structural problems near the top cannot be fixed by good intentions, while the ones toward the bottom are negotiable if the rest of the offer is strong.
How heavily each signal pushes a teaming offer toward no
Editorial weighting of decision drivers. Illustrative of priority, not a measured statistic.
Four declines that are structural, not judgement
Most teaming decisions are close calls that turn on price and timing. Four are not. If one of these is true, the answer is no until the structure changes, and a prime with an experienced contracts group will already know it.
You would perform the primary and vital work on a small-business set-aside. Under 13 CFR 121.103(h)(4), SBA may find affiliation where a subcontractor that is not a similarly situated entity performs the primary and vital requirements of a contract, or where the prime is unusually reliant on that subcontractor. SBA case law applies a four-factor test for unusual reliance: the proposed subcontractor is the incumbent and is ineligible to compete; the prime plans to hire the large majority of its workforce from the subcontractor; the prime's proposed management previously served with the subcontractor on the incumbent contract; and the prime lacks relevant experience and must rely on its more experienced subcontractor to win. A finding of an ostensible subcontractor makes the offeror ineligible as a small business concern for that award. Running alongside it, 13 CFR 125.6 and FAR 52.219-14 cap what a small prime may pass outside the team: for services other than construction, the prime may not pay more than 50 percent of the amount the government pays it to firms that are not similarly situated. When a prime asks a specialist sub to carry the technical core of a set-aside, the arithmetic decides the question before anyone's judgement does.
A conflict that FAR Subpart 9.5 will make somebody's problem. Contracting officers are directed to identify and evaluate potential organizational conflicts of interest as early in the acquisition process as possible and to avoid, neutralize, or mitigate significant ones before award. For firms doing assessment, evaluation, or advisory work, joining a development team can foreclose the independent role you would rather hold on the same program. That trade may be worth making. It should be made deliberately, with the other work named, and not discovered in month two.
Exclusivity wider than the pursuit in front of you. An exclusivity clause scoped to a named solicitation with an end date is ordinary. One scoped to a program, an agency, or a technology area for an open period is a different transaction, and it should be priced like one. If the prime will not narrow it, the offer is asking you to close doors you cannot see for a return nobody has quantified.
A named person you cannot furnish. Covered above, and worth repeating because it is the one that damages a relationship permanently rather than temporarily. Everything else on this list can be renegotiated next quarter. A substitution request in the first month of performance is remembered for years.
The research programs have their own arithmetic. Under the SBA SBIR and STTR Policy Directive, at least two-thirds of the research or analytical effort on an SBIR Phase I must be performed by the awardee, and at least one-half on Phase II. On STTR, not less than 40 percent of the work must be performed by the small business and not less than 30 percent by the partnering research institution. A firm invited to carry the technical heart of someone else's research proposal is being asked for a share the directive does not allow, and deviations require written approval from the funding agreement officer.
The signals in the offer, and what each one costs
Below are the six lines that show up most often in a first teaming email, what each one usually means once you look behind it, and whether it warrants a decline, a negotiation, or a yes. The distinction that matters is between a term that can be fixed with a sentence and a term that reveals the prime has not done the work.
| What the offer says | What it usually means | Decline, negotiate, or accept |
|---|---|---|
| "We can give you about 25 percent" | A percentage with no tasks, CLINs, or labor categories behind it. Work-share language that leaves the subcontract to later negotiation has failed in court | Negotiate. Ask for the intended statement of work and rates as an exhibit and a definitization deadline. Decline if both are refused |
| "Just send resumes by Friday" | Your engineers become representations the agency will rely on, with no discussion of availability at an award date nobody can predict | Negotiate. Name only people you will furnish, state the percentage, and put the substitution path in writing. Decline if you cannot commit |
| "You'd own the core technical work" on a set-aside | Possible ostensible subcontractor exposure under 13 CFR 121.103(h)(4), plus the 50 percent services limit at 13 CFR 125.6 | Decline as structured. Restructure the split, or ask whether a similarly situated arrangement is available |
| "Exclusive with us in this space" | An option on your firm across future pursuits, granted for free, at the moment you have the least information | Negotiate to a named solicitation with an end date. Decline if the clause stays open-ended |
| "We'll paper the subcontract after award" | The scope you agreed to is the scope you renegotiate from zero eight to eighteen months later, once every card you held has been played | Negotiate the exhibit and the deadline now. Decline if the prime treats both as unusual requests |
| "The customer knows us well" | Sometimes true and decisive. Sometimes it means one conference conversation in the spring | Accept if they can name the office, the requirement's history, and what changed since the last award. Otherwise treat it as an unpriced bid |
What you hold if the deal goes wrong
Read the remedies before you read the upside, because they are thinner than most technical firms expect. A subcontractor has no privity of contract with the government. It generally cannot sue the government directly for a loss the government caused, and it usually cannot protest. Under GAO's bid protest regulations, an interested party is an actual or prospective bidder or offeror whose direct economic interest would be affected by the award or the failure to award, and proposed subcontractors generally do not qualify. If the prime is passed over and does not want to protest, your view of the evaluation does not matter.
Claims work the same way. A subcontractor's claim against the government moves as a pass-through, sponsored by the prime, and the Severin doctrine, from Severin v. United States, 99 Ct. Cl. 435 (1943), bars a pass-through where the prime bears no liability to the sub for the costs in dispute. Whether that door is open turns on how your subcontract allocates responsibility, which is a drafting question you get to influence exactly once.
Cash flow runs behind the prime by construction. FAR 52.232-40 requires a contractor, within 15 days after receiving accelerated payments from the government, to make accelerated payments to its small business subcontractors to the maximum extent practicable, without further consideration or fees, and to flow the substance of that clause down. That is a real protection and a narrow one: it moves money faster only when the government has already moved money faster.
The timeline is also longer than the pitch implies. GAO's bid protest report for fiscal year 2025, published in December 2025, recorded 1,688 protests filed, a 6 percent decline from the prior year, with an effectiveness rate of 52 percent and a sustain rate of 14 percent. Effectiveness counts any relief, including voluntary corrective action. Award is frequently not the end of the clock, and a firm that has budgeted for a decision in nine months should look at what happens to its cash if the answer arrives in fifteen.
The seventy-two-hour version of this decision
Speed is itself a form of respect here. A prime under deadline pressure would rather have a clear no on Wednesday than a hopeful maybe that becomes a no the week of the pricing review. The sequence below is how the decision gets made without stalling anyone.
Answering a teaming invitation in three days
What to have answered before you answer
None of these questions is adversarial, and a capture manager who has run teams before will have most of the answers already. The ones that go unanswered are the finding.
- Which sections do we own, in the solicitation's own numbering, and who reviews them before submission.
- What scope do we hold if the team wins, expressed as tasks or CLINs rather than a percentage, and is it attached to the teaming agreement as an exhibit.
- Is there a definitization deadline, meaning a stated number of days after award to execute a subcontract, with the exhibit as the default terms if it slips.
- Which of our people are named, at what percentage of time, from what start date, and what the written substitution path is if award moves two quarters.
- Is this a set-aside, and if so, how the prime is meeting the limitation on subcontracting with our scope included.
- What flow-downs will apply. On defense work involving covered defense information, DFARS 252.204-7012 flows down without alteration and carries the NIST SP 800-171 control set plus reporting of a cyber incident within 72 hours of discovery.
- Who else is on the team, and whether any of them competes with us on the scope we are being offered.
- How wide is the exclusivity, and when does it end.
- What happens to our technical material if the team does not bid, or bids and loses, and how long the confidentiality obligation runs.
- Who signs, and how fast their contracts group turns a redline.
Enforceability is a drafting question, and it varies
Firms often assume a signed teaming agreement locks the work share. It frequently does not. In Cyberlock Consulting, Inc. v. Information Experts, Inc., the Eastern District of Virginia held in 2013 that a teaming agreement promising the prospective subcontractor 49 percent of the work on an Office of Personnel Management award was an unenforceable agreement to agree, because the subcontract terms were left to future negotiation. The Fourth Circuit affirmed in January 2014. The reasoning rests on Virginia contract law, under which an agreement to negotiate in good faith toward stated objectives within an agreed framework is treated as an agreement to agree.
Two honest qualifications. Outcomes turn on the governing law named in the agreement and on how specifically the terms are written, so this is not a universal rule that teaming agreements are unenforceable. And the regulation offers no help either way: FAR 9.604 preserves the government's own rights, including its right to hold the prime fully responsible for performance regardless of any team arrangement, and nothing in Subpart 9.6 makes the contracting officer a referee between two companies. The practical response is not to give up on the document. It is to attach the scope and the rates as an exhibit so the later subcontract is a fill-in rather than a fresh negotiation, and to set a clock on execution.
How to decline and still get the next call
Answer fast, in writing, with the reason. "We are not bidding this one because our two data engineers are committed through October" is a sentence a capture manager can plan around and will remember favorably. Silence, or three weeks of maybe, is what gets a firm removed from the list.
Decline the offer, not the relationship. Name the version of this you would say yes to. "Send us the next one at least eight weeks out and we will hold the window" is a real commitment that costs nothing today.
Give something small on the way out. An introduction to a firm that fits the gap better, a paragraph on how you would approach the technical problem, a pointer to the standard or dataset the customer actually uses. It takes twenty minutes and it changes how the no is filed.
Do not explain by criticizing the bid. Telling a prime its capture is thin is rarely persuasive and never welcome. "This one is not a fit for our calendar" carries the same information without the cost.
Say what would change the answer. Named scope, a definitization deadline, a narrower exclusivity clause, a later close. Primes reuse teammates who make their constraints legible.
The three yeses that are smaller than a subcontract
A flat no is not the only alternative to a full teaming position, and the middle options are underused. You can be named as a consultant on a defined, small scope rather than as a major subcontractor, which limits your exposure and still puts real capability in the proposal. You can support the pursuit without being named at all, reviewing the technical volume against the evaluation criteria as paid work. Or you can sign the confidentiality agreement, take the technical conversation, and defer the teaming decision to the next pursuit, which costs an hour and keeps a real relationship warm without putting your name in a document you have doubts about.
One caution worth stating plainly, because it is in flux. Cyber posture has been a gate on defense teams since the CMMC acquisition rule took effect on November 10, 2025, opening a phase built around Level 1 and self-assessed Level 2. On July 13, 2026, the Department of War suspended the phase that would have required third-party assessment starting November 10, 2026 and stood up a reform task force with a public request for information. Phase one self-assessment requirements and existing DFARS obligations were not suspended. If a prime tells you the certification question is settled in either direction right now, ask them to point at the memo.
Bottom line
A teaming offer is a request for four assets at once, and the firms that get this right price all four before answering. Read the solicitation rather than the summary. Establish whether the prime has a customer or a hope. Run the structural screens, because ostensible subcontractor exposure, a conflict under FAR Subpart 9.5, open-ended exclusivity, and a name you cannot furnish are not close calls. Look at the remedies, which are thin, and at the timeline, which is long. Then answer in three days either way. A fast, reasoned no protects the relationship far better than a slow yes that turns into a substitution request, and the primes worth teaming with already know that.
Frequently asked questions
A fast, specific no rarely does. What damages a relationship is a slow maybe that collapses near the pricing review, or a yes followed by a key-personnel substitution request in the first month of performance. Give the reason, name the version you would accept, and offer something small on the way out.
Generally no. GAO's regulations define an interested party as an actual or prospective bidder or offeror whose direct economic interest would be affected by the award or the failure to award, and proposed subcontractors usually do not meet that test. The decision to protest belongs to the prime.
It depends on the governing law and the drafting. In Cyberlock Consulting v. Information Experts, a 49 percent work share was held unenforceable under Virginia law as an agreement to agree because the subcontract terms were left for future negotiation, and the Fourth Circuit affirmed in 2014. The practical fix is to attach the intended statement of work and rates as an exhibit and to set a deadline for executing the subcontract after award.
On a set-aside, when the subcontractor is not a similarly situated entity and performs the primary and vital requirements, or when the prime is unusually reliant on it. That is the ostensible subcontractor rule at 13 CFR 121.103(h)(4), and a finding makes the offeror ineligible for that award. The separate limitation at 13 CFR 125.6 caps payments to firms that are not similarly situated at 50 percent of the amount the government pays the prime for services other than construction.
Under the SBA SBIR and STTR Policy Directive, the awardee must perform at least two-thirds of the research or analytical effort on an SBIR Phase I and at least one-half on Phase II. On STTR, at least 40 percent goes to the small business and at least 30 percent to the partnering research institution. Deviations require written approval from the funding agreement officer.
Three days is a workable standard: read the solicitation and price the ask on day one, send written questions on day two, and answer on day three. Primes plan around answers, not around enthusiasm, and responsiveness is one of the few things a teammate can demonstrate before award.