Growth

RFP, RFQ and RFI: what they are, how they differ and how to respond in B2B

RFP, RFQ and RFI: what they are, when to ask for each in B2B purchasing and how a commercial proposal is evaluated without losing margin. A guide for industrial and SaaS.

Updated 14 min read

TL;DR · executive summary

What you’ll find in this article

An RFP (request for proposal) is the formal request a company uses to ask several suppliers for a complete proposal: solution, plan, team and price. An RFQ (request for quotation) asks only for price and terms for something already specified, and an RFI (request for information) is used to get to know the market before deciding. In industrial B2B and SaaS the three are often chained: RFI to filter, RFP to compare app...

An RFP (request for proposal) is the formal request a company uses to ask several suppliers for a complete proposal: solution, plan, team and price. An RFQ (request for quotation) asks only for price and terms for something already specified, and an RFI (request for information) is used to get to know the market before deciding. In industrial B2B and SaaS the three are often chained: RFI to filter, RFP to compare approaches and RFQ to close the numbers. This guide to RFP, RFQ and RFI explains when each is used, how responses are scored and which proposal mistakes end up costing the supplier margin.

This guide focuses on purchasing between companies. Public procurement has its own rules and is not covered here.

In short

  • Formal requests weigh on revenue: in the 2026 Loopio report with APMP they influenced an average of 40% of the revenue of the companies surveyed.
  • The response is scored with a weighted matrix. Explaining well earns points.
  • Decide with a go/no-go scorecard before writing a single line.
  • Margin is lost in scope and exclusions, not in the last discount.

Why RFPs weigh on revenue

For many B2B companies, formal requests are not a formality. The annual Loopio report with the Association of Proposal Management Professionals (APMP), in its 2026 edition, surveyed 1,533 companies worldwide:

  • RFPs influenced 40% of the average company’s revenue, the highest level the report has recorded since 2019.
  • Teams sent an average of 166 RFPs last year, up from 153 the year before.
  • 79% already use AI in their response process.
  • 75% use some kind of go/no-go process to decide what to respond to. Among teams that win half or more of the RFPs they enter, the figure rises to 81%.

It is a global sample, not a Spanish one, but the conclusion travels well: responding more is not the strategy. Choosing better what you respond to, and responding better, is.

What is an RFP (request for proposal)

An RFP (request for proposal) is the document a company uses to ask several suppliers how they would solve a specific problem, with their solution, work plan, team and price. It is used when there are several valid ways to do it and the buyer wants to compare approaches, not just amounts.

For example, an industrial company that wants to roll out a predictive maintenance system across its plants, or a SaaS company looking for a partner to migrate its billing to another system. In both cases the buyer knows what problem they have, but not which solution suits them best.

What a typical RFP contains

  • Context. Who the company is, what problem it wants to solve and why now.
  • Requirements. Functional, technical and service requirements, separating mandatory from desirable.
  • Evaluation criteria. How responses will be scored and how much weight each criterion carries.
  • Deadlines. Date for submitting questions, submission date and decision timeline.
  • Response format. Structure, length, attachments and the pricing model the buyer wants to receive.

Reading this part carefully saves work. An RFP that does not publish evaluation criteria or does not allow questions is already telling you something about how the decision will be made.

Another acronym you may come across: RFT

The RFT (request for tender) is the usual form in tenders with more formal submission rules. In public procurement the reference document is the tender specification, which this guide does not cover.

What is an RFQ (request for quotation)

An RFQ (request for quotation) asks suppliers for price, lead times and terms for a product or service that is already specified: part numbers, quantities, tolerances or service levels. The technical side is settled, and the decision depends mainly on cost, lead time and delivery reliability.

The response to an RFQ is short and comparable: a price table, payment terms, lead times and offer validity. Precisely for that reason, margin is won or lost in the details.

An example of an industrial RFQ

An example to understand the logic: a machinery manufacturer asks three suppliers for a price on 2,000 units of a machined part, with a drawing attached, a defined tolerance, delivery in two batches and payment at 60 days. All three can make the part, so the decision depends on unit price, lead time and delivery reliability. The supplier who protects their margin is the one who writes down what the price includes (packaging, transport, material certificate) and what it does not.

For the supplier, the key is to quote with up-to-date raw material, capacity and transport costs, and to leave nothing to the buyer’s interpretation.

What is an RFI (request for information)

An RFI (request for information) is used to get to know the market before deciding: which solutions exist, which suppliers can provide them and with what capabilities. It does not ask for a firm price or a detailed proposal.

The buyer uses it to build a shortlist of suppliers who will later receive an RFP or an RFQ. For the supplier, responding well to an RFI is the way into that list, even if there is nothing to quote yet.

RFI vs RFP vs RFQ: differences in a table

The difference between RFI, RFP and RFQ is the degree of definition: the RFI asks what exists, the RFP asks how you would do it and the RFQ asks how much something already defined costs. They go from most open to most closed.

