Writing an RFP and submitting it to prospective website developers is one of the first steps in the website project life cycle (following a comprehensive web strategy session).

Developing a website is a risky undertaking, and many result in failure. The primary reason for project failures is a disconnect between the client's and the developer's expectations. This usually occurs because it is impossible for the client to understand the vender's "language" and nearly impossible for the vendor to clearly understand the client's needs based on a single document.
Unfortunately, the typical RFP process accepts this type of interaction, and the possibilities for jeopardizing the success of a web project increases.

The best way to reduce the likelihood of a project failing is to communicate your expectations within the RFP.  This is easier said than done.  Without having a wealth of experience in web design projects, it is difficult to know your own expectations.  For instance, a good RFP contains the following items that are essential for a prospective vendor to write a solid proposal.

• timelines
• technologies
• documentation requirements
• licenses and software fees
• functionality requirements
• design and usability expectations
• testing and debugging procedures,
• project management expectations
• meetings  and communication requirements
• hardware and hosting requirements
• resumes of senior staff
• previous related work
• database requirements
• third party integration

The best way to prepare an RFP is to have someone who understands both the client and vendor sides to write the document.  This ensures that if there are breakdowns in communication, a seasoned expert can translate for both parties.  District Agency can help you strategize and formulate a plan for your project.  This includes understanding your expectations, and properly requesting them in a well written RFP.  We have written and responded to 100's of web project RFP's and can offer your organization expertise in creating your own.