|
|
Posted by CptDondo on 11/29/06 01:09
battle.chris@gmail.com wrote:
> Hi.
>
> Our development team has been offered a project that's far bigger than
> anything we've done previously.
>
> The client wants time estimates and quotes, but has only provided a
> fairly brief outline of requirements. My question is: how do we address
> this? Should we make a best guess? Quote for the development of a
> function spec, then quote on the project once it's been completed?
I agree with the other posters. I would also add that you allocate and
specify the number of client contact hours in the job, especially if you
think the client is unsure of the whole process. I got a really nice
job once, we bid it lump sum at 300 hours, and the post mortem showed we
did it in just about 225. Should have made a good profit. But the
client *required* over 300 hours of meetings over many days, and we had
nothing in the contract to limit that. Needless to say, we lost our ass*s.
There are very good contract books for consultants. Google for "errors
and omissions insurance". Many insurance companies have contract
handbooks you can download for free. (And don't be afraid to download
one for engineers, architects, whatever. The principles are the same.)
Navigation:
[Reply to this message]
|