Guide
RFI vs RFP vs RFQ: what each one is and which to send
An RFI (request for information) asks vendors to describe what they offer so you can learn the market. An RFP (request for proposal) asks them to propose how they would solve a problem you have defined, and at what price. An RFQ (request for quotation) asks for a price on something you have already specified exactly.
The rule of thumb: send an RFI when you do not know the options, an RFP when you know the problem but not the solution, and an RFQ when you know the exact item and only price and terms differ.
Updated November 17, 2026 ยท 12 min read
Key takeaways
- RFI = learn. No commitment, no price comparison, the output is a shortlist.
- RFP = choose an approach. Vendors propose a solution; you score them on several weighted criteria, price is only one of them.
- RFQ = choose a price. The spec is fixed; the lowest compliant quote usually wins.
- They are often used in sequence (RFI, then RFP or RFQ), but a small company rarely needs all three for one purchase.
- A fourth option, publishing an open need and letting vendors come to you, works when you do not even know who to invite.
The three documents, defined
What is an RFI (request for information)?
An RFI is a short questionnaire sent to several vendors to find out what exists, what it roughly costs, and who can deliver it. It is a research tool, not a buying tool. You are not promising to buy anything, and vendors are not expected to submit binding prices. A good RFI ends with a shortlist of three to five vendors worth a deeper look.
What is an RFP (request for proposal)?
An RFP describes a business problem, your goals, constraints and budget range, and asks each vendor to propose a solution: their approach, team, timeline and price. Because every vendor proposes something slightly different, you cannot compare RFP responses on price alone. You compare them on weighted criteria, which is why an RFP needs a scoring sheet before it goes out (see our vendor evaluation criteria and scorecard).
What is an RFQ (request for quotation)?
An RFQ lists exactly what you want to buy (item, specification, quantity, delivery date, terms) and asks vendors for a price. Because every vendor quotes on the same spec, responses are directly comparable, and the award usually goes to the lowest quote that meets every requirement. RFQ is sometimes expanded as "request for quote"; it is the same document.
RFI vs RFP vs RFQ: side-by-side comparison
The single biggest difference is how much you already know when you send it. Everything else in the table follows from that.
| RFI | RFP | RFQ | |
|---|---|---|---|
| Purpose | Learn what is available and who offers it | Pick the best solution to a defined problem | Get the best price and terms for a defined item |
| When | Early, before you have a budget or a spec | Once the problem, goals and budget range are clear | Once the exact spec and quantity are fixed |
| What you know | The problem, vaguely | The problem and the outcome you want, not the method | Exactly what you need, down to model or scope |
| What vendors send back | Capabilities, company facts, pricing model, indicative ranges | A tailored proposal: approach, team, timeline, references, price | A priced quote with line items, validity date, delivery and payment terms |
| Evaluation basis | Fit and credibility; no winner, just a shortlist | Weighted scorecard (approach, experience, team, price, risk) | Lowest compliant price, sometimes with delivery time as a tiebreaker |
| Typical length (your document) | 1 to 3 pages, 10 to 20 questions | 4 to 15 pages for a small company; much longer in enterprise and public sector | 1 to 2 pages or a single spec table |
| Typical response time | 1 to 2 weeks | 2 to 6 weeks, plus a Q and A window | 3 to 10 business days |
| Commitment | None on either side | You commit to a fair process; contract is negotiated after selection | Quotes are often firm for a stated period; accepting one can form the order |
Lengths and response times are typical ranges for private-sector purchases by small and mid-sized companies. Public tenders follow their own legal timelines.
Which one should you send? A decision flowchart
Answer the questions in order and stop at the first one that gives you an answer.
Step 3 is where most people go wrong. "Website redesign" can be written as a spec, but two agencies meeting that spec will produce very different websites. That is an RFP. "Forty laptops of model X with a three-year on-site warranty" produces the same laptops whoever delivers them. That is an RFQ.
Real examples for small companies
Most RFx guides are written for enterprise procurement teams. Here is how the three documents look when the buyer is a 20 to 200 person company with no procurement department.
RFI example: exploring AI tools for customer support
Your support team spends most of its day answering the same questions, and someone suggested "an AI tool". You do not know whether that means a chatbot, an agent-assist tool inside your help desk, or a full outsourced service, and you have no idea what any of it costs. That is RFI territory.
- Send to: 6 to 10 vendors from different categories, so you learn the shape of the market, not just one product type.
- Ask: what problem the product solves, which help desks it integrates with, how it uses and stores your ticket data, pricing model (per seat, per resolution, flat), typical setup time, and two comparable customers.
- Outcome: you learn that per-resolution pricing exists, that two vendors cannot integrate with your help desk, and that data handling varies a lot. You shortlist three and move to an RFP or straight to paid pilots.
RFP example: choosing an SEO agency
You know the problem (organic traffic flat for a year, few inbound leads) and the outcome you want (more qualified demo requests from search), but not the method. One agency will push technical fixes, another content, another link building. Their prices will not be comparable without context. That is an RFP.
- Send to: 3 to 5 agencies. More than that and you will not read the answers properly.
- Include: current traffic and lead numbers, what you tried before, budget range, decision date, who will work with the agency internally, and how you will score.
- Score on (example weights): approach and diagnosis 30, relevant experience 25, team actually doing the work 15, price and pricing model 20, references 10.
- Outcome: a winner, a negotiated statement of work, and polite notes to the others (our vendor rejection letter templates cover that step).
RFQ example: buying 40 laptops
IT has already chosen the configuration: 14 inch screen, 16 GB RAM, 512 GB SSD, the operating system your device management needs, three-year next-business-day on-site warranty, delivered and pre-enrolled by a fixed date. Any reseller meeting that spec delivers identical machines. That is an RFQ.
- Send to: 3 or 4 resellers.
- Ask for: unit price, total including shipping and tax, delivery date, warranty terms, payment terms, and how long the quote is valid.
- Compare: total landed cost, not unit price. A cheaper unit price with paid shipping and 14-day payment terms can lose to a slightly higher one with free delivery and 30-day terms. Our guide to comparing vendor quotes has a side-by-side template.
When you use two of them in a row
The classic sequence is RFI to narrow the field, then RFP or RFQ to choose. For the AI tools example you might run an RFI, then an RFP with the three shortlisted vendors. For laptops you would skip the RFI entirely, because you already know the market. If you are new to running a full selection, the vendor selection process guide puts these steps in order.
RFQ vs RFP: the differences that actually matter
RFQ vs RFP is the comparison people get wrong most often, because both end with a price. Four differences decide which you need:
- Who writes the spec. In an RFQ you write it. In an RFP the vendor writes it as part of the proposal.
- How the winner is picked. RFQ: lowest price that meets every requirement. RFP: best overall value against weighted criteria, which can be a more expensive bid.
- What happens after. An accepted RFQ often becomes the purchase order almost unchanged. An RFP is usually followed by negotiation and a statement of work.
- Effort. An RFQ costs vendors an hour. A serious RFP response can cost a vendor days, so sending one for a small purchase gets you fewer and weaker answers.
Copy-ready outlines for an RFI, RFP and RFQ
These are deliberately short. A small company that sends a 40-page RFP gets answers from vendors who specialize in answering RFPs, not from the ones who are good at the work.
RFI outline
RFP outline
RFQ outline
The fourth option: publish an open need and let vendors come to you
RFIs, RFPs and RFQs all assume you already know which vendors to invite. Often you do not. A "request for pitches" flips the direction: instead of hunting for suppliers, you publish a short public brief and let any qualified vendor answer it in a fixed format.
- The brief: what you are looking for, rough budget, deadline, and the three or four facts every answer must contain (service, scope, price, availability).
- Where it goes: your website, your LinkedIn, a supplier page, or a link you paste into replies to vendors who contact you anyway.
- Why it works: it reaches vendors you would never have found, and because the format is fixed, answers stay comparable, which is the main thing an RFQ gives you.
- The catch: you will get volume. You need a way to filter out senders without a real business and to keep every answer in one place instead of scattered across inboxes.
This is what buying needs do in PitchBin: you publish "we are looking for X" as its own link, vendors submit company, service and price in a structured form, only senders with a confirmed work email get through, and matching offers are tagged and counted against the need. Offers that arrive by cold email can be forwarded to save@pitchbin.com and land in the same catalog, so the shortlist for your next RFP may already exist before you write it.
Common mistakes buyers make
- Sending an RFQ for something that is really an RFP. You get comparable prices for non-comparable work, pick the cheapest, and discover the difference after signing.
- Sending an RFP when you have not decided to buy. Vendors invest days in proposals; if you are still exploring, say so and send an RFI instead.
- Hiding the budget. Without a range, RFP answers spread across a factor of ten and you cannot compare them. A range costs you nothing.
- Scoring after reading. Decide the criteria and weights before responses arrive, or the most charming proposal wins.
- Inviting too many vendors. Three to five for an RFP is plenty. Ten responses you skim are worse than four you read.
- Answering one vendor's question privately. Share every clarification with all bidders, or the process stops being fair and good vendors stop bidding.
- Forgetting the losers. Vendors who never hear back do not bid next time. A two-line "not this time" keeps them in your pool.
- Skipping the checks on the winner. Picking a vendor is not the same as vetting one. Run proportionate vendor due diligence before you sign.
Frequently asked questions
What is the main difference between an RFI, RFP and RFQ?
How much the buyer already knows. An RFI gathers information when you do not know the options, an RFP asks for proposed solutions when you know the problem, and an RFQ asks for prices when you know the exact item.
Is an RFQ the same as a request for quote?
Yes. Request for quotation and request for quote are the same document. In construction and engineering, RFQ can also mean request for qualifications, so check the context.
Which comes first, RFI or RFP?
The RFI comes first. It narrows the market to a shortlist, and the RFP then goes only to the shortlisted vendors. If you already know the vendors, skip the RFI.
Can I send an RFP and an RFQ for the same project?
Not usually at the same time. A common pattern is an RFP to choose the approach and vendor, then an RFQ later for repeat or standard items once the spec is fixed.
Is an RFP response legally binding?
Usually not by itself. The binding contract is normally signed after selection and negotiation. A quote with a stated validity period can be closer to a binding offer. This depends on the wording and local law, so it is not legal advice.
Does a small business need a formal RFP?
Only for purchases where vendors would deliver different results and the spend matters. For small, standard purchases, asking two or three vendors for a quote by email and keeping the replies is enough.
Keep reading
Have vendors answer your need in one format.
Publish a buying need as a link, collect offers with service and price filled in, and keep every quote in one searchable company catalog. Free for buyers.