We can develop a web site if you don't have your projects requirements documented in detail. But, this article's aim is to show you that writing a Request for Proposal (RFP) is in your best interest as it will save your business time and money in the long run. When developing a custom web development project  without a detailed RFP will need to allot budget time to draft a requirements document before we start  developing the application. The time it takes depends on the complexity of the application and how quickly the specifics can be communicated but this item will need to be budget for.

Why should you prepare a detailed Request for Proposal?

• A detailed RFP allows us to itemize the cost of features
• An RFP allows us to provide a more accurate cost estimation
• It helps convey your priorities and expectations
• Provides a level "playing field" for competing vendors and allows you to compare apples to apples when receiving proposals

 
A detailed RFP will give us or any other web developers a precise explanation of what is to be developed and it's high level functionality. With a well written RFP in hand you will avoid the low bidding firms who get you started for a low price and then all through the project all you hear is "that will cost more" which inevitably leads to an overall higher project cost than that of the original "higher bidding" vendors.

How to write an RFP

The fundamental purpose of a RFP is to provide enough information for vendors to accurately bid on a project.

Things that the typical RFP contains.

• Company Background - established business, startup, etc.
• Project Summary - brief description of the project
• Project Purpose & Scope:
  • Purpose - sell products, marketing, provide customer service to existing clients, etc.
  • Target Audience - existing clients, consumers, specific niche, etc.
  • Technical Requirements - any specific technical, platform or hosting requirements, if known
  • Design Requirements - look & feel, style preferences
  • Features / Functional Requirements - at least high level functionality description
  • Content Requirements - formatted text, images, video, streaming, Flash, etc. and in what context each type of content will be used.
  • Maintenance Requirements - who will be maintaining the content after launch and what are their skill levels, etc.
  • Security Requirements - identify specific protection needs, SSL or other security features required
• Assumptions  - i.e. what you plan on providing vs. what you expect us to provide in terms of content, etc.
• Budget - if you have an established budget, it is best to include this
• Timeline - how soon do you need it? Is there a scheduled event driving the launch date?
• Decision Factors - it helps to let vendors know what your priorities are in choosing the vendor (cost, experience, etc)
• Decision Date and/or Response Deadline - include the deadline for submitting proposals

Our broad based experience will assure all aspects of the planning process are in place before development of your project begins. When you choose Point B Web you can be confident that your project will be completed in the most efficient manner.

If you have an RFP, you can send it to sales@pointbweb.com and we will respond with a formal proposal.

If you do not have an RFP and you still would like a proposal, please fill out our Request for Quote form and provide as much detail as possible.