Export controls and patents sound like two different worlds.
One is about shipping tech across borders. The other is about protecting ideas.
But for deep tech founders, they collide more often than you think. And when they collide, it can slow down your patent filing, block your global rollout, or create legal risk you never planned for.
Most teams miss this because they are moving fast. They are building models, tuning systems, training robots, testing edge devices, hiring talent from anywhere, and sharing code in Slack like it is air. That speed is good. But export rules do not care that you are early. They apply even when you are tiny.
So in this article, I will walk you through the real traps we see founders fall into. Not theory. Not fear. Just what tends to happen in real life, and how to set things up so your patents and your company do not get boxed in later.
Before we go deeper, one quick note: if you are building robotics, AI, or any hard tech and you want help with patent strategy and filings early, Tran.vc invests up to $50,000 in in-kind patent and IP services. You can apply anytime at https://www.tran.vc/apply-now-form/
Why export controls show up in patent work
A patent is not only a legal document. It is also a “technical disclosure.” You describe how the invention works. You explain the parts. You often include details that would help a skilled engineer rebuild it.
Now here is the key point most founders miss:
In many countries, sharing certain kinds of technical info with certain people can count as an “export,” even if nothing ships. Even if the data never leaves your laptop. Even if you are just emailing a draft patent to a teammate who sits next to you.
Export rules are not only about boxes crossing a border. They are also about knowledge crossing a line.
This matters because patent work creates knowledge transfers all the time:
- You send invention notes to your patent lawyer.
- You share design docs with a contractor overseas.
- You give a pitch deck to an investor group that has partners in other countries.
- You use a global dev team.
- You publish a preprint.
- You file a patent in another country.
- You run cloud training on servers that may sit anywhere.
- You post code or model weights to a public repo.
Most founders treat these like normal startup actions. But depending on what you build, some of these actions can trigger export control issues.
And export control issues can be expensive, slow, and distracting. Worse, they often show up at the worst time: right when you are raising, signing a big partner, or trying to file internationally before a deadline.
The deep tech “risk pattern” that trips founders
If you build in software only, export control risk can still exist, but it is often lower.
Deep tech changes the picture because it mixes software with things governments care about: sensing, navigation, autonomy, drones, encryption, chips, radar, satellites, advanced manufacturing, quantum, biotech tools, and more.
Many of these areas touch “dual use” tech. That means it can be used for normal business, but also for military or security uses.
Here is the pattern we see:
A founder builds something for a good reason. For example:
- A drone system to inspect bridges.
- A robot to move boxes in a warehouse.
- A vision model to detect defects on a factory line.
- A secure comms layer for devices in the field.
- A navigation system for mining sites.
- A chip-level optimization for edge AI.
All of these can be normal and useful.
But the same core pieces can overlap with controlled areas, especially when they include:
- High-precision positioning.
- Advanced sensors.
- Autonomy at scale.
- Secure encryption.
- Long-range comms.
- Guidance, targeting, or tracking features.
- Hardware that can run in harsh conditions.
- Training methods that improve performance in sensitive tasks.
Founders do not build “weapons.” They build tools. But export rules often look at capability, not intent.
So a founder gets surprised later when someone says, “Wait, we might need a license for that,” or “We cannot share that spec with this person,” or “We need a government review before we file in that country.”
That surprise is what we want to remove.
Why this matters for patents in a very practical way
A patent strategy has two jobs:
- Protect what matters.
- Do it in a way that helps the business, not slows it down.
Export controls can mess with both jobs if you ignore them.
They can affect your patent work in at least five real ways:
First, they can block or delay foreign filing. Many countries require foreign filing permission, and some inventions may need review before you file outside the home country. If you plan to file globally fast, you cannot treat export controls as an afterthought.
Second, they can limit who can work on your patent drafts. If part of your team is abroad, or if your patent counsel is in another country, or if you use overseas contractors to help write or draw figures, you might trigger a “deemed export” problem. That is the case even if you never “sell” anything.
Third, they can shape how you write the patent. Sometimes the safest move is not to dump every working detail into one place. You still must disclose enough to meet patent rules, but you can choose what to claim, what to describe at a high level, and what to keep as a trade secret. This is not about hiding. It is about smart separation of what must be public versus what does not.
Fourth, they can affect your publishing timeline. Some deep tech teams publish papers or blog posts to recruit and build trust. But publishing can count as a public release of controlled tech. If you publish too early, you can create a legal issue and also hurt your patent rights in many countries.
Fifth, they can show up in diligence. A strong investor will ask about compliance. A defense or aerospace customer will ask even harder. If you have no story, no policy, and no control over who sees what, you look risky. That can kill deals.
This is why export controls are not only “legal stuff.” They are part of your moat plan.
And this is exactly why Tran.vc exists: to help technical founders build the right IP foundation early, while keeping speed. If you want to talk through your situation, apply anytime at https://www.tran.vc/apply-now-form/
The biggest myth: “We’re too small for this”
This myth causes most of the pain.
Export control rules are not based on revenue. They are based on what the tech is and who has access to it.
A two-person robotics startup can have more export risk than a 200-person SaaS firm, simply because of what they build.
Also, you do not need to “export a product” to have an export issue.
A few examples that surprise founders:
If you are in the U.S. and you share controlled technical info with a foreign national inside the U.S., that can be treated like an export. This is often called a deemed export.
If you push certain code to a public repo, that can be treated like an export, because anyone can access it.
If you store controlled tech on a cloud service and allow overseas access, that can count too.
And yes, sending a patent draft that includes controlled details to someone abroad can create a problem.
This is why “we’re early” is not a shield.
The good news is that you do not need a giant compliance team. You need a clear process and a few smart habits.
The patent angle founders miss: your disclosure can create the export event
Founders often think export controls are about later, when they ship devices or sell internationally.
But patent filings can be the first moment where you put sensitive details into a formal package and send it around.
Think about the normal patent flow:
You do an invention disclosure.
You meet a patent attorney.
You share data, diagrams, code snippets, training results, system specs, and sometimes customer use cases.
You iterate drafts.
You send the draft to co-inventors.
You file.
Then you decide where else to file.
That whole chain involves moving technical data.
So if your invention touches a controlled area, you want to handle export controls early, not after the draft is in five inboxes and on three drives.
Also, keep in mind that once a patent application is published (often 18 months after filing, depending on the country and choices you make), it becomes public. That public release is a kind of distribution event. Even if it is “legal,” you still want to be sure you are not publishing something that later blocks a deal or creates risk with a government customer.
A smart patent plan includes this question:
“What do we want the world to learn from reading this?”
In deep tech, that question is not only about competitors. It is also about compliance and future market access.
What counts as “controlled” in simple terms
You do not need to memorize the rules. But you do need a basic map.
In practice, export controls often apply to:
- Hardware with certain performance levels.
- Sensors with certain precision.
- Navigation, guidance, and control features.
- Encryption and secure comms.
- Certain chip designs and manufacturing tools.
- Some AI and autonomy capabilities, depending on the country and the use case.
- Anything tied to defense, aerospace, or space systems.
Different countries have different lists. The U.S. has a major role here because many startups are based there, and many tools and components are U.S.-made. U.S. export controls often show up even when the company is global.
And “controlled” does not mean “illegal.” It often means you may need a license, or you may have limits on sharing.
A founder-friendly way to think about it is:
If your tech can help someone see farther, move faster, target better, hide better, break security, or build advanced weapons faster, then it is more likely to trigger controls.
That does not mean you are doing anything wrong. It just means you should be careful.
A very common patent mistake: filing first, thinking later
Here is the situation we see again and again:
A founder is excited. They have a breakthrough. They rush to file.
They use a freelance illustrator overseas to make clean patent figures.
They send drafts to a team member abroad.
They include deep implementation details in the draft because they want a “strong patent.”
They start planning a PCT filing (a common path to preserve the option to file in many countries).
Then, later, a lawyer or customer asks: “Did you get the right clearance for foreign filing?” Or: “Did you share controlled technical data with non-U.S. persons?” Or: “Where did those drawings get made?”
Now everyone has to backtrack.
The founder is confused because they did not ship anything. They only wrote a patent.
But the issue is the sharing of technical data, not the shipping of a box.
This is painful, but it is avoidable.
What to do instead: a simple early workflow that keeps speed
You do not need to slow down. You need a small set of actions that become your normal way of working.
Step one is not “hire a compliance officer.”
Step one is: classify what you are building at a high level.
This means you ask, early:
Does our system include advanced encryption?
Does it include autonomous navigation or guidance?
Does it include drone flight control?
Does it include high-end sensing, radar, or thermal imaging?
Does it include space or satellite links?
Does it include chip-level design that might be restricted?
Does it include training methods that could be sensitive?
If the answer might be yes, you treat export controls as part of the IP plan from day one.
At Tran.vc, this is one of the first screens we run in early patent strategy sessions for deep tech teams. It helps you avoid creating a mess later.
If you want help with that, apply anytime at https://www.tran.vc/apply-now-form/
The key concept: “deemed exports” and why founders get shocked
This is the one phrase you should remember.
A “deemed export” is when controlled technical info is released to a foreign person, and the law treats that release like an export to that person’s home country.
The part that shocks founders is that the release can happen inside your own office, inside your own country.
Why does this matter for patents?
Because patent drafts, invention notes, and even live whiteboard sessions can count as technical releases.
This does not mean you cannot hire global talent. It means you need a plan for what they can access, and how you handle sensitive parts.
In a startup, the default is “everyone sees everything.” That is good for speed. But it is risky if your tech falls into a controlled area.
A better default is “need to know” for the sensitive core. That keeps you safe and also strengthens your moat, because fewer people have full visibility into the secret sauce.
Where founders accidentally export without knowing it
Let’s look at real habits that create issues.
One habit is using overseas contractors for core work. A contractor who helps tune control loops, optimize flight stability, improve radar signal processing, or modify encryption might be receiving controlled technical data.
Another habit is sending a detailed deck to investors without thinking. Many funds have global partners. Some have LPs abroad. That does not always create an issue, but if your deck contains technical details that fall into a controlled category, you want to be careful.
A third habit is storing everything in shared drives with open access. If your Google Drive includes detailed schematics, code, or model weights and your team is global, you may be giving access across borders by default.
A fourth habit is open sourcing too early. Some founders do it for hiring. Others do it to gain trust. But once something is public, you cannot pull it back. If that code falls into a sensitive category, the risk can be serious.
A fifth habit is using foreign patent drafting help. Many founders use low-cost patent drafting support outside the home country. That can be fine for many areas. But in controlled tech, it can be risky, because it is literally sending the core technical details abroad.
I am not saying “never do these things.” I am saying “do them with eyes open.”
Patents versus trade secrets: the export control twist
Founders often ask: “Should we patent this, or keep it secret?”
Usually the tradeoff is:
Patents give you legal rights, but you must publish details.
Trade secrets stay private, but you must keep them protected.
Export controls add a new layer:
If publishing the details would create problems, you may want to patent the parts that can be safely disclosed, and keep the most sensitive implementation details as trade secrets.
This hybrid approach is common in deep tech. It is not a hack. It is normal strategy.
For example:
You might patent the system architecture, the workflow, the integration method, the safety checks, the hardware layout, and the high-level training method.
But you might keep specific parameters, tuning methods, data pipelines, and certain performance tricks as secrets.
This can also help you reduce export exposure because you limit the spread of the most sensitive technical data.
The “right” split depends on your tech and your market.
This is exactly the kind of strategic IP planning Tran.vc helps founders do early, before it becomes expensive to change course. If you want to explore this for your company, apply anytime at https://www.tran.vc/apply-now-form/
The real problem: patents make you share your “how”
A patent is a public teaching document
A patent is not just a badge that says “we own this.” It is a document that teaches. It tells a trained engineer what you built, how it works, and how to repeat it. That is the deal you make with the government: you share the method, and in return you get rights.
That “teaching” part is where founders get caught. Even if you never ship a product, a patent draft can carry very detailed technical facts. The moment you send that draft to someone outside your country, or to someone who is treated as “foreign” under local rules, you may have created an export event.
Export controls are about knowledge, not boxes
Most people think export controls only matter when a device crosses a border. In deep tech, the bigger risk is often the transfer of technical details. Sharing code, architecture, or build steps can be treated the same as shipping a physical product.
This is why patents matter so much. Patents create a routine of sharing technical info with lawyers, inventors, contractors, and sometimes investors. If you do not plan for that, you can create risk by accident.
Why deep tech is different from “normal software”
Deep tech often sits close to areas governments watch closely. Robotics, drones, advanced sensors, secure comms, and high-end chips can overlap with “dual use” rules. That does not mean your product is bad. It means the same capability can be used in sensitive ways.
A normal SaaS app can still face export rules, especially around encryption. But deep tech founders see more edge cases because their work often touches hardware performance, autonomy, navigation, or sensing. Those are common trigger zones.
What founders think export controls are
The “shipping mindset” that causes blind spots
Many founders only think about export controls when they imagine selling outside their home country. They picture a product in a box, going through customs, and needing paperwork. That is not wrong, but it is incomplete.
In real life, the first export event may be a PDF, a Git repo, a CAD file, or a patent draft. The risk starts early because startups share constantly. In deep tech, sharing is part of building.
The “we are too early” myth
Early stage teams believe rules are for big companies. They assume that if they do not have revenue, the risk is low. Export rules do not work like that. They are based on what the tech can do and who can access it.
A two-person drone startup can trigger more export issues than a large marketing software company. It is not about size. It is about capability and access.
The “we are not defense” myth
Founders often say, “We are not building weapons.” Most of the time, that is true. But export rules often focus on what the system can enable, not what you intend.
A warehouse robot might include navigation features that also matter in other settings. A vision model for factory checks might also improve tracking. A secure comms layer for field devices might look like something regulated. Intent helps your story, but capability is what gets tested.
What export controls actually are in startup terms
The short meaning of “export”
In many places, “export” can include sending technical data to another country. It can also include giving controlled information to a foreign person even when they are inside your country. This is one reason the rules feel strange.
Founders do not expect an email to be treated like a shipment. But if the email contains controlled technical detail, that email can count. That is why simple habits matter.
The idea of “deemed exports”
A “deemed export” is when sharing controlled technical info with a foreign person is treated like exporting it to that person’s home country. This can happen even if both of you are sitting in the same room, in the same city.
Patent drafting can trigger this because drafts often contain the full method, the steps, and key design details. If those drafts circulate without control, you can create a deemed export issue without noticing.
Why “public” sharing changes everything
When information is made public, it is no longer limited by your internal controls. That can include a published paper, a public repo, a conference talk, or a published patent application. Public release is a point of no return.
That does not mean you should never publish. It means you should plan what you publish, when you publish it, and how it aligns with patents and compliance. In deep tech, timing is part of strategy.