Teaming is one of the most consequential decisions in federal BD, and it is almost always made too quickly. A firm encounters an opportunity that looks attractive but exceeds their current capabilities. Someone suggests reaching out to a company they worked with before. A teaming agreement gets signed. The proposal goes in.
Sometimes that works. More often, the team was assembled for the wrong reasons, the partner brought the wrong things, and the bid either lost or, if it won, created a performance arrangement that was difficult to execute. The teaming decision deserves more deliberation than it typically gets.
This article is a framework for making that decision systematically. When should you prime alone? When does teaming make the bid stronger? How do you identify what you actually need from a partner? And how do you structure the arrangement so that it enhances your competitive position rather than complicating it?
The case for priming alone
The default position for an SDVOSB firm should be to prime alone whenever it is reasonably possible to do so. That is not a matter of pride. It is a matter of contract mechanics and long-term competitive development.
When you prime a contract, you build past performance. The CPARS rating goes to your firm. The dollar value accumulates on your record. The reference is yours to cultivate: the contracting officer or program manager who can speak to your performance. These are compounding assets. Every prime contract makes the next prime contract more accessible.
When you subcontract, you typically receive none of these assets in the same form. You may receive a subcontractor CPARS rating, but it is attached to the prime contractor's record and does not flow to yours with the same weight. The reference belongs to the prime. The dollar value on your record is your subcontract value, which may be a fraction of the prime contract value. The relationship with the contracting officer belongs to whoever is sitting at the table for contract administration.
This is why firms that subcontract heavily can have years of federal work experience and still struggle to win prime contracts. They have been building someone else's past performance record while their own remains thin.
So the first question before any teaming discussion is not "who should we team with?" It is: "Can we realistically prime this alone?" If the honest answer is yes, meaning you have the technical capability, the past performance, the staffing capacity, and the certifications, then you should. The teaming conversation can still happen for strategic reasons, but it should not happen by default.
When teaming actually makes sense
There are four legitimate reasons to bring in a teaming partner. If none of them applies, the teaming conversation should stop.
1. You have a specific capability gap the solicitation will score
The clearest case for teaming is when the solicitation requires a technical capability you cannot demonstrate, one that will cost you points in the evaluation. Not a general capability gap. Not something you could theoretically do. A specific, scored requirement in Section M that your past performance does not address.
The discipline here is to identify the gap precisely before you start looking for a partner. What is the specific requirement? What past performance or technical expertise would satisfy it? What kind of firm has that? A partner selected to fill a precise gap is easy to evaluate and easy to contractually scope. A partner selected because they seem relevant is neither.
2. You need to demonstrate scale or dollar value you haven't primed before
If this contract is significantly larger than anything you have managed as a prime, a teaming partner who has managed comparable-scale work can partially offset the past performance gap. The key word is "partially." A teaming partner's past performance helps, but it does not replace yours in the evaluation. The agency is still primarily evaluating your capacity as the prime.
Be realistic about what this accomplishes. If you have primed contracts under $500K and this is a $4M requirement, bringing in a partner who has primed $4M contracts does not make you equivalent to an incumbent who has primed at $4M. It signals that you have relationships and judgment, but the gap is still visible. Teaming helps at the margins; it does not close a large past performance gap entirely.
3. You need a specific certification or clearance
Some solicitations require facility clearances, specific ISO certifications, or other credentialing that takes months or years to obtain and cannot be acquired for a single bid. If the requirement is real and non-waivable, a partner who brings that credential is necessary rather than optional.
Clearances are the most common case. A facility clearance at the Secret or Top Secret level cannot be obtained quickly. If a DoD requirement mandates it and you do not have it, you either team with a firm that does or you do not bid.
4. The opportunity is large enough that capacity genuinely requires it
On very large contracts, a single small firm may legitimately need more staff than they can realistically hire before performance begins. In these cases teaming is a delivery requirement, not just a competitive strategy. The caution here is that very large contracts often have large business prime contractors as competitors, and a small business prime with teaming partners may still be at a disadvantage on price or past performance compared to the incumbents.
The limitation on subcontracting rules
For SDVOSB set-aside contracts, the FAR requires that the prime contractor perform a specific minimum percentage of the work. This is the "limitation on subcontracting" rule, and it is one of the most important factors in any teaming decision.
For services contracts, the SDVOSB prime must perform at least 50% of the cost of the work, excluding materials. For supply contracts, the prime must supply the product from its own inventory or manufacture at least 50% of the total value. Construction and specialty construction contracts have their own thresholds.
This has a direct implication for teaming: your partner cannot perform more than 50% of the work (on a services contract). If the arrangement you are structuring effectively makes the partner the primary performer and you the pass-through, you are at risk of a protest and potentially a False Claims Act exposure if you certify eligibility on a set-aside you do not genuinely qualify for.
The practical test before signing any teaming agreement is to map the work scope explicitly. Who performs what? What is the estimated dollar value of each party's work? Does the SDVOSB prime perform at least 50%? If you cannot answer that question concretely before the proposal is submitted, you are not ready to team on this bid.
Mentor-protégé arrangements
The SBA's All Small Mentor-Protégé Program (ASMPP) is a specific teaming structure designed for small businesses that creates different rules from standard teaming. Under the ASMPP, an approved mentor-protégé joint venture can bid as a small business even if the mentor is large, and the joint venture's past performance includes the mentor's past performance.
For SDVOSB firms, this is one of the most powerful mechanisms available for bridging a past performance or capability gap. A properly structured ASMPP joint venture allows a smaller SDVOSB to bid on contracts that would otherwise require past performance they do not yet have, while maintaining set-aside eligibility.
The tradeoff is setup time and relationship commitment. ASMPP agreements require SBA approval, which takes several months. The mentor-protégé relationship is designed to be developmental. The mentor is supposed to be actively helping the protégé build capabilities over time, not just participating on individual bids. This is not the right tool for a quick teaming decision on a near-term bid. It is the right tool for a firm that has identified a specific large contract they want to compete for in 12 to 18 months and needs a structured way to build toward it.
How to evaluate a potential teaming partner
Once you have decided that teaming is appropriate and defined exactly what capability gap you need to fill, the evaluation of a potential partner should be structured around five questions.
Do they fill the specific gap? Not a related gap. Not a general capability in the right area. The specific requirement you identified. If the solicitation requires demonstrated experience supporting DoD supply chain management systems and your prospective partner has IT support experience for DoD but not supply chain specifically, the gap may not be filled. Be precise.
Do they have a conflict of interest on this opportunity? If the potential partner is already teaming with a competitor on this bid, or has an existing relationship with the incumbent, or has recent work for the agency that gives them access to information you do not have, those are complications to understand before signing an agreement. A teaming partner who is also talking to your main competitor is not necessarily disqualified, but the arrangement needs to be explicitly addressed.
Can they deliver the scope you need them to deliver? Past performance tells you what they have done. A reference check tells you how well they did it. Do not take their capability representation at face value. Call the references. Ask specifically about the type of work you need them to perform. A firm that has delivered similar work in a different context may or may not be able to deliver it under your prime contract structure and schedule.
Are they financially stable? A subcontractor who cannot make payroll will crater your performance. On a federal contract, you are responsible for the work regardless of whether your subcontractor delivers it. Ask for financial references if the subcontract scope is significant. At a minimum, run a SAM.gov check to confirm they have active registration and no exclusions.
Is the relationship manageable? This is the softest question but often the most predictive. Have you worked with this firm or these specific people before? If not, is there a basis for trust: shared colleagues, agency references, a track record in the industry? A teaming relationship where you do not trust the partner's judgment is a performance liability, not an asset. On federal contracts, you do not get to terminate a subcontractor easily once performance begins.
What to put in a teaming agreement
A teaming agreement is a binding contract, and it should be treated like one. The informal handshake arrangements that small firms sometimes use, like a one-page letter of intent, are not adequate protection for either party and will not hold up if the relationship deteriorates.
A proper teaming agreement should specify:
- The specific opportunity it applies to (solicitation number, agency, contract title)
- The scope of work each party will perform, described specifically enough to be unambiguous
- The workshare percentage committed to the subcontractor if the prime wins
- Exclusivity: whether either party is restricted from teaming with competitors on the same bid
- Intellectual property ownership for any work product developed for the proposal
- What happens if the prime does not receive an award, including whether the agreement terminates or whether there is any obligation to bring the partner on a resubmission
- A non-disclosure provision covering any proprietary information shared during proposal development
- A duration. Teaming agreements should not be open-ended and should specify the period they cover
The workshare commitment is the most consequential provision. A partner who performs due diligence, contributes to the proposal, and then receives a smaller scope than expected because the prime adjusted the work split post-award is a partner who will not team with you again and may create legal exposure depending on how the agreement was worded.
Commit to a specific scope. Hold to it. If performance conditions require adjustments, address them through a formal subcontract modification, not an informal understanding.
Teaming to expand into new agency types
Beyond filling a capability gap on a specific bid, teaming is the primary tool for SDVOSB firms to expand into agency types where they have no prior performance. If all of your past performance is with civilian agencies and you want to break into DoD, teaming with a firm that has strong DoD experience lets you enter the agency with a credible proposal while building the relationship and performance record you need to compete independently in the future.
This only works if you are genuinely learning during the subcontract performance: building relationships with the contracting officer and program management staff, understanding how the agency operates differently from what you know, positioning yourself for the recompete. A subcontract relationship that is purely transactional (you deliver your scope, you invoice, you move on) does not build the agency-specific intelligence you need to prime the next contract.
Use every subcontract engagement as a research exercise. Who makes decisions at this agency? What are their priorities? What frustrates them about current contract performance? What are they going to need in the next acquisition cycle? The answers to those questions are worth more than the subcontract revenue in the long run. The firms that convert subcontract experience into future prime wins understand recompete positioning early.
When teaming is the wrong answer
Teaming is the wrong answer when the primary motivation is to pad the proposal with brand names rather than to fill a real capability gap. Agencies evaluate past performance on the relevance and quality of the cited work, not on the number of firms listed. A proposal with four teaming partners whose experience is marginally relevant is not stronger than a proposal with one teaming partner whose experience directly addresses the requirement.
Teaming is also the wrong answer when it is driven primarily by an existing business relationship rather than by what the contract requires. A firm you have worked with before, or one you have a social relationship with, is not automatically the right partner for a specific bid. The partnership decision should start with what the contract requires and then identify who fills that requirement, not the reverse.
And teaming is wrong when the scope split violates the limitation on subcontracting rules. An arrangement that looks like teaming but functions as a pass-through, where the SDVOSB prime wins the set-aside but the large business partner performs most of the work, is a compliance violation, not a competitive strategy. The reputational and legal consequences of a successful size or eligibility protest are significant, and they are entirely avoidable.