IP Protection Checklist for Startups Raising Series A: What Investors Check Before Signing

Series A due diligence has changed. Five years ago, IP review was often a light-touch process — a quick look at whether there were obvious ownership disputes or blocking patents. Today, institutional investors and their counsel run structured IP audits before term sheets are issued, not after. The reason is straightforward: post-investment IP disputes are expensive, distracting, and in the worst cases existential. The checks that used to happen at legal close now happen before the lead investor commits.

For founders, this shift means that IP preparation is now part of fundraising preparation — not a downstream legal task. A startup that enters a Series A process with documentation gaps will slow the process, invite renegotiation, or lose the deal. A startup that enters with a clean, documented IP trail moves faster, builds investor confidence, and commands better terms.

This post sets out the ten items that institutional investors and their IP counsel check most consistently, explains what each one requires, and identifies where qualified cryptographic timestamping fits in the preparation process.

Item 1: IP Ownership Chain — Founders and Early Employees

The most common and most serious IP problem investors find in early-stage companies is ambiguous ownership of foundational IP. The specific scenario: a founder or early employee wrote significant code, designed core product elements, or developed the core methodology before employment agreements or invention assignment agreements were in place. That work may not legally belong to the company.

Investors check: Do all founders have executed IP assignment agreements assigning pre-formation work to the company? Do all employees have invention assignment clauses in their employment contracts? Were contractors engaged under agreements that transferred IP to the company (not just licensed it)?

Preparation: Audit every contribution to the company's core IP assets. Trace each contribution to a signed agreement. Where gaps exist — prior to employment or contractor engagement — execute retroactive assignment agreements. Where the founder is also a co-inventor on a patent application, confirm the assignment is recorded with the patent office. This is a legal task; involve your counsel. The timestamp record (Item 6 below) supports this by establishing when each contribution was created, which helps map contributions to the correct agreement.

Item 2: Contractor and Freelancer IP

A specific variant of Item 1 that deserves separate treatment: work performed by contractors and freelancers under arrangements that did not include an explicit IP transfer. In many jurisdictions, including Switzerland, the UK, and Germany, the default rule for contractor-created works is that the contractor retains copyright unless the contract explicitly transfers it. A work-for-hire assumption — common in the US — does not apply in these jurisdictions.

Investors check: Are there contractors who contributed to the product without executing IP assignment agreements? Is there a risk that a contractor holds copyright in a material component of the product?

Preparation: Identify every contractor or freelancer who contributed to the current product. Review their agreements. Where assignment was not included, execute supplemental assignment agreements. Retain signed copies in your IP register. If a contractor cannot be located or refuses to sign, take legal advice on the exposure before the due diligence process begins — do not let investors discover this gap during their review.

Item 3: Open-Source Licence Compliance

Open-source code is present in almost every software product. Most open-source licences are permissive (MIT, Apache 2.0, BSD) — they allow commercial use with attribution requirements. Some are copyleft (GPL, AGPL) — they require that any product incorporating the code be released under the same licence, which can create significant commercial problems for proprietary software products.

Investors check: Has the company conducted an open-source licence audit? Are there any copyleft components in the core product? Are attribution requirements being met? Is there a documented policy for approving new open-source dependencies?

Preparation: Run an automated licence audit using tools such as FOSSA, Black Duck, or similar. Document the results. Resolve any copyleft contamination issues before the process. Establish a written policy for open-source usage going forward. Provide the audit report to investors as part of the data room — proactive disclosure of a clean audit is a positive signal.

Item 4: Trade Secret Identification and Protection Measures

For most software and technology companies, trade secrets are commercially more important than patents. Algorithms, model architectures, training datasets, pricing models, customer analytics, and product roadmaps are all potentially trade secret — but only if the company takes reasonable steps to maintain their secrecy. Without those steps, trade secret protection does not exist regardless of commercial sensitivity.

Investors check: Has the company identified its trade secrets? Are there access controls limiting exposure to need-to-know personnel? Are NDAs in place with all parties who have access? Are confidential documents labelled as such? Is there a trade secret policy?

Preparation: Document your trade secrets in a register. Implement access controls appropriate to the sensitivity of each asset. Ensure NDAs with employees, contractors, investors, and advisers cover the relevant assets explicitly. Label confidential materials. Timestamp the trade secret assets (see Item 6) to establish chronology. For a detailed discussion of trade secret protection, see our post on Trade Secret vs. Copyright: Which IP Protection Is Right for Your Business.

Item 5: Patent Freedom to Operate

Even if the startup does not hold patents, its product may infringe existing patents held by third parties. Investors in capital-intensive hardware, biotech, medtech, and some software sectors now routinely require a freedom-to-operate (FTO) analysis before closing. In software, the analysis is more targeted — focused on any proprietary claims in the product's core innovation that might overlap with known patent thickets.

Investors check: Has the company conducted a patent search or FTO analysis? Are there identified blocking patents? Does the company have a plan to design around, license, or challenge any blocking patents?

Preparation: Engage patent counsel to conduct at least a preliminary FTO analysis for the core product innovation. Identify any relevant pending applications from competitors. If there are blocking patents, identify mitigation options. Document the analysis in the data room. This is particularly important if the company is seeking to expand into markets where patent enforcement is active (US, DE, JP).

Item 6: IP Timestamp and Prior Art Trail

This is the item that has grown in importance most rapidly over the last three years, driven by disputes in AI, software, and design-intensive sectors. Investors — and their acquisition counsel — want to see evidence that the company's core IP was created when and by whom the company claims. Not a git commit history that the company controls. Not an internal version management system. An independent, immutable record.

