Intellectual Property Lawyers for Cleveland, Ohio

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

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.

When you're dealing with a technology transfer agreement, it's important to understand that you're not selling your software. You're licensing it. That might seem like a small difference, but it really isn't. Licensing means you're keeping ownership of your intellectual property while letting someone else use it under clearly defined terms. If you're based in Arizona, you've got a legal system that takes written contracts seriously and generally holds both parties to exactly what’s spelled out. So clarity matters—a lot. Be Specific About What's Being Licensed Don't just say you're licensing "software." Spell out what that includes. Are you talking about the source code? Object code? Documentation? APIs? Maybe there's configuration data, algorithms, or some embedded proprietary know-how. Lay it all out. Also, be clear on whether things like updates, bug fixes, or patches are part of the deal or if those require separate terms. Courts in Arizona won't guess what you meant. They’ll go by what’s in the document. Keep Your IP Rights Locked Down Make sure the agreement says you're not transferring ownership. You're only granting the rights specifically listed in the license. Anything not spelled out stays with you. Without that language, you could run into disputes later—especially if the licensee makes improvements. Want to avoid headaches? Clearly state that you own any enhancements unless you decide otherwise. Be Intentional About the License Structure Think through how you’re structuring the license. Is it exclusive, non-exclusive, or somewhere in between? An exclusive license can be powerful, but it limits your flexibility. If you're giving up other opportunities, it's reasonable to ask for higher compensation and make sure the licensee meets clear performance targets. On the flip side, a non-exclusive license gives you room to work with others. You can also narrow the license by geography, industry, or even specific use cases. And don’t forget to address sublicensing. If it’s allowed, include approval rights and make sure you’re compensated fairly if they sublicense to others. Choose a Payment Model That Reflects Value There’s no one-size-fits-all way to get paid. You might go with an upfront fee for past development work, ongoing royalties based on sales, or milestone payments tied to things like product launches or regulatory approval. Each has its pros and cons. Whatever you choose, protect yourself with audit rights. You want access to the licensee’s records if something seems off. That usually means giving them notice, checking things during business hours, and shifting the audit costs if the discrepancies are significant. Protect Your Work from Unintended Use If you’ve used open-source components, you need to disclose that—and understand how those licenses impact what you can legally offer. GPL code, for example, can bring in obligations that might not work with your business model. Copyright registration isn’t mandatory, but it gives you the ability to sue in federal court and can unlock statutory damages and legal fees. If you've developed novel algorithms, you might consider a patent—but only if the innovation meets the standards. It's not always worth the cost, so weigh that carefully. Make Sure the Licensee Does Something with Your Tech If you’re giving someone exclusive rights, set performance expectations. What does commercialization look like to you? It might mean releasing a product by a certain date, hitting minimum sales, or committing to a marketing budget. If those things don’t happen, you need a remedy—like converting the license to non-exclusive or ending the agreement altogether. The goal is to make sure your technology doesn’t sit unused. Clarify Support and Ongoing Involvement Are you expected to provide support? If so, spell out exactly what that means. Documentation, training, installation help, bug fixes, future updates—whatever it is, define it. Also decide whether that’s included in the license or billed separately. If you’re providing source code, put strict confidentiality and usage terms in place. In some cases, a source code escrow might be appropriate, with release conditions like your bankruptcy or failure to maintain the code. Limit Your Liability Arizona has adopted the Uniform Commercial Code, so if you don’t include specific disclaimers, you might be stuck with certain implied warranties. That includes things like fitness for a particular purpose. You’ll want to limit that while still affirming that you own the software and that it generally works as described. Also, set a cap on liability. Most developers limit it to the total fees paid under the agreement and exclude indirect or punitive damages. You don’t want to be held responsible for how someone else uses your tech. Mutual Indemnification Matters If someone accuses your software of infringing their intellectual property, you might agree to cover the licensee’s costs. But it needs to go both ways. They should indemnify you too—especially if they modify your code or use it in a regulated environment where compliance issues could come up. You don’t want to be liable for something outside your control. Don’t Skip Export Control Compliance Yes, export control rules apply even to downloadable software. If your product includes encryption or certain types of AI or analytics, it may fall under specific federal regulations. Many tools qualify for License Exception ENC, but that’s not automatic. Misclassification can lead to serious fines. If you're licensing internationally—or even just to a foreign-owned company based in the U.S.—you need to get this right before moving forward. Understand How Arizona Law Will Handle Your Agreement Arizona courts usually enforce what’s written. If it’s not in the contract, don’t expect the court to fill in the gaps. That makes detailed drafting essential. Arizona also supports reasonable non-competes and confidentiality terms, which isn’t true in every state. Just make sure any restrictions are tied to legitimate business interests and kept within reasonable limits for time and geography. Spell Out What Happens at the End Termination clauses are your safety net. Cover scenarios like breach, bankruptcy, missed milestones, or even changes in company control. Include cure periods where appropriate. Be specific about what happens when the agreement ends—does the licensee have to stop using the software immediately? Can they finish selling what’s already been produced? Make that clear. Also, specify which obligations survive termination. Usually, confidentiality and IP rights continue, even after the main agreement ends. Plan Ahead for Disputes Choose Arizona law to govern the agreement. If your licensee is in another state or country, decide where and how disputes will be handled. Arbitration can be quicker and cheaper, but it might limit your access to things like injunctive relief. Consider requiring mediation first to give both sides a shot at resolving issues early. And don’t forget a prevailing party clause—Arizona courts do enforce them, and it could help you recover attorneys’ fees if you end up in a legal fight. The Final Analysis Technology licensing isn't just about protecting your IP. It's about setting clear, enforceable expectations from the start. Arizona law gives you the tools to do that, but it only works if your agreement is well-drafted and forward looking. Define what you're licensing, retain ownership, protect your downside, and make sure the deal drives results, not just risk. If you're a software developer navigating a tech transfer deal or reviewing an agreement someone else drafted, don’t go it alone. Having the right legal language in place from day one can prevent years of headaches down the road.

