Developing Effective Websites: A Project Manager's Guide

The following minimum information should be included in a request for proposal:
project overview
analysis of site and anticipated audience needs
functional requirements
technical requirements
scheduling requirements
performance criteria
Do:
Consider the fit with your potential partner in the client contractor relationship.
Describe in detail and comprehensively what you want in a site, using plain language and no technical smokescreens.
Be as brief as possible, while still covering all the major points, and write with clarity.
Write an RFP that reads like a good business plan, presenting expected outcomes, willingness to invest, and technology resources.
Align the effort required to respond to the RFP to the size and scope of the project.
Get at least a ballpark estimate of the budget and timeline before responding to an RFP.
Get whatever other information is reasonable from the other party before responding to an RFP or evaluating a response.
Know when to walk away.
Don t:
Be overly restrictive in RFP requirements.
Present bleeding-edge features as requirements.
Assume that big companies will work only with big development houses; or small companies with small houses.
Ask for free consulting from a developer.
Be in any way unethical or dishonest in using RFPs, such as writing specs that only one supplier can fulfill but sending them to others for the sake of appearances.
Send RFPs to an overly large pool sending a few recommended vendors is sufficient and actually as many as a client can reasonably handle if vendors...