Invention Assignment Agreements and Employer IP Risk: A Guide for Texas Hardware Founders

The Semiconductor Boom's Hidden IP Trap

Texas is in the middle of a semiconductor and deeptech manufacturing surge. Samsung's $17 billion Taylor fab, Texas Instruments' Sherman expansions, Tesla's Gigafactory, and NXP's Austin operations have turned Central Texas into one of the densest hardware engineering corridors in the country. Engineers at these companies are building startups on the side — and most of them signed invention assignment agreements when they were hired that could give their employer ownership of their startup's core IP.

We've seen it repeatedly in our practice: a hardware founder comes in for incorporation or a pre-seed raise, and during diligence we discover their employment agreement contains a broad invention assignment clause that sweeps in after-hours work. The investor pauses. The deal stalls. Sometimes it dies. Employer-IP disputes are the single most common deal-killer in hardware startup diligence, and they're almost always preventable if you understand the legal landscape before you start building.

If you're a hardware founder in Texas — or anywhere with a large semiconductor or deeptech employer base — this guide walks you through how to read your employment agreement, what Texas law does (and doesn't) protect, why the Supreme Court's Stanford v. Roche decision matters to your assignment clause, and how to structure a clean IP break before you incorporate. We also cover what to do if your employer has already claimed ownership of your startup's patents or code.

For a broader overview of how employer IP claims can sink a startup, see our earlier guide on employer IP and invention assignment risks for deep-tech founders.

How to Read Your Employment Agreement's IP Assignment Clause

Most engineers sign their employment agreement on day one and never look at it again. That document almost certainly contains an invention assignment clause — sometimes called a "PIA" (proprietary information and inventions agreement) — that determines who owns the intellectual property you create during and sometimes after your employment.

Here's what to look for:

1. Scope of the Assignment

Some clauses are narrow: they assign only inventions "related to the employer's business" or "conceived or reduced to practice during working hours." Others are breathtakingly broad — claiming all inventions you conceive during employment, regardless of whether they relate to your job, whether you worked on them on your own time, or whether you used employer resources. Broad clauses are common at large semiconductor and tech companies, and they're the ones that create the most risk for side-venture founders.

2. Present Assignment vs. Promise to Assign

This distinction is critical. A present assignment uses language like "I hereby assign" — meaning ownership transfers automatically the moment the invention is created. A promise to assign uses language like "I will assign" or "I agree to assign" — meaning the employer gets a contractual right to receive the assignment, but title doesn't transfer until the paperwork is executed. As we explain below, this difference determined the outcome of Stanford v. Roche at the Supreme Court.

3. "Relates to" Language

Many clauses assign inventions that "relate to" the employer's "actual or demonstrably anticipated" business. If you work at a semiconductor company and your startup is in semiconductors, this language is likely to cover your startup IP — even if you developed it entirely on your own time with your own resources.

4. Moral Rights and Copyright

Don't just look for patent assignment language. Many agreements also assign copyrights in code, designs, and technical writings. If your startup involves software — and most hardware startups do — the copyright assignment clause can be just as dangerous as the patent assignment clause.

Texas Shop Rights and the "Employed to Invent" Doctrine

Texas does not have a statute equivalent to California's Labor Code § 2870, which protects employee inventions developed on personal time without employer resources. That absence matters enormously. In Texas, the default rules come from common law doctrines, and they tend to favor employers more than California's statutory framework does.

The "Employed to Invent" Doctrine

Under the common law "employed to invent" doctrine, when an employee is hired specifically to solve a particular problem or develop a particular technology, inventions resulting from that work belong to the employer — even without an explicit assignment clause. This doctrine is especially relevant in semiconductor and hardware engineering, where employees are often hired precisely to innovate in a specific technical area. If your job title or job description includes "research," "design," or "development" in a field overlapping with your startup, the employed-to-invent doctrine may give your employer a strong claim.

Shop Rights

The "shop right" doctrine provides that when an employee uses employer resources — equipment, materials, facilities, or trade secrets — to develop an invention, the employer may receive a non-exclusive, non-transferable license to use that invention, even if the employee retains ownership. Shop rights don't give the employer ownership, but they create an encumbrance that can scare investors and complicate IP diligence. A shop right means your employer can use your startup's core technology without paying you — a fact that tends to kill deals.

The Fifth Circuit addressed a closely related situation in ATOM Instrument Corp. v. Petroleum Analyzer Co., where an engineer developed technology on his own time in his own laboratory but also performed tests using the employer's resources. The dispute went to arbitration and then to federal court — illustrating that even when an engineer develops technology independently, employer resource usage can trigger years of litigation over ownership and licensing rights.

