Request for proposal (RFP): most of the work happens before you write it
A good request for proposal starts with research on users and suppliers. Then use an 11-part outline and publish weighted evaluation criteria before bids arrive.
A good request for proposal (RFP) is mostly decided before you write a word. An RFP is the document a buyer sends several suppliers saying what it needs, how to respond and how responses will be judged.
Writing it is the easy part: state the problem, split must-haves from nice-to-haves, ask every supplier for the same information in the same format, and publish the evaluation criteria. The quality comes from talking first to the people who will use what you buy and learning what suppliers can actually offer.
Use an RFP when price isn't the whole answer
An RFP earns its effort when the purchase is large or hard to reverse, several suppliers could do it, and the right choice depends on more than price. For a simple item where price is the main difference, a request for quotation (RFQ) is enough. If you don't yet know what the market offers, start with a request for information (RFI). CIPS's procurement and supply cycle places an RFI before the formal tender, to learn suppliers' size, capabilities, financials, strengths and weaknesses. The procurement process shows where the RFP sits among the other steps.
The example: a warehouse system before a second site
Here is a made-up example used throughout. A regional food distributor with one warehouse wants a warehouse management system before opening a second site. Its operations director, IT lead and finance lead will judge the result, and four or five suppliers could bid.
Before you write: three pieces of research
1. Talk to the people who will use it
Ask warehouse supervisors, pickers and finance what goes wrong today and what they'd need to see in a demo. Write each requirement as a problem ("pickers need to confirm a pallet location without walking back to a terminal"), not a feature name from one vendor's website.
2. Learn what the market can offer
US federal rules are a useful model. FAR 15.201 encourages early exchanges with industry, such as market research, one-on-one meetings with potential suppliers, draft RFPs, RFIs, pre-proposal conferences and site visits. The purpose is to improve understanding of the buyer's requirements and industry capabilities, so suppliers can judge whether they can meet them.
It also says that once specific information needed to prepare proposals goes to one potential supplier, it must be made public. Private companies aren't bound by these rules, but sharing information evenly protects any process from bias and complaints.
3. Talk to people who have bought or run this kind of system
Operations managers at other distributors, or people who implemented a warehouse system at a previous job, know which requirements mattered, which nobody used and what implementation looked like. Vendors can't, because every vendor's answer is shaped by what it sells. (They will still offer.)
An 11-part RFP outline you can adapt
The US federal uniform contract format is one well-tested structure. Among other parts, it separates the statement of work (Section C), instructions to offerors (Section L) and evaluation factors for award (Section M). A private RFP can be much shorter, but keep those three parts distinct.
- Introduction and background. Who you are, why you are buying, what happens after selection.
- Scope and statement of work. The problem, the current situation and what the supplier would deliver. In the example: one warehouse in phase one, the second site next.
- Requirements. Split into must-have and nice-to-have; CIPS advises distinguishing requirements from preferences in the specification. Number each one so suppliers can answer line by line.
- Technical and security questions. Integrations, data location, access control, uptime commitments.
- Implementation and support. Plan, timeline, roles, training, support hours.
- Pricing format. A table every supplier fills in the same way, with one-time, recurring and optional costs over a fixed period, such as three years.
- Supplier information. Company background, financial stability, relevant customers and references.
- Instructions for responding. Format, page limits, where to send questions, and the deadlines for questions and submissions.
- Evaluation criteria. The factors you will score and their relative weight.
- Timeline. Issue date, question deadline, submission date, demos, decision date.
- Terms. Confidentiality, your right to reject all proposals, and whether your standard contract applies.
Set the evaluation criteria before you read a single proposal
Decide the factors and weights first and publish them in the RFP. In US federal buying, FAR 15.305 requires agencies to evaluate proposals solely on the factors and subfactors in the solicitation, and allows any rating method, including numerical weights. Private buyers aren't bound by it, but the habit stops the loudest person in the room from changing the rules after seeing the bids.
A hypothetical weighting for the example:
| Factor | Weight |
|---|---|
| Fit to must-have requirements | 35% |
| Implementation plan and support | 20% |
| Three-year total cost | 20% |
| Security and integration | 15% |
| Supplier stability and references | 10% |
The weights add up to 100%. Yours will differ; agree on them with the operations, IT and finance leads before proposals arrive. Vendor selection shows how to score against a table like this and run reference calls.
Five mistakes that make proposals impossible to compare
- Copying one vendor's feature list into the requirements. Suppliers will notice, and every proposal will be shaped around that product.
- No must-have split. Every supplier says yes to everything.
- Pricing in free text. You can't compare totals when each supplier structures pricing differently.
- Too many suppliers. Each proposal takes time to read well. Narrow the list first with an RFI.
- Treating suppliers unevenly. CIPS's evaluation guidance stresses the same deadline for everyone, recorded clarifications, and notifying all bidders of any major change.
Your next step
Before drafting, list the three people inside your company whose requirements matter most and two or three outsiders who have run a similar system. Talk to them first.
If nobody you know has run a warehouse system, the outsiders in research step 3 are the hardest to find. On Instant Expert you describe them, for example "operations managers who implemented a warehouse management system at a food distributor," or paste the LinkedIn URLs of people you have already spotted. You set what each person receives for a 15, 30, 45 or 60 minute call, and our fee is added on top, so a $100 offer costs you $125 (how it works). You're charged only when someone books; declines and invitations nobody answers within 7 days cost nothing. The directory pages for operations professionals in food distribution and procurement professionals in food distribution are one place to start, and how to prepare for an expert interview covers what to ask.