RFI RFP RFQ
What it asks for Information on solutions and capabilities A complete proposal: solution, plan, team and price Price, lead time and terms for something specified
When it is used When exploring the market When there are several valid ways to solve the problem When the specification is closed
Preparation effort Low High Medium, with fine cost calculation
What the buyer decides Who to invite to the next phase Which approach and which supplier to choose Who to buy from and on what terms
What the supplier delivers Capabilities and references A proposal with solution, plan, team and price A quotation comparable line by line
Typical outcome Supplier shortlist Chosen supplier or finalists to negotiate with Order or contract

Many B2B purchases use all three in order. Others jump straight to the RFQ when the technical specification is already clear. From the buyer’s side, the rule is simple: ask for an RFI when you do not know what is on the market, an RFP when you know what problem you have but not how to solve it, and an RFQ when you know exactly what you want to buy. Each fits a different moment of the sales funnel stages, seen from the buyer’s side.

How a response is evaluated in industrial B2B and SaaS

A response to an RFP is evaluated with a weighted matrix: the buyer scores each criterion, multiplies it by its weight and compares the total. The matrix is not always published, but it almost always exists.

The matrix criteria

  • Requirements. Whether you meet all the mandatory ones and how many of the desirable ones.
  • Technical soundness. Whether the solution holds up and is well explained.
  • Experience. Similar cases and references the buyer can check.
  • Plan and team. Who does what, when and with what dedication.
  • Risks. What can fail and how you manage it.
  • Total cost. Not just the initial figure: licences, maintenance, changes and out-of-scope work.

If the RFP publishes the weights, organise your response in the same order. If it does not, ask for them in the question round.

Example of a weighted matrix

Example weights and scores to understand the logic, not a market standard. Each score runs from 0 to 5 and is multiplied by its weight:

Criterion Example weight Supplier A Supplier B
Requirements compliance 30% 5 4
Technical soundness 20% 3 5
Experience and references 15% 4 3
Plan and team 15% 4 4
Total cost 20% 3 4
Weighted total 100% 3.90 4.05

Notice what decides it: B meets the requirements less well and still wins, because its technical solution is better understood and its total cost scores higher. In an RFP, explaining well earns points.

What the evaluator does not tell you

Beyond the matrix, there are things that rarely appear in writing. Clarity: if the evaluator has to hunt for the answer to a requirement, they score lower. Visible assumptions: a proposal that says what it has assumed and what is left out conveys control. And a price that can be understood without calling the supplier: if comparing your offer requires asking for clarifications, you are at a disadvantage.

Have an RFP or an RFQ on your desk?

In the audit we review with you how you prepare your bids: reading requirements, scope, assumptions, exclusions and margin, and where work that nobody costed slips away. Free audit

Go or no-go: a scorecard to decide whether to respond

It is not worth responding to everything. In the 2026 Loopio report with APMP, 75% of teams use some kind of go/no-go process, and among those who win half or more of their RFPs the figure rises to 81% (Loopio and APMP). The decision is made with written criteria, not out of inertia. This scorecard is an example to copy and adapt:

Question If the answer is yes If the answer is no
Do we meet all the mandatory requirements? Continue No-go
Does the expected margin cover the presales hours? +2 No-go
Did we know the client or the decision-maker before receiving the request? +2 0
Do we have a similar case the client can check? +2 0
Does the deadline allow a response reviewed by someone who did not write it? +1 -2
Do the requirements look copied from another supplier’s product? -3 0

The maximum score is 7. Set your threshold in advance (for example, respond from 4 upwards) and adjust it with your history. Below the threshold, if you decide to respond anyway, write down why. Record each decision in the CRM with its reason: after a year you will know which bids are worth competing for. The questions resemble the BANT criteria, adapted to purchasing.

Mistakes that cost margin in the proposal

A proposal’s margin is lost before it is sent: in the scope, in the exclusions and in the cost.

  • Scope copied from another offer. A previous proposal is reused without reviewing what changes for this client, and the project ends up including work that nobody costed.
  • Exclusions not written down. What does not appear as excluded, the client understands as included.
  • Costs with outdated rates or timings. Quotes use supplier prices, internal rates or hour estimates that are no longer real.
  • Penalties accepted without measuring. Deadlines, service levels or clauses accepted so as not to lose the bid, without calculating what they would cost if triggered.
  • Discounts to make up for a late response. If the proposal arrives late or weak, the team tries to compensate with price, and the discount stays on the whole contract.

Almost all of them are prevented with a scope and margin review before sending, done by someone other than the person who wrote the proposal.

Where RFQs arrive: purchasing portals

In industry, many RFQs do not arrive by email. They arrive through the client’s purchasing portal (platforms such as SAP Ariba, Coupa or itbid) or are generated by the buyer’s own ERP from a material need, as the purchasing module of Odoo does. We name them as examples of portals, not as tools you have to use.

If you respond from a portal, keep a copy of each response and its outcome in your CRM. The portal belongs to the client, and your bid history has to be yours.

From the request to the commercial proposal: how to organise presales

A solid commercial proposal comes from an orderly presales process, not from last-minute effort. Presales is part of the B2B pipeline and is managed like any other stage: with owners, criteria and records. As with any inbound lead, it helps to be clear about how to respond quickly to an incoming request and who decides whether to respond.

