Contracts and grants, modeled by recipient and award.
Federal spending data is public but scattered — USAspending awards, SAM.gov registrations, Grants.gov opportunities, and sub-award pass-throughs, each keyed differently. Sloe joins them on UEI into one source-backed research layer. Obligations are not revenue — recipient, agency, award, and outlay stay distinct.
Available now. The govcon lane is built and source-backed — recipients, awards, agencies, and opportunities joined by UEI-bearing identifiers, with obligation and outlay kept separate.
Government Contractor & Grant is its own structure.
The govcon model anchors on UEI, then joins prime awards, sub-awards, recipient registrations, and opportunities as separate source-backed layers. Obligations, outlays, and award ceilings stay distinct — never collapsed into 'revenue.'
Recipients and identifiers.
UEI (and legacy CAGE) resolve recipients across awards and registrations; parents are reviewed, not inferred from names.
Prime awards.
USAspending contract and grant awards keep agency, action date, obligation, and outlay separate.
Sub-awards.
Pass-through and sub-award records surface the second tier of recipients behind a prime.
Opportunities.
Grants.gov and solicitation records are matched to recipient profiles by fit, not assumed wins.
Recompete timing.
Period-of-performance end dates surface expiring contracts for BD and capture timing.
Affordable access.
Recipient diligence, pipeline building, and competitor mapping at a price smaller teams can justify.
Built on the primary public record.
The govcon layer is built around official federal public data first, joined by UEI. No paywalled aggregators; obligations are never presented as company revenue.
Common questions.
What sources is the government-contracting data built from?
Official federal public data — USAspending prime and sub-award records, SAM.gov entity registrations, and Grants.gov opportunities — joined on UEI.
Are award obligations the same as company revenue?
No. Obligations, outlays, and award ceilings are kept distinct and are never presented as company revenue.
Can I track expiring contracts for business development?
Yes. Period-of-performance end dates surface expiring contracts so you can time business-development and capture work.
How do I get access?
Access for recipient diligence, pipeline building, or bulk export is by request, priced so smaller teams can justify it.
Tell us what govcon data needs to do.
Recipient diligence, pipeline building, recompete tracking, or bulk export — share the workflow and we'll get you access, including custom cuts.
Related datasets.
Every Sloe lane is built on the same source-backed pipeline. Explore an adjacent dataset.