4 ms·
It seems to me you have a number of options here. The simplest is to give him the source code, and walk away, and chalk the whole thing up as a learning experi
by michael_dorfman 16y ago
It seems to me you have a number of options here.
The simplest is to give him the source code, and walk away, and chalk the whole thing up as a learning experience. In the unlikely event he is able to make something happen with the product, you're entitled to 30% of the profit, but I wouldn't count on it. In this option, you do not keep a copy of the code for yourself, or do anything with it in the future.
Option #2 is to have a long, hard talk with him. Lay everything out on the table, as clearly as possible. Explain that you have developed a product that you think is ready to ship, and that you don't want to do any more work until it does ship. If he has a list of things he things are necessary to get in the product before the initial ship date, have him itemize the list in detail, and then discuss and agree (in writing) on each one.
Option #3 is to buy your "partner" out. Ask him to assign all rights to the product to you, in exchange for some consideration you both agree on (cash, or a share of the profits.) Needless to say, you need to get the agreement in writing this time.
Option #4 is to talk to a lawyer. I'm not a lawyer, but I would be absolutely shocked if you have any direct rights to the source code. I believe you'd be exposing yourself to potential legal action if you tried to release this code, or do anything else with it on your own. You really don't want to go down that road.