I'm looking for guidance from someone who has successfully hired a freelancer to assist with writing software they later marketed publicly. Simply, what kind of software agreement should I have the freelancer sign so I have full rights over the code and cannot be sued later. I'm currently independent but have plans to launch a software company once I've perfected my software products.
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
closed as not constructive by maple_shaft♦ Mar 6 '13 at 15:50
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.
As a former lawyer, and as someone who sometimes hires contractors, I'd say you have two broad concerns in this type of arrangement:
As to 1) you're generally going to want a perpetual, royalty-free assignment in full of all copyrightable material, patentable concepts & ideas, potential trade-secrets, or any know-how that the person obtains or creates while working for you. Additionally you'll want to prohibit them from using any creations created for you for any other purpose, including from creating derivative works without your permission, or after the term of the contract is over. Sometimes, I also see these contracts try to tie up anything these guys create that could arguably have something to do with their work for you or that has stemmed from anything they've done for you. There may be other things I'm not remembering and there are probably better ways to word these things that legitimate lawyers have spent days poring over to get the wording just right.
As to 2) You want them to make clear that anything you reveal to them about your business or product(s) that isn't public knowledge, including the stuff they create for you, is to be deemed confidential and can be used by them for no purposes other than completing the job they are given, and can't be disclosed for any reason other than as required by law. Additionally they generally have to return all materials (including digital "materials") to you when the job is done and destroy their own copies. If you're worried about it you can throw some non-competition language in there if you're worried they'll go into business against you based on stuff they figure out while working for you (this includes elements of both ownership and confidentiality, and overreaches are unenforceable.) Once again, there may be other concepts around the fringe here, but that's the basic gist.
These are off the top of my head, and this isn't legal advice... either get a lawyer to draft you a contract, pay for a contract from something like LegalZoom, roll the dice with stuff you can find on the internet (or your own hybrid of stuff), or try your hand at drafting your own. I've never never heard of anyone suing someone else for copying their contract, but I'm sure there's probably a case to be made that contracts themselves are copyrighted.
Good contracts are structured like well-written code: easy to read & understand without outside context, cleanly organized, and soundly logical. Most are not well-written. Knowing what bases need to be covered is the tricky part.