Over the past few months, I have answered the same question in several different forms. A founder builds something internal, useful, and maybe even a little clever, but never stops to ask whether it is protectable. The founder assumes patents are for products sold to customers, not tools used inside the company.
That assumption can cause valuable work to go unexamined. So I pulled together the questions I hear most often about software and artificial intelligence built inside a company and answered them in one place.
Please note before we start that nothing below predicts whether a particular invention will qualify for protection. Patentability depends on the claimed invention, the prior art, and the specific way the system works. These answers are intended to help you ask better questions.
We Built This Tool for Ourselves, Not to Sell. Can It Still Be Patented?
Potentially. Internal use does not, by itself, exclude an invention from patent protection.
Federal law identifies processes, machines, manufactures, compositions of matter, and improvements to them as statutory categories of potentially patentable subject matter. 35 USCS § 101. But fitting within a statutory category is only the beginning. The claimed invention must also satisfy other requirements, including novelty and nonobviousness.
For software, it is especially important to identify what the claims would actually cover. Merely implementing an abstract idea on a generic computer does not transform the idea into a patent-eligible invention. Alice Corp. Pty. Ltd. v. CLS Bank Int’l, 573 U.S. 208, 212 (2014). The analysis therefore focuses not simply on whether software is involved, but on whether the claimed system or method presents a specific technological solution rather than using a computer as a generic tool.
If your team built an internal system that changes how a computer processes data, improves a technological operation, or uses a specific technical architecture to solve a concrete problem, it may be worth evaluating. By contrast, automating a familiar business practice through conventional computer functions may face substantial eligibility difficulties.
The harder part is often recognizing the internal tool as an asset. Teams become accustomed to the systems they build and start thinking of them as merely “the thing we use.” That is exactly why internal technology can go unevaluated: nobody pauses to identify the potentially protectable contribution.
Does Adding AI Make Our Software More Patentable, or Less?
Neither, by itself. The presence of artificial intelligence does not decide the question.
Some founders assume that a product must be patentable because it uses AI. Others assume that using an existing model makes protection impossible. Both approaches skip the necessary analysis.
The relevant questions include what the inventors devised, whether the claimed subject matter is eligible, whether it was new when measured against the applicable prior art, and whether the differences would have been obvious to a person having ordinary skill in the relevant field. Federal patent law expressly makes nonobviousness a separate condition of patentability. 35 USCS § 103.
A team may have developed a particular training method, data-processing architecture, validation mechanism, or technical control over how model outputs are generated or used. Those details may matter. Simply instructing a generic computer or model to perform an abstract task is different from claiming a specific improvement in computer functionality or another technological process.
Calling an existing application programming interface does not automatically prevent protection, and building a custom model does not automatically establish it. The question remains: What did the inventors actually devise, and how does the claimed invention differ from what was already available?
One of Our Contractors Wrote Most of the Code. Do We Even Own It?
That depends on which rights are at issue and what was documented when the work was done.
Copyright in the source code, inventorship of a patentable invention, and ownership of the resulting patent rights are not the same thing. A contractor may write copyrightable code without being an inventor of every patent claim associated with the product. Conversely, a person who contributes to the conception of claimed subject matter may be an inventor even if someone else wrote most of the code.
Patent applications and patents may be assigned through a written instrument. 35 USCS § 261. Federal law nevertheless begins from the premise that rights in an invention belong to the inventor; even in the federally funded research context, ownership does not automatically vest in the contractor without a transfer of rights. Bd. of Trs. of the Leland Stanford Junior Univ. v. Roche Molecular Sys., 563 U.S. 776, 780 (2011).
The practical lesson is that “we paid for it” should not substitute for reviewing the agreement. Employment status, authorship, inventorship, assignment language, and the timing and execution of the documents can each matter.
An ownership gap may surface during due diligence, a financing round, an acquisition, or a dispute with a former contributor. Whether a particular company has a problem requires review of the agreements and the contributions made by the people involved.
A Competitor Just Launched Something Similar. Does That Mean We Waited Too Long?
Not necessarily, but it makes prompt evaluation important.
United States patent law measures prior art against the claimed invention’s effective filing date and recognizes certain earlier-filed patents and published applications as prior art. 35 USCS § 100. A competitor’s launch may also reveal publications, public uses, sales activity, or patent filings that require analysis.
The phrase “first to file” is useful shorthand, but it should not be treated as a complete legal rule for every dispute. What matters can include the effective filing dates, who invented the claimed subject matter, what disclosures occurred, whether an exception applies, and the degree of overlap between the competing technologies.
A similar launch therefore does not automatically close your filing window. It does mean that delay can create additional prior-art and ownership questions. The answer depends on what each party developed, what was disclosed or filed, when those events occurred, and how the potential patent claims would be written.
An Acquirer Asked What IP We Have. We Don’t Have Patents. Does That Hurt Us?
It can affect the discussion, but the absence of patents is not automatically fatal to a transaction.
A company may have value in its copyrights, trade secrets, trademarks, contractual rights, data, technical know-how, or other assets. It may also have sound business reasons for deciding not to pursue patents.
What creates a harder diligence conversation is not always the absence of patents. It is the absence of a deliberate review. We evaluated the technology and chose a different protection strategy communicates something different from we never considered whether we had anything protectable.
If your team has never evaluated its internal systems, AI architecture, or proprietary processes, that is a gap that can still be addressed. It is usually easier to do so before an acquisition process begins than while responding to an acquirer’s diligence requests.
Where This Leaves You
This is not an argument for filing a patent application on everything your team has built. It is an argument against allowing potentially valuable work to go unexamined because nobody thought to ask.
A reasonable first step is an internal review of the systems, models, and processes the company has developed. Ask which ones solve a problem differently from what came before, who contributed to them, what has been disclosed, and what agreements govern ownership.
You do not need a final answer on the first day. You need to stop assuming the answer is no by default.
If you have been meaning to hold that conversation, we would be glad to discuss what your team has built and what may deserve a closer look. The Garcia-Zamor Law Firm serves as general counsel and fractional general counsel for businesses and innovators, helping protect business operations and intellectual property. Contact the firm through its website or at (410) 531-9853.
