ProcureMind

RFQ vs RFP vs RFI: What They Mean and When to Use Each

Here is the short version. An RFI (request for information) is how you learn about suppliers before you buy anything. An RFQ (request for quotation) is what you send when you know exactly what you want and you need a price. An RFP (request for proposal) is for complex purchases where how the supplier would do the work matters as much as what they charge.

Most buying done by a small business needs only one of these, and it is almost always the RFQ. This guide explains each document in plain English, puts them side by side, shows when a smaller operation should use which, and gives you an RFQ template that suppliers actually respond to.

In this guide:

What is an RFI?

An RFI, or request for information, is the document you send when you are exploring, not buying. You use it to find out who is in a market, what they can do, and roughly how they work, before you commit to anything.

Say you want to stop relying on the same two wholesalers for copper fittings. You do not yet know who else supplies your region, who keeps stock, or who delivers to site, so you cannot ask for a serious price yet. You send a short set of questions instead. What product ranges do you carry? What are your standard lead times and minimum orders? Do you offer trade accounts?

The RFI builds your shortlist, quietly prequalifies it (suppliers who cannot answer basic questions about their own business get crossed off early), and teaches you the vocabulary of the market, which makes every RFQ you send afterwards sharper.

An RFI is not a promise to buy, and suppliers know it. Keep it to ten questions or fewer and say plainly that you are gathering information ahead of future purchases. If the responses come back as PDFs and spreadsheets, our RFI extraction tool can pull the answers into structured fields so you can compare suppliers without retyping anything.

What is an RFQ?

An RFQ, or request for quotation, is what you send when you already know what you want, down to the specification, and the only real question left is price and terms. The RFQ meaning in procurement is simple: here is exactly what I need, tell me exactly what it costs.

The defining feature of an RFQ is that the specification comes from you, not the supplier. You are not asking "how would you approach this". You are saying: 500 lengths of 22mm copper tube, grade to this standard, delivered to this postcode by this date, quoted per unit with volume breaks at 250 and 1,000. Every supplier prices the same thing, which is the whole point. When the quotes come back, you can line them up and compare like for like.

That comparability is why the RFQ is the workhorse of small business purchasing. The supplier's answer is mostly numbers: unit price, extended price, lead time, freight, payment terms, validity. The decision is largely arithmetic plus judgement about reliability.

A worked example. You are a fit out contractor pricing a café job. You need 40 sheets of 18mm birch ply, 12 sheets of melamine board, and 200 metres of aluminium edge trim, delivered to site in Leeds by a fixed date. You send the same one page RFQ to four suppliers, and four quotes come back. One is cheapest but misses your install date on lead time. One is 4% dearer and delivers in three days with free freight. The decision takes ten minutes, because the RFQ forced everyone to answer the same questions.

What is an RFP?

An RFP, or request for proposal, is for purchases where the thing you are buying is not fully definable up front, and the supplier's approach is part of what you are paying for. Price still matters, but it sits alongside method, team, timeline, and track record.

Think about the difference between buying a pallet of screws and hiring a firm to run your IT for three years. The screws are an RFQ. The IT contract is an RFP, because two providers quoting the same monthly fee will deliver wildly different service. You need each one to explain how they would handle onboarding, who would actually do the work, and what similar clients they have served. Then you score the answers against criteria you decided in advance.

RFPs are the standard tool for services and complex projects: design work, software builds, facilities management, equipment with installation and commissioning. The document itself is heavier than an RFQ, typically covering your background, the problem you are solving, the scope as far as you understand it, the questions you want answered, and the evaluation criteria with their weightings.

That weight is a cost, and it cuts both ways. Writing a good RFP takes you days, and responding to one takes the supplier days too, which is why good suppliers decline RFPs that look like fishing exercises. If you can write the full specification yourself, you do not need proposals, you need prices.

RFQ vs RFP vs RFI: the comparison table

