Fearn x Flux AI: Patent fireside chat for hardware founders
Flux hosted “Fearn x Flux AI: Patent Fireside Chat for Hardware Founders,” a San Francisco Hardware Meetup focused on patent strategy and building a patent portfolio as an early-stage startup.
The Fearn team answered questions from hardware founders and builders preparing to file patents in the coming months. Fearn is an AI-native patent firm for startups, combining former Big Law patent expertise with purpose-built AI to file patents across software, hardware, robotics, and biotech in days rather than months.
Watch the take away of the talk below or read the full transcript.
The takeaway
Recorded live at Flux HQ in San Francisco.
The full talk
Lightly edited for readability.
What is a patent, and why is it relevant?
I will jump in with three questions that we hear a lot about—basic hardware-related questions or patent-related questions often from hardware founders—and then I have three case studies. We don't have to run through them all. I'm going to ask some questions to see which ones are relevant to those of us in the room. One question that we get a lot is, 'What is a patent and why is it relevant? Why do I even care?'
Well, a patent is an exclusive legal right granted for an invention. And typically we see that a lot of hardware companies will patent either their product—so for example, a physical product like a robotic arm—or a process, such as the software behind how they control their arm or any more intangible thing that makes their invention unique and special.
When should I start thinking about a patent?
Another question we get a lot is, 'When should I start thinking about a patent?' And I think especially if you're in the case where you're still building very early stage, so many ideas, everything is changing, you might not be entirely sure when to start thinking about it. And so the actual time to file might vary depending on your own considerations, but at least starting thinking about a patent: it's never too early, but sometimes it can be too late.
So there's this idea known as a public disclosure bar that exists across many countries, US included, where it's your initial disclosure—which could be your product manual, it could be a blog post, it could even be a pitch to investors that you've given publicly, or any sales that you've made—they can count as a first disclosure.
So once your invention is first disclosed and in the public, the US will give you a 12-month window in which you should file your first patent application. If you're past that 12-month, one-year window, it still is possible to file; it'll restrict your options somewhat.
And I want everyone to know early in advance: when you're thinking about patenting something, keep in mind what your public disclosure is, and then we can help figure out what timeline you should follow from there.
How do I prepare to file a patent?
And then the third and final question that we get a lot is, 'So how do I actually prepare to file a patent?' There's so much going on in your own company, the IP might not be top of mind, but if you want to keep some steps in mind for what you should do for helping make it easier down the line, we would recommend keeping consistent and private records of what you're building.
So, for example, if you have any internal documentation about your key features and who is the person who worked on or invented that key feature, as well as any technical specs or files that you have on hand, you should store them somewhere safe and private. And then if you ever need to share them with an IP attorney to help you draft your patent application, that way you're in good hands. It's also very good to keep in mind any external documentation that you have.
For example, if you've worked with a manufacturer or a collaborator, making sure who you've worked with, whether you have any IP agreements with them, and also the dates of any of your public disclosures, like I mentioned on the previous slide. And then finally, it can be helpful as you're preparing for the patent process if you're curious to reach out to a law firm to help you put together some ideas for drafting or to search for prior art from your competitors.
Prior art means any patent publication, or even non-patent literature publication, from your competitors that indicates that they might have some IP protection in a similar field as what you're doing. So, these are the three most common questions we have. I'm sure you might also have questions of your own that we can definitely talk about later on.
Case studies
Next, I wanted to move on to three case studies of hypothetical companies. Any resemblance to real people is entirely coincidental, but these are hypothetical examples of what situations you might face if you're thinking about, when should I patent something and what are some considerations I might find myself going through.
So, here's the three case studies I wanted to present: There is this first case study of a pre-funding company, we'll call it Amy's Accelerometers, that's still in the process of building out a sensor. They don't have any IP yet. They're still in stealth, but starting to think about the patent process.
And then we have Case Study B, which is a more advanced company, BryceBotics, which is building robotic arms and maybe writing their own software for certain types of robotic controls. And let's say that they also have some IP considerations they want to go through. And then finally, we have Smart Clothes by Kate, which is our third company that is, let's say, part of an accelerator.
They're building their product, getting ready to demo and launch, and have a lot of competitors in the wearable space, trying to figure out what is the next best step to go from here. So, for each of these companies, I'm going to start off with a question for the room. Based on what the vibe in the room is, I can either skip through the case study fast or we can spend a little more time and go into a little bit more detail about what you might want to know.
Amy’s Accelerometers: filing before disclosure
So, starting with Amy's Accelerometers, I have a question for the room: Have any of you sold your product yet? A handful of people, maybe half of the room. So, this is a question that might come up related to that 12-month public disclosure bar. We'll go into it in a little more detail here.
So, let me set the case of Amy's Accelerometers. Like I said, they're still in stealth. They're still building, trying to figure out, what is a good sensor design, what should I actually create?
But then Amy receives an offer for someone to buy an early prototype of her design and she's thinking maybe I should sell this early version, get some money, and then it'll help her prepare for when she's eventually fundraising down the line showing that people are willing to buy her product. But the dangerous part here is that Amy doesn't have any patent protection yet.
And so actually, what many people don't know is that a sale or an offer to sell, even a private one, could count as public disclosure against her. So, it's good practice to file a patent application first. You don't necessarily have to if you have a sale, and then you have, in the US at least, a 12-month period after that in which you could file your first patent application. But in many other jurisdictions like Europe and China, your rights may be lost at once.
So, not to scare you guys, I know this is something that might come up pretty often, but if you are looking at IP protection and you want to file your patent application and it's been more than a year, it's one thing that you'd have to keep in mind.
We'll go into this in some of the later slides, too, is what is different about your current commercial version versus what you originally sold or originally disclosed. But in this case, fortunately for Amy, she didn't actually go through with a sale.
She was considering it, ended up realizing, 'Okay, maybe it's better for her at this stage to stay in stealth, keep building, keep developing.' And then at this point, what would be a good strategy for Amy is actually to start filing provisional patent applications early. Provisionals are a type of application that you file with the US Patent Office, and they actually remain private.
They're never disclosed unless you convert them to a non-provisional application within the 12-month window. So, this can be a way where you have your initial idea, you want some form of protection—maybe it's right before a pitch or right before a sale and you need to get something on file—you can file a provisional. It'll never get disclosed unless you choose to eventually convert it to a non-provisional, which will get published.
But in that case, you can have even multiple 12-month windows if you end up abandoning a provisional, then refiling it again down the line and resetting the clock.
Essentially, what you need to know is provisionals are a good strategy if you're still building and you want to stay stealthy, but you want some IP protection. So, you might have heard the term 'patent pending.' You can actually have your invention or your design be patent pending as soon as you file your first application. If it's a provisional application, it'd be patent pending from the time it's provisional all the way through the time it is non-provisional.
When it's eventually granted as a patent, then that's when you would say you have a patent on something. But the entire time in between, you can say patent pending. Even if no one can see your application, even if no one knows it's there, it's still patent pending with the US Patent Office. And another thing I wanted to emphasize is that an investor pitch is also something that counts as a public disclosure.
Generally, we recommend best practice is file a patent application first. If you can't, at least try and file something within that 12-month window.
BryceBotics: protecting an evolving product
So, we've finished our first case study. We have a second one that's for BryceBotics, the slightly more advanced company. And I wanted to ask the room: Has it been over a year since you first revealed your product to anyone? A couple of hands. So, I will go through this a little bit more quickly, but I still think there's some useful takeaways from this case study that might apply to some of you. So, in the case of BryceBotics, they've been developing their product.
They might have released some information about their earlier prototypes, but they're still working on their product. It's still getting better and better every day. And so, the thing is Bryce is about to go fundraising, maybe trying for Series A, and is now at the stage where it's, 'Oh, I need some IP protection. But I didn't file any back when I first published my prototype.'
For example, this arm on the left, which is, as you can tell, a slightly older version of the arm: If it's been over a year, it might be too late to file a patent application on what was disclosed about that earlier version, but he might still have a chance to file some patents about this latest version, which was never shown.
What he would need to do, though, is to focus on what is new since the previous disclosure. So in this case, Bryce would have to see, 'What is new about my arm that wasn't there for the prototype?' Maybe it's something in the actual utility that wasn't there before. Maybe it could even be the design is something new that isn't there before.
Or maybe something that we don't see on the page because it's not something that you would typically see visually is code or software. Maybe they've built a lot more software to help control this arm, and that was not even published for the prototype. It has developed since then, but it's something that he's been keeping secret to himself the entire time.
So these are all things that he could think about as, 'What are some areas that I haven't told the world yet that might be a good idea to build my IP portfolio on?' Another thing he could consider is a design application for the visual design of this robot arm, and maybe some trade secrets. So when I mentioned earlier the visual appearance of this arm looks different, that could be in a design application.
Or maybe the software that he never published is not really something that anyone would be able to figure out by looking at it. That could be a good subject for a trade secret. If you have any questions about those areas, happy to talk about it more after this presentation.
But in Bryce's case, he is working with people all across the world. Let's say that he has his factory that's manufacturing in Shenzhen, and he also has customers maybe in America and in Europe, and he has competitors maybe all across the world. And Bryce is trying to figure out, 'Well, I need patent protection,' but he can't file only in the United States because that would leave out his manufacturer, leave out some of his competitors and customers.
So what he could do instead is actually a route that we recommend called the Patent Cooperation Treaty, the PCT. So there is no one worldwide patent that will ever get granted as something that covers every country in the world, but you can be strategic if you file a PCT. And then that will be like a placeholder in line for being able to file in individual countries that are important to you.
Maybe let's say right now he's still in the process of fundraising and doesn't have the funds to file in all these countries yet.
The good thing about a PCT is that it holds his place in line for at least 18 more months after that PCT filing. As you can see, around month 30 or so, that's when time would be due to file in individual countries. By then, maybe he's gotten funding. Maybe he has a better sense of where his business needs are, and he can selectively choose a few jurisdictions that are important. The most common ones we see are the US, Europe, and China.
And here is something that we would also recommend: in Bryce's case, it seems like these three jurisdictions cover what's most important to him. Not perfect coverage as you can see by the map, but still is generally what he needs to protect. Also, some special considerations in Bryce's case: maybe he used AI to help with his code, but it's important to realize that AI is not the inventor itself that's listed on a patent application.
It can be used as a tool, but the person coming up with the inventive concept generally needs to be a human. And similarly related is trade secret where it's cloud code. So maybe if you have code that is related in some sense to your product, keeping it hidden is the best option—gives you most options for trade secrets down the line.
One thing I wanted to flag, too, is ownership, which is who owns the IP rights to your patent. So in some cases, if you are working in conjunction with a collaborator—let's say the manufacturer he works with in Shenzhen is helping actually develop some parts of his product—well, then they would need to make sure they have clear ownership, so by getting assignments, patent assignments, from those manufacturers in writing back to BryceBotics.
There's also design patents, like I briefly mentioned, protecting visual appearance, and then the idea of building a patent moat. So as your product evolves and as you get a better sense of which business direction is important to you, you can file what's called a continuation, or a con, or maybe even new patents to protect your product as it develops.
Smart Clothes by Kate: searching before filing
And so that wraps up Case Study 2. We have one last one that I wanted to ask one final question to the room: Are there any aggressive competitors in your space? We've all been there. We've seen that happen quite a lot. So this case study might be relevant to you, which is Smart Clothes by Kate. In this case, let me say that Kate is in an accelerator.
She's still building her product, but she knows there's so many other people out there who might be trying to eat her cake. So, let's say that in Kate's case, she sees all these other companies doing something in her space, maybe clever clothes and smart shirts or similar to the concept she's working on, and she gets a little bit nervous. And so, she actually does go ahead and she does file a provisional before her public disclosure—in her case, her demo day.
However, the provisional was a bit rushed and it didn't have quite what she needed in order to differentiate herself from her competitors. So here we see she didn't actually do a search on her competitor's prior art before she filed her provisional. And then what that can sometimes lead to is you might end up with patent claims that are a bit too broad and not specific enough on what your actual product is.
Maybe you're overlapping substantially with your competitors here, and then that can be dangerous because then they will have claims that overlap with yours and then they might say, 'Oh, we filed before you.' So then it might help give them more leverage as saying, 'Well, we got here before you so you don’t have any rights here.'
And then maybe the most dangerous part is if you don't do a search before you file, sometimes you don't actually get a sense of what is novel. And so maybe in your own teams, you're building something different in your space, you are the ones inventing what you're doing, but then your competitors might be out there filing patents in a way that muddies the water in front of the Patent Office.
And so sometimes it can be good to figure out what is actually novel in the eyes of the Patent Office, make sure that your application describes it. And so what we would recommend Kate have done in this case is to actually search first and focus on what her competitors are doing and what IP they have. Try and find the gap where what feature of her invention looks novel.
Maybe Kate's shirt has a different connector that helps create all the different connections in between the wiring, and then that holds up better in the wash or something like that. So then for her filing, her patent filing, she would make sure to describe that feature in great detail, make sure her claims claim that feature and avoid the prior art.
And then finally, the last step she might do is to keep watching by doing further searches as needed or setting up a competitor alert to see what our competitors are doing.
Four takeaways
Four final takeaways: To summarize what we talked about: Don't disclose before you file if possible. If you have to, then you still have a small window, but generally better to try and file before you disclose. File provisionals early and often. That can be a good way to capture the evolution of your product. Get IP assignments in writing where possible—for example, from your manufacturer or from a collaborator, assigning their IP rights clearly back to your company.
Finally, search before you spend because, especially if you're in a very competitive field, sometimes it can be good to get a sense of what is out there before you spend a lot of time and effort on a patent application. So, that is it. Thank you guys all so much for tuning in today. If you have any questions, happy to open up the floor. I think Han is willing to be a moderator here if we do have questions.
Otherwise, I'm happy to let you all chat amongst yourselves and happy to open up to any further discussion.
Q&A
Audience question: So the PCT filing is different from a regular filing. How is it different?
Fearn: So the question was: Is a PCT filing different from a regular filing? And so the terminology that is used, it can be a little confusing. We have non-provisional, which is what you might be thinking of as a regular filing, and a PCT filing. So, yes, PCT tends to be its own category. It's something that you would file almost as a provisional is a placeholder for 12 months until you file non-provisional. PCT can also be a placeholder.
You can file a PCT before you file the non-provisional, or you can file provisional, then PCT, then national filings, which are the non-provisionals in this flowchart. Essentially, it is its own filing. It opens up the door internationally to many different filings in one country, whereas the non-provisional we showed in the previous slides, that would be something that would be essentially one country.
Audience question: So who is governing the PCT? What countries are...?
Fearn: I think there's several hundred member countries. So there's US, there's European Union—which we had as EP on that other slide. Pretty much a lot of the major jurisdictions in the world are part of that. If they are not part of that, there is a different route you can take where you can file directly in Argentina, for example, but those tend to be countries where there's not as frequent IP filing.
Audience question: You mentioned there's two types of patents, right? One for the product, the other one for process. In these case studies, how would the process filing differ?
Fearn: Actually, when I show both the product and the process, both of these can be covered in several different ways. For a physical product, you can cover its utility through the filing of what we described previously: provisionals and non-provisionals and that terminology. Utility meaning what is the function and what is it doing, or you could cover its design—so that would be a design patent that covers its visual appearance, its ornamentation.
And so that's typically the two types that you would consider for product. For process, so for example a software method, you could also do a utility patent, where people do file—if you've ever heard 'software patent,' typically those are utility patents that people file.
It wouldn't be your code itself; it would be, conceptually, 'Here is Step A, Step B, Step C that I would do in order to reach a certain end goal that is the end goal of my method.' Another thing that you could consider is a trade secret, which is not a type of patent, but it is a type of IP protection in a way where instead of a patent where you tell people about your invention and then get the right to exclude it, instead what you would do is you would keep it secret to yourself, document that you're keeping it secret.
You don't have the right to exclude other people from doing exactly what you're doing, but the goal there is they can't figure out exactly what you're doing because you haven't told anyone about it. And then you would get protection indefinitely for that.
Audience question: How do expiration dates work for patents?
Fearn: Good question. So for a utility patent, let's say from the very first day that you file your provisional application, that starts setting off a clock on how long your patent will be alive for. Generally, it's around 20 years. So from the time you first file, within 20 years, as long as your patent gets granted, you'll have some level of patent enforcement. For design patents, it's closer to 15.
And then there's a few other exceptions as well in different countries, but generally 20 years. Trade secrets can be indefinite as long as they actually remain a secret indefinitely. I think some types of secrets are easier to keep secret than others.
You could, for example, try and say, 'I want a trade secret on this part of my hardware device,' but then if your competitor does a teardown and finds out how to use the internal workings of your device in a way that maybe you were hoping that they wouldn't find out, then unfortunately it wouldn't really be a secret. So trade secrets tend to be more robust if it's something like software or code that is not physically able to be torn down or seen easily.
Granted, there are still ways to reverse engineer software, but it can be harder to do than reverse engineering a physical product.
Audience question: What's the process for software?
Fearn: If you're interested in patenting both software and hardware, what some people like to do is, if there's such deep connection between the software and hardware, you can combine them in one patent application. So you describe both simultaneously, and then as it goes to the Patent Office, they'll only let you get a claim typically on one or the other, but then you can file a continuation application.
So for example, they only let you get a claim more on the hardware-focused pieces. And then you say, 'That's all right. I'm going to file a continuation that uses the same disclosure, but then is a separate application,' and then you can get claims on the software. That's one way that some people like to do it. Other companies sometimes prefer to separate the two.
So let's say I have one hardware-focused omnibus and one software-focused omnibus—meaning all your hardware ideas and all your software ideas split among these two big patent filings. And then as both of those go through the different patent offices, they can say,
'Actually, this part of my software I'm not really doing anymore. I want to pivot and focus on a different part of my software application and not have any of that affect what you're doing on the hardware side,' for example.
Audience question: Question: So apparently there are millions of patents. If I invent something, I don't use it commercially. How do the people that potentially hold a patent on it really understand that I released something? What happens in that situation?
Fearn: Are you saying a situation where you've invented something, you choose not to patent it, you're already selling it? Are you worried about competitors trying to do what you're doing?
Audience question: No, about people that have already patented similar or the same thing, and I simply have no idea that that's happened.
Fearn: That does come up quite often where sometimes competitors who are aggressive will start sending out these scary letters: 'You're doing what we're doing, we're going to assert our patents against you.' You do not need to have your own patents to protect against what they're doing. What you would need to do is make it very clear how what you're doing does not infringe what they're doing.
You don't need your own patents for that, but it can be very helpful if you have any leverage.
So, if you did have a patent application pending about that, you could say, 'Well, I've patented this, and if you sue me, I'll countersue you because we're in a similar space.' But I think in general, if that is a competitor reaching out to you and saying, 'You're doing something similar to me,' and you don't have your own patents, you can work with what's called a patent litigator—you don't need a patent of your own.
It's essentially like defending yourself against someone else's patent assertion. That might be something that's a bit beyond the scope of the patent writing process, which is more so what we focus on, but I'm happy to talk more with you if you have a specific scenario.
Audience question: If I have a patent, how do I monitor the whole world if no one is using it?
Fearn: The patent, as you said, you're thinking of it the right way: It's a right to exclude. So it doesn't mean that it's 'Oh, nobody else can do what I'm doing.' It means if they try doing what you're doing, you go after them, you exclude them from it. So typically what you would need to do is be aware of competitors in your space. Unfortunately, you can't exclude something that you don't know is happening.
And if it's someone that's in your own country, that's the easiest way to actually enforce it. You can send demand letters. You can use the legal system in your favor against them.
If it's someone in another country trying to rip you off and you don't have any patent filings in that country, you can still reach out to them and still try to say, 'Hey, I know that you're knocking off what I'm doing.' Maybe if they're on Amazon, you can post an Amazon takedown with your own patent as evidence, but it can be a little bit trickier if you don't have any patents in that country.
More from the night
The event was part of SF Hardware Meetup. Community partner informal is a freelance collective of independent hardware professionals.
Learn more about Fearn and its patent work for startups.
Related Content
Let’s start building.
Let’s build your idea together. All you need to do is describe what you want to make, or what problem you want to solve. Flux will work with you to make it a reality.