The pilot product
The pilot launches in the Austin, Texas metro on public data: permit filings, published solicitation documents, and public procurement postings. Subcontractors are served first, to build verified coverage. The manufacturer specification layer follows in the same metro, off the same records.
Every subscription is worked from records shaped like this one: project, trade, stage, deadline, source, and history on a single record, checked against the document it came from. The record below is a labeled sample, built from the pilot record design. At opening it is replaced by a real published record from the pilot metro.
A sample project, invented to show the shape of a live record. No real project, firm, or posting is shown here.
Stage history, as a live record keeps it (sample entries):
The pilot feed covers projects at bidding stage in your trade: the stage where the work is real, the documents are published, and the deadline is fixed. Each record is checked against its source, carries its bid deadline, and keeps its history as the project moves.
One project, one record, however many sources reported it. The record names its source and keeps every stage change, so what you read is what the documents say.
Records are scored against your trade and your working radius, and the score shows its reasons. Alerts run ahead of bid deadlines, not after them.
The verified project count for the metro and your trade is published before the feed opens for sale, and republished each period. Thin counts stay closed.
The feed is a working tool, not a report. These are the mechanics every record runs through, named plainly so the offer can be checked against them.
Save a search by trade or category and working radius. It runs against every new and changed record, so the list maintains itself instead of going stale in a spreadsheet.
One digest each morning: the records that entered your saved searches overnight, and every change to the records you already hold, with deadline moves first.
Follow a project, a general contractor, or a specifying firm. Every change lands as a dated event on the record, never as a silent overwrite.
Search the published bid documents in the feed by keyword. The hit is shown inside its section of the document, so you read it in context; the document itself is never republished.
Where the public record publishes them, the record names who took out plans, who bid, and which contractor was awarded, so you can see the field you are bidding against.
Export any list in CSV, PDF, and spreadsheet formats, on the plans that carry export. A data push sends new and changed records to the tools your team already runs, in standard formats, on the plans that carry it.
Public owners publish complete bid documents, specifications included. SubPursuit reads those published documents for the pilot metro and parses them by category: which sections appear, which products are specified, and what changes when an addendum lands.
Every source in the feed has its terms read and recorded before a single record is taken from it. Where a source is silent about reuse, it is treated as not permitted until counsel confirms otherwise. Specification documents are read for their facts; the documents themselves are never republished. That discipline is the product as much as the software is.
The pilot feed covers bidding stage: the stage where the solicitation is published, the documents are public, and the bid deadline is fixed. It does not cover private planning stage projects, because no public source delivers them completely. Earlier stage contents join the feed only when a lawful source for them exists, and subscribers are told in writing when they do.
Permit filings, published solicitation documents, and public procurement postings. Every source has its terms read and recorded before a single record is taken from it. Where a source is silent about reuse, it is treated as not permitted until counsel confirms otherwise. Documents are read for their facts; the documents themselves are never republished.
The project and its location, its stage, its bid deadline, the published documents where they exist, the planholders and bidders the public record names, and the source the record came from, with the project's full stage history kept as dated events and never overwritten.
One project counts once, however many sources reported it, and only records checked against their source document are counted, for a stated period and scope. The count is published before an area opens and republished every period. The full counting method stands on the method page.
It is the specification content of published bid documents on public projects at bidding stage in the pilot metro, parsed by category, with addenda tracked. It is not an early design stage influence product, it carries no forecasts, and it is not sold as any of those, at any price.