Federal Software Contracts

US federal software contracts, matched to the public companies that win them.

120+tickers mapped
500+contractor mappings

Sample

2 records

Reseller-attributed contract (the moat in one row)

Representative, modeled on the public-record shape. The prime is a reseller; the description is keyword-matched to the software ticker; publication_date is the point-in-time field.

contracts.jsonl

{
  "record_id": "CONT_AWD_2033H624F00068_...",
  "ticker": "CRWD",
  "vendor": "CrowdStrike",
  "product_category": "endpoint_security",
  "prime_contractor": "FCN, INC.",
  "prime_is_reseller": true,
  "awarding_agency": "Department of the Treasury",
  "obligated_amount": 4752615.89,
  "award_date": "2024-02-01",
  "publication_date": "2024-02-15",
  "is_modification": true,
  "fiscal_quarter": 2
}

Direct-vendor award, ceiling exceeds obligated

Representative. The prime is the vendor; potential_total_value (the ceiling) exceeds the dollars obligated so far.

contracts.jsonl

{
  "ticker": "PLTR",
  "vendor": "Palantir",
  "product_category": "data_analytics",
  "prime_contractor": "PALANTIR USG INC",
  "prime_is_reseller": false,
  "obligated_amount": 292680689.24,
  "potential_total_value": 480000000,
  "is_new_award": true,
  "fiscal_quarter": 3
}

Specifications

Federal Software Contracts specifications
Formats	JSON, CSV, Parquet
Delivery	S3, REST API, SFTP on request
Cadence	Daily ingestion, weekly delivery
Tickers mapped	120+
Contractor mappings	500+
History	FY2018-present
Source	USASpending.gov (FPDS-NG)
Sectors	Cybersecurity, Cloud, DevOps, Analytics, IT Services
Access	The underlying data is US-government public record under FOIA and FFATA, with no use restrictions on the source. Gerra mapping, categorization, and aggregation layer is the proprietary value-add. No PII or MNPI.

What ships

Contract-Level Records
Individual contract awards with vendor, agency, amount, period, and product categorization.
Ticker Aggregation
Quarterly revenue attribution by ticker with market share calculations and competitive positioning.
Pipeline Tracker
Track upcoming contract expirations and recompetes as forward-looking revenue signals.

Fields

13 fields

Field	Description
record_idstring	Unique award or action id from the federal record.Example CONT_AWD_2033H624F00068_...
tickerstring	Public ticker the spend is attributed to.Example CRWD
vendorstring	Software vendor behind the contract.Example CrowdStrike
product_categorystring	One of 12 investment-relevant categories.Example endpoint_security
prime_contractorstring	Awardee of record, often a reseller rather than the vendor.Example CARAHSOFT TECHNOLOGY CORP
prime_is_resellerbool	Whether the prime is a value-added reseller vs the vendor itself.Example true
awarding_agencystring	Agency placing the award.Example Department of the Treasury
obligated_amountfloat · USD	Dollars obligated on the action.Example 4752615.89
potential_total_valuefloat · USD	Ceiling value; can exceed obligated.Example 480000000.00
award_datedate	Obligation / award date.Example 2024-02-01
publication_datedate	First appearance in the federal feed - the point-in-time field for backtesting (lags award 3 to 30 days).Example 2024-02-15
is_modificationbool	Whether the action is a modification vs a new award or option exercise.Example true
fiscal_quarterint	Federal fiscal quarter.Example 2

Quality checks

2 checks

Award-to-earnings lead

Whether quarter-over-quarter changes in obligations predict government-revenue beats and misses.

Aggregate obligations per ticker per fiscal quarter using publication_date, then compare to subsequently reported revenue and consensus. Typical signal horizon is 30 to 90 days because awards publish ahead of the quarterly report.

Methodology-stage. A backtest covering several large vendors is available on request; no headline number is published here.

Competitive displacement detection

Catching vendor switches in agency accounts before either company reports.

Track market-share and year-over-year share change in the competitive view and the migration of agencies between vendors.

Methodology-stage. No published metric.

Ground truth

What is correct	Two anchors: the public federal record itself (the award is ground truth that the contract happened), validated against the SEC EDGAR and federal entity registries; and, for the investment signal, the vendor subsequently reported quarterly government revenue.
How it is established	Ticker-mapping correctness is graded against the EDGAR CIK registry and the federal entity registry, with new entity mappings reviewed weekly. Signal correctness would be graded against realized earnings.
Agreement	No inter-rater figure; the mapping is validated against authoritative government registries rather than human raters.

How it is built

01
Public-source ingestion
Automated daily ingestion via the USASpending.gov API over FPDS-NG, the official US system of record for federal contract actions above the micro-purchase threshold. No web scraping, no manual entry.
02
Ticker and reseller attribution
The moat: most federal software flows through resellers (Carahsoft, Thundercat, FCN), not directly to vendors. A 500+ entity-to-ticker map with keyword matching on contract descriptions attributes spend to the correct software ticker.
03
Product categorization
Generic federal product codes are mapped to 12 investment-relevant categories aligned to how analysts model these companies.
04
Action-type classification
New awards, modifications, option exercises, and de-obligations are flagged and tracked separately; modifications are linked to their base award.
05
Point-in-time construction
Every record carries a publication_date - its first appearance in the feed - so backtests use publication_date, not award_date, to avoid look-ahead. Typical lag is 3 to 30 days.
06
Quality checks
Ticker mapping is validated against the SEC EDGAR registry, IDIQ ceiling modifications are de-duplicated from new obligations, contractor names are cross-referenced against the federal entity registry, and new entity mappings are reviewed weekly.

05RequestReplies usually within one working day

Request a sample

We send real records in the format you would receive, with the field list and where each record came from. Access for evaluation is limited and covered by a mutual NDA.

ProductFederal Software Contracts