“The company owns the technology” is a conclusion. During financing or acquisition diligence, a startup must prove it.
That proof rarely sits in one agreement. It runs through the people who designed the product, the dates they did the work, the contracts they signed, the repositories they used, the third-party components they incorporated, and the entity that owns the relevant patents, copyrights, trademarks, domains, data rights, and accounts.
A signed invention-assignment form is important. It is not a substitute for testing the startup’s actual chain of title.
A startup IP ownership review follows each core asset from creation or acquisition through the company’s present rights and control.
Begin with an asset map, not a form search
The first question is what the business depends on. For a software company, the answer may include source code, model weights, training and evaluation data, product designs, technical documentation, deployment scripts, domain names, social accounts, and confidential know-how. A life sciences company may add patent rights, laboratory notebooks, biological materials, licenses, and sponsored-research results. A consumer company may depend heavily on trademarks, creative assets, customer data, and manufacturing specifications.
List those assets and identify who created, acquired, licensed, or controls each one. Then match the evidence to the asset. Copyright ownership may depend on authorship, work-made-for-hire rules, and signed transfers. Patent rights turn on inventorship and written assignments. Trademark ownership depends on use, registration records, and transfers that carry the associated goodwill. Contract rights may limit whether licensed technology or data can be assigned to an acquirer.
The U.S. Copyright Act generally vests initial ownership in the author. The work-made-for-hire doctrine can change that result, but its treatment of employees and qualifying commissioned works is specific. A copyright transfer generally must be in a signed writing. Paying an independent developer’s invoice, standing alone, does not transfer all copyright in the delivered code.
Founder work often predates the company
Many products begin before incorporation. A founder may have written code personally, used a former employer’s laptop, developed an idea while employed elsewhere, or collaborated through an informal entity. Incorporating a Delaware company does not automatically move those assets into it.
The review should establish:
- when the relevant work was created and by whom;
- whether the creator was subject to another employer, consulting, university, accelerator, or grant agreement;
- which equipment, facilities, confidential information, and accounts were used;
- whether collaborators contributed protectable material;
- what the founder actually assigned to the company; and
- whether the company accepted and recorded the transfer.
A broad present-tense assignment is generally more useful than a promise to assign later, but wording alone cannot erase a third party’s existing rights. If a former employer or university may have a claim, the company should investigate the governing agreement and applicable law before making an unqualified ownership representation.
The same discipline applies to repositories and infrastructure. If the code sits in a founder’s personal account, the domain is registered personally, or production credentials depend on one person’s device, legal ownership and operational control may diverge. Transfer the account or asset where possible, document company control, and establish recovery and administrator access.
Contractors create a predictable break in the chain
Startups often treat a contractor agreement as procurement paperwork and discover later that it never assigned intellectual property. Common problems include a statement that deliverables are “work made for hire” without a fallback assignment, an assignment limited to final deliverables rather than underlying code and documentation, or no treatment of subcontractors and pre-existing tools.
For each developer, designer, scientist, agency, or consultant who touched a core asset, confirm:
- the correct legal party signed;
- the agreement was effective during the work;
- the assignment covers the relevant rights and deliverables;
- the contractor obtained matching rights from personnel and subcontractors;
- background technology is identified and properly licensed;
- confidentiality and return-of-material obligations apply; and
- further-assurances language supports later filings or recordation.
If the agreement is missing, a current confirmatory assignment may be appropriate. It should accurately describe the history and be signed now. Backdating the document creates evidence risk rather than fixing it.
Employee agreements must match the workforce
An employee form is only useful if every relevant employee signed the correct version at the right time. Compare the employee roster with executed confidentiality and invention-assignment agreements, including early hires, interns, part-time staff, international personnel, and employees who changed entities after a restructuring.
Local law matters. Some jurisdictions limit the inventions an employee can be required to assign or mandate specific notices. A U.S. parent’s form may not work for an employee of a foreign subsidiary. The company should use locally appropriate documentation while ensuring that rights ultimately reach the entity meant to own or license the technology.
The review should also reconcile departures. Confirm that access was terminated, company materials were returned, continuing obligations were acknowledged when appropriate, and any patent or registration cooperation can still be obtained.
University and sponsored work require their own analysis
A founder’s university affiliation is not automatically a problem, but it is not something to handle by assumption. Faculty, student, laboratory, grant, and sponsored-research policies can differ. Rights may depend on the person’s status, use of facilities, funding source, field of research, and contractual commitments.
Obtain the policies and agreements that applied when the work was performed. If the university owns or may own relevant rights, determine whether the startup needs an assignment, option, or license and whether the license contains diligence milestones, royalties, sublicensing restrictions, patent-cost obligations, or change-of-control provisions. A license can support the business, but it should not be described to investors as outright ownership.
Open-source software is a rights and compliance issue
Using open-source software does not mean the company lacks proprietary technology. It does mean the company should know what it uses and on which terms.
Build a current software bill of materials and connect packages to their licenses, versions, modifications, deployment method, and product use. Pay particular attention to copyleft and network-copyleft obligations, attribution and notice requirements, source-offer requirements, license incompatibilities, and components copied without reliable provenance. Also review code brought from prior projects and snippets obtained from forums or code-generation tools.
An automated scan is a starting point, not the conclusion. It can miss copied code, private dependencies, build artifacts, or operational use that changes the license analysis. The legal and engineering teams need a process for approving new components, preserving notices, responding to vulnerabilities, and documenting exceptions.
Veritas Global’s discussion of source-code license agreements addresses the separate question of how a company permits customers or partners to use code it owns or controls. Both sides matter: the company needs sufficient inbound rights to build the product and disciplined outbound terms that do not give away more than intended.
Diligence also tests data, brands, and contractual restrictions
Source code is rarely the entire product. The company should identify the legal basis for collecting, using, sharing, and retaining data; whether customer contracts allow the intended use; and whether acquired datasets carry consent, license, or deletion restrictions. An IP assignment cannot cure the unlawful or unauthorized use of personal or third-party data.
For trademarks and domains, compare the name used in commerce with registration records, domain registrants, social accounts, and any founder-owned entities. Patent and trademark assignments may also need to be recorded with the appropriate office. Confirm that filings name the correct owners and that prosecution deadlines are controlled by the company and its counsel.
Finally, review outbound contracts. Customer licenses, reseller agreements, strategic partnerships, development agreements, and covenants not to assert rights can narrow exclusivity or complicate a sale. An NDA may also contain provisions that affect later negotiations; Veritas Global’s analysis of NDA language in M&A discussions explains why labels do not capture every consequence.
Build a file that supports the ownership statement
A financing-ready IP file should contain an asset and inventor/author matrix, executed founder and workforce assignments, contractor and subcontractor documentation, university and grant materials, inbound licenses, open-source records, patent and trademark files, data-rights support, and evidence of company control over repositories and accounts.
Record exceptions rather than forcing a clean conclusion. A disclosed, bounded license or missing signature with a credible remediation plan is easier to evaluate than an absolute ownership statement that diligence disproves.
Veritas Global advises startups on IP chain-of-title reviews, invention assignments, technology licenses, open-source issues, and financing diligence. If the product has been built across founders, contractors, universities, or multiple entities, contact us before an investor asks the company to certify ownership.
Disclaimer: This article is provided for general informational purposes only and does not constitute legal, tax, employment, export-control, privacy, or other professional advice. It does not create an attorney-client relationship. Intellectual-property ownership and transfer requirements depend on the asset, jurisdiction, contracts, contributors, and facts. Readers should consult qualified advisers before acting.
