Re: VB Project cost estimation
From: Ralph (nt_consulting32_at_hotmail.com)
Date: 02/19/04
- Next message: Bob O`Bob: "Re: Runtime error 381 in VB app"
- Previous message: Bob O`Bob: "Re: VB Project cost estimation"
- In reply to: Peter Aitken: "VB Project cost estimation"
- Next in thread: Bob O`Bob: "Re: VB Project cost estimation"
- Reply: Bob O`Bob: "Re: VB Project cost estimation"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 19 Feb 2004 14:45:23 -0600
"Peter Aitken" <paitken@CRAPnc.rr.com> wrote in message
news:fa6Zb.20165$eL2.1935717@twister.southeast.rr.com...
> In the past all my paid VB programming has been billed on an hourly basis.
> Now a client wants me to quote a figure for an entire project and I am not
> quite sure how to go about it. I thought that perhaps someone has
developed
> a set of guidelines for estimating the time a project will take given the
> number of forms, database tables, etc. Or, perhaps a utility to assist in
> the process?
>
> --
> Peter Aitken
>
> Remove the crap from my email address before using.
Peter,
This is good question for which there is no good answer. I have been doing
this for 20+ years and never came across a easy answer - it aways 'depends'.
But I have two suggestions to offer:
1) Set down and figure out what you can reasonable do, afford or live with.
Add a bit of risk for EVERYTHING that you are in doubt of. And then STICK TO
IT. Don't even think about what you think someone might pay until you have a
decent feeling for what you can live with. Do your homework.
Because it doesn't matter if someone else can do it for half, or if you
could have gotten twice - it is only important that you do a good job and
the client is happy and you are happy. There is nothing worse than putting
in 12 hours days while going broke. Also consider the customer isn't going
to be any happier if he paid low dollar for a crappy application, than if he
paid too much. <g>
Don't be afraid to walk away. I have had a ton of clients initially turn my
quote down only to later have me come back either to clean-up somebody
else's 'low-bid' or because after shopping around they found I was lowest
after all.
2) With any kind of negotiation - the first one to mention a dollar amount -
usually LOSES! Don't be afraid to ask. Repeatedly and in different ways. As
a collary - until it is time to sign on the dotted line - consider all
quotes to be a 'range', and jump on anything that is beyond what you figured
on. - "Well for that degree of security I will have to add another week for
testing, so we are looking at the high-side of ...".
-ralph
- Next message: Bob O`Bob: "Re: Runtime error 381 in VB app"
- Previous message: Bob O`Bob: "Re: VB Project cost estimation"
- In reply to: Peter Aitken: "VB Project cost estimation"
- Next in thread: Bob O`Bob: "Re: VB Project cost estimation"
- Reply: Bob O`Bob: "Re: VB Project cost estimation"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
