Source Code Ownership in SaaS Acquisitions: What the Asset Purchase Agreement Actually Transfers

Buying a SaaS company means buying its software, but software ownership is a legal construct that does not transfer automatically just because money changes hands. The asset purchase agreement (APA) is the document that defines exactly what the buyer receives, and vague drafting in that document can leave a buyer holding a product it does not fully own.

What "Owning" Software Actually Means

Source code is protected primarily by copyright. Copyright in software vests automatically in the author at the moment of creation — not in the company, unless the work qualifies as a "work made for hire" or was validly assigned. This distinction matters enormously in acquisitions.

A SaaS company typically has code written by:

• Full-time employees (usually covered by employment agreements containing assignment clauses)
• Independent contractors (covered only if a written assignment exists — work-for-hire doctrine generally does not apply to contractors outside enumerated statutory categories)
• Co-founders who may have contributed code before signing anything
• Open source projects incorporated into the codebase

If any of those contributors never signed a valid assignment, the company may not own what it thinks it owns — and the buyer inherits that problem.

What the APA Needs to Say

A well-drafted APA does not just say "seller transfers all intellectual property." It itemizes the transferred assets with enough specificity to leave no ambiguity.

Schedules and Exhibits

The APA should attach schedules that list:

• All registered IP (patents, copyrights, trademarks) by registration number
• Pending applications
• Unregistered IP, including identified source code repositories, proprietary algorithms, and trade secrets
• Domain names and social media handles
• Software licenses the seller holds (both inbound and outbound)

Generic language like "all IP used in the business" can be argued over. A numbered list is harder to dispute.

The Assignment Mechanics

A representation in the APA that the seller owns the IP is not the same as transferring it. The transfer requires a separate assignment instrument — often an IP Assignment Agreement executed at closing — that actually conveys the rights. For registered patents and patent applications, that assignment should be recorded with the USPTO to put the world on notice. For copyright, recordation with the Copyright Office is optional but useful.

Buyers should also require the seller to deliver assignment agreements from any individual contributors who were not covered by a prior employment or contractor agreement. This is sometimes called a "clean-up assignment" and is often negotiated as a closing condition.

Representations and Warranties the Buyer Should Demand

The IP representations in an APA are where the seller makes legally binding statements about what it actually owns. These should specifically cover:

• Chain of title: The seller has valid, unencumbered title to all listed IP
• No liens or encumbrances: The IP has not been pledged as collateral (check UCC filings)
• Contractor and employee assignments: All contributors have executed written assignments
• Open source compliance: The product does not incorporate open source code in a way that would impose license obligations on the buyer (such as copyleft provisions that could affect proprietary code)
• No pending or threatened IP claims: No third party has asserted ownership or infringement claims against the seller's IP
• No key-person dependencies: The seller does not rely on a license personal to a named individual that would not transfer

These representations are backed by indemnification obligations, which means the seller (or its principals) compensates the buyer if a representation turns out to be false. The scope of that indemnification — its cap, basket, and survival period — is heavily negotiated.

What Buyers Routinely Miss

Even sophisticated buyers sometimes overlook:

• Software-as-a-Service delivery: If the seller's product relies on third-party APIs or platform services, the buyer needs to confirm those agreements are assignable and that assignment does not require counterparty consent
• Employee invention assignment gaps: Some states, including California and Washington, limit what employers can require employees to assign; prior employees may retain rights to certain inventions
• Data and the product: Customer data and trained model weights are not automatically part of an IP transfer; they require separate treatment under the APA and applicable privacy law
• License restrictions on resale: Inbound software licenses that the seller relies on to operate its product may prohibit assignment without the licensor's consent

Practical Takeaways

• Never rely on generic "all IP" language; require itemized schedules attached to the APA
• Confirm that a separate assignment instrument is executed and, for patents, recorded at the USPTO at or before closing
• Conduct a contributor audit before closing to identify anyone who wrote code without signing an assignment
• Review all inbound software licenses for anti-assignment clauses that could disrupt the product post-closing
• Check UCC filings against the seller to identify any security interests in IP that must be released at closing
• Negotiate indemnification provisions that survive closing long enough to surface title defects, which often take time to appear

This guide is general education, not legal advice, and does not create an attorney–client relationship. For your specific situation, talk to a registered patent attorney.