The IP You're Giving Away in Partnership Agreements

The clause everyone signs and no one reads twice can decide who owns what gets built.

Two companies sign a partnership agreement. They negotiate price, term length, exclusivity, termination triggers. The intellectual property section reads like boilerplate lifted from the last deal, and both sides initial it without a second look.

Three years later the partnership ends, or the product becomes valuable enough to fight over. That is when someone finally reads the IP language closely and discovers the agreement never answered the one question that mattered: who owns what got built.

This is not a rare mistake. It is close to the default outcome of how partnership agreements get drafted and negotiated, and the stakes keep climbing. Corporate intangible assets worldwide, the patents, software, data, and know-how that increasingly define enterprise value, approached USD 100 trillion in 2025, according to WIPO's Global Innovation Index research with Brand Finance. Separately, long-term tracking from the Ocean Tomo Intangible Asset Market Value Study shows non-physical assets now command 90 to 92 percent of S&P 500 market value, up from a mere 17 percent in 1975. Ownership often changes without anyone intending it, and increasingly, ownership is the whole ballgame.

Work For Hire Rarely Means What the Parties Assume

The term work for hire carries a specific legal meaning that rarely matches how the parties use it day to day. Under Section 101 of the U.S. Copyright Act, work-for-hire status is confined to two specific legal paths: an employment relationship, or a written agreement covering one of a limited set of specific categories of commissioned work. Partnership agreements between two independent companies typically satisfy neither path, which is why they regularly fall outside the doctrine's scope.

A vendor's engineers build a feature for a partner's platform. Everyone calls it work for hire in the hallway. The underlying code stays owned by whoever employed the engineers who wrote it, work-for-hire label or not. The gap surfaces at the worst possible moment: an acquisition, a licensing negotiation, or a dispute over who gets to commercialize what the two companies built together.

Background IP and the Problem Joint Development Creates

One of the most instructive disputes in joint development history involves the MP3 audio compression standard. Employees of AT&T, later Lucent Technologies, and the German research organization Fraunhofer Gesellschaft collaborated on digital audio compression technology under a joint development agreement, as detailed by Primerus. Each company retained separate ownership of its existing technology developed before a fixed date in 1989.

That structure looked clean on paper. What it did not fully resolve was the treatment of technology that combined contributions from both sides going forward, a gap that shaped years of licensing complexity around one of the most commercially significant patent families in modern computing.

Background IP clauses look simple. Each party keeps what it brought to the table. In practice, once two engineering teams start building together, unpacking whose contribution belongs to which pre-existing technology becomes difficult, particularly when a joint invention combines elements each side owns separately.

Patent law adds another layer most executives never think about until it costs them. Under U.S. patent law, a joint inventor who contributes to even a single claim in a larger patent becomes a joint owner of the entire patent, not just the piece that inventor built. Leave one contributor off the inventorship list, intentionally or by oversight, and under 35 U.S.C. § 262, that omitted co-owner can independently license the invention to a third party, including a competitor, without the other owners' consent and without sharing the royalties. A well-documented dispute involving Ethicon and U.S. Surgical Corporation turned on exactly this issue: Ethicon, Inc. v. United States Surgical Corp. (1998), where an engineer's overlooked contribution to two of a 55-claim patent gave him the right to license it independently, and his refusal to join the infringement suit got the case against a competitor dismissed entirely.

The lesson holds regardless of what the contract calls the arrangement. As Thomas Jefferson observed in an 1813 letter to Isaac McPherson on the nature of inventions, "Stable ownership is the gift of social law." Ownership was never automatic, even for the person who built the thing. It exists only where the agreement establishes it.

The License Carve-Out That Resurfaces Later

Licensing carve-outs create a different problem. A carve-out grants one party rights to use IP within a defined field, geography, or product line, while ownership stays with the other party. Norton Rose Fulbright describes how a party licensing valuable proprietary technology into a joint venture for one specific use case will sometimes push to retain rights over anything the venture later develops from that technology, an arrangement known in practice as a grant-back clause.

These carve-outs are supposed to protect the licensing party. What they often produce instead is two parties with overlapping, loosely defined claims over the same improvement, each certain their reading of the license is the correct one.

The field-of-use definition is where most of these arrangements quietly fail. A carve-out written around a specific product category rarely anticipates the adjacent products that show up two years later, built on the same underlying technology.

The scope creep rarely arrives in one clause. It arrives through amendments, statements of work, and technical appendices signed months apart, each one reasonable in isolation. A license granted for one purpose gradually becomes something broader than either party intended, and the agreement stays silent exactly where the money eventually shows up.

