Just completed a proposal this week for a Web site that needed to be revamped. I got another one to do early next week. When I first started this business, I hated doing proposal. I just wanted to sit down with the client and ask about 50 questions. It was a pretty self-centered approach on my part.

This week’s proposal was almost fun. Why, what was the difference? I have most of the support verbage worked out in a document template, so I don’t have to waste time on getting all the support materials together or writing from scratch. I used to have to assemble my resume, statement of qualifications, etc. With the template that is all complete and I can focus on the client and the problem.

The problem: Out-of balance content. Almost every Web site that I see for redesign or revamping has the same problem. The Web site has become hard to manage with all the various added applications and sections. Web sites grow like bushes and sometimes they grow in odd directions. A redesign is time to cut back the odd branches, consolidate applications and balance out the content.

Problem two: Initial purpose. Most Web sites were started with the clear goal of saving time and money for the operation. “Oh, we can just put those documents on the Web site,” says the perky and ambitious marketing person. Sounds good, but then someone has to update it or add the new updated document. You think your closet is cluttered – you should see most Web site’s main file area.

One client has a Human Resources intranet with all the HR documents from the last five years. Even with the hundreds of PDF files, I know the problem is not a concern because of the number of files, but the degrading of the site performance by all those obsolete files.

Most Web sites admins focus on the site itself and forget that the initial purpose was to network in the industry and build links with others. With almost every proposal, I encourage the client to do a Launch campaign and get out there and network with others sites that can help them achieve their initial goals.

Problem three: proprietary applications. Many Web site developers choose proprietary applications and only later discover that the functionality they need costs more and more with every update. I am a proponent of open-source applications. From a programmer standpoint, I can make changes without having to finance the national debt of some third world country. Also open-source applications work well together more often than proprietary applications where programmers are seeking unique code not commonality.

Just my thoughts to keep you in the loop. Now get out there and Webify!