A patent is not always the right answer
Getting a patent is treated as a kind of “given”
Whether someone is building a business strategy or launching a startup, “patents” are one of the things people tend to worry about. Partly this is because investors and decision-makers almost always ask about patent status, partly because companies with large patent portfolios do land huge funding rounds, and partly because research institutions are sometimes evaluated, to some degree, by patent counts.
To begin with, a patent is something you file to protect a technical invention as a right, once that invention exists. Something turned into a right this way is granted patent rights, which let you impose certain restrictions on other companies’ use of that technology. A nearly identical system exists not just for technology but for designs and trademarks too, protecting intellectual property. It’s a very elegant, civil idea, and for researchers and engineers, getting a patent is a kind of honor.
None of that is wrong.
For a company that places particular weight on technology, IP strategy matters a great deal. Botch it and you can lose the company in an instant; get it right and you can substantially raise the company’s value.
Everyone knows this, I think so too, and I’ve personally obtained several patents over the course of my career. Still, here I want to deliberately write about how this “isn’t necessarily the right answer.”
As always, I write about a given topic here because several different people asked me for similar advice. Which is to say, I’m hoping this post will carry at least some meaning for a variety of people.
Coming up with topics is a hassle, and saying the same thing over and over is also a hassle, so this is an extremely efficient operation. Lol
On the downsides of getting a patent
Concretely, the downsides of getting a patent are as follows.
1. In the process of filing, your company’s broad strategy gets exposed to other companies 2. It costs money 3. It eats up time 4. What matters isn’t getting the patent, it’s being able to fight it out in a dispute (which takes financial strength and know-how) 5. Software patents in particular are hard to prove infringement on
Let me go through these in order below.
1. In the process of filing, your company’s broad strategy gets exposed to other companies
For example, sites like this exist. iPhone-Mania It’s a site that tracks Apple’s patent filings and speculates about them.
Of course patent information concerns “a product that may or may not ship,” and moreover the “seed” of that product. But in the case of things like utility models, information that lets people reasonably picture the actual product often leaks out, so in many cases you can tell roughly where a company’s interest (or target) lies.
A similar story applies to radio equipment filings. With the FCC and similar bodies, once a radio filing is made and the product is cleared for sale, the information gets disclosed on their website. Looking at that, you can predict that some rumored product is probably about to launch. In other words, to gain a public benefit you have to disclose a certain amount of information, and depending on who’s receiving it, that information can be something they’re practically drooling over.
2. It costs money
Before filing, you need to research similar existing patents and work out a strategy with a specialist (a patent attorney) on how to narrow or broaden your claims. Naturally, this costs money. When you file, you need a patent attorney to prepare the documents. Naturally, this costs money. Filing and registration themselves cost money too. And maintaining the patent quietly costs money as well.
A company developing an extremely high-unit-price product, or a product it can sell in very large volumes, might think that’s not a big amount relative to the whole. A large company that already sets aside an annual patent budget might even think it actually wants to increase its patent count. But for an organization like an early-stage startup, it’s not cheap enough to say “let’s get a patent first” or “well, let’s just grab as many patents as we can for now.”
3. It eats up time
This is especially a startup problem. Not enough people, not enough money, and not enough time — that’s a startup. There’s no time to spend on anything beyond what’s truly necessary. What matters is judging for yourself, from zero, whether something is truly necessary, rather than doing it because someone else said so.
Looked at that way, in what scenes does getting a patent actually rise to being “one of the top priorities worth spending time on even at a cost”? Just to be clear, there are of course plenty of cases where the judgment does come out as “this is necessary.” I’m not saying don’t file patents.
4. What matters isn’t getting the patent, it’s being able to fight it out in a dispute (which takes financial strength and know-how)
This one is dead serious. Holding a patent isn’t the end of the story, happily ever after. If someone infringes it, you have to sue them. You, yourself. People loosely believe that merely holding a patent exerts some deterrent effect, but the world isn’t nearly that well-behaved. Even when a design is so obviously yours that anyone could see it, some people will attack it aggressively anyway. If you’re seen from the outside as someone who probably doesn’t have the stamina to sue even if infringed, then that patent means nothing at all.
5. Software patents in particular are hard to prove infringement on
The basic rule of damages claims is that “the burden of proof lies with the plaintiff.” Strictly speaking this is very difficult: it’s unclear how much the plaintiff actually knows about the defendant, and internal information isn’t handed over. Even so, you spend money, spend effort, gather evidence, finally file suit, and only then does the dispute actually begin. I’m not a professional, so I don’t know exactly how much evidence you need to assemble, but as an engineer I understand very well how hard it is to gather that kind of information. For a circuit patent, getting hold of the other party’s schematic would settle things in one shot, but that’s rarely so easy. For a mechanical structure patent, you can tell at a glance that something is “similar,” but if the other side argues differences in the materials they used or their own particular characteristics, it gets very thorny. And when it comes to the internals of analysis or software, it’s extremely difficult. It’s impossible to judge from the outside, and making an accusation based on an app’s behavior is also tough. The usual approach people imagine is something like feeding in the same parameters and getting the exact same result, but it’s unlikely the other side will grant you that much latitude. I don’t know case law well, but I do know at least this much: software patent infringement suits often end up in a muddle.
Something more important than obsessing over the patent race
So far I’ve laid out the headaches of getting a patent and raised the question of whether you really need this. Let me close with a different angle.
Startups set all kinds of goals, but it’s extremely rare for someone to be developing a product in order to win or lose a patent lawsuit. Everyone is presumably sweating through their daily development work because they want to put a good product or service out into the world.
For example, a friend of mine recently introduced an interesting article. It was about how AMD manages to go up against the giant Intel. https://jp.quora.com/AMD-ha-naze-shikin-men-de-attouteki-ni-masaru-to-omoi-wareru-Intel-wo-ryouga-suru-CPU-wo-kaihatsu-dekiru-node-shou-ka/answers/207102983?ch=10&share=3c0a5c10&srid=7Ndeg&fbclid=IwAR09Ss1iTQaBU3ds-454cYl5XlHK0ymwAWxfW1ziYOiCh8YaP-RiVR8lfUs The gist, I think, is that if you have excellent engineers, there’s a chance somewhere even if you’re overwhelmingly disadvantaged financially. For a startup, there’s never any guaranteed certainty of winning — isn’t it fair to say that “there’s a fighting chance” is enough? I do this myself sometimes too, so I have a bit of self-reflection to do here, but when a young team member brings me an idea, I sometimes smugly ask, “Can that idea beat some Chinese company even if they throw $100 million and 100 engineers at it?” Naturally, investors and mentors like me aren’t actually interested in the answer to the question itself — what we want to know is what kind of person answers something like that. So there’s no single correct answer; there are plenty, such as:
**- Just sprint ahead on first-mover advantage
- Defend entirely through patents
- Right now all we have is first-mover advantage, but we have a team capable of continually creating technology with an edge over competitors going forward
- Carve out a unique position through design or content, an angle different from other companies
- Execute fast and go for a buyout**
None of these are wrong. What matters is whether that answer fits the entrepreneur themselves. Answers like the ones above are the kind of thing you can find in practically any startup how-to book, so anyone can say them out loud. What matters is that if what someone says seems to match who they actually are, investors can watch with some peace of mind.
I want you to choose a patent strategy that fits you and your company
Since strategy differs from person to person, just choose the one that fits you. Someone who puts on a brave front with newly learned patent jargon, saying “Our patent defenses are airtight!”, is far less trustworthy than someone who just says plainly, “Honestly it’s too much hassle, so we basically want to go open source. Giving back to society probably fits this business better.”
By the way, my position and opinions differ from those of investors, bank loan officers, and your boss, so don’t take everything here at face value. Lol
【YouTube video】
Getting a patent isn’t always the right answer
Originally published in Japanese at https://clazytech.com/2020/04/355/. Translated with LLM assistance and reviewed before publication.