Texas vs. California: Why Your State Matters (or Doesn't)

If you've heard that California protects employee inventions, you're partially right. California Labor Code § 2870 provides that an employment agreement cannot require an employee to assign inventions that were developed entirely on the employee's own time, without using the employer's equipment, supplies, facilities, or trade secrets, and that do not relate to the employer's business or the employee's work. This statute creates a safe harbor for California employees who build startups on the side — as long as they can satisfy all three conditions.

Texas has no equivalent statute. There is no Texas law that automatically exempts your after-hours, independently-developed inventions from your employment agreement's assignment clause. If your agreement says "I hereby assign all inventions I conceive during my employment," Texas courts are generally willing to enforce that language as written — subject only to common law limitations like the shop right doctrine and general contract defenses.

This means a Texas hardware founder faces materially more risk than a California founder working under the same agreement. In California, § 2870 can invalidate an overbroad assignment clause as applied to your startup IP. In Texas, the clause is likely enforceable, and your only protections are whatever carve-outs your agreement itself contains (if any) or common law doctrines that may limit but not eliminate the employer's claim.

The practical implication: if you signed your employment agreement in Texas, or your agreement specifies Texas law as the governing law, you need to take the assignment clause seriously as a threat to your startup's IP — not assume it's unenforceable.

For more on how non-compete clauses interact with your ability to start a company in Texas, see our guide on Texas non-compete enforceability for founders.

Stanford v. Roche: Why the Exact Words in Your Agreement Matter

The single most important patent assignment case in U.S. law is Board of Trustees of Leland Stanford Junior University v. Roche Molecular Systems, Inc., 563 U.S. 776 (2011). The Supreme Court held that an assignment clause using present-tense language — "I hereby assign" — effects an immediate transfer of ownership at the moment the invention is created. A clause using future-tense language — "I will assign" or "I agree to assign" — creates only a contractual promise, not an automatic transfer.

In Stanford v. Roche, a researcher signed two agreements: one with Stanford saying he "will assign" his inventions, and one with a company called Cetus saying he "hereby assigns" his inventions to Cetus. The Supreme Court ruled that the "hereby assigns" language created a present transfer to Cetus, while Stanford's "will assign" language created only a promise. Cetus (later acquired by Roche) owned the patents — not Stanford.

The Federal Circuit continues to apply this principle rigorously. In Roku, Inc. v. ITC, 90 F.4th 1367 (Fed. Cir. 2024), the court confirmed that language stating an employee "hereby sell[s] and assign[s] . . . [his] entire right, title, and interest" constitutes a present conveyance, not merely a promise to assign. The court cited FilmTec Corp. v. Allied-Signal Inc., 939 F.2d 1568 (Fed. Cir. 1991), for the principle that "hereby grant" language "expressly granted . . . rights in any future invention."

What this means for you: pull out your employment agreement and read the assignment clause word for word. If it says "I hereby assign," your employer may already own your startup's IP — automatically, without any further action. If it says "I agree to assign" or "I will assign," your employer has a contractual right to demand the assignment, but title hasn't transferred yet. Both situations are dangerous, but the "hereby assign" language is worse because it may be difficult or impossible to unwind.

Structuring a Clean IP Break Before You Incorporate

The best time to address employer-IP risk is before you incorporate — ideally before you start building anything that could become your startup's core technology. Here are the practical steps we recommend:

1. Audit Your Employment Agreement

Read every IP-related clause in your employment agreement, PIA, confidentiality agreement, and any other document you signed at onboarding. Pay attention to: assignment scope, present vs. future tense, "relates to" language, and any moonlighting or outside-employment clauses. If your agreement has a carve-out for inventions developed entirely on personal time without employer resources, identify it — but don't assume it protects you if your startup is in the same field as your employer.

2. Document Your Innovation Timeline

Keep meticulous records of when and where you developed your startup's IP. Lab notebooks, git commit timestamps, emails, and dated design documents all matter. If you can demonstrate that key inventions were conceived and reduced to practice outside working hours, without employer equipment, and before or after your employment period, you strengthen your position against an employer claim.

3. Avoid Employer Resources

Do not use your employer's laptop, lab equipment, software licenses, email, or facilities for your startup work. Even incidental use can trigger a shop right claim. Use your own devices, your own tools, and your own time. This is harder than it sounds — if you're used to your employer's EDA tools or prototyping lab, you'll need to find alternatives.

4. Get a Written Waiver or Release

The cleanest solution is a written waiver or release from your employer that explicitly disclaims any ownership interest in your startup's IP. Some companies have formal processes for this; others will require negotiation. This is where having legal counsel matters — the waiver needs to be broad enough to cover all your startup's current and future IP, and it needs to survive your departure from the company.

5. File Patents in Your Startup's Name — Carefully

If you file patent applications before incorporating, make sure the assignment chain is clean. When you incorporate, you'll need to assign all founder IP to the company. But if your employer has a claim to that IP, the assignment to your startup may be invalid — you can't assign what you don't own. This is why resolving employer-IP issues before incorporation is critical. For more on the founder IP assignment process, see our guide on founder IP assignment and why you can't raise without it.

6. Consider a License-Back Arrangement

If your employer won't release its claim entirely, consider negotiating a license-back arrangement: your employer retains ownership but grants your startup an exclusive (or non-exclusive) license to use the IP. This is less clean than full ownership, but it can unblock a fundraising round and may be acceptable to investors if the license terms are favorable enough.

What to Do When Your Employer Claims Your Startup's IP

If your employer has already asserted ownership over your startup's patents, code, or other IP — whether through a cease-and-desist letter, a demand during diligence, or a lawsuit — you need to move quickly and strategically.

1. Don't Ignore It

Employer IP claims don't go away on their own. If an investor discovers the claim during diligence and you haven't addressed it, the deal will stall or fail. If your employer files suit, the litigation costs alone can destroy a pre-seed startup. Engage counsel immediately.

2. Analyze the Assignment Clause Language

Have your attorney analyze the exact language of your assignment clause under the Stanford v. Roche framework. Is it a present assignment ("hereby assign") or a promise ("will assign")? Is the scope limited to work-related inventions, or does it sweep in everything? Is there a carve-out for personal-time inventions? The answers to these questions determine your available defenses.

3. Build Your Evidentiary Record

Gather evidence that your startup IP was developed outside the scope of your employment: personal-time development records, proof you didn't use employer resources, evidence the invention doesn't relate to your employer's business (if the clause is limited to related inventions). In the ATOM Instrument case, the fact that the engineer developed the technology "on his own time and in his own laboratory" was a central factual issue — but the case still went through years of arbitration and litigation because he also used employer resources for testing.

4. Negotiate a Resolution

Many employer-IP disputes settle through negotiation rather than litigation. Your attorney can approach your employer's legal team to negotiate a release, a license, or a co-ownership arrangement. Employers often prefer a clean resolution over litigation, especially if the startup's technology is only tangentially related to their core business.

5. Consider Insurance and Indemnification

If your startup has raised capital, your investors may require you to obtain IP infringement insurance or negotiate indemnification from your former employer. Some investors will walk away if the IP chain of title isn't clean; others may invest with appropriate risk-mitigation measures in place.

For guidance on hardware-specific patent strategy, including what to file and when, see our article on hardware patent strategy for early-stage founders.

Actionable Next Steps

If you're a hardware founder currently employed at a semiconductor, deeptech, or technology company in Texas, here's what you should do — in order:

1. Pull your employment agreement and every IP-related document you signed. Read the assignment clause word for word. Identify whether it's a present assignment or a promise to assign. Note the scope and any carve-outs.
2. Audit your startup's development timeline. Document when, where, and how you developed each piece of core IP. Confirm whether you used any employer resources — even incidentally.
3. Stop using employer resources for startup work immediately. Switch to personal devices, personal tools, and personal time. This won't cure past use, but it prevents the problem from getting worse.
4. Consult with a startup attorney who understands both IP law and employment agreements. The intersection of employment IP assignment and startup IP chain of title is a specialized area. A generalist may miss issues that a specialist would catch immediately.
5. Get a written release or waiver from your employer before you incorporate or raise capital. This is the cleanest fix and the one investors will demand. If a full release isn't possible, negotiate a license or co-ownership arrangement that your investors can accept.
6. Incorporate and assign all founder IP to the company. Once the employer-IP issue is resolved, execute a clean founder IP assignment to your new entity. This is a prerequisite for any priced round — investors will require it in their diligence checklist.
7. Keep your innovation records current. Maintain lab notebooks, design documents, and development logs that establish the independence of your startup IP from your employment. These records are your best defense if a claim arises later.

The Texas semiconductor boom is creating enormous opportunities for hardware founders. But the same employment agreements that protect your employer's IP can silently claim your startup's most valuable assets. Understanding the legal landscape — from Stanford v. Roche's "hereby assign" vs. "will assign" distinction to Texas's lack of a § 2870-style safe harbor — is essential to building a startup with clean, investable IP. The earlier you address these issues, the cheaper and easier they are to resolve.