Normally, if you want a professionally designed, custom-built website for your new virtual assistant business, you should be prepared to spend at least a few hundred dollars.

But, all that can change if you know where to find the best deals and the best designs for the lowest price.

First, it costs more to have a brick-and-mortar company design a website for you. Have you seen those newspaper ads that offer a 5-page website for $500? These are probably companies with physical locations. They have to charge more simply to pay for their overhead: office rent, designers' wages, advertising costs and so on.

Therefore, it would be wise to use a virtual assistant (VA) instead! As you already know, VAs often work from home so they do not have high operating costs like a big company does. On the other hand, a VA will be able to design images with quality similar to (or better than!) those of designers from big companies.

However, choose your VA with care. The best way to find the right VA for your project would be to go to visit the website of a VA association. There you can post your RFP (request for proposal) and have hundreds of talented VAs bid on your project, so you will get the best deal. You will also be able to choose your designer based on her experience, past transactions and client testimonials, so your value for money is secured.

Another route you can take is to purchase the Virtual Business Startup System, created by Tawnya Sutherland. It comes with several beautiful, easy to use templates, perfectly suited for a new VA. The templates are easy to edit wth the help of WYSIWYG (what you see is what you get) programs such as Microsoft Frontpage, Macromedia Dreamweaver and so on.

Most web development projects include one or more of the following elements...

• Database design and creation
• Server-side computer programming
• Client-side computer programming
• Web page design

Each of these elements has to work in its own right, and in cooperation with the other elements. The more complex the project, the harder it is to bring it all together and make it work correctly.

How to keep the cost down

Here's how you can make sure your web development costs don't run over budget...

1. Insist every aspect of the development is described in an Agreement document, and make sure both you and the developer sign it
2. Don't make changes after work has started

The key to achieving the second of these two items lies with the first. You should insist that an Agreement document be created, and sit in on the process.

You need both end-users and developers in the same room, working through each aspect of the development. The end result must be a document that fully describes the development, is clear (unambiguous), and easily understood by both users and programmers.

Every minute you invest creating this document greatly increases your chance of bringing the project in on budget.

Why it's worth it

Many of the problems that usually cause headaches during a complex development could have been discovered in advance, if an Agreement document had been created. When users and programmers get together and discuss their respective needs thoroughly, the resulting development is far more likely to go smoothly.

This kind of interaction forces both users and programmers to think through what's actually required to make the system work. The ongoing interaction reduces the risk that person A assumes person B knows what they're talking about.

Users are committing to a specific set of functions for an agreed price. The developer is committing to develop those functions for an agreed price. This means both users and developers have a self-interest in being thorough.

Should a user change his/her mind about something after the Agreement document is signed, the cost of development must be renegotiated. This punishes the user for failing to think things through.

Should the developer discover he/she hasn't fully understood what's required to complete some aspect of the project, he/she can't ask for more money. This punishes the developer for failing to break down each stage of the development and understand what's involved in completing it.

Assuming you do your part, you won't need to make changes after the work has started. As a result, you'll bring the project in on budget even if the developer hasn't done his/her job properly.

I've done quite a bit of research into web analytics lately, and I have found a couple of things. Google analytics Is a great tool, but it cannot be the only tool an organization relies on. Because it is a purely JavaScript based, it is unable to catch browsers that do not have JavaScript enabled, this includes the search engine robots, some hand held devices, as well as a percent of users that manually turn this off. That being said we need a tool to parse the log files from the server and to give us information about these users, as well as providing us with "on demand" stats where as Google's stats are next day. The server logs also contain a wealth of other information that we are collecting automatically, so we might as well take advantage of it.

I have come to the conclusion that we need to use Google Analytics but we also need a tool that reads the server logs. There are quite a variety of tools that would fill this need. Google recently purchased Urchin who's web analysis product runs Google analytics, costs about $3k and will work with the Google Mini, Urchin also gives the ability to read logs from server software other than IIS (like apache, the software used for open source applications) .

Urchin will be releasing another version shortly, and this will be the first release since the Google buyout. Another option is WebTrends Analytics it costs about $4k. It Like Urchin will read both IIS and Apache logs, and has a web interface for users. The last product is NetTracker, it runs about $4k for the software, and another grand for support. it was recently bought out by Unica. The administration of netTracker is not the smoothest, and the support seems to have declined on quality since the buy out.