RFQ vs RFP vs RFI: Differences, Examples and How to Reply

An RFI asks what you can do, an RFQ asks what it costs, and an RFP asks how you would solve the problem. Buyers send an RFI when they are still learning the market, an RFQ when they know exactly what they want and need a price, and an RFP when they need suppliers to design the solution.

Most guides to these three are written for the buyer deciding which document to send. This one is written for the supplier on the receiving end: how to tell which one just landed in your inbox, what each is really asking, and how to answer it well. If quote requests are the ones piling up, our page on RFQ software for inbound quote requests covers the tooling side.

Key takeaways

• RFI: the buyer is exploring. Answer briefly, show fit, and ask the question behind the question.
• RFQ: the buyer has decided what they want. Speed and a clear, complete price matter most, because the first full answer sets the benchmark.
• RFP: the buyer wants a solution. Decide go or no-go first, because a proper response takes real time.
• Many RFQs never say "RFQ". They arrive as ordinary emails asking for price and availability, and they get buried with everything else.
• A US federal quotation is not an offer (FAR 13.004(a)). Commercial quotes can bind you once accepted, so every quote needs a validity period and terms.

RFQ vs RFP vs RFI at a glance

The buyer-side definitions follow the US General Services Administration: an RFI is used "when an agency is gathering information," an RFQ "when an agency knows what it needs and is looking for pricing information," and an RFP "when an agency is seeking a complete solution," with evaluation "based on multiple factors, not just price" (GSA, RFIs, RFQs and RFPs). Commercial buyers use the same words the same way.

What is an RFI?

A request for information is a buyer's market research. They have a problem or a project and want to know who can help, how, and roughly at what cost. GSA describes RFIs as a way to "understand what's available in the market" and "explore possible solutions."

How to answer an RFI as a supplier: keep it short and specific. Say what you do that matches their problem, give one relevant example, state a price range only if you are comfortable being anchored to it, and ask one good question about what they are trying to achieve. An RFI rarely produces an order directly, but it decides who gets the RFQ or RFP that follows.

What is an RFQ?

A request for quotation asks for a price on something already defined: a part number, a quantity, a delivery date, a service with a clear scope. The buyer has usually sent the same RFQ to several suppliers, and in GSA's words, "selection is often based on price and basic qualifications."

How to answer an RFQ as a supplier. A complete quote answers every question the buyer would otherwise have to email back about:

• Price per line, with quantity breaks if you offer them.
• Lead time from order, and whether it meets their date.
• Freight and delivery terms, or the one detail you need to confirm them.
• Validity period: how long the price holds.
• Payment terms and any minimum order.
• One clarifying question where the request is ambiguous, such as a finish, a variant, or a tolerance.

Speed matters as much as completeness. The buyer is waiting on several suppliers, and the first complete answer becomes the benchmark every later quote is compared against. Acknowledging the request the same day, even before the price is ready, keeps you in the running; our guide on how to acknowledge an email has wording for exactly that.

Is an RFQ response binding? In US federal purchasing, no: "A quotation is not an offer and, consequently, cannot be accepted by the Government to form a binding contract" (FAR 13.004(a)). The Government's order is the offer, and the contract forms when you accept it. In commercial deals the rules depend on your terms and the law that applies, so treat every quote as something the buyer might accept, and state its validity and conditions.

What is an RFP?

A request for proposal asks suppliers to propose a solution. The buyer describes the outcome they need, the constraints, and how responses will be scored, and expects a structured document back covering approach, team, timeline, references, and price.

How to answer an RFP as a supplier: decide go or no-go before writing anything. Check whether you meet every mandatory requirement, whether you have a relationship with the buyer, and whether the evaluation criteria favor what you do best. If it is a go, mirror their structure exactly, answer every requirement in the order asked, and make the price section easy to compare. Teams that answer many RFPs use dedicated RFP response software to reuse approved answers; that category is built for long proposals, not for the short quote requests that arrive by email.

In what order do they arrive?

Usually the RFI comes first. What follows depends on how well the buyer can define the need:

• Defined need: RFI (optional) → RFQ → order.
• Undefined need: RFI → RFP → shortlist → sometimes an RFQ or negotiation to settle final pricing.
• Repeat purchases: RFQ alone, often to the same small group of suppliers every time.

GSA's own training presents RFIs as early-stage, RFQs as mid-stage and RFPs as the final stage of its contracting process, so the order is a convention, not a rule. What matters for a supplier is recognizing which one you are holding.

How to tell which one just landed in your inbox

Formal RFPs and RFIs usually say so in the subject line and arrive as attachments or portal notices. RFQs are the ones that slip past, because many never use the acronym:

• "Can you price 200 of the SS-40 brackets, delivered to Tulsa?"
• "Need a rate for a 53' dry van, Dallas to Atlanta, Friday pickup."
• "What would 3 months of weekly cleaning cost for a 5,000 sq ft office?"

Each is an RFQ in everything but name: a defined need, a request for price, and a buyer who is almost certainly asking someone else too. Treat any email that asks "how much" for a specific thing as a quote request, and give it the same priority as a formal one.

Where software helps, by document type

• RFIs and RFPs: RFP response tools help teams reuse approved answers across long questionnaires and proposals.
• Formal RFQs through buyer portals: the buyer's sourcing platform dictates the format; your job is to respond inside it on time.
• RFQs that arrive as email: this is where most small and mid-size suppliers lose time. The request has to be spotted, the prices looked up in a price list or spreadsheet, and the reply written, often by one person who is busy with something else.

For that last case, InboxPilot, which publishes this guide, reads incoming quote requests in Gmail or Outlook, drafts the reply from your own price lists and catalogs, and holds it for your approval. It does not handle RFP portals or long proposals. The RFQ automation page shows a full example, and our post on AI for freight brokers covers the same pattern for rate requests.

Related reading

• RFQ software for inbound quote requests: what supplier-side RFQ software does and how to choose it.
• AI for freight brokers: answering rate and quote emails from your own lanes and rates.
• How to acknowledge an email: same-day acknowledgments for quote requests you cannot price yet.
• What an AI email agent does: how quote requests, support questions and sales emails get handled in one inbox.
• RFQ response email templates: eight quote replies, from the complete quote to the polite no-bid.

---

Definitions quoted from the US General Services Administration and the Federal Acquisition Regulation, checked 2026-09-23. Commercial practice varies by industry and country, and nothing here is legal advice. InboxPilot is the publisher of this guide.