What is a Web Development RFP
A web development RFP (short for Request for Proposal) is a popular tool used by companies to invite vendors to bid on web development services. We've received hundreds of RFPs over the years, and two things we can say with complete confidence is 1) no two RFPs are alike, and 2) most are dreadful. (Anyone who has had to fill out RFPs on a regular basis feels our pain.)
The idea behind an RFP is that, since the same document is sent to multiple vendors, it provides an apples-to-apples vendor comparison for the company seeking services. And it will, assuming you ask on-target, relevant questions (and follow our guidelines below). It won't if your questions are confusing or off-base. Garbage in, garbage out, as they say.
RFPs vary wildly in size and scope. Some stick to just a few basic questions while others want to know a vendor's every nook and cranny. Some are as short as one page while others drag on for 50+ pages. And some are good, while most are atrociously bad.
What Makes a Good Web Development RFP?
A good RFP should be exceptionally well-researched and thought-out, although not necessarily long. Long does not equal good. Make sure it includes:
- An introduction, including the project goals and requirements
- Key questions related to your project needs and vendor capabilities, broken out by each service (i.e., web design, content management, programming, etc)
- Details that are as specific as possible for what you are looking for (and be sure to point out when you aren't positive what exactly you want and would like the vendor to make recommendations)
- Request detailed vendor information, such as how long they've been in business, how many employees will be on your team, etc
- Specific guidelines for how you would like cost/pricing information conveyed (ensures easy comparison of quotes)
- A request for references
What Makes a Bad RFP?
Oh, where to begin? There are so many ways an RFP can go off-course, but here are some of the most common ways:
- Using an uncustomized, generic RFP template, perhaps not even created for web services at all
- Not determining goals, functionality and budget before sending out the RFP, thus making it difficult (to say the least) to give you a proposal that meets your goals and functionality while fitting into your budget
- Asking too many closed-ended or Yes/No questions
- Asking the wrong questions due to poor research or understanding of the web development business
- Vague instructions and requirements
- Too much detail or not enough detail
If you're planning on using a web development RFP (and we really hope you're not), at least do all the Web firms a favor and use ours. And be sure to send us one to submit while you're at it!
