>>I would recommend you Whil Hentzen's "The 1997 Developer's Guide", ISBN 0-9655093-1-1. It's the best source I found this problem.
>>
>>Vlad
>>
>>>I have a potential client who wants to pay a fix price per project, as opposed to an hourly rate. As things might get trcky, I would like to know what should I expect. Does anybody know where I can find a draft to a similar contract ?
>>>TIA
>>>Sorin
>
>***WARNING, WARNING, WARNING WILL RODGERS, you are about to
>fall into a hole!!!!!!!
>
>i would agree with getting Whil's book, but be aware that the
>fixed cost route is GOING to cost you either uncompensated time,
>or a law suit...
>
>so sayth the dinosaur. ;^)

Oh pooh!

I agree and disagree at the same time. Would you buy a car w/o knowing what you were going to pay for it first? I know all the arguments about not comparing cars to programming contracts, but all in business is not logical. Companies want fixed costs and budgets. So long as the specs are clear and agreements are made regarding add-ons and change orders, then that eliminates many issues.

In terms of uncompensated time...duh. I give time to my clients all the time. Again, it's business. If a client is good to me, then I'm good to the client.

As far as a law suit, you'll know going in if it's a bad client. My recommendation is: if a client gives you the willies now, don't bother, it will only get worse. If there isn't an element of trust and respect going into the contract, it doesn't have a chance. (Gee, didn't my wife say that to me last week about marriage?? lol) Anyway, business is business, don't fight against it, fight with it.

JMHO (yeah right, humble)

Matt