Product / Pursue · Stream 2 of 3
You find out a teammate cannot comply after the bid closes.Pursue moves that check to the front.
Pursue reads a solicitation the way Assure reads an award: derive the requirements, then screen your prospective team against them before you commit capture hours.
This is on the roadmap, not shipped. The page below shows the shape of what Pursue derives once it is live, using the same obligation engine Assure runs today with Design Partner Program accounts and Founding Cohort members.
One obligation engine
Solicitation in. Requirements out. Team pre-screened.
Pursue points the engine at a sought award, not an active one: the solicitation, the requirement set it derives, and the teammates screened against it.
Product concept · illustrative record, fictional entities
What Pursue will run
The differentiator for the teaming decision.
Assure is the stream you are required to run. Pursue is the one that changes which awards you chase, and with whom.
Solicitation to requirements
Pursue reads the solicitation and derives the real requirement set: the clauses, certifications, and thresholds your team would actually inherit if you win.
Can-comply pre-screen
Every prospective teammate is checked against the derived requirement set while bid/no-bid is still open, so the gap surfaces before the commitment, not after.
Capture hours protected
A pursuit that dies on a teammate’s compliance gap costs the same capture hours as one that wins. Pursue moves that discovery to the first week, not the last.
Help shape Pursue before it ships.
Design Partner Program accounts get the Pursue build as it lands, and a direct line into what it derives first. Assure is available today to Design Partner Program accounts and Founding Cohort members; Pursue joins it on the same engine.