Intellectual Property Lawyers for Broken Arrow, Oklahoma

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. If the Creative Commons License that you mentioned (CC BY-NC 4.0) does not allow for commercial usage, using that content commercially would violate the license. If you tranform the work sufficiently, you could potentially use it without violating the terms of the license.

Yes, you can achieve this through an IP license agreement versus a sale of your IP rights. In your license you would want to protect against gray market product manufacturing and also have provisions on how to handle defective products and components during the manufacturing process. I am available for a free consultation if you would like.

The terms of your specific agreement are the most important factors to consider. In general, an invention assignment agreement usually means that an employee gives the company any ideas or inventions they come up with while working. The rules can vary by agreement, but they often cover ideas made during work hours, using company resources, or related to the company’s business. In Texas, an agreement can apply to inventions made outside of work hours if they’re related to the company’s business or came from work the company assigned. In one case, the agreement said the employee had to give up all inventions made during or after regular work hours, whether on or off the job, if they were related to the company’s business or came from work the company assigned. Usually, an invention assignment agreement doesn’t apply to ideas that aren’t related to the employee’s job unless the agreement says otherwise. In Atlas Brick Co. v. North, 2 S.W.2d 980, the court said that the title to an invention wouldn’t belong to the employer unless the agreement said that ideas made and perfected under the employee’s contract of employment belong to the employer. Also, if a discovery is made outside the scope and purpose of employment, it belongs to the employee unless there’s an agreement to give up such inventions to the employer. So, it all depends on the terms of the invention assignment agreement. In the case of Halliburton Energy Servs. v. Axis Techs., LLC, the agreement required the employee to turn over all materials related to inventions created during employment, making them the company’s property. But, if the agreement doesn’t cover certain inventions or if the inventions are made outside the scope of employment without using company resources, the employee might still retain ownership.

Hello! This is Attorney Damien Bosco. My law office is in Forest Hills, Queens County, New York City. My practice covers the New York City metropolitan area and Long Island. In some situations, I also handle matters throughout New York State. If your phrase contains common jewelry terms, registering it may be challenging. One suggestion is to check the USPTO Database for similar trademarks. If other businesses have brands using the same common word in their brand name, that could give an indication that you may still be able to use it in your brand name. Nonexclusive use means that the word or phrase can be used by other parties and is not solely owned or controlled by the trademark holder. Consult with a trademark attorney for guidance on the registration process and the viability of your chosen phrase.