🚀 go-pugleaf

Peter Nolan wrote:
> 
> On Fri, 23 Jul 1999 22:21:52 GMT, Mr_Pibb <mr_pibb_@hotmail.com>
> wrote:
> 
> >>Just some things maybe to consider:
> >>Figure out how much time it will take you to program it.
> 
> That's basically why I wanted the going rate to give him an idea of
> what it might cost. He has seen some of the stuff I have written
> specifically for our CNC division but doesn't appreciate the hours
> that sometimes goes into them, specially tweaking after using it for
> some time.
> 
> >>you should consider how much time this will save him and
> >>thus how much money that will put in his pocket. If he plans on putting it
> >>on many computers you need to change per licensed copy.
> 
> That's true in real life, but it is a small business and he is a
> friend. In fact I offered to do it as a part-time project for free but
> he insists on paying a fair price. I aint going to argue with someone
> who *wants* to give me money! <g>
> 
> Thanks for the thoughts though.



Treat the project as you would any professional project.  Work out your
entire agreement and put it in writing.  Work together to consider the
-whole- project, including his unspoken expectations, his budget,
support issues, usage-rights, and so on.

Remember this:  when someone asks what you charge "per hour," that's not
really what they want to know.  They want to know, bottom line, what it
will COST, and at what times and in what ways ... and you must be
prepared to tell them and to stick to it, even with a friend.