There are a handful of crucial steps to take when ironing out a website details before ever approaching a web designer.  Over the next few weeks I will illustrate the approximate process that we use while conceptualizing projects.  

For the average person, and especially developers, the potential of the Web as a media platform has long been understood. In my experience, it didn't take long to recognize the benefits the Web could offer to even the smallest businesses. Compared to traditional media, the overhead costs are extremely low and markets can be targeted accurately with the right techniques.

Often when organizations and large companies are searching for contractors for a particular project, they will write an in-depth document called an RFP, or Request for Proposal. Contractors in turn submit proposals based on requests in the RFP, essentially presenting a number of line-item services that comply with the RFP's scope of services in a manner that is clear, concise and complete, leaving no questions unanswered. The burden here lies not only on the contractor to respond adequately to the RFP, but on the originating organization to follow certain guidelines when writing the RFP in the first place. With that said, here are some issues that companies should avoid when sending out an RFP.