What is an RFQ? A guide to requests for quotation, from both sides

An RFQ is a procurement document a buyer sends to selected suppliers asking for a price on something the buyer has already defined down to the specification. No creativity requested. No solution to invent. Just a number, a lead time, and terms.

Almost every guide to requests for quotation is written for the person sending one. That makes sense: procurement teams issue them, so procurement publishers explain them. But for every buyer writing an RFQ, there are five or six vendors reading it, deciding whether to bid, and pricing a response under deadline. That half of the document is barely covered anywhere.

This guide covers both. Same document, read twice: what the buyer should put in, and what the vendor should read out.

What is a request for quotation?

A request for quotation (RFQ) is a formal document in which a buyer asks one or more suppliers to quote a price for goods or services whose specifications, quantities, and delivery terms are already fixed. The buyer is not asking how to solve a problem. The buyer is asking what a known solution costs.

The U.S. General Services Administration frames it the same way for federal contracting: an RFQ is used when the agency already knows what it needs and is looking for pricing information. That single distinction, "we know what we want," is what separates an RFQ from every other document in the RFx family.

Because the requirement is fixed, quotes come back in a comparable format. That comparability is the whole point. A buyer who receives eight quotes on the same spec can line them up in a spreadsheet and decide. A buyer who receives eight proposals cannot.

What RFQ stands for, and the second meaning that trips people up

RFQ usually stands for request for quotation (or request for quote, which means the same thing). But in construction and public sector procurement, the same three letters often mean request for qualifications, which is something else entirely: a prequalification step where an owner screens contractors on experience, capacity, licensing, and safety record before letting them bid at all.

The two are not interchangeable:

• Request for quotation: you already qualified. Now give me your price.
• Request for qualifications: prove you are allowed to give me a price.

If you work in construction, engineering, or government contracting and someone forwards you "the RFQ," check which sense is meant before you start pricing. Answering a qualifications request with a price sheet is a fast way to get disqualified. This ambiguity is common enough that it appears directly in Google's own AI-generated summary of the term.

When buyers issue an RFQ instead of just asking for a price

Buyers formalize a quote request when informal pricing stops working. Four triggers come up repeatedly:

• Repeat or high-volume purchasing. Consumables, components, and standard services bought on a cycle justify a structured process.
• Internal approval requirements. Finance or audit policy often requires a documented number of competing quotes above a spend threshold.
• Comparability. Three vendors emailing three differently structured price lists cannot be compared. A structured quote request forces one format.
• Regulated or public spend. Public entities generally have to demonstrate a fair, documented sourcing process.

RFQ vs RFP vs RFI vs IFB: which document, when?

The four RFx documents differ by one variable: how much the buyer already knows. An RFI is issued when the buyer is still exploring the market. An RFQ is issued when the buyer knows the solution and needs the price. An RFP is issued when the buyer knows the problem but not the solution. An IFB is a formal, usually sealed, price competition on a fully specified scope.

The one question that decides it

Before choosing a document, a buyer only has to answer this: do I know what I want, or only what is wrong?

If you can write a specification, you want an RFQ. If you can only write a problem statement, you want an RFP. Everything else follows from that. Buyers who get this wrong produce the most expensive failure mode in sourcing: an RFP that receives eight strategically different responses to a problem that actually had one obvious standard solution, and now someone has to evaluate all eight.

What comes first: RFI, RFQ, or RFP?

There is no fixed sequence, but the common order is RFI, then either an RFQ or an RFP depending on what the RFI revealed. The RFI narrows the field of possible suppliers and clarifies what the market can actually deliver. The buyer then picks the right follow-up document. Many sourcing cycles skip the RFI entirely when the buyer already knows the supplier landscape.

When an RFQ turns into an RFP mid-process

This happens more often than the procurement literature admits, and it matters enormously if you are the vendor. A buyer issues a quote request believing the requirement is standard. Quotes come back with wildly different assumptions, exclusions, and implementation caveats. The buyer realizes the requirement was not standard after all, and reissues the sourcing event as an RFP.

For a vendor, this is a signal, not an accident. Wide quote variance on a supposedly fixed spec means the spec was incomplete. If you spotted the ambiguity while pricing and flagged it in writing, you are now the vendor who understood the requirement first. That is a genuine competitive position, and it is available only to vendors who read the RFQ carefully instead of just filling in the price column.

The anatomy of an RFQ, read from both sides

Every RFQ contains roughly the same eight sections. What changes is who is reading. The buyer sees eight things to specify. The vendor sees eight sources of risk, margin, and qualifying information about the deal.

The pattern is consistent: everything the buyer writes to standardize the comparison is simultaneously telling the vendor something about how the decision will actually be made, how much competition there is, and how much the price can move. Vendors who only read the specification and the deadline are throwing away the rest of the document.

How to write an RFQ (the buyer side)

Writing an RFQ is a five-step process that starts well before the document and ends after the award. Most of the quality is determined in step one.