RFI RFQ RFP
Purpose Learn about suppliers and a market before buying Get a price for something you have fully specified Get a proposed solution to a complex problem
When to use it Entering a new supplier market, or you do not know who can supply you You know the exact item, spec, quantity and delivery terms Services and projects where method and track record matter as much as price
What the supplier answers Capabilities, ranges, lead times, terms, company background Unit price, extended price, lead time, freight, payment terms, validity Their approach, plan, team, timeline, references, and pricing
Typical length Half a page to one page, ten questions or fewer One page: line items plus terms Several pages: background, scope, questions, scoring criteria
How you decide Build a shortlist Compare prices like for like, check terms and reliability Score proposals against weighted criteria

The difference between RFQ and RFP is the one people mix up most: an RFQ assumes you have already made the technical decisions, and an RFP asks the supplier to help make them. Send an RFQ for something you cannot fully specify and you will get quotes for four different things. Send an RFP for a commodity and you will annoy every supplier on your list, then choose on price anyway.

Which one should a small business use?

Here is the honest answer for trades, contractors, and small ops teams: most of your purchasing only needs an RFQ. You buy defined things, from known categories, and the decision is price, lead time, and whether you trust the supplier to deliver. Anything heavier slows everyone down, and slow quotes cost you jobs.

Use an RFI when you are entering a supplier market you do not know. New material, new region, a category your usual wholesaler does not cover, or a push to stop depending on a single source. One round of RFIs to six or eight candidates and you have a shortlist that will serve you for years.

Use an RFP when the purchase is a service or a project where a bad choice is expensive to unwind. A maintenance contract, a firm to handle your bookkeeping, a fabricator for a complex one off structure. If the words "we will know a good job when we see it" apply, you are buying judgement, not goods, and you need proposals.

A ten second test: can you write down exactly what you want, in enough detail that two suppliers would quote the identical thing? If yes, send an RFQ. If no, ask whether you need information about the market (RFI) or ideas about the solution (RFP). Nine times out of ten, for a small business, the answer is the RFQ.

Common mistakes

These errors all have the same effect: worse answers, slower answers, or no answers at all.

  • Sending an RFP for a commodity buy. Ask a timber merchant for "a proposal outlining your approach to supplying sheet materials" and the good ones will ignore you or send padding you did not need. Match the document to the purchase.
  • No deadline. Suppliers triage their inbox by urgency, and an RFQ with no closing date reads as "quote it whenever". Give a realistic date: three to five working days for standard items.
  • No evaluation criteria. If you do not decide in advance what matters, price, lead time, terms, reliability, the decision gets made by whoever emailed back first. Write down your criteria before the quotes arrive, even if it is three lines in a notebook.
  • A vague specification. "20 sheets of plywood" is not a spec. Thickness, grade, standard, dimensions: leave any of it open and each supplier fills the gap with whatever suits their stock, and your comparison collapses.
  • Sending to too many suppliers. An RFQ to fifteen suppliers tells each one their odds are one in fifteen, and the sharp ones respond accordingly. Three to five is the sweet spot: enough competition to keep pricing honest, few enough that everyone thinks the work is winnable.
  • Not stating it is a live requirement. Suppliers get burned by tyre kickers. One line, "this is for a confirmed project starting in May", moves your RFQ up the pile.
  • Letting responses rot in the inbox. You asked four suppliers to do work for you by a deadline. If the replies sit unread for a fortnight, you have spent their goodwill for nothing, and next time the answers will be slower and the prices softer.

An RFQ template suppliers actually respond to

A good RFQ fits on one page and answers every question the supplier would otherwise have to email back to ask. Here is the structure that gets fast, complete replies:

1. Header. Your company name, contact name, email, phone. An RFQ reference number, even something simple like RFQ-2026-014, so both sides can refer to it later.

2. One line of context. What the purchase is for. "Materials for a confirmed fit out project in Leeds, install starting 12 May." This is the line that separates you from the tyre kickers.

3. The item table. One row per item: description, specification or standard, quantity, unit of measure. If the grade matters, name the grade. If a brand or equivalent is acceptable, say "or approved equivalent" so you get options.

4. Delivery. Full delivery address, required date, and any access constraints that affect freight cost. A quote that assumes forklift access when there is none is not a quote, it is a future argument.

