A request for proposal (RFP) is a formal invitation from a buyer asking suppliers to propose how they would solve a problem or deliver a project, and at what price.
Public procurement · Reviewed by Ray Rasouli
Ask about request for proposal (RFP)
Plain answers, with your setup in mind.
Ask anything about request for proposal (RFP). For example, how it works in your current tools.
A scripted guide for now. It does not store what you type.
Buyers use an RFP when the solution is not fully defined and price alone should not decide the winner. The RFP describes the need, the rules, the deadline and how proposals will be scored. Suppliers answer with their approach, team, experience and pricing.
A mid-size city might issue an RFP for a new permit tracking system. It explains the current process, the must-have features and the evaluation criteria. Vendors send proposals, the city scores them, may hold demos, and then awards the contract.
Public sector RFPs in Canada, the US, the UK and Australia follow strict rules on fairness and openness. Questions usually go through one contact, answers are shared with all bidders, and late or non-compliant bids are rejected.
The usual flow, step by step.
In practice
Mandatory requirements are missed.
A strong proposal can be disqualified for a missing form or signature.
The scope is unclear.
Vague needs lead to proposals that cannot be compared fairly.
Bidders answer what they want to say.
Proposals that do not follow the RFP structure are hard to score and often lose points.
Questions are asked too late.
Most RFPs have a cut-off for questions, after which no clarifications are given.
An RFP asks for a proposed solution and is scored on several factors. An RFQ asks for a price on something already clearly defined.
It varies widely. Simple ones may close in a few weeks, while large public projects can take months from posting to award.
A 30-minute discovery call with Ray, then a clear list of what to fix first. No obligation.
With Ray Rasouli. No obligation.