How to respond to an RFI (with examples)

RFP Tips

Author:

Chris Mabry

Short answer: To respond to an RFI (request for information), answer exactly what the buyer asked, in the order and format they asked for, and keep it shorter than an RFP response. An RFI is market research: the buyer is learning what's possible and who can do it, so your goals are to show you understand the problem, prove you can solve it with specific evidence, and earn a place on the RFP invitation list. Don't price unless asked, don't over-commit, and say clearly where you don't fit.

In Iris: RFIs run through the same project as RFPs: questions extracted, answers drafted from your approved content with sources, and gaps flagged rather than guessed.

Who this is for: sales engineers, proposal managers and account executives who received an RFI and need to respond well without a full RFP effort.

On this page

  1. What is an RFI, and how is it different from an RFP or RFQ?
  2. Should you respond at all?
  3. How to respond to an RFI, step by step
  4. What format should an RFI response follow?
  5. RFI response examples, annotated
  6. Government RFIs: what's different
  7. RFI response checklist
  8. How Iris handles RFIs
  9. FAQ

What is an RFI, and how is it different from an RFP or RFQ?

RFIRFPRFQ
Buyer's goalLearn what's possible and who can do itChoose a solution and vendorGet prices for a defined item or service
StageEarly, researchSelectionPurchase
Your goalGet shortlisted for the RFPWinWin on price and terms
Typical length of responseShort to mediumLongShort, price-led
PricingRanges or none, unless askedDetailedThe main content
Binding?Usually notOften leads to contractOften leads directly to an order
What winsRelevance and clarityFit, proof, price, riskPrice and compliance

Should you respond at all?

An RFI costs less than an RFP, but it's still a bid decision. Respond if at least two of these are true:

  • The problem described matches what you already do well.
  • You know (or can reach) someone on the buyer's team.
  • A follow-on RFP is likely and you'd want to be invited.
  • Your answer could shape the requirements in your favor, honestly.

If none are true, a short, polite decline keeps the relationship. A go/no-go scorecard helps make the call consistent.

How to respond to an RFI, step by step

  1. Read the whole RFI and list every question and instruction. Note the deadline, submission method, page limits, required format and contact person.
  2. Ask clarifying questions before the question deadline. Buyers often share answers with every respondent, which also tells you who else is responding.
  3. Map each question to an owner. Product, security, delivery and commercial questions usually need different people.
  4. Draft from approved content, then tailor. Reuse your best existing answers, but rewrite the opening of each to use the buyer's words.
  5. Mark gaps honestly. If you don't do something, say so and say what you do instead.
  6. Write a short cover note or summary (one page): your understanding of their goal, why you're relevant, and one proof point.
  7. Review for compliance: every question answered, in their order, in their format, within limits.
  8. Submit early and confirm receipt. Then follow up to ask about the RFP timeline.

What format should an RFI response follow?

Always use the buyer's format if they give one. If they don't (common in commercial RFIs, and US federal RFIs have no required format), this structure works:

SectionWhat goes in itLength guide
Cover noteWho you are, what you're submitting, one contactHalf a page
Understanding of the needTheir problem in their words1–2 paragraphs
Company overviewSize, focus, relevant customers (named only with permission)Half a page
Answers to questionsNumbered to match the RFIAs needed
Relevant experience1–3 short examples close to their situationHalf a page each
Approach and timeline (if asked)High level; no detailed plan yet1 page
Pricing (only if asked)Ranges or model, with assumptionsHalf a page
AttachmentsOnly what was requested—

For the cover note itself, adapt our RFP cover letter template.

RFI response examples, annotated

Examples for Larchmont Systems, a fictional software company responding to a fictional hospital network's RFI for a patient-scheduling platform.

Example 1: a capability answer with a source

Question: Describe how your solution integrates with existing electronic health record (EHR) systems.
Answer: Larchmont integrates with EHR systems through HL7 FHIR APIs and supports scheduled file-based exchange for systems without FHIR endpoints. Our standard integration covers patient demographics and appointment data; custom fields are mapped during implementation. [Source: Larchmont Integration Guide v4, §2.]

