Intellectual Property Lawyers for Dayton, Ohio

A person that owns the intellectual property rights in a product (i.e., the IP owner) can transfer all rights of ownership to another party. You would need to enter into an Intellectual Property Transfer/Assignment Agreement. This agreement would transfer the intellectual property ownership of the product from you to the other party. This is a permanent transfer and you would not have any further rights to the intellectual property in the product once the agreement was signed.

I can do that. I am an IP lawyer over 20 years experience in this area. I work on SAAS and similar agreements daily.

Here’s how I’d approach structuring an Employee IP Agreement if your goal is to protect your company’s intellectual property without running into enforceability issues under U.S. law. Covering Core IP OwnershipCovering Core IP Ownership First, start with a “work made for hire” clause. It’s a good foundation, but it’s not enough on its own. Under U.S. copyright law (17 U.S.C. § 101), only certain types of work qualify as “made for hire,” and many employee-created assets may fall outside that definition. So you’ll want to pair it with a present-tense assignment clause. Be specific here. Use language like “the employee hereby assigns” rather than “will assign.” That slight shift matters. It ensures the company owns the rights immediately when the work is created. Also, define “intellectual property” broadly. Don’t just list patents or source code. Include software, algorithms, documentation, trade secrets, databases, and anything tied to your business. The scope should clearly include anything created during work hours, using company tools or systems, or connected to your current or future business operations. Disclosure and Documentation You’ll want to require employees to promptly disclose any inventions or creative works they produce. Put it in writing. This gives your company the chance to evaluate whether the work is covered under the agreement. It’s also a good idea to require them to maintain proper documentation. Accurate records can make a real difference in patent filings or if a dispute ever comes up. Pre-Existing IP and Legal Carve-Outs There should be a section where employees list anything they’ve developed or own before joining the company. If they don’t list anything, the agreement should include language confirming they’re representing that no such prior inventions exist. This prevents claims down the road that something developed during employment was actually theirs from before. Now, depending on your state, you may need to include statutory carve-outs. California, Illinois, and Washington all have laws that limit how far IP assignment clauses can go. For example, in California, you’re required to carve out inventions developed entirely on the employee’s own time, without company resources, and unrelated to your business (see California Labor Code § 2870). Without that carve-out, your entire assignment provision could be thrown out. Confidentiality Obligations Make sure there’s a strong confidentiality section. This should cover source code, technical documentation, designs, product plans, customer lists, financial data, and anything else proprietary. Make it clear that the obligation continues even after the employee leaves. You’ll also want to require that all company property and digital assets are returned at the end of employment, including devices, credentials, and files. Ongoing Cooperation and Enforcement Mechanisms Include a clause requiring employees to cooperate in IP protection efforts even after they leave. That could mean signing patent paperwork or providing testimony if needed. To make that enforceable, add a power of attorney clause. This gives the company the authority to act on the employee’s behalf if they’re unwilling or unreachable. It’s a simple way to prevent delays when you’re trying to secure or enforce rights. It’s also smart to include a waiver of moral rights where allowed. This is especially useful for creative works and software. It gives the company full freedom to modify or use the work without needing future approval. Legal Remedies and General Terms Be clear that the company can pursue equitable relief, like an injunction, if there’s a violation. Sometimes monetary damages aren’t enough to prevent harm. Include a severability clause so that if one part of the agreement is invalidated, the rest still stand. Don’t forget to specify the governing law and venue for any disputes. As for restrictive covenants, keep in mind that non-compete clauses are unenforceable in California and heavily restricted elsewhere. Non-solicitation clauses may still be allowed, but they need to be narrowly written. You should have your legal team confirm their enforceability based on your state. Finally, think about consideration. For new hires, the job offer itself usually counts. But for existing employees, you’ll likely need to offer something extra, like a bonus or promotion, to make the agreement stick.

You’re not the first to confuse a KISS Note with intellectual property protection, and you definitely won’t be the last. It’s a common mix-up in the startup world. But here’s the truth: A KISS Note has nothing to do with protecting your software. It’s a financing instrument created by 500 Startups, designed as an alternative to convertible notes and SAFEs for early-stage fundraising. It’s a way for investors to give you money now in exchange for equity later. It does not offer any legal protection for your code or ideas. So What Do You Actually Need to Protect Your IP? If you're building software in California, there are several key legal tools you’ll want to have in place. Start with the ones that offer immediate protection and work your way toward longer-term strategies. Always Start with NDAs If you're showing your software to anyone (whether it's a co-founder, a contractor, an investor, or a beta tester) you need a solid non-disclosure agreement in place before you share anything. It’s your first line of defense, especially if you want to preserve trade secret protection. Your NDA should spell out exactly what you consider confidential. This might include your source code, algorithms, user data, business plans, or any other proprietary information. The agreement should also state how long confidentiality lasts and what the other party can and cannot do with your information. One important note here: California law prohibits non-compete clauses under Business and Professions Code Section 16600. Do not include one in your NDA. It won't be enforceable. Instead, focus strictly on confidentiality and use limitations. Copyright is Automatic, but Registration Matters As soon as you write your code, it’s protected under federal copyright law. That protection applies to the actual expression (the specific code) not to your underlying ideas, functionality, or algorithms. Even though protection is automatic, registering with the U.S. Copyright Office gives you significant legal benefits. You can’t file a federal lawsuit without registration. And if your copyright is registered before infringement occurs, you may be eligible for statutory damages of up to $150,000 per work and recovery of attorney’s fees. The process usually costs between $65 and $85 and takes a few months. Trade Secrets Require Real Effort to Stay Protected If your software includes proprietary algorithms, confidential processes, or unique technical methods that provide a competitive edge, you may be eligible for trade secret protection under the California Uniform Trade Secrets Act. But here’s the catch. That protection only lasts as long as you actively protect the information. This includes limiting access to your source code, using secure development environments, marking documents as confidential, and having everyone involved sign NDAs. You need to treat your trade secrets like actual secrets if you want the law to do the same. Considering Patents? Proceed Carefully Software patents are complex, especially following the Supreme Court’s 2014 Alice decision. You can’t patent abstract ideas, mathematical formulas, or generic computer processes. Your software needs to solve a specific technical problem in a novel, non-obvious way or improve the functionality of a computer system itself. If you've developed something truly unique — like a new data compression algorithm, a better machine learning architecture, or a new way to optimize networking — a patent might be worth exploring. Just keep in mind that the process is expensive, often costing $10,000 to $15,000 with legal fees. It can also take several years. Many software companies choose to rely on trade secrets and copyrights instead. How to Put All of This Into Practice Begin with what you can implement right away. Create a strong NDA template and use it consistently. Register your copyright as soon as your codebase is developed enough to be meaningful. Protect your trade secrets by putting real technical and legal safeguards in place. Track your development process carefully. Version control, timestamps, and contributor logs can all serve as useful evidence in a legal dispute. If you’re working with employees or contractors in California, be especially cautious. The state has employee-friendly laws, so your contracts must clearly state that all work product belongs to your company and that all confidential information stays confidential. When Should You Talk to a Lawyer? Once you’re dealing with patents, investor negotiations, infringement threats, or user data privacy, it’s time to bring in professional legal help. These are complex areas, and the risks are too high to wing it.

Do you have a license to use the intellectual property? Consult with an attorney.