Prime or Sub: How to Choose Your Role Before You Bid
Your teaming decision shapes your risk, revenue, and past performance. Here is how to make the call before the RFP drops.
A small 8(a) IT services firm wins a spot on a large IDIQ vehicle as a prime. Task orders start flowing, but each one requires cleared personnel, a PMO infrastructure, and bonding capacity the firm does not have. Eighteen months later, the contracting officer issues a cure notice. The firm had the vehicle but not the operational depth to perform. The right call at capture would have been to sub to a mid-tier integrator and build toward priming on a smaller, better-scoped opportunity.
The prime-versus-sub decision is not about ambition. It is about fit: your past performance record, your technical bench, your cash flow tolerance, and what the specific solicitation actually rewards. Getting it wrong costs you more than the bid. It can cost you a CPARS rating you will carry for up to three years.
What the Government Actually Evaluates
Before you decide your role, read the evaluation criteria. Most RFPs under FAR Part 15 score offerors on some combination of technical approach, management approach, past performance, and price. The weight given to past performance, and how the agency defines "relevant" experience, is the single biggest factor in your role decision.
A typical Section M might read: "Past performance will be evaluated for relevance based on contract size (within 50% of the estimated contract value), scope similarity, and recency (within five years)." If the ceiling is $25M and your largest prime contract was $4M, you have a relevance gap. You can close it by flowing down a larger prime contract from a teammate, but only if the RFP allows you to cite team past performance and the evaluators will credit it. Some do. Many do not, especially for small business set-asides where the agency wants to see the prime's own record.
Check Section L for instructions on how past performance is submitted. If the RFP says "submit three references for the prime contractor," your sub's references do not fill that column. Know the rules before you build the team.
The Five Factors That Drive the Decision
1. Past Performance Relevance
Map your CPARS-rated contracts against the solicitation's relevance criteria. Size, scope, NAICS code alignment, and recency all matter. If you cannot cite at least two contracts that a reasonable evaluator would score as "relevant" or "very relevant," priming a competitive full-and-open or even a set-aside with strong competition is a long shot. Subbing gives you the chance to build a new CPARS reference under a prime who already clears the bar.
2. Technical and Staffing Depth
Can you staff the key personnel positions the RFP will require on day one of performance? Many RFPs, particularly in defense IT and professional services, require key personnel resumes in the proposal and Letters of Commitment. If you are stretching to fill two of five key positions, you are a sub looking for a prime who has the bench, not the other way around.
3. Cash Flow and Bonding
Construction and facilities contracts often require payment and performance bonds. Even in services, priming a large IDIQ means you are carrying payroll and overhead for 30 to 60 days before your first invoice clears. If your line of credit cannot absorb a two-month float on a $5M annual run rate, subbing to a prime who handles billing and collections protects your business. Subcontract payment terms under FAR 52.232-40 require primes to pay subs within 30 days of receiving government payment, but disputes happen and cash timing still matters.
4. Incumbent and Competitive Intelligence
If there is a strong incumbent with a clean CPARS record and a locked-in team, priming against them as a new entrant is a steep climb. Subbing to the incumbent or to a credible challenger who needs your specific capability (a cleared facility, a niche NAICS, a socioeconomic certification) may generate more revenue with less proposal investment. Capture intelligence, including who holds the current contract, what the incumbent's CPARS says, and whether the agency has signaled a desire for competition, should inform your role decision before you write a single page of your technical approach.
5. Socioeconomic Set-Aside Structure
If the opportunity is a small business set-aside, an 8(a) sole source, or a WOSB/SDVOSB restricted competition, the set-aside designation determines who can prime. Under FAR 19.502-2 and SBA regulations, the prime on a set-aside must meet the applicable size standard under the solicitation's NAICS code. If you are above the size threshold, you cannot prime the set-aside. You can sub, but you need to understand the limitations on subcontracting rules (FAR 52.219-14 for small business set-asides (note: FAR 52.219-14 specifically covers limitations on subcontracting for small business set-asides, which is correct in context, but the clause applies to set-asides for small business, not all set-aside types listed above)) before you commit to a workshare percentage. Violating the limitations on subcontracting is a False Claims Act exposure, not just a protest risk.
Building a Teaming Agreement That Reflects Your Role
Once you decide to sub, the teaming agreement and eventual subcontract define your actual position. Key terms to negotiate before the proposal is submitted include: workshare percentage and the specific task areas you own, exclusivity (will the prime shop your capability to a competitor?), flow-down clauses (which FAR clauses the prime will push to your subcontract), and past performance citation rights (can you use this contract as a reference on future proposals?).
Do not sign a teaming agreement that gives you a vague "up to 30% of work" with no defined task areas. That language gives the prime discretion to minimize your role post-award. Tie your workshare to specific Contract Line Item Numbers (CLINs) or labor categories wherever the RFP structure allows.
If you are priming and bringing in subs, the same logic applies in reverse. Define what you need from each sub, get their past performance references and key personnel commitments in writing before RFP release, and make sure your teaming agreement includes a no-compete clause so your sub does not show up on a competing team.
When to Walk Away from Both Roles
Not every opportunity is worth pursuing, even as a sub. If the prime has a weak past performance record, a thin technical team, and is priming primarily because of a socioeconomic certification rather than delivery capability, your CPARS on that contract will reflect the team's performance, not just yours. A poor CPARS as a subcontractor is less damaging than as a prime, but it still shows up in your record and can be cited by evaluators on future bids.
Run a simple bid/no-bid against four criteria: (1) Can the team win? (2) Can the team perform? (3) Does your role generate meaningful past performance? (4) Is the revenue worth the proposal cost and performance risk? If you score below three out of four, pass and redirect that BD budget toward an opportunity where your role is cleaner.
For a practical framework on structuring your capture process from opportunity identification through teaming decisions, see our services at IT Custom Solution LLC, the team behind Winrove.
The Short Version
Your role on an opportunity should be driven by your past performance relevance, your staffing depth, your cash position, and what the RFP actually rewards. Prime when you can clear the evaluation criteria on your own record and staff the contract from day one. Sub when you need the reference, lack the bench, or face a dominant incumbent. In either case, lock down your workshare and key terms in writing before the proposal goes out the door. The teaming decision made at capture is the one you will live with through performance.
If you are working through a specific teaming or bid strategy question, reach out for a brief consult. Winrove, a product of IT Custom Solution LLC, is available at winrove.com starting at $49/mo and can help you screen opportunities against your past performance profile before you commit to a role.