5. What the quote must include. Spell it out: unit price and extended price per line, lead time, freight cost shown separately, payment terms, and quote validity period. This sentence is what makes the replies comparable.

6. Deadline and process. Closing date and time, how to submit (reply by email is fine), and when you expect to decide. "We will place the order by 28 March" is courteous and it speeds everyone up.

That is the whole document. No cover letter, no company history, no legal boilerplate for a routine buy. Suppliers respond to clarity, and every extra page is a reason to quote you tomorrow instead of today.

Once the replies land, the next problem is comparing them. We have a walkthrough with a ready to use layout in our supplier quote comparison template, which pairs well with the RFQ structure above.

How to track responses without chaos

An RFQ to four suppliers means four replies, and they never arrive in the same shape. One is a neat PDF, one is a spreadsheet, one is a scan of a handwritten price book, and one is a wall of text with the freight terms buried in paragraph six. Multiply that by every live job you are pricing.

The starting point is a spreadsheet, and honestly it covers a lot. One row per quote: supplier, RFQ reference, date received, total price, lead time, validity, notes. Sort by RFQ, then by price, and your comparison is mostly done. The failure mode is not the spreadsheet, it is the typing: every quote has to be read, interpreted, and keyed in by hand, and that is the hour of admin that does not happen on a busy week.

The next step up is pulling the data out of the emails automatically. ProcureMind is built for exactly this: it is a Chrome extension that reads supplier quotes, POs, BOMs and RFIs straight from Gmail and Outlook, extracts 23 structured fields per document with a confidence score on every field, and lets you review everything before it is saved. The output lands in Google Sheets or a branded Excel download, so the comparison spreadsheet above builds itself while the quotes are still arriving. The free plan covers 25 extractions a month with no credit card, enough to run it on one live project and see whether the time saving is real for you.

Whichever route you take, the discipline is the same: every quote logged, nothing compared from memory, every decision recorded with its reason. Six months from now, when a supplier asks why they lost or a client queries a price, that record is worth more than the few minutes it took to keep.

FAQ

What does RFQ stand for? RFQ stands for request for quotation. It is what a buyer sends when they know exactly what they want, item, specification, quantity, delivery, and need suppliers to come back with a price and terms. The RFQ meaning in procurement is simply: here is what I need, tell me what it costs.

What is the difference between an RFQ and an RFP? An RFQ assumes you have already made all the technical decisions, so the supplier only prices what you specified. An RFP is for complex purchases where you are also buying the supplier's approach, so they propose how they would solve your problem alongside their price. If you can fully specify the item yourself, send an RFQ. If you need the supplier's ideas and method, send an RFP.

When should I use an RFI instead of an RFQ? Use an RFI when you do not yet know the supplier market: who can supply you, what they carry, what their terms and lead times look like. It builds your shortlist before any money is discussed. Once you know who the credible suppliers are and what you want to buy, you move to an RFQ.

Do small businesses really need these documents, or are they just for big companies? Small businesses need them more, not less, because they have less slack for a bad buy. The difference is scale: a small business RFI is ten questions in an email, and a small business RFQ is one page with an item table. The formality is what makes supplier answers comparable, and that works at any size.

How many suppliers should I send an RFQ to? Three to five. Fewer than three and you have no real competition on price. More than five and each supplier's odds of winning drop enough that the good ones stop putting effort into their quotes. Quality of shortlist beats quantity every time.

How long should I give suppliers to respond to an RFQ? Three to five working days for standard materials and equipment is the norm, and always state the deadline in the RFQ itself. Complex fabricated items may need a week or more. A quote with no stated deadline drifts to the bottom of every supplier's inbox.

Send better RFQs, compare the replies without the admin. ProcureMind reads supplier quotes, POs, BOMs and RFIs straight from your Gmail or Outlook inbox, extracts 23 structured fields with confidence scores, and pushes everything to Google Sheets or a branded Excel download after your review. Free plan includes 25 extractions a month, no credit card, set up in two minutes. Start free.