Key Information to Include and Request from an RFP for a New Website
Nov 17, 2011 by Marissa Berger
When writing a Request for Proposal for a web development project, consider writing it with the end goal in mind: to find the most qualified vendor for your project who can work within your requirements. If you want a good response with accurate pricing and schedule, then you will need to put effort in providing the same level of detail and accuracy in your document.
An RFP can be organized into three main sections.
- Information about the company requesting the proposal
- Requirements the vendors responding to the proposal must meet
- Clear instructions about the process itself
Information about the company requesting the proposal
The goal of this section is to quickly inform the vendor of who the company is, what it does, and what it needs. Consider including:
- Company description
- Brief history
- Key competitors
- Current website situation
- Reason(s) for developing a new website or re-designing an existing website
- Primary goals (what would make the project a success?)
- Secondary goals (what are other important but not critical goals?)
- Functionality list as clear as possible. For each task, include the name of the task, a description, what its purpose is, and links to examples if any. Such a list can include the need for:
- a content management system
- file, image, and video management
- search engine optimization
- social media marketing
- press release archiving
- searchable staff directory
- etc.
- Any technical mandatories with their detailed specifications, such as:
- site must be compatible with an internal CRM or inventory system
- site must be hosted in-house
- etc.
- Budget range for project
- Desired timeline
Requirements the vendors responding to the proposal must meet
This is your chance to gather all the information you need about the vendor in order to make an informed decision. Consider asking:
- How many years have they been in business?
- Who makes up the team? Is it in-house? Is it local?
- Can they provide a diversified portfolio?
- Do they have comparable experience?
- What will their process be?
- Can they provide current references?
- Are they insured for general liability and errors and omissions?
This is also your chance to gather information specific to the scope of the project. Consider evaluating:
- Is each item adequately described?
- Have all functionality items been included?
- Was the project cost itemized?
- Was a timeline provided?
- Did they define technical terms?
Clear instructions about the process itself
It’s important that the process is described so all deadlines are met. Consider including:
- Who the decision makers are
- What criteria will be used to choose the final vendor
- All deadlines:
- Deadline for questions about the RFP and how they should be submitted
- Date when questions will be answered and where to find the answers
- Deadline for proposal submission and how they should be submitted (online, printed, number of copies, etc.)
- Date when vendors will be notified if they made it to the in-person interview step
- Approximate dates for in-person interviews
- Date when final vendor will be chosen and notified
- Date when the contract will be finalized
- Date when project is expected to start
- Date when project is expected to be completed
The more specific the RFP is, the more specific the proposal will be. However, expect vendors to have questions, to include the assumptions they are making, and to provide costs in ranges since not all questions will be answered. Finally, the most important consideration is to make sure you compare apples to apples so you end up with indeed the best candidate.



















There are many details to think about when developing an e-commerce site. We have developed the list of questions below which help us discover what “size” e-commerce site we will be building. An important part of our job is to guide a client through these to determine what is really needed to meet goals, budget, and timeline.
E-commerce websites seem straightforward, and some of them are. However, we tend to end up building the complicated ones! They are only complicated because there are many, many details to consider and test… both on our end and the client’s end. It’s best to do all of the planning at the beginning to avoid changing specifications as the site is being built. Here are a few key items to consider.
It is widely understood that a content management system allows you to both edit the current content of your site and add new content using the provided templates. One advantage of a CMS that’s not that widely known is personalization. Instead of sending everyone to your homepage and hoping that they connect the dots properly, you can create custom “mini-sites” for each prospect, using hand-picked samples to show how you meet their particular needs. Using a CMS in this way evolves your website from an informational brochure to a user-friendly sales tool.
Unless you have an e-commerce website where the action you want your visitors to take (buy now) happens within the site itself, you have to work a little harder on adding legitimate calls to action to your site without going over the top with “click here” buttons.




Recent Comments