1. Company overview (3 to 5 questions)
Founded year; headcount; revenue band; geographic coverage; key certifications (SOC 2, ISO, etc.). Establishes that the vendor is a real and viable counterparty.
Comparison: RFP vs RFIScenario Deep Dive
Decision Guide / Document Choice
When to Issue an RFI Before You Write the RFP
Going straight to RFP when you do not yet know the vendor landscape is the expensive way to learn. The RFI is a 4 to 8 hour per vendor casting net exercise that lets you see which vendors exist, what they actually do, and what pricing band they sit in, before you commit 40 to 80 vendor hours each to a full RFP response. This guide is the decision (RFI first or skip), the RFI structure, and how the RFI responses translate into a sharper RFP.
The RFI vs RFP Decision
| Dimension | RFI | RFP |
|---|---|---|
| Purpose | Gather information about market and capabilities | Solicit detailed proposals with pricing and methodology |
| When to use | Vendor landscape unknown; solution approach unclear | Vendors known; success criteria defined; ready to buy |
| Number of vendors | 10 to 20 (cast wide) | 5 to 7 (focused shortlist) |
| Vendor effort per response | 4 to 8 hours | 40 to 80 hours for technical + cost proposal |
| Buyer evaluation effort | 20 to 40 hours analysis | 80 to 200 hours full scoring |
| Timeline | 2 to 4 weeks | 6 to 12 weeks |
| Commitment | No purchase commitment | Implicit commitment to award if proposals meet criteria |
| Pricing | General bands only | Detailed line-item with sealed-cost separation |
| Typical output | Vendor landscape map; RFP design input | Awarded contract |
For the three way comparison with RFQ included, see RFP vs RFQ vs RFI. For the sole source decision, see sole source vs competitive RFP.
The RFI-then-RFP Sequence
For larger or more strategic procurements, the sequence RFI then RFP is the default. The sequence adds 2 to 4 weeks of front loaded time and produces a substantially sharper RFP. Three phases:
- Phase 1: RFI (2 to 4 weeks). Issue to 10 to 20 vendors. Standard questionnaire. Collect responses. Synthesise into a vendor landscape map: who exists, what they offer, what they cost, who would be a credible RFP respondent.
- Phase 2: Internal RFP design (1 to 2 weeks). Use the RFI insights to write the RFP. Adjust scope, requirements, weighting, and pricing model based on what the RFI revealed about the market. This is where the RFI pays back the time investment: the RFP is calibrated to the actual market, not to internal assumptions.
- Phase 3: RFP (6 to 12 weeks). Standard RFP process with a focused shortlist of vendors drawn from the RFI responses. Vendors who responded to the RFI know the buyer is serious; response quality is typically higher than for cold RFPs.
Federal procurement explicitly allows pre solicitation exchanges with industry per FAR 15.201 (exchanges with industry before receipt of proposals) including RFIs and industry days. Private sector procurement should adopt the same practice for engagements where the market is unfamiliar.
The RFI Questionnaire Structure
A good RFI is short. 15 to 25 questions across five sections. Vendors complete in 4 to 8 hours. Longer RFIs reduce response rate without producing proportionately more insight.
2. Solution overview (4 to 6 questions)
What does your offering do; what does it not do; what is it best suited for; what are the main alternatives in the market and how do you differ. The fourth question often produces the most candid market intelligence.
3. Pricing (2 to 4 questions)
Typical engagement size range; pricing model (subscription, project, hourly, hybrid); discount range for committed multi-year engagements. Ranges only at this stage; detailed pricing is for the RFP.
4. References + case studies (2 to 3 questions)
Two to three case studies relevant to the buyer's situation; willingness to provide references in the subsequent RFP process. Vendors who refuse references at RFI stage are signalling early.
5. Open / other (2 to 3 questions)
What would you do differently if you were us. What questions should we have asked but did not. Is there anything in our published context that suggests we are pursuing the wrong approach. The open questions surface the insight vendors have but rarely volunteer.
Translating RFI Responses Into a Sharper RFP
The RFI delivers insight only if the buyer translates it into RFP changes. Common translation patterns:
- Adjust scope to market reality. If 18 of 20 vendors offer the must-have feature only as a year-2 roadmap item, the scope should reflect that gap or the procurement should be reframed.
- Adjust budget expectations. If the median RFI pricing band is 2x the internal budget, either the budget needs to increase or the scope needs to shrink. Discovering this at RFP stage instead of RFI stage wastes everyone's time.
- Adjust evaluation weights. If the RFI reveals that all vendors are functionally similar but differentiated by support and implementation methodology, increase the weight on those criteria in the RFP.
- Narrow the shortlist. The 20 vendor RFI becomes a 5 to 7 vendor RFP. RFI responses make the shortlist defensible; the buyer can point to specific evaluation criteria applied to RFI responses to justify who was invited to the RFP and who was not.
- Add or remove sections. If multiple RFI responses surfaced a topic the original draft RFP did not cover (data portability, training, deployment options), add a section. Vendors will appreciate the sharper RFP.
For the master RFP that follows the RFI, see the master template at requestforproposaltemplate.com and the when to issue an RFP decision framework.
Frequently Asked Questions
Q.When does an RFI make more sense than going straight to RFP?+
A.Three signals point to an RFI first. You do not yet know the universe of vendors who can solve the problem; you do not yet know which solution approach is right (build vs buy, on-premise vs cloud, in-house vs outsourced); you have a stakeholder group that needs market education before they can write a useful RFP. If you can already name the 5 to 7 vendors and you know what success looks like, skip RFI and go straight to RFP.
Q.How long should an RFI take?+
A.Two to four weeks from issue to analysis. Vendors complete an RFI in 4 to 8 hours of work (vs 40 to 80 hours for an RFP), so the response window can be shorter: typically 10 to 15 business days. Allow another week for the buyer team to digest responses and translate insights into the RFP design that follows.
Q.How many vendors should I send the RFI to?+
A.10 to 20. RFI is a casting-net exercise; the goal is breadth not depth. Include vendors you would not necessarily shortlist for the RFP because their answers may surprise you. The RFP that follows narrows to 5 to 7 vendors based on the RFI responses, so casting wide at RFI stage is the only way to find vendors you would otherwise miss.
Q.Are vendors obligated to respond to RFIs?+
A.No, and a meaningful percentage will decline. Mature vendors with limited proposal capacity often decline RFIs from buyers they do not yet have a relationship with, on the basis that responding is unfunded work with no guarantee of consideration in the follow-on RFP. Make explicit in the RFI invitation that all responding vendors will be considered for the RFP shortlist; this improves response rate substantially.
Q.What goes in an RFI questionnaire?+
A.Five sections, 15 to 25 questions total. (1) Company overview (size, financials, years in business, geographic coverage). (2) Solution overview (what does your offering do, what does it not do, what is it best for). (3) Pricing range and structure (general bands, typical engagement size, pricing model). (4) Reference clients and case studies in your category. (5) Open question on what the RFI buyer should know but did not ask. The last question often produces the most useful insight.
Q.Can I commit to purchasing after an RFI?+
A.Generally no. An RFI is explicitly non-binding; vendors are told no purchase commitment is implied. Some vendors offer pricing in the RFI response; this is indicative not contractual. For a binding offer, run the full RFP process. There are narrow exceptions where an RFI converts to direct procurement (typically sole-source justifications based on the RFI confirming only one viable vendor), but these are not the default path.