Re: When to quote?
- From: Erwin Moller <since_humans_read_this_I_am_spammed_too_much@xxxxxxxxxxxxxxxx>
- Date: Tue, 28 Nov 2006 12:03:14 +0100
battle.chris@xxxxxxxxx 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?
Thanks.
Hi
My 2 cents:
If you have a client like that you are in risk of producing something that
is not what they want. That is trouble.
In most cases the client don't know excactly what they want and need your
help to form their own opinion.
How I approach this: Make a rude estimate of the project, confirm that it
will cost them 20.000 plus or minus 25%. And tell them you EXPECT that at
least one person will be available to make quick decisions during
development.
In that way you can get the job, AND make sure the endproduct will be what
they want.
It also helps a lot to put one day time into it and produce a raw HTML
version that doesn't work, but show the process to the client in big lines.
(Like, here you can log in, this is what you see if you click XXX, etc)
It helps the client to form their opinion.
In case you don't trust them, and they will not help during development,
think twice before taking the job.
I NEVER develop stuff anymore without expecting the client the look over my
shoulder during development.
Just my 2 cent.
Best of luck!
Regards,
Erwin Moller
.
- References:
- When to quote?
- From: battle . chris
- When to quote?
- Prev by Date: Re: xml beginner - hierarchies
- Next by Date: Re: What is the best way to debug/test a PHP code ?
- Previous by thread: Re: When to quote?
- Next by thread: Re: When to quote?
- Index(es):
Relevant Pages
|
