🚀 go-pugleaf

In article <1991Feb16.072856.5644@gpu.utcs.utoronto.ca> tateishi@gpu.utcs.utoronto.ca (Nao Tateishi) writes:

>This may be okay for shrink wrapped software which sell off the shelf, but for
>custom designed control software for industrial applications which you are 
>lucky to sell two versions but take three months developing, the honour system
>is playing with your livelyhood.
>
>The main reason I went this direction is that the customer specifically asked
>for source code.  If that's not a hint that they want to copy the system, I 
>don't know what is.
>
>/nt

I'd ordinarily mail you, but I think the point that needs to be made here
is of general interest to PC users.  IMHO, you are being too inflexible about
the customer's request.  Think of it from his or her point of view.  Suppose
you were run over by a truck tomorrow, or moved to Cairo or some such thing.
Where would the customer be then?  That's right, with an expensive control
system with zero support.  It only makes good business sense to require
the source code for all custom projects.

When you do custom work like this, you have to be selective with your
customers, just as they have to be selective when choosing you.  They
are going to have to ready, willing, and able to amortize your risk and
pay extra for source code.  You could even have them sign non-
disclosure agreements; that is a routine procedure in the software 
development and customization business.

If your customer has problems with all of this, then you should reconsider
whether or not you ought to be doing business together.  Shady deals or
deals where one party is distrustful of the other ought to be avoided 
to ensure long term good will, health, and happiness.


-- 
Robert C. White, Jr.          Right lane of .signature closed, merge left
The WhiteStar Corporation 					/\/\
rcw@scicom.alphacdc.com       The Owls are not what they seem. /    \