>>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
>
>I don't know where to get the language, but make ABSOLUTELY sure that you have VERY STRONG language outlining the definition and requirements of change orders. A fixed price can be good for both sides, but if the project is not scoped out in detail prior to starting, then there's no way you can predict what kinds of twists and turns the road ahead may carry. I've never seen a project where there weren't reasonably significant changes in scope in the middle of the project. I think it's called development feature bloat. Be very cautious.
>
>HTH
>
>Matt

Hi Sorin - I have had contracts and found that a lot of clients
want a fixed price. As long as you scope things out and are
very clear as Matt said, you will not have any problems. YOU MUST
GET THE SPECS DOWN IN THE BEGINNING or your client will eat you
lunch. hth