What this capability changes
A pursuit record can hold decision criteria, owners, actions, evidence gaps, deadlines, clarifications and approval status.
Qualify, assign, plan and track opportunities without exporting the search result into disconnected spreadsheets. The design starts with a commercial question and preserves the trail back to the authoritative record, instead of forcing a team to trust a relevance label it cannot inspect.
How it works in the platform
Role-based access, audit events and source links keep opportunity intelligence distinct from confidential bid content.
Source identity, observation time, transformations and user decisions remain separate fields. That distinction allows the product to update a notice without erasing what a user saw when a pursuit decision was made.
Production controls
The reference implementation exposes API contracts and a clean extension path for document and workflow integrations.
Deployment begins with a source register, access roles, retention rules and measurable acceptance criteria. Features that depend on customer systems or third-party rights remain disabled until those dependencies are approved.