Teaming with a federal prime as a small business: a playbook

The prime-sub relationship, honestly

Teaming with a federal prime is the most common path to federal revenue for a small technical business, and one of the most misunderstood. The mythology on both sides is unhelpful. Some small businesses treat primes as predatory; some primes treat small businesses as line items in a subcontracting plan. Both miss the point. A well-run prime-sub relationship is an economic exchange where both parties win — the prime gets subcontracting credit and specialist capability, the small business gets access to contract vehicles and clearance posture they could not build alone. Run well, it is the single highest-leverage path from a small business's first day to a real book of federal revenue.

Run poorly, it is the fastest way to spend eighteen months on a pursuit that never awards, never pays, or pays so little that the small business is funding the prime's proposal effort. This playbook is about the discipline to get the former, not the latter.

Part 1: Finding the right prime

Start from the agency, not the prime

The instinct is to list "the primes" (the five names everyone knows) and start calling. That is backwards. Start from the agency and mission you want to serve, then find which primes are active there. A prime who dominates DoD may be peripheral at NIH. A prime with deep FEMA past performance may have no footprint at Treasury. Match the prime to the agency first.

Use public data to build the shortlist

Three public sources give you everything you need:

• USAspending.gov — Awards by agency and NAICS. Filter by your target NAICS (541512 for most AI work) and target agency. The list of prime recipients sorts itself.
• SAM.gov Contract Data — Current vehicles and task orders. Shows who is on which IDIQ and which BPA.
• Small Business Subcontracting Reports (eSRS / SBA) — Tells you which primes are actually flowing money to small businesses vs. merely reporting subcontracting plans. Primes with real active small-business spend are your target list; primes with subcontracting plans and no spend are not.

Assess each prime for fit

For each prime on your shortlist, check:

• Vehicle presence at your target agency. Any IDIQ/BPA seats?
• Recent wins in your capability area over the last 24 months. Is this a growing practice for them or a dying one?
• Subcontracting ratio of small-business dollars to total dollars on their active vehicles. Published; real signal.
• Partnership style. Reach out to two or three small businesses who currently sub to this prime and ask, frankly, whether the prime pays on time and protects the sub's position.
• Growth areas. Look at their earnings calls (if public), press releases, and job postings for clues about which practices they are investing in.

Part 2: The pitch

What the prime actually needs to hear

Primes hear small-business pitches constantly. Most are ignored. The ones that work address three questions quickly:

• What specific capability do you bring that I do not already have in-house?
• Where is that capability relevant to a specific pursuit I am working on right now?
• How do you make my life easier rather than harder?

A pitch that says "we are an AI company with a great team" dies instantly. A pitch that says "we have built production ML on SAMHSA data and we see you are pursuing the next SAMHSA-BRSS award — we can own the ML scope for you" gets a meeting.

The capability statement

One page. Top third: company snapshot — UEI, CAGE, NAICS, socioeconomic classifications, location, DUNS (legacy), clearance status. Middle third: three-to-five crisp capability areas with specific technical depth. Bottom third: three concrete past performance examples with named agency customers and specific scope delivered. Contact information. That is the document. Anything longer loses the prime's business-development lead in thirty seconds.

Precision Federal's capability statement, for example, leads with SAMHSA production ML, then federal AI engineering and cloud architecture, then specific programmatic past performance, plus the founder's credentials (Kaggle Top 200, fifteen years of federal program experience). One page. That is enough.

Finding the right human at the prime

Primes have two kinds of people you can pitch to: capture managers and practice leads. Capture managers own specific pursuits; practice leads own capability areas. For a specific pursuit, go to the capture manager. For a general capability relationship, go to the practice lead. Small-business liaison offices exist but are often ceremonial — they forward your capability statement internally and rarely change outcomes. Identify the capture or practice lead directly via LinkedIn, conference speaker lists, or warm introductions from other small businesses.

The first meeting

Thirty minutes. Introduce yourself in sixty seconds. Put a specific pursuit or capability question on the table in the next sixty. Let them talk for the bulk of the meeting — their pursuits, their pain, their needs. Close with one specific ask: "If you have an opportunity where our ML depth fits, we'd like to be on the team." Do not ask for a teaming agreement on the first call. That comes after the prime has a specific pursuit in mind.

Part 3: The teaming agreement

Two kinds of agreements

• NDA / MOU — early-stage mutual confidentiality and interest. Sign quickly. Limit to the specific pursuit. Mutual, not one-way.
• Teaming Agreement (TA) — binding commitment to pursue a specific opportunity together with defined scope and workshare. Sign carefully. Negotiate hard.

What every TA must include