Hi, Yes, intellectual property created by you as an employee, within the scope of your employment, under a work-for-hire agreement, probably belongs to your employer. To learn more about your rights under the agreement and any exceptions, you should consult with a qualified attorney.

Yes, you can and should include clauses in an Intellectual Property License Agreement that protect your rights as the licensor. A license agreement is your main tool for controlling how your software is used, setting boundaries for your clients, and limiting your financial exposure. The key is to draft it in a way that leaves no doubt about what rights are granted, what’s restricted, and what happens if there’s a breach. Grant of License Start with a clear license grant. Spell out that you’re giving the client only limited rights, not ownership. Most licensors define the license as non-exclusive, non-transferable, and revocable if the client doesn’t follow the terms. For example, you might allow a client to use the software only for its internal business operations, and only on a set number of machines. It’s equally important to list what the licensee cannot do, such as reverse engineering, modifying, sublicensing, or providing the software to third parties. Intellectual Property Ownership Reinforce that you retain all ownership rights in the software and any related intellectual property. A simple but strong statement is that you hold all right, title, and interest in the software, and the client only receives a limited right to use it under the agreement. This prevents confusion between a license and a sale. You can also require the licensee to notify you if they discover third-party infringement and confirm that you alone have the right to pursue action against infringers. Confidentiality If you’re providing source code, algorithms, or other sensitive information, a confidentiality clause is essential. Define confidential information broadly to include not just the software itself but also any documentation or business information you share. Require the client to protect that information with at least the same care they use for their own confidential material, and make the obligation survive termination of the agreement. Termination Every strong license has a termination clause. Termination for cause should allow you to end the agreement if the client fails to pay, violates the license scope, or breaches confidentiality. Many agreements include a short cure period, such as thirty days, for the licensee to fix the breach before termination takes effect. Spell out the consequences of termination: the licensee must stop using the software immediately, return or destroy all copies, and certify that they’ve complied. Without this, you risk losing leverage if the relationship breaks down. Payment Terms Protect your revenue by making payment terms clear. Define license fees, support or maintenance fees if applicable, the payment schedule, and penalties for late payment such as interest. Courts generally enforce these provisions as long as they’re reasonable. Disclaimers and Limitation of Liability These clauses protect you from lawsuits if things go wrong. A limited warranty might cover basic performance for a set time, but beyond that you should disclaim all other warranties. Standard language is that the software is provided “as is” and you disclaim implied warranties of merchantability and fitness for a particular purpose. To limit your exposure, cap liability at a defined amount, often the fees paid by the licensee in the previous twelve months, and exclude liability for indirect or consequential damages such as lost profits. Courts usually enforce these limits, except in cases of fraud or intentional misconduct. Audit Rights If your pricing model depends on the number of users or installations, an audit right is valuable. This allows you to check, on reasonable notice, that the licensee isn’t exceeding their rights. For example, you might reserve the right to inspect usage records once a year during normal business hours. Governing Law and Dispute Resolution Designating which state’s law governs and how disputes are resolved reduces uncertainty. Many licensors choose their home state’s law and either local courts or arbitration for disputes. Remedies Make sure your agreement lets you seek injunctive relief if the licensee misuses or discloses your software. Monetary damages often aren’t enough to protect intellectual property, so courts will enforce contract terms that authorize immediate injunctive relief. Protect Your Software with Legal Guidance When you’re licensing valuable software, the details in your agreement can make the difference between real protection and unnecessary risk. The lawyers on Contracts Counsel are available to draft, review, or negotiate a license that secures your rights and keeps your business protected.