Will there be potential conflict of interest/ legal issues in the future if I launch my product?
Should I take some steps to indemnify me from the other startup?
Any help is highly appreciated.
1–10 of 11 posts
Will there be potential conflict of interest/ legal issues in the future if I launch my product?
Should I take some steps to indemnify me from the other startup?
Any help is highly appreciated.
This kind of thing happens all the time. People who are experts in a field get hired by competitors in the same field.
It might be possible to avoid future problems by having a contract where you disclose that you are working in the same space as the startup and that you will not use your code in their product, nor their code in your product. It is of course, difficult to prove that down the track.
If I was in your situation, I would decline the work. 10-16 hours doesn't generate enough revenue to pay for lawyers in the future.
Put it in the contract. Get a lawyer to double check. Make it clear to them as well. I usually triple check the anti-competition and the IP clauses in all contracts. This kind of thing happens all the time. People who are experts in a field get hired by competitors in the same field.
Don't work for them, don't have them send you anything remotely technical (specifications, code, documentation).
So even in your opinion it's in the same space and similar. Don't work for them, don't have them send you anything remotely technical (specifications, code, documentation).
You could always put an escape clause into your agreement that indemnifies any and all of your projects if the alliance fails to take off financially.
The only reason I suggest this is because you're actively considering doing the work for money, suggesting that your own project is underfunded (and less financially urgent than doing the work of others). They can obviously help you with this problem if they're offering to pay you.
A lot of deals are better than 100% of nothing.
So even in your opinion it's in the same space and similar. Don't work for them, don't have them send you anything remotely technical (specifications, code, documentation).
They're a scrappy startup, and don't have much legal firepower. They're having hard time find people, so I agreed to help them. But after reading the comments here, I think it's better to back out instead of having potential future legal troubles.
And if your project becomes big money, they may sue because they are still struggling to get by and you aren't.
So I think your impetus to turn it down is the correct one.
1. Make what you're working on explicit and transparent in the contract you draw up with that startup. This has to be made / checked by lawyer in order to avoid any ambiguity.
2. Don't work for the startup.
If option #1 is worth it depends on how much profit you expect to make from the contract.