The whole record, read every night, for the whole team
A supplier with many product lines and many buyers does not need a better search box. It needs every award and every notice, in every code it sells under, cleaned, resolved and watched, and it needs that in front of every person who decides what to pursue.
What is in the ledger today
Some of these are still being counted. The record is loaded; the totals across it are aggregates over every row, so they are worked out a few at a time and land within minutes. A figure that has not been counted shows a dash rather than a zero.
Every code, every agency, every fiscal year back to FY2001
Coverage is not a list you request codes onto. It is the entire 2022 NAICS table, every awarding agency, and every notice SAM.gov posts, with award history back to FY2001 behind it. A division that sells fasteners and a division that sells training services see the same treatment.
Watches are unlimited on Capture and Enterprise, so a BD team can watch every code it sells under, every buyer it serves, every incumbent it competes with, and every keyword its capture plans depend on.
- Unlimited NAICS, PSC, buyer, vendor, state and keyword watches
- Recompetes sixty months out, scored, with the signals shown
- Result lists to 50,000 rows on Capture and 200,000 on Enterprise
UEI, CAGE, then normalized name
How a BD team uses it
The recompete table is the pipeline. Sort by end date and score, filter to the codes and buyers that matter, and every row is a contract someone on the team should own a year before it ends. The incumbent profile shows who holds it, under every name the sources used, and what else they hold. The buyer profile shows how that office competes, how often it sets aside, and how many offers it drew last time.
Open notices are matched to the same history, so a sources sought reads next to the last award for the same requirement. Alerts run hourly. Saved views and Excel and CSV exports feed the tools you already run; the API feeds the ones you build.
Seats, billing and terms
Capture carries ten seats and an API key. Enterprise carries fifty seats across divisions and sites, larger result lists, an API onboarding call, invoice billing against a purchase order, yearly terms, and custom data cuts on request: a state, a set of buyers, a code family, delivered as files.
Every seat sees the same record. Each person keeps their own watchlist, alert schedule and saved views. The owner gives each seat a role: a member works in the account, a viewer reads and changes nothing, a manager also invites and removes seats, and an advisor from outside the company reads everything and changes only the proposal work, pursuits and tasks. Pay in the books is closed to a seat until the owner opens it for that seat. See seats and roles.
What it does, and what it does not
It does not write the proposal. It keeps the work around one: a pipeline with six stages, gate and color-team reviews recorded against each pursuit, and a document library that matches your own files to the requirements of a solicitation. For the record itself it reads what the government publishes and nothing else: no purchased contact lists, no agency budget leaks, nothing from any employer. What it gives a large team is the complete federal record, cleaned and current, at a fraction of the cost of an enterprise platform, with an honest description of every gap.
Read next
- Methodology: entity resolutionWhy the incumbent column can be trusted.
- Data and sourcesCoverage, freshness and the boundary.
- CompareNext to the government sites and the enterprise platforms.
See who was last awarded in your NAICS
Every code, every buying office, every vendor and every recompete, organized from the federal record and read nightly. Start on one code with no card. A plan opens every code.
Try the live demo The real app on one code. No email needed.