Why it works: answers the question directly, states scope (what's standard, what's custom), and the source note means a reviewer can verify it before it goes out. Remove internal source notes before submission if the buyer's format doesn't call for them.

Example 2: a gap, handled honestly

Question: Does your solution support on-premises deployment?
First draft from the content library: There is not enough information to answer the question.
Final answer, written by the product lead: Larchmont is delivered as a cloud service only; we don't offer on-premises deployment. For organizations with data-location requirements, we host in [region] and can provide our security documentation for review.

Why it works: the library had no approved answer, so nothing was guessed. The product lead answered it, and the final answer says "no" plainly and offers what is available. Buyers screen out vendors who claim everything; a clear "no" builds trust for the RFP stage.

Example 3: an experience answer, tightened

Weak: "We have extensive experience with healthcare organizations of all sizes."
Rewritten: We currently support [n] healthcare customers, including [two named references, with permission]. The closest to your situation is a [size] regional network that moved from phone-only scheduling to online booking across [n] clinics in [timeframe]. [Fill in only from a published case study or with the customer's approval.]

Government RFIs: what's different

In US federal contracting, FAR 15.201(e) says RFIs may be used when the government "does not presently intend to award a contract" but wants price, delivery, market information or capabilities for planning, that responses "are not offers," and that "there is no required format for RFIs." Practical consequences:

  • Follow the notice's instructions exactly: page limits, file names, required identifiers (such as your UEI) and the submission email or portal.
  • Answer the market-research questions directly: set-aside eligibility, relevant contract vehicles and past performance often matter here.
  • Use the RFI to shape the solicitation, honestly: point out requirements that would exclude capable vendors.
  • Track the opportunity: a sources-sought notice or RFI often precedes a solicitation.

State and local RFIs vary widely; read each notice.

RFI response checklist

CheckDone?
Every question answered, in the buyer's order and numbering
Format, page limit, file type and file name followed
Deadline and submission method confirmed
Clarifying questions sent before the question deadline
Each answer reviewed by its owner
Gaps stated honestly, with alternatives
No pricing unless requested; assumptions stated if included
Customer names used only with permission
One named contact with email and phone
Receipt confirmed; follow-up date set

How Iris handles RFIs

  • Upload the RFI as it arrives (Word, PDF, Excel or CSV) or work in a portal through the Chrome extension. Iris extracts every question, keeps the numbering and makes each numbered sub-item its own row.
  • Drafts come only from your content: your Knowledge Map and Approved Answers Library. Each answer links to its sources and carries a High, Medium, Low or Contradictory label.
  • Gaps are flagged, not filled: when your content doesn't cover a question, Iris answers "There is not enough information to answer the question," exactly as in Example 2. Those rows can't be approved as-is.
  • Assign and review: route questions to product, security or delivery owners, comment and approve, then export back into the original file or a branded template.
  • Decide first: the RFP Analyzer works on RFIs too: upload the document to get a summary, key dates and requirements checked against your content, with a Go, Review or No-Go recommendation.

Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered, or an RFI.

FAQ

How long should an RFI response be?
As long as the questions require and no longer. Respect any page limit; without one, aim for a response a reviewer can read in one sitting.

Should I include pricing in an RFI response?
Only if asked. If you do, give a range or model with clear assumptions.

What's the difference between an RFI and a sources-sought notice?
Both are government market research. A sources-sought notice usually asks whether capable vendors exist, often to decide on a set-aside; an RFI may ask broader questions.

Is an RFI response binding?
In US federal RFIs, FAR 15.201(e) says responses are not offers. Commercial RFIs usually say so in their terms; read them.

How do I write an RFI response email?
Short: what you're submitting, the RFI number and title, a one-line summary of fit, attachments listed, and one contact. Follow any submission instructions exactly.

What comes after an RFI?
Often an RFP or RFQ. See how to write an RFP response.

See it live

Respond to RFPs
without the grind.

Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.