Intellectual Property Lawyers for Wisconsin

To protect your interests and maximize the value of your invention, a well-structured Patent License Agreement should include several key provisions and considerations. Here are some essential elements: Grant of License The grant clause is crucial as it defines the scope and extent of patent rights given to the licensee. Be specific about: -Type of license (exclusive or non-exclusive) -Geographic territory covered -Market segments or fields of use -Duration of the license Clearly outlining these aspects helps prevent misuse and ensures you retain control over your invention's application. -Financial Terms -Royalties and Fees Establish a clear compensation structure that may include: -Upfront fees -Ongoing royalties (consider tiered rates based on sales volume) -Minimum annual guarantees -Milestone payments Ensure the royalty calculation method is well-defined, whether based on net sales, profits, or another metric. -Payment Terms -Specify payment frequency (e.g., monthly, quarterly, annually) and reporting requirements. -Term and Termination Define the agreement's duration and include provisions for: -Early termination conditions (e.g., breach of contract, bankruptcy) -Renewal options -Effects of termination on rights and obligations Intellectual Property Protection Include clauses that: -Affirm your ownership of the patent -Prohibit the licensee from challenging the patent's validity -Outline responsibilities for maintaining and enforcing the patent -Address ownership of improvements or modifications to the invention Performance Obligations Consider including: -Minimum sales targets -Marketing commitments -Development milestones These ensure the licensee actively commercializes your invention. Confidentiality Protect your sensitive information with robust confidentiality provisions, specifying: -What information is considered confidential -How it can be used -Duration of confidentiality obligations Sublicensing Rights If allowing sublicensing, clearly define: -Conditions under which sublicensing is permitted -Your approval rights for sublicensees -How sublicense revenue will be shared Quality Control If your patent is associated with a trademark, include provisions for: -Inspecting and approving the quality of goods before sale -Maintaining quality standards -Indemnification and Liability Include clauses that: -Protect you from legal claims arising from the licensee's use of the patent -Define limitations on liability for both parties -Dispute Resolution Specify mechanisms for resolving conflicts, such as: -Mediation -Arbitration -Litigation Governing law and jurisdiction By carefully addressing these key provisions and considerations in your Patent License Agreement, you can better protect your interests and maximize the value of your invention. Remember to tailor the agreement to your specific situation and consider seeking legal counsel to ensure all aspects are properly covered.

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.

Since the user uploaded copyrighted material to your website without your knowledge, generally you will not be automatically liable under the DMCA “safe harbor” provision. As you have already removed the content, make sure that your site has a published DMCA policy and that you have registered your designated agent with the U.S. Copyright Office. Generally, if you have everything in place, most of these matters are resolved without ongoing liability. Feel free to reach out if you need guidance on setting up a policy and agent registration.

You might think that because you wrote the code, you have the right to share it, but that’s not how developer agreements usually work. In Washington State, these contracts are enforceable, and they can absolutely stop you from sharing or reusing code you created during a project. It really comes down to ownership, and under most contracts, that ownership belongs to the company, not you. Let’s Talk About Who Owns the Code When you sign a developer agreement, you’re usually agreeing to one of two things: either it’s a “work-for-hire” deal or you're assigning your intellectual property rights. Either way, the result is the same. The company owns whatever you build for them. Since they own it, they get to decide what happens to it. Even if you’re the one who wrote every line, that doesn’t mean you have the right to reuse or share it if you’ve already signed those rights away. This kind of setup is standard in the tech world. Companies need to protect their IP, especially when it includes competitive advantages or trade secrets. That’s why they ask developers to assign rights and agree to keep things confidential. What About Washington State Law? Washington does offer some protection to developers, but it’s limited. There’s a statute, RCW 49.44.140, that says employers can’t claim ownership of inventions you created entirely on your own time, using your own resources, and completely unrelated to their business. That sounds helpful, but here’s the catch. It only applies if you’re an employee, not an independent contractor. And even then, the second your work overlaps with their business or involves any company resources, the protection probably doesn’t apply. So if the code you’re writing is part of a contract, or even just loosely connected to the company’s business, then the company likely owns it. Why This Matters If you violate the agreement, you’re not just risking a slap on the wrist. The company could send a takedown notice to GitHub, file for an injunction, or even sue for breach of contract or copyright infringement. If the code includes anything proprietary, like business logic or algorithms, they might also go after you for trade secret misappropriation. And beyond the legal problems, there’s your reputation to think about. Word travels fast in development circles, especially in local communities. Getting labeled as someone who mishandles IP can make future contracts harder to land. How to Protect Yourself The good news is that you still have leverage before you sign. A lot of companies start with broad IP assignment language, but they’re often open to carving out exceptions. You can ask to include a “prior inventions” schedule that lists tools, frameworks, or libraries you already created. That way, you can keep using your own work in other projects. If open-source contribution is important to you, say so upfront. Some companies will allow developers to contribute non-proprietary or generic components to open-source projects, especially if those contributions don’t compete with their business. Just make sure it’s all clearly spelled out in writing and approved in advance. You might also negotiate a time limit on confidentiality terms. The company will likely want to own the core project code permanently. That doesn’t mean you can’t eventually talk about general techniques or patterns you used, especially after some time has passed. Smart Moves Before You Sign Before you agree to anything, take a moment to list any existing code or tools you plan to use. Try to get those explicitly excluded from the IP assignment, or at least confirm that you’ll retain the right to use them elsewhere. And again, if open-source is part of your career plan, be upfront. Get language in the contract that allows you to publish select components with written approval. If you develop a useful utility during the project and think it might have broader uses, talk to the company before the contract ends. See if they’d be open to letting you open-source it or license it back to yourself for use in future projects. When It’s Time to Bring in a Lawyer If all this feels high-stakes, and it often is, consider having a tech-savvy attorney take a look. A good lawyer can help spot overly aggressive clauses, suggest better language, and help you protect both your rights and your long-term goals. This is especially important if you’re actively contributing to open-source or if you’ve built up your own libraries over time. A little legal help now can save you a lot of trouble later.

