>Hi everyone,
>
>What are the basis in computing programming costs?
>
>Thanks,
>
>Sonny

Well, I don't consider myself an expert on this subject, but since nobody answered so far...

Estimating programming costs is a very difficult subject. It is here, more than anywhere else, where Hoffstäter's Law applies: "It always takes longer than planned, even if you take Hoffstäter's Law into account."

Anyway, you must try, because the client expects a cost estimate.

First of all, don't expect to get a good estimate on a short visit. You must reserve (at least) a few days for consultations about the exact requirements. Who is going to pay for this is another problem, but even if you get nothing for this, it would be much more expensive to find out, too late, that the work is ten times more complicated than you expected initially.

It would be ideal to make a good written agreement, what is included and what is not. And what are the exact requirement of the client.

Then, in the end, what you charge - in my opinion - should be more or less proportional to the time you expect to spend. But if you expect to do the programming in one month, don't charge for one month; remember Hoffstäter's Law (see above).

Of course, you could also charge based on the benefit you give the client - and that might be much more than the time you spend. But don't let it be less. If the time it costs you is more than what it saves the client, then it isn't worth-while to do the programming.

Then, don't forget the maintenance. After delivering the software, your program will have some problems - or simply, the users won't use it correctly. So, it would be good to have some sort of maintenance contract, where you charge either "per incident" (per visit), or a yearly maintenance fee.

HTH,

Hilmar.