What is the difference between RFI, RFP and RFQ?

RFI, RFP and RFQ are the three documents a company uses to question the market before buying, and they differ by how much the buyer already knows about what it wants. An RFI (request for information) fits when the problem is clear but the solution is not: it asks suppliers how they would approach it, with no commitment on either side, and it is the private-sector counterpart of the preliminary market consultation that Article 77 of the Italian public procurement code provides for. An RFP (request for proposal) comes once requirements are defined but the approach is still open: the supplier proposes method, team, timeline and price, and the choice rests on the whole package. An RFQ (request for quotation) assumes a specification that is already closed, where the variable that matters is price, with lead times and terms. Picking the wrong one is not a formal slip: it produces answers that cannot be compared with each other.

See also: RFQ automation · Automating the request-for-quote (RFQ) cycle by extracting specs from mixed documents and reconciling them against product master data.

Why the choice weighs more on an IT project

A batch of sheet metal or a laptop order can be described on a data sheet, and there an RFQ works. A software, data or AI project almost never can: until someone has decided what the system must do, with which data and at what quality threshold, a price request makes every supplier quote a different project. The lowest quote is usually the one that pictured the narrowest scope, and the difference comes back later as change requests. The healthy sequence is different: an RFI to learn which routes exist, an RFP with measurable success criteria to choose who and how, an RFQ only for the genuinely standard parts, such as licenses or infrastructure. If the problem is not yet clear enough even for an RFP, the right step is a short feasibility test, and the way to pay for it is the choice between time and materials or a fixed price.

An enterprise example

A manufacturing SME wants to read its customers' requests for quotation automatically, often PDFs and technical drawings that differ from one another, and sends three suppliers a two-line RFQ. Three quotes come back an order of magnitude apart, and none of them says the same thing: one priced a model to try out, one a system integrated with the ERP, one a monthly service. Done with method, the same tender starts with an RFI that clarifies the options, including full-blown RFQ automation, and continues with an RFP that sets a verifiable criterion, such as the share of documents processed with no manual correction on a sample of the company's own. Only then can the proposals be set side by side.

Why it matters for decision makers

The document you choose decides what you will be able to compare, so it has to be chosen before writing a line. Upstream sits the build or buy decision, which no RFx takes on the company's behalf. And a serious RFP also asks how you get out: ownership of code and data, delivery format, handover terms. That is where vendor lock-in gets prevented, far more than in the price negotiation.