Dispute over the software that I used to complete my task for our company [on hold]
up vote
4
down vote
favorite
my friend and I set up a e-commerce company together as %50-%50 partnership. My part of work was get product information from websites and keep the inventory accurate for our online store. We do not have any written agreement over task division among company. Since my friend has no coding skills, I was doing that part.
I have developed a web scrapper from scratch on my personal computer and the software was running on my personal computer as well. I took the software from updating an Excel file to web store daily to updating the web store inventory with webstore's provided API continuously. Since software does all my work, I look like I am not doing anything.
Now we are dissolving the partnership and there is dispute over the software. He states that it belongs to company and I should leave it. But It did not feel right to me because I created it to do my part and that does not make it companies property. During the software development none of company's resources has been used. Since we split the profit %50-%50, I was not on payroll as software developer and paid to create that software. Also we would both ship the orders so there was no clear distinction on other job duties.
I would appreciate your inputs regarding this software ownership dispute since I don't know anyone to consult regarding this issue. Thank you all already!
P.S. We are located in NJ, USA
software-development startup intellectual-property
New contributor
put on hold as off-topic by gnat, IDrinkandIKnowThings, David K, Kate Gregory, Dan Neely 3 hours ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address only a specific company or position are of limited use to future visitors. Questions seeking legal advice should be directed to legal professionals. For more information, click here." – gnat, IDrinkandIKnowThings, David K, Kate Gregory, Dan Neely
If this question can be reworded to fit the rules in the help center, please edit the question.
|
show 3 more comments
up vote
4
down vote
favorite
my friend and I set up a e-commerce company together as %50-%50 partnership. My part of work was get product information from websites and keep the inventory accurate for our online store. We do not have any written agreement over task division among company. Since my friend has no coding skills, I was doing that part.
I have developed a web scrapper from scratch on my personal computer and the software was running on my personal computer as well. I took the software from updating an Excel file to web store daily to updating the web store inventory with webstore's provided API continuously. Since software does all my work, I look like I am not doing anything.
Now we are dissolving the partnership and there is dispute over the software. He states that it belongs to company and I should leave it. But It did not feel right to me because I created it to do my part and that does not make it companies property. During the software development none of company's resources has been used. Since we split the profit %50-%50, I was not on payroll as software developer and paid to create that software. Also we would both ship the orders so there was no clear distinction on other job duties.
I would appreciate your inputs regarding this software ownership dispute since I don't know anyone to consult regarding this issue. Thank you all already!
P.S. We are located in NJ, USA
software-development startup intellectual-property
New contributor
put on hold as off-topic by gnat, IDrinkandIKnowThings, David K, Kate Gregory, Dan Neely 3 hours ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address only a specific company or position are of limited use to future visitors. Questions seeking legal advice should be directed to legal professionals. For more information, click here." – gnat, IDrinkandIKnowThings, David K, Kate Gregory, Dan Neely
If this question can be reworded to fit the rules in the help center, please edit the question.
14
You probably should consult with a lawyer, but if you developed the software specifically for a project in this company it belongs to the company and I don't think it matters that you didn't use company equipment.
– sf02
8 hours ago
5
See a lawyer, and for future reference, if you do this again, license any software you develop to the company, and make it a contract. That way you're better protected.
– Richard U
8 hours ago
3
VTC This is about law not navigating the workplace.
– IDrinkandIKnowThings
7 hours ago
4
"It did not feel right to me because I created it to do my part and that does not make it companies property" - your feeling is incorrect. That said, you both should discuss it with your company lawyer.
– Joe Strazzere
7 hours ago
1
If you developed that software to respond to your company needs, it belongs to the company.
– Danny Coulombe
4 hours ago
|
show 3 more comments
up vote
4
down vote
favorite
up vote
4
down vote
favorite
my friend and I set up a e-commerce company together as %50-%50 partnership. My part of work was get product information from websites and keep the inventory accurate for our online store. We do not have any written agreement over task division among company. Since my friend has no coding skills, I was doing that part.
I have developed a web scrapper from scratch on my personal computer and the software was running on my personal computer as well. I took the software from updating an Excel file to web store daily to updating the web store inventory with webstore's provided API continuously. Since software does all my work, I look like I am not doing anything.
Now we are dissolving the partnership and there is dispute over the software. He states that it belongs to company and I should leave it. But It did not feel right to me because I created it to do my part and that does not make it companies property. During the software development none of company's resources has been used. Since we split the profit %50-%50, I was not on payroll as software developer and paid to create that software. Also we would both ship the orders so there was no clear distinction on other job duties.
I would appreciate your inputs regarding this software ownership dispute since I don't know anyone to consult regarding this issue. Thank you all already!
P.S. We are located in NJ, USA
software-development startup intellectual-property
New contributor
my friend and I set up a e-commerce company together as %50-%50 partnership. My part of work was get product information from websites and keep the inventory accurate for our online store. We do not have any written agreement over task division among company. Since my friend has no coding skills, I was doing that part.
I have developed a web scrapper from scratch on my personal computer and the software was running on my personal computer as well. I took the software from updating an Excel file to web store daily to updating the web store inventory with webstore's provided API continuously. Since software does all my work, I look like I am not doing anything.
Now we are dissolving the partnership and there is dispute over the software. He states that it belongs to company and I should leave it. But It did not feel right to me because I created it to do my part and that does not make it companies property. During the software development none of company's resources has been used. Since we split the profit %50-%50, I was not on payroll as software developer and paid to create that software. Also we would both ship the orders so there was no clear distinction on other job duties.
I would appreciate your inputs regarding this software ownership dispute since I don't know anyone to consult regarding this issue. Thank you all already!
P.S. We are located in NJ, USA
software-development startup intellectual-property
software-development startup intellectual-property
New contributor
New contributor
edited 7 hours ago
David K
23.2k1581118
23.2k1581118
New contributor
asked 8 hours ago
Lamazone
271
271
New contributor
New contributor
put on hold as off-topic by gnat, IDrinkandIKnowThings, David K, Kate Gregory, Dan Neely 3 hours ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address only a specific company or position are of limited use to future visitors. Questions seeking legal advice should be directed to legal professionals. For more information, click here." – gnat, IDrinkandIKnowThings, David K, Kate Gregory, Dan Neely
If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as off-topic by gnat, IDrinkandIKnowThings, David K, Kate Gregory, Dan Neely 3 hours ago
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address only a specific company or position are of limited use to future visitors. Questions seeking legal advice should be directed to legal professionals. For more information, click here." – gnat, IDrinkandIKnowThings, David K, Kate Gregory, Dan Neely
If this question can be reworded to fit the rules in the help center, please edit the question.
14
You probably should consult with a lawyer, but if you developed the software specifically for a project in this company it belongs to the company and I don't think it matters that you didn't use company equipment.
– sf02
8 hours ago
5
See a lawyer, and for future reference, if you do this again, license any software you develop to the company, and make it a contract. That way you're better protected.
– Richard U
8 hours ago
3
VTC This is about law not navigating the workplace.
– IDrinkandIKnowThings
7 hours ago
4
"It did not feel right to me because I created it to do my part and that does not make it companies property" - your feeling is incorrect. That said, you both should discuss it with your company lawyer.
– Joe Strazzere
7 hours ago
1
If you developed that software to respond to your company needs, it belongs to the company.
– Danny Coulombe
4 hours ago
|
show 3 more comments
14
You probably should consult with a lawyer, but if you developed the software specifically for a project in this company it belongs to the company and I don't think it matters that you didn't use company equipment.
– sf02
8 hours ago
5
See a lawyer, and for future reference, if you do this again, license any software you develop to the company, and make it a contract. That way you're better protected.
– Richard U
8 hours ago
3
VTC This is about law not navigating the workplace.
– IDrinkandIKnowThings
7 hours ago
4
"It did not feel right to me because I created it to do my part and that does not make it companies property" - your feeling is incorrect. That said, you both should discuss it with your company lawyer.
– Joe Strazzere
7 hours ago
1
If you developed that software to respond to your company needs, it belongs to the company.
– Danny Coulombe
4 hours ago
14
14
You probably should consult with a lawyer, but if you developed the software specifically for a project in this company it belongs to the company and I don't think it matters that you didn't use company equipment.
– sf02
8 hours ago
You probably should consult with a lawyer, but if you developed the software specifically for a project in this company it belongs to the company and I don't think it matters that you didn't use company equipment.
– sf02
8 hours ago
5
5
See a lawyer, and for future reference, if you do this again, license any software you develop to the company, and make it a contract. That way you're better protected.
– Richard U
8 hours ago
See a lawyer, and for future reference, if you do this again, license any software you develop to the company, and make it a contract. That way you're better protected.
– Richard U
8 hours ago
3
3
VTC This is about law not navigating the workplace.
– IDrinkandIKnowThings
7 hours ago
VTC This is about law not navigating the workplace.
– IDrinkandIKnowThings
7 hours ago
4
4
"It did not feel right to me because I created it to do my part and that does not make it companies property" - your feeling is incorrect. That said, you both should discuss it with your company lawyer.
– Joe Strazzere
7 hours ago
"It did not feel right to me because I created it to do my part and that does not make it companies property" - your feeling is incorrect. That said, you both should discuss it with your company lawyer.
– Joe Strazzere
7 hours ago
1
1
If you developed that software to respond to your company needs, it belongs to the company.
– Danny Coulombe
4 hours ago
If you developed that software to respond to your company needs, it belongs to the company.
– Danny Coulombe
4 hours ago
|
show 3 more comments
4 Answers
4
active
oldest
votes
up vote
14
down vote
I'm not familiar with USA/NJ laws, but this seems really straightforward to me.
My part of work was get product information...
...Since my friend has no coding skills, I was doing that part.
You agreed you would do something and you decided to do it as an automated software. It was done within the company and what you both understood as "work" or your responsibility, and for the company. And therefore it's owned by the company.
Who owned the tools to create the software doesn't matter.
Also, as a former entrepreneur I have to say that being an entrepreneur requires you to have a bit of good faith, and not to dive into disputes like this. I'm sure your partner made calls with his personal phone and wore a suit he had bought himself. Starting to argue that YOUR contribution was somehow more special for any reason is counter-productive.
2
If there's no contract, any code you write is yours. Enforcing is an other costly matter.
– dan-klasson
3 hours ago
In California law, what you develop on your own time with your own money is yours, even if you signed an employment agreement to the contrary.
– Joshua
3 hours ago
@dan-klasson Founders aren't employees, they don't sign normal employee contracts (who would have authority to sign the first contract from company's side?). He signed the paper saying he owns 50% and that's if that doesn't show the intent of doing work would be ridiculous.
– Sopuli
3 hours ago
1
@Sopuli That's not ridiculous. Just because he's the co-owner doesn't mean that anything he writes is owned by the company.
– dan-klasson
3 hours ago
1
@Sopuli: These are not simply assets but copyrighted materials that fall under strict copyright laws.
– dan-klasson
2 hours ago
|
show 1 more comment
up vote
11
down vote
You seem to have worn two hats in this transaction:
- Manager responsible for selecting software.
- Developer of a software package.
Wearing Hat 1, you were responsible for selecting software with a license that meets the company's needs. There are many ways you could have done that. For example, if picking freeware you would need to check it was licensed for business use. It would have been very irresponsible to select software with a license that says "This license is valid only as long as Lamazone remains with the company.".
Back when you decided to develop the software you should have sorted out the terms and licensing. If you were doing it as part of your contribution to the company, it probably belongs to the company anyway. If it does not belong to the company, wearing Hat 1 you should have required, from yourself wearing Hat 2, a suitable license that meets the company's needs. To avoid self-dealing, you should have discussed the license with your co-owner and got his approval. Using it to do part of your job without a formal license strongly suggests that you developed it as part of your contribution to the company and the company owns it.
To fix all this now without paying a fortune to lawyers, I suggest offering your partner an exchange in which he drops any claim to company ownership of the software, so you can use it and license it to others, and you grant the company a perpetual source license to modify and use the software.
add a comment |
up vote
5
down vote
Based on experiences, it seems you own 50% of a company that owns the software you created.
Unless you can prove the software was created for other consideration (payment, trade, etc.) the company owns it. That you used your personal resources likely doesn't matter.
Meaning, when dissolving the partnership, you are entitled to 50% of the value of the assets which includes the value of the software. You can negotiate retaining the software as part of your 50%.
Since it seems there is already disagreement, you should now focus on locating legal counsel.
add a comment |
up vote
1
down vote
So many wrong answers in here.
If there is no written contract between you and your friend, you own it. If you haven't licenced it as open source it's proprietary by default. That's why when you work for professional companies they specifically mention in their contract that any code you write during work time is owned by them.
Enforcing this is another matter however. It would require a lawyer. You could always document as much as you can now and then hit the company with a lawsuit later down the road if it becomes profitable.
Keep in mind though if he has documentation himself, such as email correspondence where you discuss ownership, he could use that against you in court.
New contributor
Too short a fix for me to make an edit...did you mean proprietary where you wrote propitiatory?
– mkennedy
3 hours ago
@mkennedy yes I did. thanks
– dan-klasson
3 hours ago
add a comment |
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
14
down vote
I'm not familiar with USA/NJ laws, but this seems really straightforward to me.
My part of work was get product information...
...Since my friend has no coding skills, I was doing that part.
You agreed you would do something and you decided to do it as an automated software. It was done within the company and what you both understood as "work" or your responsibility, and for the company. And therefore it's owned by the company.
Who owned the tools to create the software doesn't matter.
Also, as a former entrepreneur I have to say that being an entrepreneur requires you to have a bit of good faith, and not to dive into disputes like this. I'm sure your partner made calls with his personal phone and wore a suit he had bought himself. Starting to argue that YOUR contribution was somehow more special for any reason is counter-productive.
2
If there's no contract, any code you write is yours. Enforcing is an other costly matter.
– dan-klasson
3 hours ago
In California law, what you develop on your own time with your own money is yours, even if you signed an employment agreement to the contrary.
– Joshua
3 hours ago
@dan-klasson Founders aren't employees, they don't sign normal employee contracts (who would have authority to sign the first contract from company's side?). He signed the paper saying he owns 50% and that's if that doesn't show the intent of doing work would be ridiculous.
– Sopuli
3 hours ago
1
@Sopuli That's not ridiculous. Just because he's the co-owner doesn't mean that anything he writes is owned by the company.
– dan-klasson
3 hours ago
1
@Sopuli: These are not simply assets but copyrighted materials that fall under strict copyright laws.
– dan-klasson
2 hours ago
|
show 1 more comment
up vote
14
down vote
I'm not familiar with USA/NJ laws, but this seems really straightforward to me.
My part of work was get product information...
...Since my friend has no coding skills, I was doing that part.
You agreed you would do something and you decided to do it as an automated software. It was done within the company and what you both understood as "work" or your responsibility, and for the company. And therefore it's owned by the company.
Who owned the tools to create the software doesn't matter.
Also, as a former entrepreneur I have to say that being an entrepreneur requires you to have a bit of good faith, and not to dive into disputes like this. I'm sure your partner made calls with his personal phone and wore a suit he had bought himself. Starting to argue that YOUR contribution was somehow more special for any reason is counter-productive.
2
If there's no contract, any code you write is yours. Enforcing is an other costly matter.
– dan-klasson
3 hours ago
In California law, what you develop on your own time with your own money is yours, even if you signed an employment agreement to the contrary.
– Joshua
3 hours ago
@dan-klasson Founders aren't employees, they don't sign normal employee contracts (who would have authority to sign the first contract from company's side?). He signed the paper saying he owns 50% and that's if that doesn't show the intent of doing work would be ridiculous.
– Sopuli
3 hours ago
1
@Sopuli That's not ridiculous. Just because he's the co-owner doesn't mean that anything he writes is owned by the company.
– dan-klasson
3 hours ago
1
@Sopuli: These are not simply assets but copyrighted materials that fall under strict copyright laws.
– dan-klasson
2 hours ago
|
show 1 more comment
up vote
14
down vote
up vote
14
down vote
I'm not familiar with USA/NJ laws, but this seems really straightforward to me.
My part of work was get product information...
...Since my friend has no coding skills, I was doing that part.
You agreed you would do something and you decided to do it as an automated software. It was done within the company and what you both understood as "work" or your responsibility, and for the company. And therefore it's owned by the company.
Who owned the tools to create the software doesn't matter.
Also, as a former entrepreneur I have to say that being an entrepreneur requires you to have a bit of good faith, and not to dive into disputes like this. I'm sure your partner made calls with his personal phone and wore a suit he had bought himself. Starting to argue that YOUR contribution was somehow more special for any reason is counter-productive.
I'm not familiar with USA/NJ laws, but this seems really straightforward to me.
My part of work was get product information...
...Since my friend has no coding skills, I was doing that part.
You agreed you would do something and you decided to do it as an automated software. It was done within the company and what you both understood as "work" or your responsibility, and for the company. And therefore it's owned by the company.
Who owned the tools to create the software doesn't matter.
Also, as a former entrepreneur I have to say that being an entrepreneur requires you to have a bit of good faith, and not to dive into disputes like this. I'm sure your partner made calls with his personal phone and wore a suit he had bought himself. Starting to argue that YOUR contribution was somehow more special for any reason is counter-productive.
answered 7 hours ago
Sopuli
1,351311
1,351311
2
If there's no contract, any code you write is yours. Enforcing is an other costly matter.
– dan-klasson
3 hours ago
In California law, what you develop on your own time with your own money is yours, even if you signed an employment agreement to the contrary.
– Joshua
3 hours ago
@dan-klasson Founders aren't employees, they don't sign normal employee contracts (who would have authority to sign the first contract from company's side?). He signed the paper saying he owns 50% and that's if that doesn't show the intent of doing work would be ridiculous.
– Sopuli
3 hours ago
1
@Sopuli That's not ridiculous. Just because he's the co-owner doesn't mean that anything he writes is owned by the company.
– dan-klasson
3 hours ago
1
@Sopuli: These are not simply assets but copyrighted materials that fall under strict copyright laws.
– dan-klasson
2 hours ago
|
show 1 more comment
2
If there's no contract, any code you write is yours. Enforcing is an other costly matter.
– dan-klasson
3 hours ago
In California law, what you develop on your own time with your own money is yours, even if you signed an employment agreement to the contrary.
– Joshua
3 hours ago
@dan-klasson Founders aren't employees, they don't sign normal employee contracts (who would have authority to sign the first contract from company's side?). He signed the paper saying he owns 50% and that's if that doesn't show the intent of doing work would be ridiculous.
– Sopuli
3 hours ago
1
@Sopuli That's not ridiculous. Just because he's the co-owner doesn't mean that anything he writes is owned by the company.
– dan-klasson
3 hours ago
1
@Sopuli: These are not simply assets but copyrighted materials that fall under strict copyright laws.
– dan-klasson
2 hours ago
2
2
If there's no contract, any code you write is yours. Enforcing is an other costly matter.
– dan-klasson
3 hours ago
If there's no contract, any code you write is yours. Enforcing is an other costly matter.
– dan-klasson
3 hours ago
In California law, what you develop on your own time with your own money is yours, even if you signed an employment agreement to the contrary.
– Joshua
3 hours ago
In California law, what you develop on your own time with your own money is yours, even if you signed an employment agreement to the contrary.
– Joshua
3 hours ago
@dan-klasson Founders aren't employees, they don't sign normal employee contracts (who would have authority to sign the first contract from company's side?). He signed the paper saying he owns 50% and that's if that doesn't show the intent of doing work would be ridiculous.
– Sopuli
3 hours ago
@dan-klasson Founders aren't employees, they don't sign normal employee contracts (who would have authority to sign the first contract from company's side?). He signed the paper saying he owns 50% and that's if that doesn't show the intent of doing work would be ridiculous.
– Sopuli
3 hours ago
1
1
@Sopuli That's not ridiculous. Just because he's the co-owner doesn't mean that anything he writes is owned by the company.
– dan-klasson
3 hours ago
@Sopuli That's not ridiculous. Just because he's the co-owner doesn't mean that anything he writes is owned by the company.
– dan-klasson
3 hours ago
1
1
@Sopuli: These are not simply assets but copyrighted materials that fall under strict copyright laws.
– dan-klasson
2 hours ago
@Sopuli: These are not simply assets but copyrighted materials that fall under strict copyright laws.
– dan-klasson
2 hours ago
|
show 1 more comment
up vote
11
down vote
You seem to have worn two hats in this transaction:
- Manager responsible for selecting software.
- Developer of a software package.
Wearing Hat 1, you were responsible for selecting software with a license that meets the company's needs. There are many ways you could have done that. For example, if picking freeware you would need to check it was licensed for business use. It would have been very irresponsible to select software with a license that says "This license is valid only as long as Lamazone remains with the company.".
Back when you decided to develop the software you should have sorted out the terms and licensing. If you were doing it as part of your contribution to the company, it probably belongs to the company anyway. If it does not belong to the company, wearing Hat 1 you should have required, from yourself wearing Hat 2, a suitable license that meets the company's needs. To avoid self-dealing, you should have discussed the license with your co-owner and got his approval. Using it to do part of your job without a formal license strongly suggests that you developed it as part of your contribution to the company and the company owns it.
To fix all this now without paying a fortune to lawyers, I suggest offering your partner an exchange in which he drops any claim to company ownership of the software, so you can use it and license it to others, and you grant the company a perpetual source license to modify and use the software.
add a comment |
up vote
11
down vote
You seem to have worn two hats in this transaction:
- Manager responsible for selecting software.
- Developer of a software package.
Wearing Hat 1, you were responsible for selecting software with a license that meets the company's needs. There are many ways you could have done that. For example, if picking freeware you would need to check it was licensed for business use. It would have been very irresponsible to select software with a license that says "This license is valid only as long as Lamazone remains with the company.".
Back when you decided to develop the software you should have sorted out the terms and licensing. If you were doing it as part of your contribution to the company, it probably belongs to the company anyway. If it does not belong to the company, wearing Hat 1 you should have required, from yourself wearing Hat 2, a suitable license that meets the company's needs. To avoid self-dealing, you should have discussed the license with your co-owner and got his approval. Using it to do part of your job without a formal license strongly suggests that you developed it as part of your contribution to the company and the company owns it.
To fix all this now without paying a fortune to lawyers, I suggest offering your partner an exchange in which he drops any claim to company ownership of the software, so you can use it and license it to others, and you grant the company a perpetual source license to modify and use the software.
add a comment |
up vote
11
down vote
up vote
11
down vote
You seem to have worn two hats in this transaction:
- Manager responsible for selecting software.
- Developer of a software package.
Wearing Hat 1, you were responsible for selecting software with a license that meets the company's needs. There are many ways you could have done that. For example, if picking freeware you would need to check it was licensed for business use. It would have been very irresponsible to select software with a license that says "This license is valid only as long as Lamazone remains with the company.".
Back when you decided to develop the software you should have sorted out the terms and licensing. If you were doing it as part of your contribution to the company, it probably belongs to the company anyway. If it does not belong to the company, wearing Hat 1 you should have required, from yourself wearing Hat 2, a suitable license that meets the company's needs. To avoid self-dealing, you should have discussed the license with your co-owner and got his approval. Using it to do part of your job without a formal license strongly suggests that you developed it as part of your contribution to the company and the company owns it.
To fix all this now without paying a fortune to lawyers, I suggest offering your partner an exchange in which he drops any claim to company ownership of the software, so you can use it and license it to others, and you grant the company a perpetual source license to modify and use the software.
You seem to have worn two hats in this transaction:
- Manager responsible for selecting software.
- Developer of a software package.
Wearing Hat 1, you were responsible for selecting software with a license that meets the company's needs. There are many ways you could have done that. For example, if picking freeware you would need to check it was licensed for business use. It would have been very irresponsible to select software with a license that says "This license is valid only as long as Lamazone remains with the company.".
Back when you decided to develop the software you should have sorted out the terms and licensing. If you were doing it as part of your contribution to the company, it probably belongs to the company anyway. If it does not belong to the company, wearing Hat 1 you should have required, from yourself wearing Hat 2, a suitable license that meets the company's needs. To avoid self-dealing, you should have discussed the license with your co-owner and got his approval. Using it to do part of your job without a formal license strongly suggests that you developed it as part of your contribution to the company and the company owns it.
To fix all this now without paying a fortune to lawyers, I suggest offering your partner an exchange in which he drops any claim to company ownership of the software, so you can use it and license it to others, and you grant the company a perpetual source license to modify and use the software.
answered 7 hours ago
Patricia Shanahan
17.6k53461
17.6k53461
add a comment |
add a comment |
up vote
5
down vote
Based on experiences, it seems you own 50% of a company that owns the software you created.
Unless you can prove the software was created for other consideration (payment, trade, etc.) the company owns it. That you used your personal resources likely doesn't matter.
Meaning, when dissolving the partnership, you are entitled to 50% of the value of the assets which includes the value of the software. You can negotiate retaining the software as part of your 50%.
Since it seems there is already disagreement, you should now focus on locating legal counsel.
add a comment |
up vote
5
down vote
Based on experiences, it seems you own 50% of a company that owns the software you created.
Unless you can prove the software was created for other consideration (payment, trade, etc.) the company owns it. That you used your personal resources likely doesn't matter.
Meaning, when dissolving the partnership, you are entitled to 50% of the value of the assets which includes the value of the software. You can negotiate retaining the software as part of your 50%.
Since it seems there is already disagreement, you should now focus on locating legal counsel.
add a comment |
up vote
5
down vote
up vote
5
down vote
Based on experiences, it seems you own 50% of a company that owns the software you created.
Unless you can prove the software was created for other consideration (payment, trade, etc.) the company owns it. That you used your personal resources likely doesn't matter.
Meaning, when dissolving the partnership, you are entitled to 50% of the value of the assets which includes the value of the software. You can negotiate retaining the software as part of your 50%.
Since it seems there is already disagreement, you should now focus on locating legal counsel.
Based on experiences, it seems you own 50% of a company that owns the software you created.
Unless you can prove the software was created for other consideration (payment, trade, etc.) the company owns it. That you used your personal resources likely doesn't matter.
Meaning, when dissolving the partnership, you are entitled to 50% of the value of the assets which includes the value of the software. You can negotiate retaining the software as part of your 50%.
Since it seems there is already disagreement, you should now focus on locating legal counsel.
answered 5 hours ago
Johns-305
1,00027
1,00027
add a comment |
add a comment |
up vote
1
down vote
So many wrong answers in here.
If there is no written contract between you and your friend, you own it. If you haven't licenced it as open source it's proprietary by default. That's why when you work for professional companies they specifically mention in their contract that any code you write during work time is owned by them.
Enforcing this is another matter however. It would require a lawyer. You could always document as much as you can now and then hit the company with a lawsuit later down the road if it becomes profitable.
Keep in mind though if he has documentation himself, such as email correspondence where you discuss ownership, he could use that against you in court.
New contributor
Too short a fix for me to make an edit...did you mean proprietary where you wrote propitiatory?
– mkennedy
3 hours ago
@mkennedy yes I did. thanks
– dan-klasson
3 hours ago
add a comment |
up vote
1
down vote
So many wrong answers in here.
If there is no written contract between you and your friend, you own it. If you haven't licenced it as open source it's proprietary by default. That's why when you work for professional companies they specifically mention in their contract that any code you write during work time is owned by them.
Enforcing this is another matter however. It would require a lawyer. You could always document as much as you can now and then hit the company with a lawsuit later down the road if it becomes profitable.
Keep in mind though if he has documentation himself, such as email correspondence where you discuss ownership, he could use that against you in court.
New contributor
Too short a fix for me to make an edit...did you mean proprietary where you wrote propitiatory?
– mkennedy
3 hours ago
@mkennedy yes I did. thanks
– dan-klasson
3 hours ago
add a comment |
up vote
1
down vote
up vote
1
down vote
So many wrong answers in here.
If there is no written contract between you and your friend, you own it. If you haven't licenced it as open source it's proprietary by default. That's why when you work for professional companies they specifically mention in their contract that any code you write during work time is owned by them.
Enforcing this is another matter however. It would require a lawyer. You could always document as much as you can now and then hit the company with a lawsuit later down the road if it becomes profitable.
Keep in mind though if he has documentation himself, such as email correspondence where you discuss ownership, he could use that against you in court.
New contributor
So many wrong answers in here.
If there is no written contract between you and your friend, you own it. If you haven't licenced it as open source it's proprietary by default. That's why when you work for professional companies they specifically mention in their contract that any code you write during work time is owned by them.
Enforcing this is another matter however. It would require a lawyer. You could always document as much as you can now and then hit the company with a lawsuit later down the road if it becomes profitable.
Keep in mind though if he has documentation himself, such as email correspondence where you discuss ownership, he could use that against you in court.
New contributor
edited 3 hours ago
New contributor
answered 3 hours ago
dan-klasson
1134
1134
New contributor
New contributor
Too short a fix for me to make an edit...did you mean proprietary where you wrote propitiatory?
– mkennedy
3 hours ago
@mkennedy yes I did. thanks
– dan-klasson
3 hours ago
add a comment |
Too short a fix for me to make an edit...did you mean proprietary where you wrote propitiatory?
– mkennedy
3 hours ago
@mkennedy yes I did. thanks
– dan-klasson
3 hours ago
Too short a fix for me to make an edit...did you mean proprietary where you wrote propitiatory?
– mkennedy
3 hours ago
Too short a fix for me to make an edit...did you mean proprietary where you wrote propitiatory?
– mkennedy
3 hours ago
@mkennedy yes I did. thanks
– dan-klasson
3 hours ago
@mkennedy yes I did. thanks
– dan-klasson
3 hours ago
add a comment |
14
You probably should consult with a lawyer, but if you developed the software specifically for a project in this company it belongs to the company and I don't think it matters that you didn't use company equipment.
– sf02
8 hours ago
5
See a lawyer, and for future reference, if you do this again, license any software you develop to the company, and make it a contract. That way you're better protected.
– Richard U
8 hours ago
3
VTC This is about law not navigating the workplace.
– IDrinkandIKnowThings
7 hours ago
4
"It did not feel right to me because I created it to do my part and that does not make it companies property" - your feeling is incorrect. That said, you both should discuss it with your company lawyer.
– Joe Strazzere
7 hours ago
1
If you developed that software to respond to your company needs, it belongs to the company.
– Danny Coulombe
4 hours ago