The pipeline is already in the record. It just has to be read every night.
Capture work does not start when a notice posts. It starts a year before the incumbent contract ends. Every one of those end dates is in the public record, and so is who holds it, what it is worth, how it was competed and what the office did last time. The engine reads all of it nightly and hands you the list.
What is in the ledger today
The ten-year history is still loading: 308 of 2,698 fiscal-year jobs done, newest year first across every sector. These numbers grow every day. How the data is pulled.
What the job needs
Recompetes, scored, sixty months out
Every contract on record with an end date inside the horizon, scored on size, competition and how the office behaved last time, filtered to your codes and buyers.
A pipeline you can work
Put a recompete or a notice on the board with a stage, an owner note and a due date. Today shows what is due. A private calendar feed puts the dates in Outlook or Google.
Incumbent and buyer profiles
Who holds it, under every name the sources used, what else they hold, and how this office competes: set-aside mix, offers received, award sizes by year.
Ten years of awards, cut the way a capture plan needs them
Every code, office, agency, vendor, state and set-aside has its own view of the same ledger: obligated by fiscal year, the vendors who won, the offices that bought, the codes they used, the sizes they awarded. Numbers are built from what USASpending and FPDS publish, with vendor names resolved so one company is one row instead of six spellings.
Every list exports to CSV. Capture and Enterprise carry an API key, so the same cuts feed whatever you already run.
- Obligated by fiscal year for any code, office, agency or vendor
- Award size bands and medians, so a bid is sized against the record
- Set-aside mix and offers received, by buying office
- CSV on every list; an API key on Capture and Enterprise
Against what capture teams usually pay for
| What you are buying | Enterprise capture suites | LastAwarded |
|---|---|---|
| Award and notice data | Included, plus curated forecasts and contacts | Included: the full public record, read nightly |
| Recompete pipeline | Included, often the main draw | Included: scored, sixty months out, on every code |
| Proposal and color team tooling | Included | Not built, and not planned |
| Human research and agency contacts | Included, and a large part of the price | Not included: public sources only |
| Typical annual cost | Tens of thousands | Hundreds |
Where it is honest about the gap
An enterprise suite sells you two things: the public record organized, and human research on top of it. This is the first one, done well, for a fraction of the price. It does not call program offices, it does not publish forecasts that are not in the record, and it does not sell contact lists. If your capture process depends on those, it replaces part of your stack, not all of it.
Subaward reporting, contract modification history and the orders written under a vehicle are all loaded now, so a recompete read can tell an option exercise from a fresh competition, and a task order reads next to the contract it came from.
Read next
- Recompete radarThe table and the score, explained.
- Exports and APICSV on every list, an API key, the endpoints.
- Large suppliers and BD teamsSeats, invoice billing, custom cuts.
- CompareNext to the free 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 public record and read nightly. Open it with a plan.