When you're selling your business in Texas and that sale includes registered trademarks, getting the Trademark Transfer Agreement right isn’t just paperwork. It’s what protects you and the buyer from serious legal headaches. Here’s what you need to understand about how it all works and what to include. FIRST, THE LEGAL BASICS Let’s get clear on where the law comes into play. If your trademarks are registered with the USPTO, federal law applies, specifically 15 U.S.C. § 1060. If you’ve registered marks at the state level in Texas, those fall under Section 16.061 of the Texas Business & Commerce Code. A lot of businesses have federal trademarks, but some have both, and each needs to be handled the right way. Here’s a critical point: you can’t transfer a trademark by itself. Legally, it has to go with the goodwill tied to it. That means the reputation, customer trust, and market recognition associated with your brand. Courts take this seriously. If you try to assign a trademark without transferring the goodwill behind it, that assignment can be ruled invalid. The trademark has to stay connected to its original source, or the legal protection starts to fall apart. KEY PARTS OF THE AGREEMENT Identifying the Parties and Background Info Start simple. Spell out who’s selling and who’s buying, using full legal names and business addresses. Include a quick explanation in the recitals that you own the trademarks and plan to transfer them as part of the business sale. Detailed Trademark Descriptions List every trademark included in the transfer. For federal marks, include things like registration numbers, any pending application serial numbers, filing dates, and the international classes they fall under. For Texas marks, include the state registration numbers and any other relevant details. Don’t forget common law marks either. If you’ve been using a brand name or logo in business without registering it, it still has value and legal protection. The Assignment Clause Itself This is where the actual transfer happens. The language needs to make it crystal clear that you’re transferring all rights, title, and interest in the trademarks, and just as important, the goodwill that goes with them. That’s not optional. For federal trademarks, this clause has to meet the standard set by 15 U.S.C. § 1060. For Texas marks, the law requires that the transfer include “the goodwill of the business in which the mark is used.” Be sure to include language that talks about transferring the reputation, customer recognition, and market value of the marks. That’s what keeps the assignment legally valid. Purchase Price and Who Pays for What Spell out what the trademarks are worth as part of the overall deal. If the value is rolled into the full business sale price, say that clearly. Also note who’s responsible for any filing fees with the USPTO or Texas Secretary of State, legal costs, and whether there’s any money going into escrow. Warranties and Representations You’ll need to confirm that you’re the sole owner of the trademarks, that they’re valid and enforceable, and that there are no liens, disputes, or infringement claims you know of. You can qualify some of these with “to the best of your knowledge,” especially if you're not sure about everything. The buyer will also need to make some promises, like having the ability to maintain and protect the trademarks going forward. Indemnification Terms This is how you divide up risk. You should agree to cover any trademark issues that started before the sale, such as pending legal disputes or past infringement claims. The buyer takes on anything that happens after the transfer. Be sure to include who will handle any legal defense and how costs are covered. What Happens After the Sale You’ll probably need to sign additional paperwork later to finalize the transfer, especially for filing purposes. You also need to agree to stop using the trademarks after closing. If you’re going to help the buyer with trademark maintenance or recordation, lay that out clearly. Cooperation after closing is often what makes the legal side go smoothly. WHAT IF THERE'S A TRANSITION PERIOD? If you’ll still be involved in operations temporarily or helping during a handoff, add quality control provisions. This matters because if the buyer is using the trademark on the same goods or services you used to provide, the quality needs to stay consistent. Without oversight during that period, trademark rights can actually be lost. That’s called naked licensing, and it’s something you want to avoid at all costs. RECORDING THE ASSIGNMENT Federal Marks To make the transfer legally solid, you’ll need to record it through the USPTO Assignment Center. Right now, it costs $40 for the first trademark and $25 for each additional one in the same document. You have three months from the assignment date to record it to protect against third-party claims. Texas Marks For state trademarks, the process goes through the Texas Secretary of State. The fee is $25, and Texas gives you 90 days to record the assignment. That’s different from the federal timeline, so don’t mix them up. Common Law Marks Since these aren’t registered anywhere, there’s no official filing to do. Just make sure your agreement clearly spells out the transfer and ties it to goodwill. That’s your legal foundation for common law marks. A FEW EXTRA LEGAL PROTECTIONS Include standard contract language too, such as Texas law as the governing law, a venue for disputes, integration clauses, and a method for resolving disagreements. You might want to get the agreement notarized. It’s not legally required in Texas, but it adds a layer of security. If you're staying involved during the transition and helping the buyer keep up with trademark deadlines, make sure that’s written into the deal. COMMON PITFALLS TO AVOID Don’t treat all your trademarks the same. Some may be federal, some state, and some common law. They each need different handling. And never forget the goodwill piece. Without it, your trademark transfer isn’t valid. Also, make sure you stay on top of deadlines. You have three months to record federal assignments and 90 days for Texas. Missing either one could leave the buyer exposed to claims from someone else down the road. THE FINAL ANALYSIS Getting this agreement right helps avoid future disputes and protects the trademark value you’ve built over time. Trademarks are often one of the most valuable pieces of a business, so it’s worth taking the time to spell out exactly what’s being transferred, what the responsibilities are, and what happens next. Because trademark law is detailed and the consequences of mistakes can be serious, it’s smart to work with an experienced IP attorney. They’ll help you match the agreement to your specific situation and avoid costly errors. Mistakes in this area can lead to total loss of rights. If you've built a brand worth selling, make sure it's protected when you pass it on.