Intellectual Property Lawyers for Salt Lake City, Utah

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 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.

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 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.

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.