The pre-RFP window is where positioning happens, where teaming gets formed, where past performance gets indexed against the upcoming program. Bridger surfaces every public signal in that window — appropriations actions, sources sought notices, RFIs, industry days, agency briefings, congressional hearings, and DoD contract announcements.
The pre-RFP window is built on top of the same intel-signal ingest pipeline that powers Bridger’s assessments and forecasts. Every signal is timestamp-indexed, country-coded, program-tagged, and source-cited, so the chain of evidence from “agency hearing on May 9” to “sources sought July 22” to “RFP September 14” is reconstructable in retrospect — and forecastable forward.
The platform’s assessment engine periodically clusters related signals into editorial assessments (“DoD’s autonomous-logistics pre-sol pattern points to a Q3 RFP under Tradewinds OTA”); these are the editorial output that goes into the daily Brief and the Pathfinder intelligence feed.
Anyone bidding on contracts where set-aside size, eval criteria, or vehicle selection is influenced by program-office preference. Which is most contracts.
Allied vendors specifically: pre-RFP signals often telegraph whether allied participation is solicited or excluded. The 22 CFR §126.7 ITAR exemption rollout is being read in pre-sol language right now.