how-to block ads
|
jeffjs
join:2000-12-11
US
 ·Comcast
| reply to Airplane777
Re: Sub-contracted software developer owning software ?
As you described it now, the programmer will own the code, but he could license it back to the person who hired him - could be a $0 license, or he could have royalty free use, or both.
your boss should have documented his requirements and executed an agreement stating who owns what, what work is being done, what the programmer must deliever, how to ensure your boss got what he wanted, and there should have been several termination clauses (agreement terminated due to missed dates, wrong implementation, misuse, etc).
Stop the work now. Go see a lawyer.
--
I walk upon this Earth by the power of my own two legs. | |
Airplane777
join:2004-06-20
| Thanks for all the great input guys.
Our boss had the idea of what he wanted, and described it to the programmer. Our boss even helped the programmer out by finding some solutions to writing the code.
We want to be able to use the final product, mainly for all our B2B IT support clients...and even sell the product to other people who would like to use it. | |
DC DSL
Stays crunchy even in milk
Premium
join:2000-07-30
Washington, DC
 ·Covad Communications
·Verizon Online DSL
| I've been doing custom development since 1980. My standard contract gives me full, perpetual ownership of and rights to all work products, "know how" or other intellectual property developed; the client has a perpetual license to use the program product, or to subsequently modify it as may be necessary or desired as time progresses. The client is limited to using the program product solely for the purposes stated in the contract. The code or product cannot be sold or licensed to another party (though usage rights transfer automatically if the company merges or is sold). I am free to re-use the code and know-how as I choose without further consideration or obligation to the client.
In cases where there are specific business details or methods that are considered proprietary/trade secret by the client and are identified as such prior to commencement, and which have unique attributes that distinguish them from any other implementation of a similar process, those are excepted from my ownership rights. (There is very little of this in typical LOB and BO applications; it's mainly found in industrial and scientific domains.)
As for resale product, the terms and conditions have to be spelled out in the contract. I typically require my copyright be presented everywhere theirs is, prohibit distribution of source code to purchasers, and charge a considerably higher fee and require a guaranteed percentage of gross sales over the lifetime the product is sold. I also require the EULA restricts sale/use to only non-competitive customers (i.e., that don't produce the same or similar software product).
Do make sure you clearly identify and record in advance any aspects/attributes your company considers proprietary/privileged/trade secret, and include them in the contract.
For a resale product, make sure you arrive at a design strategy that makes it difficult for others to reverse-engineer the product. (There's no such thing as "impossible.") Be sure to have the EULA developed by an attorney with specific expertise in current software copyright law...this excludes 99% of corporate counsel. Do not be surprised if the developer wants a 100%-200% premium for development up front. Typically the developer will get 40%-60% of total product gross between initial development and percentage of lifetime sales. Depending on what a product does and how much of it the developer had to divine/design versus the client's input, it isn't unheard of for the developer's take to go as high as 90%.
--
There is no giant fur-bearing trout. | |
-
|
