A request for information (RFI) is a document a buyer sends to the market to learn what solutions, suppliers and costs exist before deciding how to buy.
Public procurement · Reviewed by Ray Rasouli
Ask about request for information (RFI)
Plain answers, with your setup in mind.
Ask anything about request for information (RFI). For example, how it works in your current tools.
A scripted guide for now. It does not store what you type.
An RFI is a research step, not a purchase. The buyer describes a problem or goal and asks suppliers to share what they offer, how they would approach it and rough costs. Nobody wins a contract from an RFI.
A regional health authority thinking about replacing its inventory system might issue an RFI first. Responses show which products fit, what similar organisations use and what timelines are realistic. That helps the authority write a sharper RFP later.
For suppliers, answering an RFI is a chance to help shape the requirements and get noticed early. For buyers, it reduces the risk of writing an RFP that asks for something nobody sells or that costs far more than planned.
In practice
Suppliers treat it as a sales pitch.
Glossy brochures do not answer the buyer's specific questions and get set aside.
Buyers ask for too much detail.
Long RFIs discourage replies, especially from smaller firms.
Information is not kept confidential.
Suppliers may hold back useful detail if they fear it will be shared with competitors.
Usually not. Most buyers let any qualified supplier bid on the later RFP, but responding helps you understand the need early.
An RFI gathers information to plan a purchase. An RFP asks for formal proposals that can lead to a contract.
A 30-minute discovery call with Ray, then a clear list of what to fix first. No obligation.
With Ray Rasouli. No obligation.