I could ask 10 different managers at work how to write a RFP, and get 15 different answers (but that's managers for ya).
From my experience it's a very project specific exercise, but with general guidelines. My only advice I can offer you is to do a search on good ol' Google for RFP templates, and it'll chuck up many good starting points for you.
The google search brought up loads of matches, the only problem is that all the web site I go to are trying to sell me some thing. All I need is some simple advice, in the form of a basic RFP. I get the feeling now though that there is no such thing as a simple RFP!
Try this search on Google:
|"request for proposal" example |
Thanks for the advice I think that I now have enough to go on to make an attempt at a RFP.
1. Executive Summary containing a brief description of your project development approach and costs
2. Corporate information including financial details
3. Qualifications including previous clients with contact information and relevant URLs
4. A description of your development process
5. Asset and draft delivery methods
6. Project stages
8. Quality control
10. The proposed team and their qualifications
11. Proposed schedule
12. Costs and payment details
13. Terms and conditions
Great list, odddog. Thanks.
ok so finally passed the editor ...
This info is exactly what I was looking for. Thanks for the help!
Having used RFPs what I find most useful is if you think through how you will rate the responses. I usually put the bulk of the responses into a spreadsheet and have the numerical responses total into sub-categories and then into a grand total. This helps me rank the responses. (Especially as different categories have different importance to me which I don't reveal.)
The non-numerical responses I limit in number. By reviewing both I can usually pick the top one or two vendors to then enter into discusions with.
One final but most important thing about RFPs - mandate the response format.
It is almost impossible to compare the responses if they are in different layout, use different terminology, time frames, resources, etc.
- OddDog's list is EXCELLENT - I'd start there
In general you want to do 2 things in your RFP
- 1) DETAIL WHAT YOU EXPECT
including what, when, how and address future maintenance, hosting requirements, etc
- 2) EXPLAIN HOW TO RESPOND
like someone else said, its REALLY hard to compare proposals. Look at some other sites they've done and see the type of work they do. Some designers are more graphical, some more application-minded.