Make up your bloody mind

Contracts are signed by the client and the developer. Often you hear about the client making a developer produce work without signing a contract, and the developer, for the sake of $$, does wat the client requests, and in the end the client refuses to pay, and the sort...

Then there is the case where the client signs the contract. oh now all must be well. no. Apparently many of these clients sign for the sake of making the developer hurry and produce work. Often in web development projects there is a part that states "the developer will produce work to the requirements of the client. any design which the client requires a change after approval of the prototype will be liable to charges".

How often, though, do clients keep changing their minds on a pre-agreed design?? we create the prototype for approval, and the clients say ok. after weeks of development, then the client says: "i think this and that is better. change." And how often does the developer nod and agree without charging the client? sometimes the change on paper is small, like "adding a drop-down list", but they do not realize that these changes require a lot of re-design not only on the interface, but internal components and databases as well. And when the change is done, they will say: "hmm. i think you add something more to that". Why can't these clients make these decisions during the prototype stage? the prototype is meant to be a "toy" for them to play with, but they neva take the word prototype seriously. How often do you hear a web project bust its deadline and clients complain on the competency of the developer? LOL. Make up your mind and do some soul-searching. please.