[thelist] How to estimate a job

[ERIC JOHNSON]

This is a great point.

While a contract is nice and binding and such, it's so easy to glaze over such non-personal information, no matter the level of importance.  A thorough discussion to top off the contract will oft times not only allow your client (who may not be technical and needs a "high-level" discussion anyway) to gain a deeper understanding of what you'll be doing.  It may actually be an act by which they learn to respect you as a person since you are so seemingly dedicated to providing what they want that you're willing to use some of your time to go into details on a more personal level.

When a job consists of going back to a computer and coding in order to get a final product, a lot of personality is lost.  Nothing wrong with trying to fit in as many hand shakes and as much eye contact as possible.

Good technical sense is rarely good business sense.  The likewise is also true.

Depending on your situation, it'll vary.  I often use something similar to the 1.35 calculation.  Double was good two years ago but now I like to toss some value in - nowadays it can make the difference.

Good Luck,

Eric Johnson

>>> marty at face2interface.com 07/10/02 11:02AM >>>
At 08:47 PM 7/10/02 +0200, Hershel Robinson wrote:
Best bet imo is to be
very detailed on the contract as to what you will do; more importantly have
a long detailed discussion taking care that your client understands what
you will do for the price you agree on -- and what won't be done unless
extra is paid.

hth,

Marty