• Defined scope of work assigned to the small business, ideally with a draft SOW attached.
• Workshare commitment — either a specific dollar amount or a percentage of total contract value, with an explicit minimum.
• Duration and termination conditions — when the TA expires, what triggers termination, whether expiration is automatic on non-award.
• Exclusivity — ideally mutual. One-way exclusivity (you cannot team with anyone else but they can team with anyone) is a bad deal.
• IP ownership — background IP stays with the originating party, foreground IP assignment clearly specified.
• Treatment of your past performance — explicit that your past performance cited in the proposal remains yours, not theirs.
• Scope-raiding protection — prohibits the prime from performing work assigned to you internally.
• Post-award subcontract terms — key commercial terms (payment timing, T&C reference, rate structure) previewed in the TA so there are no surprises if you win.

Red flags to refuse

• "We'll work out workshare after award." No you will not. Negotiate it now.
• One-way exclusivity with no reciprocal commitment.
• A TA that survives non-award and locks you up for future pursuits.
• IP assignment clauses that give the prime ownership of your foreground IP.
• Scope definitions so vague that the prime could hand you any task or no task after award.
• Payment terms below net-60. You will finance their working capital otherwise.

Part 4: During the proposal

Proposal work on a prime-led bid is where most small-business-prime relationships either gel or break. Principles:

• Write the sections you are accountable for, in your voice, to their style guide. Do not hand over a generic write-up and expect the prime to tailor it. Write it exactly as you want it to appear in the final document.
• Hit every internal deadline. Primes' proposal shops run brutal schedules. Missing a color-team review destroys your credibility faster than anything else.
• Assign one accountable leader on your side who owns all communication with the prime's capture manager and proposal manager. Noise is the enemy.
• Do not go around the prime to the customer during the pursuit. Full stop. This is the single fastest way to lose a teaming relationship and get blackballed across the prime's network.
• Share the pricing conversation honestly. Your rates and wrap are what they are. Primes understand small-business cost structures. Hiding them creates pricing surprises that blow up the deal.

Part 5: Post-award

The subcontract

After award, the teaming agreement is replaced by a formal subcontract. Read every clause. Every one. In particular:

• FAR flowdowns — the prime flows down prime-contract FAR clauses. Some are mandatory, some are negotiable. Know the difference.
• Payment terms — how the prime pays you. Confirm timing is triggered by invoice, not by agency payment to prime.
• Change management — how scope changes are priced and approved.
• Termination — termination for convenience costs you if you have staff on the program.
• Key personnel — if your principal engineer is named, you must deliver that person. Understand substitution procedures.

Delivery discipline

The small business that delivers well gets a second sub. And a third. The small business that ships late or hides problems gets one and never another. Specific practices:

• Weekly status updates to the prime's program manager, written, brief, honest.
• Early escalation of risks and blockers. Silence is worse than bad news.
• Clean documentation of everything. Primes love subs who make them look good to the customer.
• Direct relationship with the technical customer, protected by (not circumventing) the prime's PMO.

Part 6: Traps and how to avoid them

The ghost teaming agreement

Prime signs TA, adds you to the proposal team for subcontracting-plan credit, then assigns you trivial or no scope after award. Protect with: explicit minimum workshare in the TA and a scope-raiding clause.

The pass-through

Prime wins, funds flow to you with minimal markup, prime's PMO inserts itself between you and the customer and extracts margin without adding value. Protect with: direct technical communication rights with the customer, explicit markup caps, and a PM overhead that matches actual work performed.

The loss-leader

Prime prices the sub scope below your real rate to win the bid, then expects you to eat the loss. Protect with: price honestly in the proposal, refuse rate concessions below your floor, and get pricing in writing before the prime submits.

The locked-in exclusivity

TA that prevents you from teaming with anyone else on any opportunity in the agency for two years. Never sign. Limit exclusivity to the specific pursuit.

The scope migration

Prime gradually moves scope from you to their in-house team over the course of performance, reducing your workshare with each mod. Protect with: written minimum workshare in the subcontract, not just the TA.

Bottom line

A well-structured teaming relationship with the right prime is the highest-leverage path from a small AI business's first day to serious federal revenue. A poorly-structured one is expensive in time, money, and reputation. The difference is not the prime's name on the letterhead — it is the discipline with which you choose the partner, negotiate the agreement, deliver the work, and protect your position. Primes that pay on time, assign real scope, and protect your customer access are worth ten times the ones who look impressive on paper but burn subs for a living.

At Precision Federal we work both sides: as a sub to cleared primes on classified or large programs, and as a prime on our own SBIR and small-business set-aside awards. Both relationships teach the same lesson — clarity up front saves everyone pain later.

Frequently asked questions