Last week, we discussed submitting the proposal for your project including your sales teams. Of course, there is much you should include in your terms and conditions.
Your T&Cs should also address the intellectual property involved in the project. To begin with, there should be agreement on the ownership of the work. Is this work for hire? Or, is the purchase of solution including the licensing of the software? Ultimately, there can only be one owner. So, if you sell it, you canâ€™t re-use it.
Many developers struggle with, or even overlook, the value of their software. But since there can only be one owner, it is important for your customer to understand that you will need to start from scratch, which will cost additional time and expense. In addition, you will not be able to re-use code from previous projects which will be more reliable and robust.
Eventually, Alliance Partners often develop standard modules for re-use. By branding these modules, it may be easier to charge your customer for its use. But donâ€™t make the mistake of simply giving the value away. For instance, â€˜Oh, Iâ€™ve donâ€™t that type of project before, so I can reuse the code and do it in half the time, so Iâ€™ll charge half the price.â€™ No, the project value is still the same. Your efficiency should be your reward to keep.
But, Iâ€™m not naÃ¯ve. I understand that customers often want to â€˜ownâ€™ the software. There is the brute force logic of we bought it, so we should own it. And, the common rationale that you might go out of business, so they just want to protect themselves. In which case, you need to explain the principal of ownership and licensing.
Donâ€™t get me wrong. It is OK to appease the customer by giving them the source code, you just need to provide it with a license so you retain ownership. But, you should consider (and address) the following issues:
- What if they copy/modify?
- Can they transfer/resell?
- Can they reverse engineer
But what if there is an issue with the proprietary nature of the application? No problem, simply define which aspects of the application are proprietary. Then, section out that work which will be done and the ownership will be transferred to them without possibility for re-use and therefore no licensing is required. However, all other development should be provided under license and re-use retained.
Originally posted by Jack Barber at http://buildingstrongerpartners.wordpress.com/2010/11/30/proposals-2-of-3-terms- and-conditions/