12960 Linden Church Road
Clarksville, Maryland 21029

What Does an Acquirer Ask When It Wants to Know What Your Software Company Actually Owns?

Nov 18, 2026

Picture this call. A potential buyer has read your deck and likes the numbers. Then someone on the buyer’s side asks, Can you walk us through who wrote the core of your product and what they signed when they did?

If your answer is quick and clean, the conversation moves on. If it takes a week of digging through old emails, the conversation changes. The buyer is no longer just pricing your revenue. The buyer is also pricing what remains uncertain.

For a software company with 10 to 75 employees and $1.5 million to $3 million in revenue, the code and the methods behind it may be among the company’s most important assets. A buyer will want to understand them. I would rather you understand them first.

Here is how I would expect the questions to develop from the buyer’s side and what your answers may need to show.

What Exactly Did You Build?

This sounds easy. It usually is not.

A buyer wants to know what the product does, but also which parts your company developed and what may be different from what existed before. We have a platform for logistics scheduling tells the buyer very little. We built a scheduling engine that rebalances routes as orders change, and here is how it works gives the buyer something concrete to evaluate.

That second kind of answer matters for valuation. A product that can be described as a specific technical solution to a specific problem is easier to assess than one described as a collection of features. It also helps the buyer understand what a competitor would have to reproduce to match the product.

I came to software from mechanical engineering and equipment patents, so this is the way I tend to look at it. When someone shows me something the company has built, I ask what problem it solves, how the workflow operates, and what may be different from earlier approaches. The same questions apply to an internal tool, an artificial-intelligence-driven feature, or a data-processing method. The presence of artificial intelligence does not answer them. What the team actually devised does.

Please note that being different is not, by itself, enough to establish patent protection. Federal patent law separately considers whether the claimed invention falls within patent-eligible subject matter and whether it satisfies other requirements. A generic computer implementation does not transform an abstract idea into a patent-eligible invention. 35 USCS § 101. Alice Corp. Pty. Ltd. v. CLS Bank Int’l, 573 U.S. 208, 212 (2014).

If you cannot write a clear description of the product in a page or two, a buyer will notice. So will anyone you later ask to help evaluate or protect the work.

Who Built It, and What Did They Sign?

This is where many conversations slow down.

Suppose a company’s recommendation engine was built over two years by two founders, three employees, and a contract engineer who left long ago. The product works. Customers pay for it. But when the buyer asks for paperwork showing that the company owns each piece, the team finds agreements for some contributors and nothing for others.

How that situation turns out depends on the facts and the documents. Under federal copyright law, copyright generally begins with the author. For a qualifying work made for hire, however, the employer or other qualifying party is treated as the author and generally owns the copyright unless the parties signed a written agreement providing otherwise. 17 USCS § 201.

The phrase “work made for hire” is narrower than many businesses assume. When deciding whether someone was an employee for this purpose, courts apply common-law agency principles. A contractor’s work qualifies as a commissioned work made for hire only when it falls within one of the statutory categories and the parties expressly agree in a signed writing that it will be treated that way. 17 USCS § 101. Cmty. for Creative Non-Violence v. Reid, 490 U.S. 730, 740 (1989).

That means paying an outside developer does not necessarily transfer the copyright in the developer’s work. A transfer of copyright ownership generally must be in writing and signed by the owner of the rights being transferred or the owner’s authorized agent. 17 USCS § 204.

A contractor relationship is therefore not the same as an employment relationship, and a signed agreement is useful only if its language actually covers the work at issue. Ownership of software should not be assumed. It should be documented.

This is where business law and intellectual property meet. Contractor agreements, employment agreements, and founder documents are contracts, but they also help determine who holds the rights in what the company is selling. When those documents are written with the product in mind, the diligence conversation is usually much shorter.

What Is Protected, and How?

The buyer’s next question is what prevents someone else from copying or recreating what the company has built.

A patent application is one possible answer, but it is not the only one. Depending on the product and the company’s goals, several forms of protection may work together.

  • Confidentiality can protect nonpublic logic, methods, data practices, and business information when the company takes appropriate steps to keep that information private and uses suitable agreements with employees, contractors, partners, and other recipients.
  • Copyright can protect original expression in software, including protectable aspects of the code as written. Copyright ownership, however, leads directly back to the question of who created the code and whether the company obtained the necessary rights.
  • Trademark protection may be relevant to the product name, company name, logo, or other source-identifying branding.
  • A patent application may be worth evaluating when the team has developed a new and useful technical process, machine, manufacture, composition of matter, or improvement. Federal law identifies those statutory categories, subject to the additional requirements and limitations of the Patent Act. 35 USCS § 101.

No single tool protects everything, and the right combination depends on what the software does, how it was developed, what has been disclosed, and what the company wants to accomplish.

On patents specifically, an application must describe a claimed invention rather than an unclaimed idea of “software” in general. The evaluation also extends beyond novelty. Even if an invention is not identically disclosed in the prior art, a patent may be unavailable if the claimed invention as a whole would have been obvious to a person having ordinary skill in the relevant field before its effective filing date. 35 USCS § 103.

Public activity can matter as well. Federal law treats certain patents, printed publications, public uses, sales, and other public availability before the effective filing date as prior art, subject to statutory exceptions. 35 USCS § 102.

Please note that a public demonstration, launch, presentation, or online description does not produce the same result in every situation. What was disclosed, who disclosed it, when it occurred, and the countries in which protection may be sought can all matter. The safest course is to evaluate a planned technical disclosure before it occurs rather than assume that an opportunity to file will remain open afterward.

How to Get Your Answers Ready

You do not need a formal data room to start. A short written account of what the company built can explain the problem the product solves, how the product operates, and what the team believes is different from earlier approaches. Write it for a smart reader outside engineering.

A separate ownership account can identify each founder, employee, contractor, and outside developer who contributed to the core product, together with the agreement that person signed. The purpose is not simply to collect names. It is to connect each important contribution to the document that establishes the company’s rights.

The same file can include a dated history of demonstrations, launches, presentations, publications, and other disclosures concerning how the product works. Blanks in that history are useful. Each one tells you what to investigate first, and it is far better to find those blanks on your own timeline than in the middle of someone else’s due diligence.

Why a Clear Answer Changes the Conversation

A buyer who receives crisp answers about the product, its ownership, and its protection can evaluate what the company is selling. A buyer who receives vague answers must account for uncertainty, and uncertainty is difficult to value.

These subjects also depend on one another. The description of what the company built helps identify what may be worth protecting. The paperwork helps show who owns it. The disclosure history helps determine which options may remain available. When business law and intellectual property are reviewed together, those connections can be addressed on the first pass instead of surfacing one at a time.

A Measured Next Step

This week, write the first page: what your company built, in plain language, and how it works. It is the page a buyer, investor, and attorney is likely to ask for first.

If you would like a second set of eyes on how the pieces line up, including what your team built, who owns it, and what may be worth protecting, let’s talk. Tell us where you are, and we will start from there.

The Garcia-Zamor Law Firm serves as general counsel and fractional general counsel for businesses and high-end innovators, protecting both business operations and intellectual property. Ruy Garcia-Zamor has more than 25 years of experience in patents, trademarks, intellectual property, and business strategy and is a registered patent attorney with the United States Patent and Trademark Office. Elliott Alderman has more than 40 years of experience in intellectual property and business guidance. Claudia Castillo has decades of experience in business law, with a focus on employment matters. Amulya Annasamudram focuses on patents and intellectual property and is a registered patent attorney with the United States Patent and Trademark Office. Call (410) 531-9853.