Internal preview. Not published. Activation is gated on counsel clearance.

Austin metro pilot

See the project while it is still yours to win.

SubPursuit is new construction project intelligence built on public records: permit filings, published solicitation documents, and public procurement postings. The pilot feed covers bidding stage projects in one metro, Austin, Texas, verified record by record, with the count published before anyone is asked to pay for it. Every project labeled at the stage its record supports.

The product is the record

This is what a subscriber actually works from: one record per project, checked against its source, with the deadline, the stage, and the history on its face. 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.

Sample record Stage: Bidding

Riverside Community Recreation Center

A sample project, invented to show the shape of a live record. No real project, firm, or posting is shown here.

Location
Austin metro, Texas (sample)
Trade in scope
Electrical (sample trade)
Bid deadline
A Thursday, 2:00 PM Central (sample date and time)
Documents
Published bid documents, specifications included
Planholders
Named on the record where the public posting publishes them
Source
A city procurement posting: a published public solicitation document. On a live record, the source is named in full, with the posting date.

Stage history, as a live record keeps it (sample entries):

  • 🗂️Permit record matched to this project and merged into one record
  • 📄Solicitation published by the public owner; the bidding stage opens
  • 🔁Addendum issued; the bid deadline moved, and the record shows both dates

How the feed works

Built for the two sides of every bid

One feed, two pursuits. Subcontractors get the volume side: the right projects, in their trade, before the deadline. Manufacturers get the premium side: what the published specification documents say was specified, on the public projects in their category.

For subcontractors

Bidding stage projects in your trade and your metro, each record checked against its source document, with bid deadlines carried on the record so a date is never missed quietly.

  • 🏗️Projects at bidding stage, filtered to your trade
  • ⏰Bid deadlines on every record, with alerts ahead of them
  • 🎯Fit scoring that explains itself, record by record
  • 🔢The verified project count for your metro, published before sale

The subcontractor feed

For manufacturers

A specification layer scoped honestly: published specification documents from public projects in the pilot metro, parsed by category, so your team can see what was specified, removed, or substituted while the bidding window is still open. Read from the published bid documents themselves, section by section.

  • 📄Specification sections read from published bid documents
  • 🏷️Specified products and categories, named on the record
  • 🔁Addenda tracked, so a substitution is never a surprise
  • 📍One category, one region, covered completely before breadth

Our manufacturer prices are on the pricing page. No sales call is required to see them.

The specification layer

How a project reaches your list

Every record starts as a public document. Nothing enters the feed from a source whose terms we have not read, and every record keeps its source and its history.

1. The filing

A permit is issued, a solicitation is published, a procurement posting goes up. Public records, created by the project itself.

2. The record

The same project arriving from three sources becomes one record, with its stage history kept intact and its source named on it, so you can check it yourself.

3. The pursuit

The record is scored against your trade or your category and lands on your list while the bid window is open, with the deadline attached.

Seven states on the map, opened in order

SubPursuit's territory is a seven state footprint: Texas, Georgia, South Carolina, North Carolina, Alabama, California, and New York. Territory is not coverage, and no area in any of these states is covered today. Coverage opens area by area: the Austin metro pilot first, the Atlanta metro second, then the Texas and Georgia statewide build-out, with South Carolina, North Carolina, and Alabama following as the expansion ring, and California and New York after them in the national expansion, opened market by market. The waitlist is how each area's demand gets counted.

See the coverage areas

Counts before claims

Lead quality is a regulated promise, and this house treats it that way. Before any metro or category opens for sale, SubPursuit publishes its verified project count for the prior period. If the count is thin, the metro does not open. The feed sells only what its records can deliver, at the stage the records support, and says so on the page.

One count per metro, counted the same way every period, and the method is published with it.

How a count is computed: one project counts once, however many sources reported it, and only records checked against their source document are counted, at the stage the record supports, for a stated period and scope. How it is verified: the count is published before the area opens, republished every period after, and the counting method stands in full on the method page. The figures themselves are published at each area's opening, and not before: a scaffold filled with invented numbers would be exactly the claim this page exists to refuse.

Published at opening

Verified projects, pilot metro, prior period

Published at opening

Public sources read and recorded for the pilot

Published at opening

Records updated in the current period

Published at opening

Metros open for sale

How the count works   See launch pricing