Why these two are fundamentally different
An RFI (Request for Information) or sources sought notice is the government asking the market "what can you do?" An RFP (Request for Proposal) is the government asking "prove you will deliver this, at this price, for this period." They serve different purposes and reward different writing.
An RFI is market research — the government is studying whether to buy something and from whom. Responding positions your firm in front of the program office at the moment they define requirements. Shape the requirement in the RFI; win the contract at the RFP.
- Market research — does not buy anything
- Goal: shape the future RFP requirement
- Response: 5–10 pages, concise, opinionated
- Timing: 6–18 months before contract award
- Metric: influence — not compliance
- Formal solicitation — leads to a contract award
- Goal: prove you will deliver, at price, on time
- Response: full technical, management, cost volumes
- Timing: 30–90 days from release to deadline
- Metric: evaluation score against PWS criteria
Most firms treat RFIs as junior-grade RFPs — write the same marketing narrative, submit, move on. That wastes the single most valuable opportunity in federal procurement: the chance to shape the RFP before it drops. A well-written RFI response influences scope, criteria, and incumbency assumptions. A poorly-written one is ignored.
What an RFI actually is
The legal authority is FAR 15.201 (exchanges with industry before receipt of proposals) or FAR 10 (market research). An RFI is market research. The government is trying to:
- Understand whether qualified small businesses exist for the requirement (informing set-aside decisions under the FAR rule of two).
- Validate scope assumptions and period of performance.
- Understand pricing ranges and labor category availability.
- Identify technical approaches the government had not considered.
- Gauge industry interest (too few responses may lead to cancellation or rewrite).
An RFI response is not evaluated for award. It is read by the program office and contracting officer to inform the upcoming RFP. Influence — not compliance — is the goal.
How to write an RFI response that lands
A 5-10 page RFI response, well-written, beats a 30-page boilerplate dump. Structure:
- Capability statement aligned to the specific RFI — 1-2 pages. Reference the RFI's specific language and requirements. Show you read it.
- Relevant past performance — 1-2 pages. 2-3 projects, same scope, similar scale. Named customer, dollar value, outcome metric.
- Technical approach preview — 2-3 pages. How would you solve the problem? What tools, methods, data? Show technical depth. This is where you demonstrate credibility.
- Suggested scope refinements — 1 page. Politely flag ambiguities, suggest rephrasings, propose metrics the RFP should specify. This is where influence happens.
- Small business designation and NAICS — 1 paragraph. Help the contracting officer validate set-aside eligibility under the rule of two.
- Point of contact — name, email, phone, UEI, CAGE.
The response is addressed to the contracting officer and should be signed by the responsible corporate officer.
What NOT to put in an RFI response
- Full pricing. Give ranges or labor rate bands; the government will negotiate actual price at RFP.
- Corporate marketing boilerplate unrelated to the RFI.
- Proprietary or business-confidential information without clear marking. Assume everything in an RFI response could be seen by other bidders.
- Commitments the firm cannot honor. "Yes, we can do all of it" is not credible and weakens the response.
What an RFP actually is
An RFP (or combined synopsis/solicitation, or RFQ on Schedule) is the government asking for a priced, compliant, evaluated proposal. FAR Part 15 governs negotiated procurement; Schedule RFQs fall under FAR Part 8. Key differences from RFI:
- Evaluated for award against stated factors.
- Compliant or non-compliant — late, non-conforming, or incomplete proposals are often rejected without evaluation.
- Pricing is binding. What you propose is what you will charge.
- Response window is typically 15-45 days.
How to write an RFP that wins
RFP discipline starts with compliance:
Compliance matrix first
Map every RFP requirement (Sections L, M, C, and the instructions) to a proposal section. A missed requirement loses.
Section M (evaluation criteria) drives content
The government evaluates on the criteria stated, weighted as stated. Allocate proposal content proportional to evaluation weight.
Section L (instructions) dictates format
Page limits, font size, volume structure, page numbering. Violations get proposals rejected or down-scored.
Past performance references must be relevant
"Relevant" usually means similar scope, similar scale, similar customer type. A $10M Navy engineering contract is weak past performance for a $500K Army analytics task order.
Technical approach must be specific
Boilerplate loses. Show architecture diagrams, specific tools, named team members, sample deliverables. Demonstrate you have done this before.
Pricing must be defensible
Cost realism is a common discriminator. Rates that look padded or thin both lose. Show the basis of estimate.
The no-bid decision
The single highest-leverage proposal decision is which RFPs not to bid. A no-bid saves 200-400 hours and redirects capacity to higher-PWIN opportunities. The filters:
Incumbency
Is there a clear incumbent? Has the RFP been written around that incumbent? If yes, PWIN is below 10%; usually no-bid.
Relevant past performance
Do you have it? If no, PWIN is well below agency aggregate; consider no-bid or sub instead of prime.
Response time
Can you write a quality proposal in the window? If the window is 15 days and you have no existing capture work on the opportunity, no-bid.
Price fit
Is your rate structure compatible with the expected price range? Commercial-priced firms often lose on cost realism.
Strategic value
Even with decent PWIN, is this customer worth pursuing? Some federal customers are one-and-done; others have long-term follow-on potential.
Color team reviews
At small firm scale, color team reviews can be compressed:
- Pink Team — early draft, structure and compliance review. At small scale, 2 reviewers, 2 hours.
- Red Team — full draft, win-theme and discriminator review. 2-3 reviewers, half a day.
- Gold Team — final review pre-submission. 1 senior reviewer, 2 hours.
Large firms run elaborate Blue/Black/Pink/Red/Gold/Green cycles. A solo founder skipping color teams entirely is a common and costly mistake.
Bottom line
RFI is influence. RFP is compliance. Write them differently, allocate time proportionally (a well-written RFI response is worth three polished RFP responses in the wrong direction), and no-bid aggressively. The firms that win federal AI work are the firms that shape the RFP through early engagement — not the firms that write the prettiest RFP response after the scope is already set against them.
Frequently asked questions
No. Respond when the scope matches your capability and when you have something specific to say about technical approach or scope refinement. Generic responses dilute your brand with the contracting officer.
No. RFIs are market research under FAR 10 or pre-proposal exchanges under FAR 15.201. They inform the upcoming RFP. Influence — not compliance — is the goal.
5-10 pages is usually appropriate. Longer than that dilutes the message. Shorter may miss the influence opportunity. Read the RFI instructions — some specify page limits.
The contracting officer's finding that a proposed price is neither inflated nor unreasonably low. Based on adequate price competition, market research, commercial pricing history, or cost analysis. All proposed prices must survive this determination before award.
When the incumbent is entrenched, when you lack relevant past performance at similar scale, when the response window is too tight to produce quality work, when your price structure does not fit, or when the customer is not strategically valuable.
Potentially. Government can release RFI responses under FOIA unless clearly marked proprietary. Assume anything in an RFI response could be seen by competitors. Mark proprietary sections explicitly.