Startup IP Due Diligence Checklist: 11 Records to Prepare Before Funding or a Sale
An intellectual-property diligence checklist for startups preparing for financing, a commercial partnership, or an acquisition, from ownership records to licenses and disputes.
Key takeaways
- Build one inventory connecting each important asset to its creator, owner, protection, license, product use, and supporting record.
- Fix chain-of-title gaps before a financing or sale creates deadline pressure and negotiating leverage shifts.
- Review inbound code, content, data, open-source software, and brand rights—not only patents and registrations.
- Make diligence repeatable by assigning owners, storing executed documents, and updating the file after major releases and transactions.
What intellectual-property records should a startup prepare for due diligence?
Prepare an IP inventory, founder and worker assignments, patent and trademark records, copyright and domain records, trade-secret controls, software and open-source reports, inbound and outbound licenses, collaboration agreements, dispute history, and a list of material gaps.
Investors, acquirers, lenders, partners, and major customers may all ask whether the company owns or can use the technology, content, data, and brands on which its business depends. A strong diligence file lets the company answer with executed documents and consistent records rather than assumptions.
The process should be proportionate. A software company may focus on code provenance, open-source obligations, contractor assignments, data rights, and trademarks. A biotech company may add patents, laboratory records, university licenses, sponsored research, and material-transfer restrictions.
1. Is there a complete inventory of material IP and technology?
List the patents, patent applications, trademarks, domains, copyrights, software, databases, designs, content, trade secrets, know-how, and licensed technology material to products and operations.
- Connect each asset to the product, service, market, or internal process it supports.
- Identify the legal owner, creator, registration or application number, status, jurisdiction, and renewal deadline.
- Flag assets owned by founders, affiliates, universities, prior employers, contractors, or other third parties.
- Record where supporting agreements, filings, source files, and technical documentation are stored.
2. Can the company prove its chain of title?
For each material asset, trace rights from the original creator or owner through every assignment, merger, name change, contribution, license, or other transfer to the current company.
Entity formation does not automatically transfer a founder’s pre-existing code, invention, domain, or brand. Likewise, paying for contractor work does not necessarily transfer every IP right. Review signed documents, legal names, dates, schedules of assets, and whether any recordation or corrective assignment is appropriate.
3. Have founders and employees assigned relevant inventions and IP?
Confirm that founders and employees signed agreements addressing confidentiality, inventions, work product, prior inventions, and continuing cooperation, and that the agreements match applicable law and actual employment dates.
- Collect executed—not draft—agreements for current and former personnel.
- Review prior-invention schedules and any exclusions or side letters.
- Check whether assignments were signed before or after important work was created.
- Confirm departure records address access, devices, repositories, and return of confidential information.
4. Do contractor and agency agreements transfer the rights the company expects?
Contractor files should identify deliverables, assign or license the necessary rights, address pre-existing materials and third-party components, protect confidential information, and permit the company’s intended use.
A work-made-for-hire clause alone may not cover every commissioned work. Review a present assignment of rights, moral-rights treatment where relevant, further-assurance obligations, portfolio rights, subcontractor terms, and the contractor’s authority to contribute all included material.
5. Are patent, trademark, copyright, and domain records current?
Confirm ownership, status, deadlines, prosecution history, maintenance, registrations, office actions, assignments, coexistence arrangements, domains, social handles, and any geographic gaps material to the business plan.
- Reconcile internal schedules with USPTO and Copyright Office records where applicable.
- Verify entity names and assignments after financings, conversions, mergers, or reorganizations.
- Calendar filing, renewal, maintenance, and response deadlines with a named owner.
- Document decisions not to pursue or maintain protection when they are material.
6. Can the startup show reasonable measures to protect trade secrets?
Document confidentiality agreements, access controls, labeling, security practices, repository permissions, offboarding, vendor controls, and policies that protect valuable nonpublic information.
A diligence response should identify the information the company treats as secret and the practical measures used to protect it. Avoid a generic claim that all company information is a trade secret. Focus on source code, algorithms, product plans, formulas, data sets, customer information, methods, and other assets that derive value from not being generally known.
7. Are software, open-source, data, and AI inputs documented?
Maintain a current record of third-party software, open-source components, models, training or evaluation data, APIs, developer tools, and content used in material products.
- Identify licenses, versions, notices, attribution, source-availability, copyleft, and commercial restrictions.
- Review repository history and contributor access for unexplained or copied code.
- Document rights to collect, use, combine, commercialize, and transfer important data sets.
- Track AI-generated or AI-assisted materials when provenance or downstream rights may matter.
8. What inbound, outbound, and collaboration agreements affect the IP?
Create schedules of licenses, assignments, university or research agreements, joint-development terms, strategic partnerships, customer grants, covenants, liens, and exclusivity restrictions.
Read the clauses that affect a transaction: change of control, assignment, sublicensing, field and territory limits, milestones, royalties, audit rights, improvements, source-code escrow, termination, and rights that survive. A license that supports the product today may require consent or change economics after a financing or acquisition.
9. Are claims, notices, and freedom-to-operate concerns organized?
Disclose threatened and pending claims, demand letters, takedowns, oppositions, office proceedings, audits, license disputes, employee claims, settlement obligations, and known infringement concerns.
Diligence usually asks not only about filed litigation but also about facts that could lead to a claim. Preserve privilege and coordinate the disclosure process carefully. Summaries should be accurate, tied to source documents, and reviewed before being placed in a broadly accessible data room.
10. Do customer and vendor contracts contain hidden IP commitments?
Review material agreements for ownership, broad licenses, exclusivity, most-favored terms, feedback rights, residuals, non-asserts, indemnities, source-code obligations, data rights, and restrictions on product development.
- Compare customer-specific terms with the standard form and product architecture.
- Identify promises that exceed rights received from vendors or licensors.
- Flag agreements that limit use of generalized know-how, data, or improvements.
- Quantify obligations that may affect transaction value or integration plans.
11. Is the diligence file complete, current, and access-controlled?
Use an indexed data room with final executed documents, consistent schedules, clear file names, limited access, privilege controls, and a written list of known gaps and remediation owners.
Do not upload every historical draft without a reason. A clean file should let a reviewer connect the IP inventory to ownership, registrations, licenses, product use, and disputes. Resolve easy gaps early and escalate material questions before representations, disclosure schedules, or deal deadlines are set.
When should a startup begin IP diligence preparation?
Begin before a transaction is imminent—ideally after formation, major hiring, significant contractor work, a key product release, or a material license—and refresh the file at regular intervals.
Early preparation reduces cost and prevents avoidable surprises. It also improves ordinary operations: the same records support customer negotiations, insurance, enforcement, financing, partnerships, and employee departures.
Authoritative resources
Questions answered
Frequently asked questions
What is IP due diligence for a startup?
IP due diligence is a structured review of the intellectual property and technology a startup owns, uses, licenses, protects, and may be obligated to share, along with the records that support those rights and risks.
What IP documents do investors usually request?
Requests commonly cover an IP inventory, founder and worker assignments, patent and trademark records, software and open-source use, material licenses, confidentiality protections, collaboration agreements, disputes, and schedules of gaps or restrictions.
Does a contractor automatically transfer copyright to a startup?
Not necessarily. Payment and a work-made-for-hire label may not transfer every right in every type of work. The agreement should expressly address ownership or licensing, pre-existing materials, third-party content, and further cooperation.
Why does open-source software matter in IP diligence?
Open-source licenses can impose attribution, notice, source-code, distribution, patent, or other conditions. The company should know which components and versions it uses and whether product practices comply with applicable licenses.
How often should a startup update its IP records?
Update after major product releases, hiring or departures, contractor projects, new licenses, financings, entity changes, IP filings, disputes, and at a regular interval appropriate for the pace of the business.
This article provides general information, not legal advice. Reading it or submitting the website form does not create an attorney-client relationship. Legal outcomes depend on the facts, contract language, and applicable law.
Continue the conversation