Some gear care RFPs never post publicly. A private brigade, or a department running an invited process, can send the RFP straight to a few suppliers it knows. The RFP skips the portal, and a supplier either has the relationship to receive it or never sees it.
Why it skips the portal
A private buyer controls who receives its RFP, and even some public buyers run invited processes for specialized gear care. The package can be as detailed as any public bid, with the care standard, the verification, and the equipment or service terms, but it arrives by invitation.
What handles it
Once the RFP lands, the work is to answer it well and on time. The response agent reads the full package, builds the requirements matrix against the care standard, scores the go or no go, and drafts from past work. the bid response agent reads the full private RFP the moment it lands.
How the two work together
Our discovery agent surfaces the public fire work a supplier can find, and the response agent handles the private and invited RFPs that arrive directly, so a supplier is covered whether the work is published or not.
The agent is honest about the off portal RFP and hands it to the response side to answer. See the fire turnout gear bid agent in the interactive demo.