RFI Response Sample: The Document That Only Has to Get You Shortlisted
An RFI decides whether you make a list, not whether you win. A worked sample, and the three answers that get a response cut before the real competition starts.
An RFI response decides whether you reach the shortlist for the formal stage. It is a sorting task, so keep the issuer's question order and numbering, open every answer with a direct answer and state the boundary in the same sentence, and leave out pricing and generic collateral that nothing in the document asked for.
Key takeaways
- The RFI is a sorting task rather than an evaluation. SiftHub's guide puts the stakes plainly: the response determines whether a vendor makes the shortlist for the formal stages or is eliminated before real competition begins, which means legibility beats depth.
- Keep the issuer's numbering and question order exactly. Evaluators work across responses question by question, comparing every supplier's answer to question seven against each other, so a response reordered into a seller's narrative costs the reader time in the first minute.
- Volunteering a gap early is the strongest move available. A missing capability the evaluator discovers later reads as concealment and taints every other answer, while one disclosed up front is a data point and occasionally reveals the requirement was softer than the document made it look.
- The question set is evidence about the buyer before it is a task. Heavy weighting toward integration and migration means an incumbent is being replaced; unusually specific feature questions mean somebody has already been demonstrated to; broad even questions mean the buyer is early and genuinely surveying.
Reviewed and updated August 23, 2026
Fourteen questions arrive in a Word table with a one-week turnaround and no pricing section. The team treats it as a small proposal, spends three days on it, attaches two case studies and a capability deck, and returns twenty-two pages. The buyer wanted to know whether the company was worth putting on a list of six, and now has twenty-two pages from one vendor and four pages from each of the others.
That document was a request for information, and it is judged on a different axis from anything that comes after it.
What the RFI is deciding
An RFI sits in front of the formal process and its output is a shortlist rather than an award. SiftHub's guide on the format states the stakes directly: "Your RFI response will determine whether you make the shortlist for the next procurement stage or get eliminated before the real competition begins."
The same page draws the boundary against the later document: "Unlike RFPs that require comprehensive proposals, RFIs focus on demonstrating basic capabilities, qualifications, and approach without detailed pricing or implementation plans."
Two consequences follow, and most weak RFI responses ignore both. The reader is doing a sorting task rather than an evaluation, which means legibility beats depth. And the absence of a pricing section is deliberate, so a response that volunteers pricing has answered a question nobody asked and given an evaluator a reason to compare on the one axis you have least control over at this stage.
The failure mode is answering it like a proposal
The dominant mistake is treating scarcity of questions as an invitation to expand. It is the opposite. An RFI's question count is a statement about how much attention the reader intends to give each response.
Three specific versions of the mistake are worth naming.
Reordering the questions. Answers get rearranged into a narrative that flows. The evaluator is working across responses question by question, comparing your answer to question seven against everyone else's answer to question seven. A response that requires them to find it has spent their goodwill in the first minute.
Answering a better question than the one asked. The question asks whether you support single sign-on. The answer explains the security architecture. The evaluator reads the whole thing looking for a yes.
Sending the capability deck. Generic collateral attached to a specific request signals that the request was not read. It is also the most easily detected form of low effort, because every recipient has seen the same deck from three vendors.
- Narrative order chosen by the seller
- Company background before any answer
- Each answer expanded past the question
- Pricing volunteered that was not requested
- Generic collateral attached
- Length signals effort
- The issuer's own question order and numbering
- One direct answer per question, first line
- Supporting detail only where it changes the answer
- Pricing addressed only if asked
- Attachments only where a question names one
- Length matched to the questions asked
A worked sample
Everything in this section is invented. The company, the people, the operational detail and every figure are illustrative and none of it is a measurement of any real client, ours or anybody else's. Read the structure and replace the content.
The situation. An invented buyer, a mid-sized insurer called Harbour Mutual, has issued an RFI to eight suppliers of claims-intake automation. The invented respondent is a software company with a genuine product and no prior relationship with Harbour Mutual.
The opening, which is three sentences and not a page
The invented sample below shows the length that is appropriate here:
Harbour Mutual is evaluating suppliers for claims-intake automation. This response answers all fourteen questions in the order issued, using Harbour Mutual's numbering. Where a capability is partial or delivered through a partner, that is stated in the answer rather than in a footnote.
The third sentence is doing the work. Declaring up front that partial answers will be labelled as partial buys credibility for every unqualified yes that follows, and it costs nothing because the evaluator will discover the gaps anyway.
An individual answer, in the shape that survives comparison
Still the invented Harbour Mutual example, this time for a hypothetical question seven on document ingestion:
7. Can the platform ingest scanned documents submitted by post? Yes. Scanned documents are ingested through the same intake queue as email and portal submissions. Handwritten claim forms are supported for structured fields; free-text handwriting is passed through to a human reviewer rather than interpreted automatically.
The pattern is a one-word answer, then the boundary. Leading with the direct answer means the evaluator can score the row without reading the rest, and stating the limit in the same breath is what makes the yes believable.
The answer you do not have
The invented respondent has no answer to a hypothetical question about a specific regulatory reporting format:
11. Does the platform produce returns in the XBRL format required by our regulator? Not today. We produce structured exports that two clients currently transform into this format through their reporting layer, and we can describe that arrangement in detail if it is useful. If this is a mandatory requirement rather than a preference, we would rather say so now than at proposal stage.
Volunteering the disqualification is counterintuitive and it is the strongest move available. A gap discovered by the evaluator later reads as concealment and taints every other answer. A gap disclosed early is a data point, and occasionally the requirement turns out to be softer than the document made it look.
What goes at the end
A short close naming one person, their direct contact details, and the two questions you would want to ask if the process reaches a next stage. Not a summary. The evaluator has just read the answers and does not need them again.
Read the questions as evidence before answering them
An RFI is also the first hard information you get about how this buyer thinks, and it is worth spending twenty minutes on that before anyone drafts anything.
The question set has a shape. If two thirds of it concerns integration and data migration, the project is a replacement rather than a new capability, and there is an incumbent whose contract is ending. If several questions are unusually specific about a feature that is rare in the category, somebody has already been demonstrated to. If the questions are broad, generic and evenly spread, the buyer is early and genuinely surveying, which is the case where a clear response has the most room to influence what the eventual proposal document asks for.
That reading changes what you emphasise inside the constraint of answering each question directly, and occasionally it changes whether responding is worth it at all. It is also the cheapest competitive intelligence in the whole process, and unlike most of what follows it costs nothing but attention.
The three answers that get a response cut
The one that does not contain a yes or a no. Any question capable of a direct answer that receives a paragraph instead is read as a no with decoration.
The one that contradicts another answer. Where different people answer different sections without a single reader at the end, an RFI routinely claims a capability in one answer and a roadmap item in another. One person reads the whole document before it goes.
The one copied from the last RFI. Reuse is efficient and detectable, and the detectable version names the previous buyer's sector, or answers a question about deployment with a hosting model this buyer has already excluded. Reuse the substance and re-read every answer against this document's own questions.
- Yes: The issuer's numbering and question order are preserved exactly
- Yes: Every answer opens with a direct yes, no or qualified answer
- Yes: Every partial capability is labelled partial in the answer itself
- Yes: One person has read the whole document for contradictions
- No: Pricing appears where the RFI did not request it
- No: Generic collateral is attached in place of an answer
- Depends: A named person and direct contact details appear at the end
Where the RFI sits in the process
An RFI is the cheapest touch in a formal buying process and the one where the smallest amount of care produces the largest relative advantage, because the competing responses are usually assembled quickly.
What follows it is a different document with different rules. The proposal that comes later is read by somebody who was not in the process at this stage, and the structure that survives that reader is set out in a worked sales proposal. The emails that carry either document are their own craft, covered in proposal email templates.
It is also worth understanding the instrument from the other side. The reasons an organisation issues these documents, what the format is good at and what it suppresses, are in marketing RFPs, and reading it makes the subtext of a question set considerably easier to interpret. Where the buyer is a procurement function rather than an operating team, the approach that gets a reply at all is in cold email for procurement managers.
One boundary is worth stating because the term collides. In construction and engineering an RFI is a contractor's request for information to the design team about a drawing or a specification, which is a different document with different conventions. Everything here is about the vendor-selection sense.
The short version
An RFI decides whether you are on a list, not whether you win. It is a sorting task, so the response is judged on how easily it can be compared rather than on how much it contains.
Keep the issuer's question order and numbering. Open every answer with a direct answer and put the boundary in the same sentence. Label partial capabilities as partial and disclose a genuine gap early rather than letting an evaluator find it. Leave pricing out unless it was asked for, leave the capability deck out entirely, and have one person read the whole thing for contradictions before it goes. Then save the answers properly, because the next one will ask eleven of the same questions.
If formal processes are the only route your pipeline has into new accounts, the constraint is upstream of the document. See what a first campaign produces for your market.
Format definitions verified against SiftHub's RFI response guide as fetched on 23 August 2026. Publishers revise these pages; confirm current text before relying on it.
Frequently asked questions.
Frequently asked questions- What is the difference between an RFI and an RFP?
- An RFI comes first and produces a shortlist rather than an award. SiftHub's guide draws the line at scope: unlike RFPs, which require comprehensive proposals, RFIs focus on demonstrating basic capabilities, qualifications and approach without detailed pricing or implementation plans. Treating one as the other is the most common way to lose at this stage.
- Should we include pricing in an RFI response?
- Only if the RFI asks for it. The absence of a pricing section is usually deliberate at this stage, and volunteering figures answers a question nobody asked while handing an evaluator the one axis you have least control over before scope is settled. If a rough range is genuinely required, give the range and name what would move it.
- How long should an RFI response be?
- Match it to the questions asked rather than to a page target. The usable rule is structural: one direct answer per question, supporting detail only where it changes the answer, and nothing attached that a question did not name. Length is read as a signal about judgment rather than about effort, and a response longer than the question set warrants reads as padding.
- Can we reuse answers from a previous RFI?
- Reuse the substance and re-read every answer against this document's questions. Detectable reuse is the fastest way to be cut, and it usually surfaces as a previous buyer's sector appearing in an answer, or a deployment model this buyer has already excluded. One person should read the whole assembled response for contradictions before it goes.
About the author.
B2B cold email experts helping companies generate qualified leads through done-for-you outreach campaigns.
RevenueFlow Team
Explore more.
Ready to scale your outreach?
We build GTM engines that book real meetings. See the receipts.
Related articles.
RFP Response Executive Summary Sample: One Page, Written Last, Read First
The executive summary decides how carefully the rest of a response gets read, and is usually written last by whoever has least time. A worked sample and what to cut.
RFP Software: Who Publishes the Rankings, and What the Category Automates
Most ranked lists of RFP software are published by a product on the list. What the category automates is retrieval over a library somebody still has to maintain.
Bid or No Bid: The Decision That Costs the Most and Gets the Least Time
Responding to an RFP is usually a default rather than a decision. The standard qualification frameworks return yes here by construction, which is the problem.
Meeting Reminder Emails: Six Templates, and the Line That Makes Them Correspondence
A reminder to someone who accepted a meeting is administration of an agreement, not a bump. Six complete messages, what each has to carry, and how many is too many.
Sample Sales Proposal: Written for the Person Who Was Not on the Call
The decisive reader of a sales proposal usually reaches it by forward, having attended no calls. That one fact reorders every section of the standard template.
Sales Funnel Template: Six Stages and the Exit Criterion for Each
The exit criteria column carries all the value in a funnel template and is the one left blank. Six stages, what belongs in each, and the sizing arithmetic.