RFI vs RFP vs RFQ: Which Procurement Document Do You Need?

These three get used interchangeably, and the confusion has a practical cost: asking for the wrong one produces responses you cannot use.

The distinction is about what you already know. Each document is designed for a different stage of certainty, and the mismatch between the document you send and the stage you are actually at is why so many procurement processes produce incomparable replies.

The short version

RFI — Request for Information. You do not yet know what is possible or who does this work. You are asking the market to educate you. Responses are informational; you are not selecting anyone.

RFP — Request for Proposal. You know the problem but not the best solution. You are asking suppliers to propose an approach and a price. Responses are evaluated on approach, experience and price together.

RFQ — Request for Quote. You know exactly what you want. You are asking for a price on a defined specification. Responses are compared largely on price, because everything else is fixed.

Put another way: an RFI asks what should we do, an RFP asks how would you do it and what would it cost, and an RFQ asks what would you charge for exactly this.

Request for Information

The most under-used of the three, and the most useful when you are genuinely early.

Use one when you do not know what the solution space looks like, when you need to understand rough cost ranges before asking for a budget, when you want to find out who works in your sector, or when you need to know whether what you have in mind is even feasible.

Ask about capabilities, comparable work, general approach, typical timelines and indicative cost ranges. Do not ask for a detailed proposal — you have not given anyone enough to propose against, and asking for one wastes their time and produces guesses.

Two rules of courtesy that are also self-interest. Say plainly that this is an RFI and no selection will be made from it, so nobody over-invests. And say whether an RFP is likely to follow, because that is what determines how seriously firms engage.

The most common misuse is running an RFI when you already know what you want, in order to gather free consulting. Suppliers recognise it and respond accordingly.

Request for Proposal

The right document for most website projects, because a website rebuild is precisely the case where you know the problem and are buying expertise about the solution.

Use one when the outcome matters more than the exact method, when suppliers will differ meaningfully in approach, when you want to evaluate on more than price, and when the work is complex enough that how it is done affects whether it succeeds.

An RFP describes the problem and the constraints and invites an approach. That is the whole point, and it is where most website RFPs go wrong: they over-specify the solution, dictating a stack or a design direction, which converts the exercise into an RFQ with extra paperwork and discards the expertise you were trying to buy.

If you find yourself writing an RFP that specifies exactly what is to be built, ask whether you actually want an RFQ. If you do, write one — it is a shorter document and a faster process.

Request for Quote

Appropriate when the specification is genuinely complete and the only open question is price.

For website work that is rarer than people assume, but it does happen: a defined maintenance retainer, a fixed number of pages migrated to an existing template, a licence renewal, hosting for a known configuration, a specific integration against documented APIs.

The test is simple. Could two competent suppliers read your specification and build substantively the same thing? If yes, an RFQ works. If they would reasonably produce different things, you need an RFP, and an RFQ will get you prices for different work presented as if comparable — which is worse than useless, because it looks like a fair comparison.

Related terms you may meet

RFT, Request for Tender, is used mainly outside the US and in public procurement, generally in the RFP-to-RFQ range with a formal process attached.

ITB, Invitation to Bid, is typically an RFQ by another name, common in construction and government.

EOI, Expression of Interest, functions as a pre-qualification step: who is interested and capable, before a fuller process. It sits close to an RFI.

Terminology varies by sector and country. If a solicitation's label and its contents disagree, the contents win — read what is actually being asked for.

Chaining them

Larger organizations often run these in sequence, and the sequence is genuinely useful when the project is big enough to justify it.

An RFI establishes the landscape and rough costs. That informs a business case and a budget. An RFP then goes to a shortlist drawn partly from RFI respondents. For a large programme, an RFQ might follow for specific defined components once the approach is settled.

For most website projects this is too much machinery. A single well-written RFP to three to five shortlisted agencies is the right shape, and for smaller projects a one-page brief is better still — we cover when each applies in do you actually need an RFP.

Choosing, in three questions

Do you know what you want built, in enough detail that two suppliers would build the same thing? If yes, RFQ.

If no: do you know what problem you are solving and roughly what it is worth? If yes, RFP.

If no to both, you are at the RFI stage — or you need internal discovery before you approach the market at all, which is often the honest answer and always cheaper than finding out through proposals.

When you get to the RFP stage, our template pack has the editable document, a requirements checklist and a scoring sheet, and you can send us the result.