Peter,

These are all very good ideas, but if your system is a key element to your clients business, they may want some in place to protect their business in the long term. One way to do this  is  to escrow the code in case something happens to you support of the system. You may want to keep that in mind if there is an issue over the long term support of the system. I have had to do this with some of the system I have built in the past.

David

From: plug-discuss-bounces@lists.plug.phoenix.az.us [mailto:plug-discuss-bounces@lists.plug.phoenix.az.us] On Behalf Of AZ Pete
Sent: Friday, August 10, 2012 8:40 PM
To: PLUG Discuss
Subject: Software Contracts

Hi All,

A few weeks ago I posted about some troubles I was having regarding compensation arrangement with a long time client. I received many helpful replies, so thanks to all who shared their thoughts.  I did open a dialog with my client and things are going quite well. We are still working out some of the details, but it looks like we will be able to reach an agreement that will be equitable to both of us.

I would now like to have a more formal contract signed between me and the client such that I can protect my software. It was always understood that I retained copyright and ownership of the software (i.e. client was merely licensing it). I would now like to get that understanding in writing.  Does anyone have a standard contract that they use which has a similar clause in it.  Basically, I'm looking for some kind of contract that would:

1) State that I retain ownership and copyright to the software.
2) That they cannot take the software and modify it, distribute it, etc.
3) Other important things that I'm not thinking of. :-)

If anyone can give me a basic contract that they use (remove all references to your personal entity, of course), I'd greatly appreciate it.

Thanks,
Peter

P.S. Also posted to AzPHP list.

---

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2197 / Virus Database: 2437/5192 - Release Date: 08/10/12