Understand RFI vs RFP signals before committing sales resources. Use a checklist to assess scope, response instructions, fit and missing evidence.
A procurement notice lands in your inbox. The organization fits your target market, the subject matches your service, and there is a response date. Should you assign a proposal team—or first establish what the issuer is actually asking for?
Start with the request, not the account's apparent attractiveness.
RFI vs RFP is a distinction between requests for information and requests for proposals. For sales qualification, identify whether the issuer wants market input or a proposal for stated requirements, then read the actual documents. Neither acronym alone establishes available budget, your eligibility, a likely award or permission to approach people outside the stated process.
This guide provides a practical qualification worksheet. Official U.S. federal procurement provisions illustrate the distinction; they are not universal rules for private companies or other jurisdictions. The checklist is Kairos editorial guidance, not a legal interpretation of a particular solicitation or a prediction of win probability.
In the published U.S. Federal Acquisition Regulation, FAR 15.201(e) describes RFIs as a way to obtain information for planning when the government does not presently intend to award a contract. The requested information can concern price, delivery, market conditions or capabilities. That provision also distinguishes RFI responses from offers that could be accepted to form a contract.
FAR 15.203(a) describes RFPs in negotiated acquisitions as communicating requirements and soliciting proposals. Its competitive-RFP provisions identify requirements, anticipated terms, required proposal information and evaluation factors as material contents.
These are scoped reference examples. They do not determine which rules, agency deviations or instructions apply to a specific notice. For an actual opportunity, inspect the issuer's complete current documents and obtain qualified procurement or legal review where needed.
The operational lesson is straightforward: an information request and a proposal request deserve different work plans. Do not automatically turn an RFI into a full solution proposal, or treat an RFP as an invitation to run an ordinary cold-email sequence.
| Qualification question | If the notice asks for information | If the notice asks for proposals |
|---|---|---|
| What should we read first? | Purpose, questions, requested capabilities and response instructions | Requirements, submission instructions, evaluation approach and terms |
| What work might be appropriate? | A scoped capability or market-information response | An internal assessment of whether to prepare a compliant proposal |
| What remains to be established? | Whether a later procurement is planned and what has actually been specified | Whether we qualify, can deliver the scope and can meet the submission requirements |
| What should not be assumed? | A funded project or forthcoming award | A likely win, an open-ended sales conversation or unrestricted access to stakeholders |
Use the column that matches the documents, not simply the label on a search result. If the request combines stages or is unclear, record the uncertainty and use its designated clarification route.
The following sequence is a suggested internal review process. It is not a mandatory procurement standard, and it does not replace the issuer's instructions.
Locate the notice on the issuer's official portal or another source the issuer identifies. Retain the notice identifier, original URL and attachments. A forwarded email or aggregator summary is a lead to investigate, not the complete request.
Check for amendments, clarification documents and a cancellation or closure notice. If several websites reproduce the same request, group them under the underlying notice rather than counting them as independent opportunities. The source-provenance guide explains how to separate repeated publication from additional evidence.
Keep a record of the version inspected. “We saw a notice” is insufficient if the response team later works from a different attachment.
Write a plain-language summary of what the issuer asks respondents to submit. Examples could be a capability statement, answers to market-research questions, indicative information or a proposal against a defined scope. Use the document's wording to resolve the difference.
Then identify what your team would need to produce. If the issuer asks for a short capability response, do not silently turn the task into a detailed implementation design. If it asks for a structured proposal, a generic sales deck may leave its questions unanswered.
When the request's purpose is unclear, mark that as a qualification gap. Do not rename it “active evaluation” to make the opportunity appear more advanced.
Compare the required work with what your company can substantiate. Separate a keyword match from delivery fit.
For example, a notice mentioning “customer data” could concern migration, analytics, access controls or ongoing operations. A matching phrase is not enough to decide which service the issuer needs from you. Inspect deliverables, responsibilities, locations and exclusions.
Create a simple requirement-to-evidence table. For each relevant requirement, record the capability, reference or resource you could demonstrate—and any gap. Mark a proposed partner contribution as proposed until it is confirmed. Avoid treating a plan to recruit or subcontract as an existing capability.
Record the submission deadline exactly as written, including its time zone where stated. Keep clarification deadlines, any proposed delivery period and the date your team discovered the notice in separate fields. If a time zone is absent or ambiguous, seek clarification through the specified channel rather than inventing one.
A response deadline is not a guaranteed contract-award date. A planned delivery date is not evidence that your company can meet the work. Neither date should be replaced with a generic “buying window.”
Read the contact instructions before outreach. In the cited federal context, FAR 15.201(f) identifies the contracting officer as the focal point for exchanges after release of the solicitation. Other processes must be checked on their own terms. Do not substitute a guessed stakeholder list for the notice's communication procedure.
Choose a next action your team can defend:
These are working categories, not a scoring formula. An RFI is not automatically worth pursuing, and an RFP is not automatically worth declining because it is more formal. The decision should reflect the actual request and your ability to respond.
Hypothetical example. The organization, notice and response decisions below are fictional.
Harborline Services publishes an RFI about consolidating customer-support reporting. It asks vendors to describe relevant experience, integration approaches and implementation considerations. It says that the exercise is for planning and provides a specific channel for responses.
You supply reporting implementation services. A weak account note would say:
Harborline has approved a reporting replacement and is selecting an implementation partner. Assign a full proposal team and contact the operations director immediately.
That note adds an approved project, a selection process and a contact strategy that the fictional notice does not establish.
A more useful note would say:
Harborline requests planning information about consolidated support reporting. Our relevant experience may support a capability response. A replacement decision, procurement budget and later proposal request have not been established. Review the RFI questions and submit only through its stated process if participation is appropriate.
Now suppose a later, separate document requests proposals, specifies deliverables and includes submission and evaluation instructions. That changes the work to assess. It does not erase the need to check scope, eligibility, delivery resources and terms.
The commercial value of the distinction is practical: decide what work the notice warrants before committing a team. This example does not demonstrate a measured cost saving or a higher chance of winning.
Use one record per underlying notice and retain its amendments with that record. The fields below are a proposed internal format, not an industry requirement.
| Field | What to capture |
|---|---|
| Issuer and notice | Organization, original URL, identifier and notice type |
| Version checked | Inspection date, attachments and amendment references |
| Requested response | The specific information or proposal the issuer asks for |
| Relevant scope | Deliverables that match your offering, plus material exclusions |
| Participation conditions | Stated eligibility, evidence and submission requirements |
| Dates | Clarification and submission deadlines, time zones and stated delivery dates |
| Communication route | Named channel and restrictions stated in the documents |
| Unknowns | Unconfirmed budget, unclear scope or conditions requiring review |
| Internal next step | Owner, participation decision and the evidence needed to complete it |
Keep unconfirmed commercial assumptions visible. If budget is not stated, write “not stated in the documents inspected.” A contract-value estimate from another source needs its own attribution and scope; it should not quietly become available budget in your pipeline.
For a wider framework covering announcements, appointments and procurement events, see B2B buying triggers: six events and what to ask next. For revisiting an older notice, use the signal-revalidation checklist, together with the issuer's latest status and amendments.
It helps distinguish information-gathering work from proposal work. Identify the actual requested response, then assess fit and instructions. The acronym alone does not qualify an opportunity.
Do not infer a later RFP without evidence. The federal RFI provision cited here describes planning uses; the issuer's actual notice must establish any stated next step. Record an unstated future procurement as unknown.
The label alone is insufficient. Inspect funding statements and relevant conditions in the current documents, and retain their wording. Avoid converting a possible or estimated value into a confirmed spend allocation.
First check its communication instructions and applicable procurement requirements. Use the designated channel. A relevant executive title does not establish permission to bypass the stated process.
Keep a research or participation record, but do not assign committed revenue merely because the notice exists. Any forecast treatment should follow your company's qualification policy and the evidence actually established.
A procurement signal becomes useful when it changes a specific, justified action—not when it merely adds an account to a list.
Verify the notice, understand the requested response, test delivery fit and follow the communication process. Then record whether to respond, assess, clarify or decline. That gives a sales manager a decision they can inspect without inheriting an invented budget or award timeline.
Official sources checked on October 18, 2026:
These references are scoped to their published federal context. They are not a determination of governing rules, agency deviations or obligations for a particular procurement. The worksheet, participation categories and fictional example are Kairos editorial recommendations. No win-rate, conversion, budget or search-ranking outcome is claimed.
Kairos Intelligence
Complete intelligence packages per target — decision-maker profiles, estimated buying windows and objection handlers. Outreach sequences on request, per opportunity. Own it for US$7,500 once, founding price for the first 10 customers.
Learn how to qualify earnings call buying signals with a four-stage evidence framework, source checks, account worksheet and responsible outreach examples.
Build a buying committee map around a business decision. Identify roles, distinguish evidence from assumptions, and use a practical account template.