Request for Proposal (RFP)

A Request for Proposal (RFP) is a competitive sourcing document used when the buyer knows the problem but not the exact solution. Suppliers propose how they would address the requirement, including methodology, scope, deliverables, team, timeline, references, and commercial terms. Evaluation weighs approach and capability alongside price.

How it works

An RFP is more elaborate than an RFQ because it asks suppliers to design a solution. It is typically used for services, complex equipment, software, or any category where execution risk is high and differentiation matters.

• Define the business problem, success criteria, and any constraints

• Specify required content: technical approach, project plan, team CVs, references, pricing model

• Set evaluation criteria and weights before issuing, not after responses arrive

• Allow a Q&A window so suppliers can clarify ambiguities

• Score on the published rubric and shortlist for orals, demos, or pilots

Why it matters in procurement

RFPs are where strategy meets execution. Poorly written RFPs invite generic responses that are hard to compare; well-written ones force suppliers to demonstrate genuine differentiation. Common failure modes are over-specifying the solution (which suppresses innovation), under-specifying success criteria (which makes scoring subjective), and weighting price too heavily for outcomes that depend on quality. Mature category teams treat the RFP document itself as a strategic artifact.