Khaled Azar 
IP assignment SaaS acquisition due diligence answers one hard question: does the company own every material line of code, design, trademark, domain, and invention the buyer expects to acquire? A deal can place 5,000 to 50,000 documents in the data room, but one missing contractor assignment can cloud the asset carrying most of the value.
Founders often mistake access for ownership. The repository sits in the company account. The contractor was paid. The employee built the feature at work. None of those facts replaces a clean chain of title. The buyer will trace ownership from each creator to the selling entity, then price any broken link.
Why IP Assignment SaaS Acquisition Due Diligence Matters
The buyer is not buying a repository. The buyer is buying the right to control what is inside it.
Chain of title is the documented path from the original creator to the company. That path can include founders, cofounders, employees, freelancers, agencies, offshore development shops, acquired teams, and prior entities. It also covers trademarks, domains, product designs, documentation, data sets, and proprietary processes.
The legal baseline is narrower than many founders assume. The U.S. Copyright Office says work created by an employee within the scope of employment can qualify as work made for hire. Commissioned work qualifies only in certain relationships and categories. Software from an independent contractor does not become company property merely because the company paid an invoice.
Patent rights require their own proof. The USPTO Manual of Patent Examining Procedure explains that a partial assignee transfers only the interest it holds, and all owners must act together in patent matters. A founder cannot promise a buyer full ownership when another inventor still holds part of the right.
Run the Seven Link Chain of Title Audit
I use a seller exercise called the Seven Link Chain of Title Audit. Start with the product as it exists today. Then identify every person or entity that created a material part of it. The audit is complete only when seven links match: creator, engagement, work, agreement, assignment, company entity, and current repository or registration.
| Link | Evidence to collect | Failure to flag |
|---|---|---|
| Creator | Contributor name and legal entity | Alias, agency subcontractor, departed founder |
| Engagement | Employment, MSA, SOW, or founder record | Work began before paperwork |
| Work | Repositories, modules, designs, marks, domains | No map from person to asset |
| Agreement | Signed agreement for the correct period | Unsigned template or wrong entity |
| Assignment | Present transfer of relevant IP rights | Confidentiality only or future promise |
| Company entity | Exact entity named as assignee | Founder, affiliate, or dissolved entity owns it |
| Current control | Repo owner and registration records | Agency account or former employee controls access |
This is different from an open source review. An open source license audit asks whether the company has permission to use third party code. The chain of title audit asks whether the company owns the original work it claims as proprietary. Buyers run both tests.
Current diligence guides confirm the scope. A June 2026 checklist from Harvey describes ownership and assignment as the place where many IP findings surface. A March 2026 IP diligence guide organizes the review across five evidence groups, including ownership, inbound rights, outbound rights, disputes, and operational controls. Your seller file should connect those groups rather than scatter them across folders.
Build the audit around contributors and assets, not document names. A folder of agreements is useless when nobody can show which agreement covers which code.
Find the Ownership Gaps Buyers Find First
The first gap is founder code created before incorporation. The company did not exist when the work was made, so it could not own the work at creation. The formation file needs a signed transfer from the founder to the company, with enough detail to cover the actual code and related rights.
The second gap is contractor work. Look beyond the master agreement. Some agreements protect confidential information but never assign work product. Some statements of work name the wrong customer entity. Some agencies use subcontractors without passing assignment duties through to them.
The third gap is a break in time. An employee may have signed an assignment six months after starting. A contractor may have completed version one under an old form, then signed a better form for version two. Map the signed dates against commit history. Buyers care about the uncovered period.
The fourth gap is a carveout. An employee may list prior libraries, frameworks, or side projects on an inventions schedule. If one of those assets entered the product, the company needs a valid license or assignment. Do not treat a blank or missing schedule as proof that nothing was excluded.
The fifth gap is the wrong entity. Early contracts may name the founder personally, an old LLC, a foreign affiliate, or an agency account. Buyers will compare the legal owner with the entity on the cap table and purchase agreement.
Access control provides supporting evidence, not title. Confirm the company owns the GitHub organization, cloud accounts, package registries, domains, trademark accounts, design files, and signing keys. This belongs beside the broader technical due diligence file, because a clean assignment with no operational control still creates closing risk.
Fix Missing IP Assignments Before the LOI
A fix made during a quiet preparation period looks routine. The same fix after exclusivity looks like distress.
Start with a gap schedule. Name the contributor, affected asset, missing proof, current relationship, jurisdiction, and proposed remedy. Rank each item by product importance and difficulty. Core code from an unreachable former contractor belongs at the top. A minor design file from a current agency belongs lower.
Then ask M&A and IP counsel to choose the remedy. The answer may be a confirmatory assignment, a new assignment, a license, a founder contribution agreement, a recordation, a release, or replacement of the affected work. Do not backdate documents. Do not ask a former contributor to sign language that misstates what happened.
In one recurring diligence pattern, the company had paid every developer and controlled the repository, but several early contractor files contained confidentiality terms without a clear transfer of code ownership. The founder had to reconstruct who built which modules, locate former contributors, and execute confirmatory assignments before buyer counsel completed its review. The lesson was not that the issue was impossible to fix. The lesson was that the buyer controlled the clock once the issue surfaced.
The timing matters because buyer diligence often lasts six to twelve weeks. A hard to reach former developer can consume a meaningful share of that window. If the fix becomes a closing condition, the buyer may delay, demand a special indemnity, increase escrow, exclude an asset, or reopen price.
That is why this work belongs before a live process. Add the chain of title schedule to your SaaS exit readiness review, then place executed proof in the M&A data room with a simple contributor index.
The creator, engagement, work, agreement, assignment, company entity, and current control should point to the same conclusion: the selling company owns the asset.
Package the proof so buyer counsel does not have to reconstruct company history. Include the asset schedule, contributor matrix, founder assignments, employee and contractor agreements, prior invention schedules, registrations, repository ownership, material licenses, and gap log. Separate signed documents from templates, label former contributors, and show which service period each agreement covers.
This article provides transaction preparation guidance, not legal advice. IP ownership rules vary by asset, contract, contributor status, and jurisdiction. Have qualified counsel review the audit and all remediation documents.
Frequently Asked Questions
Who owns software created by an independent contractor?
The contractor often owns the copyright unless a valid written agreement transfers it or the work fits a narrow work made for hire rule. The U.S. Copyright Office recognizes nine commissioned work categories, and ordinary custom software does not automatically qualify.
What IP documents do buyers request in SaaS due diligence?
Expect requests for founder, employee, contractor, and agency assignments, prior invention schedules, IP registrations, material licenses, disputes, repository ownership, and a contributor matrix. A focused IP request list commonly spans five groups: ownership, inbound rights, outbound rights, disputes, and operations.
Does paying a developer mean the company owns the code?
No. Payment proves the commercial engagement, not necessarily the transfer of copyright or invention rights. The company needs an enforceable ownership path from the developer to the correct company entity.
How long does IP due diligence take in a SaaS acquisition?
It usually runs inside the broader buyer diligence period, which a 2026 Harvey guide places at six to twelve weeks for many transactions. Missing signatures, former contributors, foreign jurisdictions, and disputed assets can extend that timeline.
Prove Ownership Before Buyers Set the Clock
If your SaaS was built across founders, employees, freelancers, or agencies, test the chain of title before buyer counsel turns a paperwork gap into negotiating pressure.