How Government Contractors Vet Teaming Partners Before Bidding (Without Paying for GovWin)

If you have ever been burned by a teaming partner who turned out to have an expired SAM.gov registration, a debarment you did not know about, or a business entity that existed only on paper, you know why partner vetting matters. And if you are small or mid-sized in the GovCon space, you probably also know that GovWin and Deltek charge a lot for access to data you could assemble yourself from public sources.

Here is the vetting workflow I actually use before committing to a teaming arrangement on a federal bid.

The Three Questions That Matter

Before I spend time on a teaming agreement, I want answers to three questions:

1. Is this entity legitimately registered and active? SAM.gov registration, DUNS/UEI, active registration status, no exclusions or debarment.
2. Does the entity actually exist as a legal business? State Secretary of State filing, active status, correct legal name and entity type.
3. Is there anything in their public record that raises flags? SEC EDGAR filings if they are publicly traded, any regulatory enforcement history.

None of these require paying for a commercial intelligence product. All of the underlying data is public. The friction is that it lives across five different government portals with inconsistent search interfaces.

Step 1: SAM.gov Entity Verification

SAM.gov is the authoritative source for federal contractor registration. An entity must be active in SAM.gov to receive federal awards, and the exclusions list is the debarment check.

The SAM.gov API (requires a free API key from sam.gov) returns entity registration details including:

• Active/inactive registration status
• Entity start date and expiration
• Exclusion status (debarment, suspension, proposed debarment)
• CAGE code, UEI, NAICS codes
• Points of contact

The SAM.gov entity actor on Apify wraps this API and returns structured results without requiring you to manage the API key registration and query syntax yourself:

curl -X POST https://api.apify.com/v2/acts/pink_comic~sam-gov-entity-search/run-sync-get-dataset-items \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"companyName": "Acme Federal Solutions LLC", "maxResults": 5}'

The fields to check: registrationStatus should be Active, exclusionStatus should be null or empty, and registrationExpirationDate should be in the future.

Step 2: Secretary of State Business Entity Check

SAM.gov tells you a company is registered with the federal government. It does not tell you whether the underlying business entity is legally active in its home state. A company can have an active SAM.gov registration while the underlying LLC has been administratively dissolved.

This matters most when:

• The teaming partner is a small business claiming specific certifications (8(a), WOSB, SDVOSB) based on entity structure
• You are doing past performance verification and the company has changed names or merged
• The partner claims to be incorporated in a specific state for jurisdictional reasons

For multi-state SOS lookup, the Secretary of State business entity actors cover the major states where GovCon firms tend to incorporate — Virginia, Maryland, Texas, Florida, and Delaware being the most common. The actors return entity status, registered agent, formation date, and current standing.

{
  "companyName": "Acme Federal Solutions",
  "state": "VA",
  "maxResults": 10
}

Look for: active/good standing status, formation date consistent with the company's claimed history, and registered agent information that matches what they have represented.

Step 3: SEC EDGAR for Publicly Traded Partners

Most small GovCon teaming partners are not publicly traded, but mid-sized and large firms often are or have parent companies that are. If your teaming partner is a subsidiary of a public company, SEC EDGAR filings give you a lot of useful context: revenue trends, pending litigation, material risk disclosures, and any going-concern language in recent audits.

The SEC EDGAR actor takes a company name and returns recent filings — 10-K, 10-Q, 8-K — with links to the actual documents. A going-concern qualification in the most recent 10-K is information worth having before you put your name on a joint bid.

curl -X POST https://api.apify.com/v2/acts/pink_comic~sec-edgar-filings/run-sync-get-dataset-items \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"companyName": "Acme Defense Group", "filingType": "10-K", "maxResults": 3}'

Putting It Together: A Practical Vetting Checklist

For each potential teaming partner, I run through this in order:

1. SAM.gov lookup — confirm active registration, no exclusions, expiration date at least 6 months out
2. SOS entity check — confirm good standing in home state, formation date makes sense
3. Certification verification — if they claim 8(a), WOSB, SDVOSB, verify via SBA certification databases (separate lookup)
4. SEC EDGAR check — only if they are publicly traded or a subsidiary of a public company
5. Past performance spot check — USASpending.gov for contract award history; the USASpending actor makes this queryable

The whole workflow takes about 15 minutes per partner once the tooling is set up. Before automating, it took 45-60 minutes of manual searching across five different portals.

Why Not Just Use GovWin or Deltek?

GovWin and Deltek are useful for opportunity identification and pipeline management. For basic entity vetting, you are paying for a UI wrapper around data that is already public. If you are doing this at volume — evaluating 10-20 potential partners per quarter — the cost of the commercial tool versus the cost of assembling the data yourself becomes a meaningful decision.

The tradeoffs:

• Commercial tools: faster for one-off lookups, better UI, no engineering required
• Public data APIs: cheaper at scale, integrates with your own systems, auditable data lineage

For firms doing frequent BD work with many potential partners, the public API approach makes more sense. For occasional lookups, the commercial tool is probably fine.

Limitations to Know About

• SAM.gov API requires a free registration — takes 1-2 business days for key approval
• SOS data freshness varies by state; some states update weekly, others near real-time
• SEC EDGAR only covers publicly traded entities and their subsidiaries
• None of this replaces due diligence on past performance references, which still requires phone calls

All three actors are available on Apify. If you are integrating this into a BD pipeline or CRM workflow, the JSON output maps cleanly to standard entity fields.

Happy to talk through specific state coverage or integration patterns in the comments.