review and revision of draft documentation

At this point, we've gone through meetings, analysis, research, and draft documentation. Now that draft documentation has been prepared, it is sent out to the client. Review and possible revision of the draft documentation takes place either via telephone if the project is small, or often a meeting is advisable when the project is larger.

What usually happens is that when someone is thinking of custom system design, it is very much like going to buy a car.

Picture someone walking into a car dealership saying "I want a blue car. It definitely has to have wheels and a steering wheel, and I'd kind of like power windows".

By the time they really spend time thinking about it, and consider all the features available, and fall in love with a number, like that sun roof, the AC and full leather, they may find out that what they really prefer is a blue Mercedes. The only problem is that it's more than they have in the budget!

The great thing about web development is that we can turn a "blue car" into a "blue Mercedes" by adding features over time, it's not an either/or proposition. Helping the client to review the system draft and break development into stages is often the best solution if budget is an issue.

Your Next Step > Full System Documentation