Investors check: Is there a cryptographically sealed record of the development history of core IP assets? Can the company demonstrate that its product was created before a competitor's priority date? Is the seal from a Qualified Trust Service Provider (QTSP) that carries the eIDAS or ZertES legal presumption?

Preparation: Seal key IP milestones using a QTSP-backed service. Swiss Trust Layer's World Court Proof e-Seal, issued via Swisscom Trust Services (accredited under both ZertES SR 943.03 and eIDAS Regulation No. 910/2014 Article 41), provides seals that carry a statutory presumption of accuracy of the timestamp and integrity of the sealed data. The seal covers a cryptographic hash of the file — no confidential information needs to be disclosed in the seal — and is publicly verifiable by any investor or counsel without requiring account access.

The minimum viable trail for a Series A: a sealed version of the initial technical specification or design document, sealed versions of each major release or architectural milestone, sealed versions of training datasets if AI is core to the product, and sealed co-founder IP assignment agreements. For more on what the seal proves, see our post on Intellectual Property Certificate: What It Proves.

Item 7: Domain Names, Trademarks, and Brand IP

Investors check whether the company owns the domain names it uses commercially, has registered or applied for trademark protection in key markets, and does not infringe existing trademarks in its target markets. Brand IP is often neglected by technical founders and becomes a diligence issue when a geographic expansion is planned as part of the Series A use of funds.

Investors check: Is the company's brand name available as a trademark in the US, EU, UK, and key expansion markets? Has the company filed trademark applications? Does the company own all relevant domains?

Preparation: Conduct trademark availability searches in all target markets as early as possible — ideally before committing to a brand name, certainly before raising. File trademark applications in the jurisdictions where you have or plan to have customers. Transfer domain registrations to the company (not a personal account). Document all filings in the IP register.

Item 8: Third-Party IP in the Product

Beyond open-source code, many products incorporate third-party content, data, models, or APIs. Stock imagery, licensed fonts, data licences, API terms of service, and third-party model licences all carry restrictions that may affect the product's commercialisation or create compliance obligations.

Investors check: Is there a register of all third-party IP in the product? Are all licences current and appropriate for the product's commercial use? Are there any terms that restrict the company's ability to license, sell, or transfer the product?

Preparation: Maintain a register of all third-party IP incorporated in the product, including the licence type, the licence term, and any commercial use restrictions. Renew licences before they expire. Review API terms of service against the product's use case — unpaid or developer plans often prohibit commercial use. Confirm that data licences permit the use you are making of the data.

Item 9: Employee Departure and IP Contamination Risk

When employees leave — particularly engineers, researchers, and product managers with access to core IP — they carry knowledge with them. If a former employee joins a competitor and that competitor shortly afterwards releases a product with similar functionality, the question of contamination arises. Investors want to see that the company has protocols for managing this risk.

Investors check: Is there an IP exit procedure for departing employees? Are departure interviews conducted? Are confidentiality and non-solicitation obligations enforced? Has there been any IP dispute with a former employee?

Preparation: Implement a documented off-boarding checklist that includes return of equipment, confirmation of data deletion, reminder of ongoing confidentiality obligations, and a brief interview documenting what IP the employee worked on. Record the exit procedure for each departure. If a dispute has occurred or is threatened, disclose it proactively in the data room with a summary of the company's position.

Item 10: Data IP and Privacy Compliance

For any product that processes user data, investor IP review now overlaps significantly with regulatory compliance review. The data a company collects, the models it trains on user data, and the analytics it derives from customer behaviour may all be commercially valuable IP assets — and they are also regulated assets under the Swiss Federal Act on Data Protection (nFADP), the EU General Data Protection Regulation (GDPR), and equivalent laws in target markets.

Investors check: Does the company have a documented data processing inventory? Are data licences and privacy policies consistent with how the data is actually used? Are there regulatory exposures in planned expansion markets that affect the data strategy?

Preparation: Build a data processing inventory that maps each category of data collected to its legal basis, its use, and the applicable regulatory framework. Align the privacy policy with actual practice. Take advice on the data implications of the expansion markets listed in the investment pitch — particularly India, the US, and any Middle Eastern markets. Swiss Trust Layer's Azure Blob storage in the Switzerland region supports data residency requirements for EU and Swiss regulatory compliance — a point relevant to any company using the sealing service for data assets.

Preparing the IP Data Room

Across all ten items, the common thread is documentation. The legal protections may exist or be creatable; the question is whether you can demonstrate them when a professional due diligence team reviews your data room under time pressure.

A clean Series A IP data room contains: signed IP assignment agreements for all founders and early employees; contractor agreements with IP transfer clauses; open-source licence audit report; trade secret register with access control documentation; patent search or FTO analysis; QTSP-issued sealed IP milestone records; trademark registration certificates or pending application receipts; third-party IP licence register; data processing inventory; and employee departure records.

Building this documentation is a few weeks of work if started before the process. Rebuilding it under investor pressure during exclusivity is a different exercise entirely. The sealed IP records from Swiss Trust Layer are verifiable in real time — an investor's counsel can check any seal at swisstrustlayer.com without requesting anything from the company, which is precisely the kind of independent verification that builds confidence.

For more context on the regulatory frameworks underpinning qualified seals, see our pages on eIDAS, ZertES, and compliance. For related IP protection guidance, see our posts on IP protection for software startups in Switzerland and what an IP certificate proves.

Start sealing your IP milestones with Swiss Trust Layer — QTSP-backed timestamps that investors and courts accept, from CHF 5 per document.