Intellectual Property Lawyers for Lansing, Michigan

A Patent Assignment Agreement transfers ownership of an invention or patent rights from the inventor, known as the assignor, to another party, often a company serving as the assignee. To protect your business and ensure enforceability, the agreement should cover specific provisions that make the transfer clear, complete, and legally sound. What Is the Core Assignment Clause? The assignment clause is the heart of the agreement. It should use present-tense language such as “hereby assigns, transfers, and conveys all right, title, and interest.” Courts and the USPTO treat this as an immediate transfer, while “will assign” is only a future promise. The clause should also cover continuation, divisional, or continuation-in-part applications, along with reissues, reexaminations, and foreign filings. What Rights Should Be Transferred? The assignee should receive the full bundle of rights granted under 35 U.S.C. § 154, including the right to make, use, sell, offer for sale, import, and license the invention. The agreement should also transfer the right to sue for past, present, and future infringement, so the company can recover damages even for activity that occurred before the assignment was signed. Do You Need Consideration? Every contract requires consideration, and patent assignments are no different. Even if the transfer is to your own company, the agreement should recite consideration. This can be nominal, such as “ten dollars and other good and valuable consideration,” or it can be tied to equity or to your role as founder. How Should the Patent Be Identified? The intellectual property should be identified with precision. If a patent has issued, include the number and issue date. For pending applications, list the application number, filing date, and invention title. If no application has been filed yet, provide a detailed description and later update the record once official filing details exist. What Warranties and Representations Are Common? The assignor should warrant ownership of the rights, authority to assign, and absence of liens or conflicting assignments. Over-warranting should be avoided. Do not guarantee novelty or validity, since those are determined by the USPTO and courts. Be cautious about warranting sole inventorship unless you are certain no other inventors contributed, since misstatements on inventorship can create validity problems. What Other Provisions Should Be Included? Other common provisions include further assurances requiring the inventor to assist with future filings, litigation, or USPTO actions, a limited power of attorney for patent prosecution and enforcement, and improvements clauses that attempt to capture future modifications or developments. Improvements provisions must be drafted carefully, as vague scope language can lead to disputes. The agreement should also address corporate authority, ensuring the company has approval under bylaws or state law before accepting the assignment. What Administrative Details Matter? The agreement should contain standard contract terms such as governing law, entire agreement, amendment requirements, successors and assigns, and dispute resolution through arbitration or mediation. Both the inventor and the company should sign, and notarization is advisable because it makes USPTO recordation smoother. Do You Need to Record with the USPTO? After execution, the assignment should be recorded with the USPTO through the Electronic Patent Assignment System. Recordation should occur promptly after execution to establish clear priority and maintain a clean chain of title. While recordation is not required for validity between the parties, it protects ownership against third-party claims. The USPTO currently charges little or no fee for electronic filings, so this step is inexpensive and essential. Should You Assign or License? An assignment transfers complete ownership, which investors generally expect. A license keeps ownership with the inventor while granting defined rights to the company. Licensing may be useful when the inventor wants to retain control, license the technology to multiple companies, or test the market before giving up ownership. For most startups, assignment is the preferred approach. What About Tax Considerations? Assignments can have tax consequences, especially when IP is transferred for equity or other forms of consideration. Professional tax advice is essential to evaluate both immediate tax effects and ongoing obligations. This is particularly important if the company later earns royalties or sells the patent. What Are the Next Steps? The implementation process should include drafting the agreement with qualified legal counsel, executing it with proper corporate authority and notarization where possible, recording it promptly with the USPTO using EPAS, and consulting a tax professional to address both the transfer itself and any ongoing obligations. If you need help drafting or reviewing a Patent Assignment Agreement, the attorneys on Contracts Counsel can guide you through the process so that your company’s rights are fully protected.

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.

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

It would be a good idea for you to have the agreement reviewed by an attorney. You said there's no explicit language regarding termination or notice - is there something implied? With no language regarding termination, most likely either party can terminate at any time, with just a moment's notice, and no reason given. You have asked a lot of questions - I suggest that you post a project here on Contracts Counsel, and ask for an attorney well versed in intellectual property (not me) to discuss your rights, as that is probably the most important issue. An attorney who can also review the language of the entire agreement would be very helpful. (I'm sorry, but I'm not available for this project).

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.