1. Define the requirement completely. Specifications, quantities, tolerances, standards, delivery locations, and dates. If you cannot describe it precisely, you are not ready for an RFQ.
2. Build a supplier shortlist. Invite suppliers you would actually be willing to contract with. A quote request is not a public announcement, and inviting fifteen vendors to compete on price mostly generates work for everyone and resentment from the ones who lose.
3. Issue the document with a fixed format and deadline. Include a pricing table vendors must fill in. Free-format pricing destroys comparability.
4. Evaluate against your stated criteria. If you published evaluation criteria, use them. Vendors calibrate their entire response to what you said you would measure.
5. Award and notify. Issue a purchase order to the winner, which is what actually creates the contract, and tell the others. Notifying unsuccessful suppliers costs nothing and keeps them willing to quote next time.

Common RFQ mistakes that produce useless quotes

• Vague specifications. Ambiguity forces suppliers to guess, and guesses come back as non-comparable quotes with different hidden assumptions.
• No pricing structure. Unit price, setup fees, freight, and taxes need defined lines, or every quote arrives in a different shape.
• Unrealistic deadlines. A 48-hour turnaround on a complex quote selects for suppliers who are not busy, not suppliers who are good.
• Hiding the evaluation criteria. If price is 100% of the decision, say so. If lead time carries real weight, say that too.
• Forgetting compliance requirements. Certifications, insurance, and standards discovered after award cause rework or a cancelled contract.

The four types of RFQ, and what each one says about your odds

The four standard RFQ formats differ in how much visibility suppliers have into competing bids. That visibility level is the single best predictor of how much effort a vendor should spend on the response.

Reading this as a vendor changes the calculation. An invited bid on a spec you fit well deserves real effort. A reverse auction on a commodity, against unknown competitors, deserves a fast decision about your walk-away price and very little else. Spending three days polishing a response to a reverse auction is a margin decision disguised as a diligence decision.

How to respond to an RFQ (the vendor side)

Responding to an RFQ is the process of deciding whether to bid, pricing accurately, and returning a compliant quote before the deadline. It sounds mechanical. It rarely is, because the work of gathering specs, prior pricing, certifications, and internal approvals is spread across people and systems that were never designed to produce documents together.

The bid/no-bid call: four signals to check before you quote

Professional bid teams run a formal go/no-go review before committing resources. The Association of Proposal Management Professionals (APMP) has built much of its practice around exactly this discipline. Four signals do most of the work:

• Incumbency. Is there a current supplier? If the document reads like it was written from an existing vendor's spec sheet, you may be providing a price benchmark rather than competing.
• Spec fit. Can you meet the specification without exceptions? Every exception you have to note reduces your comparability, which is the one thing the buyer is optimizing for.
• Relationship depth. Have you spoken to anyone at this company before the request arrived? Cold requests from organizations you have no relationship with have materially lower win rates.
• Margin floor. What is the price below which you would rather not win? Decide this before you build the quote, not while you are negotiating.

A clear no is a good outcome. It returns hours to your pipeline.

What responding actually costs you

The hidden cost of RFQ response is not the pricing. It is the assembly. According to Salesforce's State of Sales report, sales reps spend under a third of their time actually selling, with the rest absorbed by administrative and document work. A "simple" quote frequently pulls in a product spec from engineering, a lead time from operations, a compliance certificate from legal, and last year's pricing from a folder nobody can find.

Run the arithmetic on your own team. If four people spend two hours each assembling a quote, and you respond to fifteen RFQs a quarter, that is 120 hours a year on document assembly for one sourcing channel. At a 20% win rate, most of those hours produced nothing.

Why an RFQ rarely arrives alone

Here is what the procurement guides leave out. An RFQ is almost never a single document. It arrives with a specification annex, a compliance questionnaire, sometimes a supplier information form, occasionally a technical clarification round, and often converts into a full RFP if the requirement turns out to be more complex than the buyer assumed.

That means the real unit of work is not "the quote." It is the deal, and the set of materials that deal will require before it closes. Teams that treat each document as an isolated task rebuild the same company knowledge every time. Teams that treat the deal as the unit reuse it. This is the logic behind Cobl, which connects to the CRM, files, and email where deal context already lives and generates the full set of response materials from it rather than one document at a time. The same approach applies further up the deal cycle, which is why proposal automation and RFQ response tend to be the same problem wearing different labels.

Structured, rule-bound documents are exactly where this pays off. Daoud Chami, Data Science and AI Manager at CBTW, put it this way: "Cobl stood out because it's designed for documents that follow an internal grammar: RFPs, technical memos, HR templates, reports. It helps generate complex content while keeping full control at every stage."

Where AI helps, and where a human has to sign off

AI is genuinely good at the assembly layer: pulling the right spec from a past response, drafting the compliance narrative, formatting the pricing table, checking that every question in the questionnaire has an answer. It is not good at deciding what number goes in the price column.

Pricing, contractual commitments, delivery guarantees, and any statement about capacity are human decisions with legal weight. Every serious response workflow keeps a human in the loop on those, and any tool that suggests otherwise is selling you a liability. If data handling matters in your sector, that is also worth checking before you route customer specifications through any AI system, which is why Cobl documents its security posture in detail.

Turn every RFQ into a deal you can move forward

An RFQ is a small document attached to a real deal. Buyers who write it precisely get comparable quotes and a defensible decision. Vendors who read it fully, rather than skipping to the price column, learn how the decision will be made and whether the deal is worth winning.

The teams that do this well have stopped treating each request as a standalone document and started treating it as one step in a deal that will need several more. Ready to try that? You can try Cobl for free, with around 5 generated documents per month.