Growth Turns Old Agreements Into New Liabilities

The most consistent pattern I have watched play out across partnership disputes involves timing. Companies audit IP ownership when a deal is happening, a lawsuit gets filed, or a buyer starts asking hard questions in diligence. Almost nobody audits it when the partnership is working well and there is still time to fix the language.

The agreements themselves rarely stay static in what they govern, even when the paperwork never changes. An internal tool becomes a commercial platform. A manufacturing process becomes licensable IP in its own right. What looked immaterial at a few million dollars in revenue can become the central asset in an acquisition once the company is a hundred times that size, governed by language nobody has reread since signing.

By the time the questions get asked under pressure, the answers are far more expensive to produce.

Where the Gaps Surface in a Deal

The moment these gaps become costly is usually the moment least convenient for discovering them. Acquirers built entire due diligence practices around this reality. Ownership disputes, missing assignments, and unresolved joint IP claims sit high enough on the risk list that a dedicated IP audit is now standard practice before an acquisition closes, according to attorneys at KPPB LAW.

Patent litigation in the United States can run up to $5 million per patent through trial and appeal once more than $25 million is at risk, according to the American Intellectual Property Law Association's Report of the Economic Survey. Few companies budget for that figure when a routine partnership clause turns into a fight over who owns the asset.

The business world has no shortage of examples showing how far these disputes can travel once they start. The decade-long fight between Oracle Corporation and Google LLC over software interface ownership went to the Supreme Court of the United States before a fair-use ruling settled it. The trade secret dispute between Waymo LLC and Uber Technologies, Inc. showed how quickly employment history and prior agreements collide once litigation exposes them to daylight. As Louis Brandeis wrote in Other People's Money and How the Bankers Use It, "Sunlight is said to be the best of disinfectants." Intellectual property provisions deserve that scrutiny long before a courtroom forces it on them.

The Partnership Agreements You Have Never Audited

A useful audit does not require outside counsel for every agreement on the books. It requires honest answers to a short set of questions for every active partnership that involves shared development, licensing, or vendor-built technology:

• Does the agreement identify what each party owned before the relationship started, specifically enough that a court could tell the difference?

• Does the work-for-hire language actually meet the legal requirements for work-for-hire status, or does it just use the phrase?

• If jointly developed IP exists, does the agreement say who can license it, sell it, or block the other party from using it?

• Are contractor and vendor assignments documented in writing, signed, and stored somewhere findable?

Most companies fail at least one of these on their most important agreements. That is not a reason for alarm. It is a reason to look now, while the fix costs a redline instead of a lawsuit. Benjamin Franklin made the point in 1735, in his essay "Protection of Towns from Fire," published in The Pennsylvania Gazette to push Philadelphia toward organizing against fire before disaster struck rather than after: "An ounce of prevention is worth a pound of cure."

The audit itself does not need to be exhaustive to be useful. Start with the three or four partnership agreements that matter most to revenue or product roadmap, the ones a buyer would ask about first in diligence. Read the IP section as if a dispute has already started. Where the language is vague, that vagueness is not neutral. It will get interpreted by whichever party has the stronger incentive to interpret it aggressively when the stakes finally rise.

The value of a partnership agreement was never only in what gets built. It is in who is left holding the rights when the partnership ends, sells, or simply outgrows the paperwork that started it.

The information in this post reflects general legal and business principles related to intellectual property ownership in commercial agreements and is intended for executive awareness and strategic planning purposes only. It does not constitute legal advice. Consult qualified IP counsel before drafting, negotiating, or relying on any specific contract language.

Where This Gets Solved

Growth, leadership transitions, and financial pressure rarely arrive one at a time, and IP ownership gaps tend to surface right alongside them, at the moment a company can least afford to unwind a problem in isolation. Aspirations Consulting Group works with mid-market and Fortune 1000 executives at these inflection points, when strategy, operations, leadership, and financial performance all move at once and internal teams need an outside read before the decision gets made. If your partnership agreements or IP position have not been stress-tested recently, a confidential consultation is the place to start. Visit aspirations-group.com.

More Insight Every Weekday

This piece is one of five published each week to more than 10 million current and aspiring executives around the world, covering the strategic, financial, and leadership questions that shape how large organizations actually run. ACG Strategic Insights goes to readers who want to think through what comes next before it becomes urgent. Request a complimentary subscription at https://www.aspirations-group.com/subscription.

Thanks for reading!

~ Jerry Justice

Living to Serve, Serving to Lead™