The Difference in One Paragraph
An RFI explores a market, an RFP evaluates solutions, and an RFQ prices a known specification — while “RFx” is the umbrella term for all of them. If you do not yet understand the supplier landscape, you issue a request for information. If you know the need but not the best approach, you issue a request for proposal. If you know exactly what you want and only need a price, you issue a request for quotation. Choosing the wrong one is one of the most common — and most expensive — mistakes in sourcing, because it sets the entire event up to answer the wrong question.
Key takeaways
- RFI — exploratory; gather information and shortlist suppliers. Not a buying decision.
- RFP — evaluate how suppliers would solve a defined need; scored on value, not price alone.
- RFQ — obtain prices on a precise specification; scored mainly on cost.
- RFx — the collective name for all request documents (also covers RFT, request for tender).
- Pick by question: are you exploring a market, comparing solutions, or pricing a spec?
RFx: The Umbrella Term
RFx is shorthand for the whole family of formal sourcing requests — RFI, RFP, RFQ and related variants such as the RFT (request for tender), common in public-sector procurement. The “x” is a wildcard. You will see the term most often in software, where e-sourcing platforms describe their capability as “RFx management” because they handle all request types through one workflow.
Using “RFx” is appropriate when you are talking about the request process generically — how events are built, distributed, and evaluated — rather than a specific document. When precision matters, name the actual instrument. The tools that run these events are tracked in our RFP & sourcing AI category and the broader strategic sourcing AI category.
RFI: Request for Information
An RFI is exploratory. You issue it when you do not yet know enough about a market, a technology or a set of potential suppliers to run a meaningful competition. It asks broad, open questions: what do you offer, what is your scale, who are your reference clients, what is your approach? The output is understanding and a shortlist — not a contract.
The most important thing to know about an RFI is what it is not: it is not a price request and not a commitment. Suppliers expect an RFI to inform a later RFP or RFQ, and treating it as a covert price negotiation erodes trust and depresses response quality. Use it when you are entering unfamiliar territory; skip it when you already know the qualified field.
RFP: Request for Proposal
An RFP asks shortlisted suppliers how they would meet a defined need, and invites them to propose an approach. It is the right instrument when the requirement is complex and the best solution is not obvious — professional services, software platforms, engineered solutions, outsourced operations. Crucially, an RFP is evaluated on value: a weighted blend of price, capability, approach, risk and fit, not lowest cost alone.
A good RFP states the problem and the evaluation criteria clearly enough that suppliers can differentiate themselves, while remaining structured enough to compare responses fairly. That tension — open enough to invite good ideas, structured enough to score — is what makes RFPs hard to write well, and exactly where AI drafting and response-scoring tools now help. Our guides on AI RFP management for sourcing events and using generative AI to write an RFP go deeper on that workflow.
RFQ: Request for Quotation
An RFQ asks for a price on something you have already specified precisely. There is little room for suppliers to propose a different approach — the specification is fixed, and the competition is mostly on cost (with delivery, terms and qualification as gates). Use it for defined commodities, standard parts, or clearly scoped services where the only open variable is price.
Because the question is narrow, RFQs are the most automatable of the three. They are the natural home of autonomous and optimisation-driven sourcing — tools such as those profiled at Keelvar (sourcing optimisation) and Fairmarkit (automated tail-spend RFQs) can run large volumes of quotation events with limited human involvement, which is why the RFQ is where AI has moved fastest.
Side-by-Side Comparison
| Dimension | RFI | RFP | RFQ |
|---|---|---|---|
| Primary purpose | Explore & shortlist | Evaluate solutions | Price a known spec |
| Maturity of need | Vague / emerging | Defined, approach open | Fully specified |
| Evaluated mainly on | Fit & capability | Value (price + quality) | Price |
| Supplier effort | Low–moderate | High | Low |
| Best for | Unfamiliar markets | Complex / services | Commodities, standard parts |
| AI maturity | Moderate | Growing fast | High (often autonomous) |
The table makes the selection logic concrete: move left to right as your need becomes more defined. The mistake to avoid is running an RFP when an RFQ would do (wasting supplier effort and your evaluation time on a commodity) or an RFQ when an RFP was needed (forcing a complex solution into a price-only frame and getting the wrong answer cheaply).
How They Fit Together
These instruments are not mutually exclusive; they often sequence. A typical complex sourcing event for an unfamiliar category runs RFI → RFP, using the information request to build a qualified shortlist before the heavyweight proposal stage. A well-understood commodity may skip straight to an RFQ. A large strategic deal might run RFI → RFP → a final RFQ-style price round with the down-selected finalists.
The art is using the lightest sequence that produces a defensible decision. Every stage you add buys rigour at the cost of weeks and supplier goodwill, so add stages deliberately, not by habit. This is the same discipline that defines a mature sourcing function in our CPO strategic guide, and it connects directly to how much of your spend ends up governed — the subject of our spend under management guide.
How AI Is Changing the RFx Workflow
AI now touches every stage of the request lifecycle. On the buy side it drafts RFx documents from a stated requirement, generates and de-duplicates supplier questionnaires, normalises and scores responses, and summarises long proposals into comparable briefs. For RFQs over well-defined categories, autonomous sourcing can run entire events — issue, collect, optimise, recommend — with a human only approving the award.
The strategic consequence is not just speed; it is reach. When running a formal event becomes cheap, categories that were never worth sourcing — the long tail — suddenly are, which raises competition and savings across spend that used to escape the process entirely. The state of that shift across vendors is part of the picture in our State of Procurement AI 2026 report. AI does not change what an RFI, RFP or RFQ is for — it changes how many you can run and how fast.
Frequently Asked Questions
Is an RFP always more formal than an RFQ?
Generally yes in effort, but not in legal weight. An RFP involves more supplier work because it asks for a proposed solution, while an RFQ is lighter because the spec is fixed. Either can be binding depending on how it is written and the jurisdiction.
Can a single document combine them?
In practice, yes — many events blend elements, asking for both an approach (RFP-style) and firm pricing (RFQ-style). The labels describe intent; real events sit on a spectrum. What matters is being clear with suppliers about how responses will be evaluated.
What about RFT?
An RFT (request for tender) is essentially a formal, often public-sector RFP/RFQ with stricter process and compliance requirements. It falls under the RFx umbrella and follows the same underlying logic of specifying a need and competing suppliers against it.
Which one should beginners default to?
Default to the question, not the document. Ask whether you are exploring (RFI), comparing solutions (RFP) or pricing a known spec (RFQ). Naming the question first makes the choice obvious and prevents the most common errors.