Three of the most confused documents in procurement do three completely different jobs. An RFI gathers information, an RFP invites a solution, and an RFQ requests a price. Pick the wrong one and you either over-burden suppliers or buy on the wrong criteria. This guide explains each document, the order they belong in, and how to choose for any sourcing event.
Last updated: · Reviewed by Fredrik Filipsson
Same prefix, three different jobs. The distinction comes down to what you are asking suppliers to send back.
The simplest way to keep these straight is to remember what each one asks for. An RFI asks “what is possible, and who can do this?” An RFP asks “how would you solve our problem, and at what value?” An RFQ asks “what is your price for exactly this?” Each request collects a different kind of answer, which is why using the wrong one quietly sabotages an otherwise sound sourcing process.
The three documents also sit at different points on a spectrum of certainty. At one end you know almost nothing about the market and the requirement is vague, which is RFI territory. At the other end you have a complete, unambiguous specification and the only open question is price, which is what an RFQ is built for. The RFP lives in the middle: you know the problem you need solved but you want suppliers to bring the “how.” Map your situation onto that spectrum and the right instrument usually becomes obvious.
A reconnaissance tool. The RFI is how you learn what the market can do before you commit to a formal competition.
A Request for Information is a structured way of asking suppliers to tell you about themselves and their capabilities. You are not buying anything yet, and you are not asking for a binding price. Instead you are collecting the intelligence you need to scope a future RFP or RFQ: which vendors operate in this space, what approaches exist, roughly what a solution might cost, and which suppliers are even worth inviting to the next stage. Treat it as the discovery phase of a larger supplier selection process.
A typical RFI asks open questions: company background, relevant experience, certifications, geographic coverage, high-level capabilities, and reference customers. Because the goal is breadth rather than depth, you can issue an RFI to a wide field without imposing a heavy response burden. Suppliers can answer in a few hours rather than the weeks a full proposal demands, which is exactly why you should not ask for detailed pricing or solution design at this stage.
The output of an RFI is knowledge and a shortlist, not a winner. You should finish the exercise able to describe the market in your own words and confident about which three to eight suppliers deserve a place in the next round. If you already have that knowledge, an RFI adds delay without adding value, which is why experienced buyers skip it for familiar categories. For a deeper walk-through, see our companion guide on what an RFI is.
The workhorse of complex sourcing. An RFP invites suppliers to propose how they would solve a defined problem.
A Request for Proposal sets out a problem, a set of requirements, and a way of being evaluated, then asks suppliers to respond with a complete solution. The defining feature of an RFP is that you are not prescribing the answer. You describe the outcome you need and the constraints you operate under, and you let suppliers compete on approach, methodology, implementation plan, team, support model, and price together. That openness is the whole point: it surfaces options you would never have specified yourself.
Because proposals differ on many dimensions, an RFP is scored against weighted criteria rather than a single number. A well-built scoring model might weight solution fit, technical approach, implementation risk, support, references, and commercial terms, with price as one factor among several rather than the deciding one. This is what distinguishes an RFP from a price-only exercise, and it is why RFPs dominate services, software, and any purchase where execution quality matters as much as cost. Getting the structure right is its own discipline, covered in our guide on how to write an RFP.
RFPs are heavier for everyone involved. Suppliers invest real effort to respond, and your team invests real effort to evaluate fairly, so the tool is best reserved for decisions where that investment pays off. When the requirement is genuinely open-ended, an RFP is the only instrument that lets the market show you what good looks like. Our deeper explainer on what an RFP is covers the anatomy of a strong proposal request, and our research on strategic sourcing AI looks at how teams are accelerating the evaluation stage.
The precision instrument. An RFQ asks for a firm price against a specification that leaves nothing open.
A Request for Quotation is what you issue when you already know exactly what you want and the only open question is the commercial one. You provide a precise specification — quantities, technical requirements, delivery dates, service levels, payment terms — and ask suppliers to return a firm quote. Because the requirement is fixed, suppliers compete almost entirely on price, lead time, and terms, which makes the responses directly comparable and the decision fast.
The discipline of an RFQ lives in the specification. If your spec is incomplete or ambiguous, you will receive quotes that are not comparable, and the apparent winner may simply be the supplier who interpreted the gaps most cheaply. That is the single most common RFQ failure, and it is the clearest signal that you should have run an RFP instead. When you cannot write a complete specification, the RFQ is the wrong tool. Our explainer on what an RFQ is covers how to build a spec that produces apples-to-apples quotes.
RFQs are the natural fit for direct materials, commodities, repeat purchases, and any well-understood requirement bought at scale. They also pair naturally with e-auctions and optimization, where the fixed specification lets software evaluate hundreds of bid combinations. This is the territory where sourcing-optimization specialists such as Keelvar add the most measurable value.
The same six questions, answered three ways. This is the comparison most buyers come for.
| Dimension | RFI | RFP | RFQ |
|---|---|---|---|
| Purpose | Gather market and capability information | Invite suppliers to propose a solution | Obtain firm prices against a fixed spec |
| Question it answers | What is possible, and who can do this? | How would you solve our problem, and at what value? | What is your price for exactly this? |
| Stage in sourcing | Earliest — discovery and shortlisting | Middle — solution evaluation | Latest — final commercial decision |
| Level of pricing detail | None to indicative (budgetary ranges) | Priced, but evaluated alongside other factors | Firm, itemized, directly comparable |
| When to use | Unfamiliar market or undefined requirement | Open-ended solution; quality matters as much as cost | Complete specification; decision is essentially price |
| Typical output | Market knowledge and a supplier shortlist | Comparable solution proposals, scored on weighted criteria | Comparable quotations ranked on price and terms |
Key takeaway: as you move from RFI to RFP to RFQ, the supplier field narrows, the specification tightens, and price weight rises.
Running a live sourcing event? See which AI agents draft and evaluate RFx faster.
RFP & Sourcing AI AgentsWhen all three appear in one event, they form a funnel — each stage narrows the field and sharpens the detail.
For a large, unfamiliar, or high-stakes category, the three documents chain together logically. You begin with an RFI to scan a broad market and reduce a long list of possible suppliers to a credible shortlist. You then issue an RFP to that shortlist, asking them to propose solutions and competing on approach and value. Finally, with one or two finalists selected, you run an RFQ to pin down firm pricing and commercial terms before contracting. Each step costs more effort than the last, so narrowing the field first keeps the expensive stages focused on serious contenders.
The sequence also manages risk. By the time you reach the RFQ, the specification is mature precisely because the RFI taught you the market and the RFP forced you to define the solution in detail. Skipping straight to an RFQ on a poorly understood requirement is the classic way buyers end up with the cheapest non-comparable quote rather than the best outcome. The funnel exists to prevent exactly that mistake.
That said, the full chain is the exception, not the rule. Many events run a single RFP. Many repeat purchases need only an RFQ. Some discovery efforts end at the RFI when the conclusion is “build internally” or “no viable supplier yet.” Treat the sequence as a menu sized to the decision in front of you, not a checklist to complete for its own sake. Our wider 2026 negotiation and sourcing AI market analysis shows how teams are compressing these stages with automation.
Match the document to your level of certainty and the nature of what you are buying.
Are entering an unfamiliar category, cannot yet describe the solution, or face a supplier field too large to evaluate in detail. The RFI educates you and produces a shortlist. Skip it when you already know the market and your requirement is clear.
Are buying a service, software, or a project where the “how” is open and execution quality matters. You want suppliers to propose an approach and you will score on weighted criteria. Choose an RFP whenever you cannot write a complete fixed specification.
Know precisely what you need, can specify it without ambiguity, and the differences between suppliers come down to price, lead time, and terms. Ideal for direct materials, commodities, and repeat purchases where the spec is settled.
A useful tie-breaker: ask whether you could write a specification complete enough that two suppliers would price it identically if their costs were identical. If yes, you have an RFQ. If the answer depends on each supplier's judgment and approach, you have an RFP. If you cannot answer the question at all, you need an RFI first. For ongoing category strategy, our coverage of strategic sourcing AI tracks how analytics tools inform that judgment.
The mechanics of RFI, RFP, and RFQ are exactly the kind of structured, repetitive work that AI agents now accelerate.
The cost of running RFx has always been the manual labor: drafting documents from scratch, chasing supplier responses, normalizing answers into comparable form, and scoring them consistently. Modern sourcing platforms attack each of those steps. AI drafting tools generate first-pass RFI questionnaires and RFP requirement sets from a short brief and a category template, cutting days of authoring to hours. Based on our analysis of the category, that drafting acceleration is where most teams see the fastest payback.
On the evaluation side, AI extracts and structures free-text proposal responses so reviewers compare like with like, and it flags gaps or non-compliant answers automatically. For RFQs, sourcing-optimization engines evaluate large numbers of bid scenarios — volume splits, multi-award combinations, freight and capacity constraints — far beyond what a spreadsheet can handle. Specialists such as Keelvar focus on that optimization layer, while broader source-to-pay suites such as Jaggaer embed RFx authoring, supplier collaboration, and award analysis in one workflow.
The judgment of which document to use, how to weight criteria, and which trade-offs matter still belongs to the buyer. What changes is the time spent on mechanics, which our analysis suggests can fall substantially across drafting, response management, and scoring. To compare the tools that handle each stage, browse our directory of RFP and sourcing AI agents.
RFI, RFP, and RFQ are not competing options to choose between — they are three instruments for three different moments in a sourcing decision. The mistake that costs buyers the most is treating them as interchangeable: forcing a price-only RFQ onto an open-ended requirement, or burdening a wide market with a full RFP when a quick RFI would have produced the shortlist faster.
The deciding question is almost always certainty. If you cannot describe the solution, run an RFI and learn the market. If you can describe the problem but not prescribe the answer, run an RFP and let suppliers compete on value. If you can write a complete, unambiguous specification, run an RFQ and decide on price and terms. When the stakes justify it, chain all three into a funnel; when they do not, use the single document that fits.
Across our analysis of sourcing teams, the ones that move fastest are disciplined about this choice and increasingly let AI absorb the mechanical work of drafting, collecting, and scoring. That frees buyers to spend their time on the parts that actually move outcomes — specification quality, criteria weighting, and negotiation.
Start with the document that matches your level of certainty, and add the stages before it only when the decision warrants the extra rigor.
Common questions from sourcing teams choosing between the three documents.
Go deeper on each document and the sourcing process around them.