Base of approved answers and up-to-date prices

Many questions come back from one RFP to the next: company description, security, certifications, methodology, references. A base of approved answers, with an owner and a review date, avoids rewriting them every time and stops old versions from circulating. The same goes for rates and costs: a single, up-to-date source of prices from which all quotes come.

Who reviews scope and margin before sending

Before sending, a person who did not write the proposal reviews three things: that the scope answers what the client asks and not the previous offer, that the exclusions are written down and that the calculated margin is the one the company expects. If it does not meet them, the proposal is adjusted or the go decision is rethought.

CRM record of every opportunity and its outcome

Every RFP or RFQ received is an opportunity in the CRM, with its type, its go/no-go decision, the amount offered, the expected margin and the outcome. If you need to review the basics, here we explain what a CRM does, and if you run long sales with many stakeholders, compare HubSpot or Salesforce for managing complex opportunities.

With that record you can track the win rate by type of request in a bid dashboard and tie it to the rest of revenue with a RevOps approach for B2B companies.

From a one-off bid to a commercial system

When every RFP is recorded with its decision, its margin and its outcome, presales stops being an isolated effort and becomes part of the revenue cycle. Organising that is what RevOps work is about: marketing, sales, CRM and revenue data aligned, so that your bids, your pipeline and your forecast come from the same data. RevOps consulting

Where AI helps in an RFP or RFQ

AI helps mainly with reading and with the first draft, always on top of your approved answers and prices:

  • Reading the client’s document. Summarises the context, the timeline and the key conditions.
  • Requirements extraction. Turns the document into a requirements table, mandatory and desirable, with its source page.
  • Draft from approved answers. Searches your knowledge base and proposes a first answer for each requirement.
  • Scope review. Compares what the client asks for with what the proposal says and flags gaps, missing exclusions or new commitments.

Technical review, price and the decision to bid remain your team’s. At cronuts.digital we set it up like this: we organise your base of approved answers and your prices, connect requirements extraction and AI drafts, and leave a scope and margin review before every submission. Without an up-to-date base of answers and prices, AI only speeds up mistakes.

What we have learned preparing proposals

The proposal that loses the most margin is not the one done in a hurry. It is the one that copies the scope of the previous one without reviewing what has changed for this client.

Frequently asked questions

What is an RFP?

An RFP (request for proposal) is the document a company uses to ask several suppliers how they would solve a specific problem, with their solution, work plan, team and price. It is used when there are several valid ways to do it and the buyer wants to compare approaches, not just amounts.

What is an RFQ?

An RFQ (request for quotation) asks suppliers for price, lead times and terms for a product or service that is already specified: part numbers, quantities, tolerances or service levels. It is common in industrial and component purchasing, where the technical side is settled and the decision depends mainly on cost, lead time and delivery reliability.

What is the difference between an RFI, an RFP and an RFQ?

The RFI asks what is on the market and who can do it, the RFP asks how you would do it and what it would cost, and the RFQ asks what something already defined costs. They go from most open to most closed. Many B2B purchases use all three in order, and others jump straight to the RFQ when the technical specification is already clear.

How is an RFP response evaluated?

The buyer usually scores with a weighted matrix: fit with the requirements, technical soundness, proven experience, plan and team, risks and total cost, not just the initial figure. Responses that lose usually do so by not answering what was asked, by hiding assumptions or by a price that cannot be understood without calling the supplier.

What mistakes make a proposal lose margin?

Copying a previous offer without reviewing the scope, not stating in writing what is left out, calculating cost with outdated rates or timings, accepting penalties or deadlines without measuring their impact, and granting discounts to make up for a late response. Almost all of them are prevented with a scope and margin review before sending.

When is it better not to respond to an RFP?

When you do not meet the mandatory requirements, when it looks written to suit another supplier, when the deadline does not allow a serious response or when the expected margin does not justify the effort. A go/no-go scorecard with written criteria avoids spending presales hours on bids with little chance.

How long do you have to respond to an RFQ?

The buyer sets it in the request itself. If it does not say, ask before quoting.

What is the difference between an RFP and a public tender?

An RFP is a process between companies, with the rules set by the buyer. A public tender follows the public sector procurement regulations and their specifications. This guide covers only the former.

Can you negotiate after responding to an RFP?

Often yes, especially with the finalists. That is why it pays to write down the assumptions and what is left out: it is what gives you room to negotiate without giving away scope.

Can AI be used to respond to RFPs and RFQs?

Yes, as support: AI can read the client’s document, extract requirements into a table, search your knowledge base for approved answers and prepare a first draft. In the 2026 Loopio report with APMP, 79% of teams already use it in their process (Loopio and APMP). Technical review, price and the decision to bid remain your team’s.

Want to know where margin slips away in your bids?

We start from your latest proposals, your base of answers, your go/no-go criteria and how you record each opportunity in the CRM. Free audit

Add cronuts.digital as a preferred source on Google

From article to pipeline

Want to apply this to your specific site?

Free diagnostic with a report in 48 business hours and real metrics from your site. If there's no lever above 30%, we'll tell you before you sign. Brutally honest.