Joint development sounds simple on day one.
Two teams shake hands. They share code, data, lab time, and ideas. They build something neither could build alone. Everyone feels like the “win” will be shared.
Then someone asks a single question that changes the whole mood:
“Who owns the global patent rights?”
If that question is not answered early, joint development can turn into a slow legal fight that hurts both sides. The product ships late. The relationship breaks. And the patents—if they get filed at all—end up narrow, messy, and hard to enforce.
This guide is about how ownership really works in joint development deals, what “global” changes, and how to write the contract so your startup does not lose control of what it helped create.
And if you want Tran.vc’s help building a strong patent plan before these deals get complicated, you can apply anytime here: https://www.tran.vc/apply-now-form/
The trap: “We’ll figure patents out later”
In joint development, the work moves fast. People want to stay friendly. Nobody wants to “lawyer up.” So the first draft of the agreement often has vague lines like:
- “Each party owns its background IP.”
- “Foreground IP will be handled in good faith.”
- “We will decide patent filing strategy later.”
Those lines sound polite. They are also dangerous.
Patents are not like a shared Google Doc. Patent law is very strict in some places and very strange in others. If the contract is unclear, the default rules can kick in. Those default rules vary by country. That’s the first reason “global patent rights” matter.
In plain words: if you don’t write the rules, the law will write them for you.
And you may not like the version you get.
What “global patent rights” really means
When people say “global patent rights,” they often mean “we want protection everywhere.”
But patents do not work like that. There is no single patent that covers the whole world. You file by country or by region. You can use tools like the PCT process to delay big costs and keep options open, but in the end you still enter countries.
So “global rights” usually means four things:
- The right to file in any country you care about.
- The right to control what gets filed (and what does not).
- The right to enforce the patents against copycats in each country.
- The right to license or sell those patents worldwide.
In a joint development deal, each of those “rights” can be split up. One party might file. The other might enforce. One might own in the US. The other might own in Europe. Some deals even split by field, like “medical robots” versus “warehouse robots.”
This is why ownership is not a single sentence. It is a full set of choices.
First, the basic building blocks: background IP and foreground IP
A joint development deal usually has two big buckets of IP.
Background IP is what each side brings in. That includes your existing code, models, designs, know-how, test rigs, and earlier patent filings.
Foreground IP is what gets created during the project.
Most fights happen because people agree on the bucket names but not on what goes inside each bucket.
Here are two real-world examples you can picture:
Example 1: Robotics startup + factory automation company
Your team has a motion planning stack. The partner has factory layout data and safety rules. Together you build a new collision-avoidance method that uses their data and your stack.
Is the new method “foreground”? Yes, most likely.
But what about your updated motion planning stack that now has new modules written during the project? Is that still your background because it’s “your product,” or is it foreground because it was built during the joint work?
If the agreement is vague, the partner may claim it is joint property. That can block you from using your own improvements in your next customer deal.
Example 2: AI startup + medical device company
You have a model architecture. The partner gives labeled clinical data. You fine-tune and discover a new training approach that improves accuracy.
Now patents come up. The partner may say, “We paid for the data and the study, so we own the invention.” You may say, “We designed the method, so we own it.”
Both sides feel “obvious.” Neither side is safe without clear contract language.
Joint inventorship is not the same as joint ownership
This is the point where founders get surprised.
In patent law, inventorship is about who contributed to the idea of the claimed invention. Ownership is about who legally owns the application and any issued patent.
A person can be an inventor and still not own the patent, because their employment contract or assignment document transfers ownership to their employer.
In joint development, you can easily end up with inventors from both sides. That part is common. The problem is what happens next:
- If inventors are from both sides, ownership often becomes shared unless there is an assignment structure.
- If ownership is shared, each country may treat shared owners differently.
This is why “global” matters. The same joint patent can act like two different assets depending on where you enforce it.
The uncomfortable truth: joint ownership can be a mess
Many teams think “joint ownership” sounds fair. In practice it can be a weak outcome.
Here’s why.
When ownership is split, you need rules for:
- who pays to file
- who picks the countries
- who controls claim scope
- who responds to office actions
- who decides whether to abandon
- who can license
- who can sue
- who must join a lawsuit
- who gets money from damages or license fees
If the contract does not cover these topics, you fall back to local law. And local law is not consistent.
In some places, a co-owner can license without telling the other owner. In other places, they cannot. In some places, a co-owner can sue on their own. In others, they must join all owners.
So if your partner owns half the patent and starts licensing it cheaply to everyone, your “global rights” can be ruined. Not because they hate you, but because their goals are different. They might want broad adoption. You might need exclusivity to build a business.
Joint ownership is not evil. It is just hard. It needs strong contract rails.
The most common deal structures for patent ownership
When people talk about joint development, they often end up in one of these patterns. I’ll describe them in simple terms and also tell you where founders get hurt.
1) Each party owns what its people invent (with cross-licenses)
This sounds clean: if your employees are inventors on a patent, you own it. If their people are inventors, they own it. If it is mixed, you may split or assign based on a formula.
Then each party grants the other a license to use what they need.
This can work, but the risk is in the details.
If you give a broad license, you may accidentally allow the partner to use your invention outside the joint project. If the license is too narrow, the partner may refuse to commercialize because they fear getting sued by you later.
The practical fix is to define a very clear “field of use” and a clear set of products or markets. That way the partner can ship what they need, and you can still grow in your core space.
2) One party owns all foreground IP (often the bigger company)
Large companies often ask for this. They say: “We are paying, so we own.”
If you are a startup, this is dangerous unless the pay is truly worth it and the scope is tightly limited. Many startups sign this early because they want revenue or a logo, then realize later they gave away their best new invention.
If you must accept it, you need guardrails.
You need to carve out:
- improvements to your platform
- generic methods that are not specific to their product
- anything you could use with other customers
You also need a license back that is strong enough so you can keep building your company.
3) Joint ownership of foreground IP
As we covered, this can feel fair but can weaken your position if the contract is not very specific.
If you do joint ownership, treat it like a high-risk asset that needs full governance. You must write the rules for filing, licensing, and enforcement. “Good faith” is not a rule.
4) Assign everything to a new entity (a joint venture)
Sometimes both parties form a JV that owns the patents. This is more common in certain industries and in cross-border deals.
This can work, but it adds overhead and can slow future fundraising. Investors often dislike messy cap tables and unclear IP chains. If you do this, keep it very narrow and make sure your core tech stays with you.
The big question: what happens when inventors are mixed?
In joint development, mixed inventorship is normal. You might have your engineer and their engineer working side by side. They brainstorm. They build prototypes. They fix edge cases.
Now you have a new invention that is truly joint.
There are three main ways to handle this.
Option A: Jointly owned patents
Both parties co-own the patent.
This is easy to understand but hard to manage, especially “globally,” because local rules differ.
Option B: One party owns, the other gets a license
This is often better for clarity.
For example, the startup owns the patents, and the larger company gets a license in a defined field, maybe even exclusive for that field. That allows the startup to keep the patent “asset” clean for investors, while the partner still gets the business value.
Or the big company owns, but the startup gets a strong license back plus rights to use the invention outside the partner’s industry.
The key is: the license has to be written carefully.
Option C: Split by field or application
You can agree that patents related to “warehouse robotics” are owned by you, and patents related to “their specific factory line” are owned by them.
This is not always easy to draft, but it can match reality. Your investor cares about your broad platform. The partner cares about their specific deployment.
Why “global” becomes the fight even when the relationship is fine
Even when both sides like each other, global filing decisions create tension because the costs and the priorities are different.
A startup often wants:
- a strong US filing
- maybe a PCT to keep options open
- selective entry into Europe, Japan, Korea, maybe China depending on market and risk
A large company may want:
- heavy filing in markets tied to its manufacturing footprint
- filings in countries where it fears copycats
- filings that support its long product roadmap
If you share ownership or share filing decisions, you need a decision process. Otherwise someone will feel forced to pay for filings they do not value, or forced to accept weak coverage in key markets.
This is where deals break.
A simple way to think about patent rights in joint development
Instead of asking “Who owns the patent?” ask these five questions:
- Who can file, and where?
- Who controls claim scope and strategy?
- Who pays, and what happens if they stop paying?
- Who can enforce, and who must join?
- Who can license, to whom, and on what terms?
If the agreement answers those five questions clearly, “global patent rights” become manageable.
If the agreement does not answer them, you will end up negotiating in the middle of a crisis, when leverage is gone.
A practical founder playbook before you sign the deal
This is the part that saves startups.
Before you sign any joint development deal, do these three things internally:
First, write down what you truly need to protect. Not in legal terms—just in plain words. The core method. The key training trick. The sensor fusion approach. The unique mechanism. The part that makes your product hard to copy.
Second, write down what you are willing to share, and what you are not. Many founders share too much because they want the partnership to work. But sharing is not the same as giving away ownership. You can collaborate without gifting your moat.
Third, decide what “success” looks like for the deal. Is it revenue? Validation? Data access? A path to a regulated market? These goals change what terms you should accept. If the deal is mainly for learning and access, don’t sell your future for it.
Tran.vc helps founders do this kind of thinking early, then turns it into a patent plan that matches how deals are actually done. If you want that support, apply here: https://www.tran.vc/apply-now-form/
Filing worldwide is not “one choice”
Patents are country-by-country assets
When you work with a partner, it is easy to talk as if you are building “one patent.” In real life, you are building a stack of rights that live in different places. A US patent is one thing. A European patent is another. A patent in Japan or Korea can behave differently in court, even if the words look similar.
The PCT is a timing tool, not a global patent
Many teams say, “We will file a PCT and cover the world.” A PCT filing is mainly a way to buy time and keep options open. You still must enter countries later, and that is when the real money and real strategy decisions show up. If the deal does not say who controls that moment, you may lose the right to protect the markets that matter most.
“Global rights” includes the right to say no
A partner can push for filings in places you do not care about. Or they can block filings in places you do care about. Global rights are not only about expanding. They are also about having the power to refuse filings that do not help your business or that expose your secrets in risky places.
Ownership is not one word
Inventorship decides names, not business control
Inventorship is about who helped create the idea. Ownership is about who holds the legal asset. These are not the same thing. A person can be named as an inventor and still have zero control, because their rights are assigned to their employer under signed documents.
Assignment language is the real ownership switch
In a joint deal, the most important sentence is often a simple one: who assigns inventions to whom. If each side assigns inventions created by its people to its own company, you may end up with split ownership when inventors are mixed. If each side assigns all project inventions to one owner, the asset becomes clean, but the license terms then decide who gets what value.
Background and foreground can blur fast
Founders often assume the “new stuff” is the only thing that matters. But many disputes are about improvements to the old stuff. If your platform gets better during the work, you must be able to keep that improvement as yours, or your product roadmap can get trapped inside a partner agreement.
Joint ownership: what it really creates
Joint ownership can weaken your leverage
Joint ownership sounds fair, but it often creates a situation where neither side can move fast. Filing, licensing, and enforcement decisions become slow. Investors also dislike unclear control, because patents are supposed to be a clean shield, not a shared steering wheel.
The same joint patent behaves differently in different countries
In some places, a co-owner may license without telling the other owner. In other places, they cannot. In some places, all owners must join a lawsuit. In other places, one owner can sue alone. This means “global” joint ownership is not one rule set. It is a patchwork.
Joint ownership needs governance like a small company
If you choose joint ownership, treat it like you are forming a tiny shared business around each patent family. You need rules for who decides filings, who pays, who can license, and how disputes get resolved. Without those rules, you do not have a deal. You have a future fight.
The filing-control question that decides everything
Who decides what gets filed
Patents are not only protection. They are also a way to describe your system in public. Filing choices decide what you reveal and what you keep secret. If the partner controls filing, they may push broad disclosures that help them and hurt you. If you control filing, you might keep the patent focused on what builds your moat.
Who decides where to file
Where you file changes the cost and the value. A partner may want coverage in the countries where they make products. You may want coverage where you sell or where competitors copy. If you do not set a clear rule, the filing plan turns into a budget fight every year.
Who controls claim scope and amendments
A patent’s strength often comes from the claims, not the story in the description. During prosecution, claims get rewritten. If your partner can change claims without your approval, they can narrow your protection or steer it toward their product only. That can leave you with a patent that looks impressive but does not defend your future markets.
Cost sharing is not a detail
Filing budgets create power
In practice, the party who pays often ends up controlling strategy. That is why cost terms are never “admin.” If your partner pays for everything, they may later say the patent is “theirs in spirit,” even if the contract is unclear. If you split costs, you need a clean process for approvals and timing.
What happens when one side stops paying
This is the clause that many agreements forget. If filings are shared, and one side stops paying, do you both lose the patent? Do you take over and become the sole owner? Do they keep a license anyway? Without clear terms, the patent can die for no good reason.
Abandonment decisions must be planned
Some patents are worth keeping. Some are not. If a partner can abandon a patent without your consent, your global plan can collapse. If you must keep paying for patents that do not help you, your runway suffers. The agreement must say who can abandon, and what notice is required.
Licensing is where startups quietly lose
A license can be broader than you think
A partner may ask for “a license to use project IP.” If you grant that license without limits, you may allow them to use your invention in other products, other markets, or even with your competitors. That can erase your moat while still looking “reasonable” on paper.
Field-of-use is the startup’s safety rail
A good field-of-use license says the partner can use the invention only for a defined product line, a defined market, or a defined industry. This gives them comfort to ship, while protecting your right to use the same invention for your own growth. This is one of the cleanest ways to keep your company fundable.
Sublicensing is often the hidden risk
If the partner can sublicense, they may pass your rights to suppliers, contractors, or even customers. Sometimes that is needed for manufacturing. But it must be written narrowly, so sublicenses are limited to what is required. Otherwise, your patent rights can spread in ways you never expected, and you cannot pull them back later.
Enforcement: owning a patent is not enough
The right to sue is part of “global rights”
Many founders focus on who is named as owner. But the power to enforce is what gives a patent teeth. If the agreement blocks you from suing a copycat without the partner’s consent, your patent might become a trophy instead of a shield.
Who must join a lawsuit
In some places, all owners must join a lawsuit. If your partner does not want conflict, they may refuse to join. That can stop enforcement entirely. A well-written deal can require cooperation, set timelines for decisions, and allow one party to step in if the other stays silent.
Who keeps money from enforcement
If a patent leads to damages or a settlement, how is money split? If that is unclear, enforcement becomes political. One side may block action because they do not like the payout structure. Clear terms keep decisions business-like, not emotional.
Clean structures that usually work better than joint ownership
One owner, strong license back
A common “clean” setup is to have one party own the patents, then grant the other party the rights they need through a carefully limited license. This keeps the patent chain of title simple. It also helps future fundraising, because investors can see who controls the asset.
Splitting by product or industry
When both sides need real control, a split by field can work well. The partner owns patents tied to their specific product. You own patents tied to the platform. The key is to write the boundary in plain language and match it to real business lines, not abstract phrases.
Decision rights can be split even if ownership is not
Sometimes one party owns, but the other has consultation rights, approval rights, or step-in rights for certain filings. This can reduce fear on both sides. Ownership stays clean, but both sides feel protected.
The contract language that quietly decides the outcome
“Conceived or reduced to practice” is not just legal talk
Some agreements define project inventions as anything “conceived or reduced to practice” during the project. That can be very broad. It can accidentally pull in ideas your team had before the deal, or improvements you build later while still using the same tools. You must be careful with timing language so your core roadmap does not get captured.
“Related to the project” can swallow your platform
A clause that says “any IP related to the project” belongs to the partner can be a trap. “Related” is a big word. If your startup works in the same space, almost everything can be argued as “related.” Strong agreements use tighter definitions, like specific deliverables, specific modules, or specific technical goals.
Confidential info and patent filings must match
If your partner shares sensitive info, they may demand review rights over filings to avoid leaking their secrets. That is fair. But review rights should not become control rights. Review should be limited to checking confidential content, with strict time limits, so filings do not get delayed or watered down.
Founder tactics to protect your global patent position
Treat the first draft as a starting point, not a test of trust
Many founders think pushing back makes them look difficult. In reality, serious partners expect negotiation. They have seen deals fall apart later because the contract was vague. A clear agreement protects both sides and keeps the partnership healthy.
Ask for a “patent steering” process in writing
Even if ownership is shared or licenses are complex, you can still reduce chaos by setting a process. Who meets, how often, how decisions are made, and what happens if there is a dispute. A simple process prevents months of delays at the worst time.
Lock down your improvement rights
Your startup must keep the right to improve its own platform. This is not greed. This is survival. The agreement should say that improvements to your background tech remain yours, even if developed during the project, as long as they are not specific to the partner’s confidential inputs or product.
If you want, Tran.vc can help you map these risks to your exact tech, then build a patent plan that makes joint deals safer instead of scary. You can apply anytime here: https://www.tran.vc/apply-now-form/