When a founder leaves with the prototype: what to do first
Secure the repository, the cloud drive and any deployment keys before speaking to the departing founder. Check the founders' agreement or employment contract for an assignment clause; without one, ownership may sit with the individual, not the company. Notify the remaining co-founders and freeze shared credentials the same day. That gap widens with every day of delay.
The legal basis
Software making up a prototype is protected as a literary work under Directive 2009/24/EC. The directive sets originality — the author's own intellectual creation — as the sole test, regardless of how polished the code is. It applies whether the prototype is a finished product or three files and a README.
Where the prototype also carries a structured dataset, a separate sui generis right arises under Directive 96/9/EC, protecting the substantial investment made in compiling that data. This right is independent of any copyright in the underlying schema, and it can survive even where the code itself is too basic to qualify for protection on its own.
Neither directive names a default owner. That question is answered by the employment or commissioning relationship in place at the moment the code or data was created, and by whatever assignment clause the parties signed, or failed to sign. The two directives set a protection floor across the EU; who holds the right on day one is a matter the harmonised rules leave open.
What changes once the founder is gone
The prototype's authorship record starts decaying the moment access stays open. Commit logs, cloud timestamps and internal messages are often the only evidence of who wrote what, and they get overwritten, archived or deleted the longer an ex-founder keeps a live account. Any later argument about ownership becomes harder to prove with each week of inactivity, no matter what the founders' agreement says on paper.
Three risks move at the same time. The evidentiary risk grows as logs age. The operational risk grows if the company still depends on infrastructure the departing founder controls personally. The commercial risk grows fastest of all: an investor doing diligence on the next round will ask for a clean assignment chain, and an open dispute over the core codebase can stall a term sheet regardless of how the underlying claim eventually resolves.
What to do, in order
The sequence below assumes the founder has already left with a working copy. Steps 1 and 2 happen the same day; the rest follow within the week.
| Step | Action | Who does it |
|---|---|---|
| 1 | Revoke repository, cloud and deployment access within hours | IT lead or CTO |
| 2 | Pull the founders' agreement, employment contract or contractor agreement and locate the assignment clause | Company secretary or admin |
| 3 | Send a written notice asserting ownership and demanding return of all copies | Legal counsel |
| 4 | Inventory every location where the prototype exists: laptops, personal cloud, third-party pipelines | Operations lead |
| 5 | Decide whether to pursue return only, or also damages, before copies are altered | Board or managing director |
| 6 | Check whether any other contractor touched the code without a signed assignment | Legal counsel |
Step 3 matters more than its position in the list suggests. A written notice, sent early and kept factual, becomes the document a court later uses to fix the date the company knew about the dispute — which affects how urgency is judged if interim relief is ever needed.
Who decides, and on what evidence
Ownership disputes over a prototype are decided by the competent civil court in the company's home jurisdiction, not by a regulator or an internal vote. Where the founders' agreement contains a jurisdiction or arbitration clause, that clause usually controls the forum instead of the default rule.
The court looks first at who created the code or the database as a matter of fact: employment status at the time, commit history, and any written assignment. Titles and investment size come second. Interim relief, such as an order to preserve or return copies, is available only where urgency is documented; a claim filed months after the departure rarely qualifies for it, because the delay itself undercuts the claim of urgency.
Three scenarios
- If the founder was an employee under a contract with a standard assignment clause, ownership already sits with the company. The task is enforcement and return, not proving who owns what.
- If part of the build was routed through a subcontractor, the assignment chain may already have a gap that predates the departure; see The outsourcing provider subcontracts abroad technology contract for how that changes the trail.
- If the prototype carries token reserves or a treasury component, evidencing what actually exists becomes a separate track; see When reserves must be evidenced in detail.
- If the founder remains a shareholder but simply refuses to hand back copies, the dispute often turns on leverage rather than law: a shareholder resolution or a buy-out clause can resolve it faster than litigation, provided the cap table gives the board the votes to act.
What this page does not resolve
This page does not value the prototype, and it does not replace a criminal complaint if the taking involved theft of physical hardware rather than a copy of code. It also does not cover the separate negotiation over equity or a severance package, which usually runs alongside the ownership question but follows its own timetable.
If the founder has already moved funds or assets before returning the prototype, tracing them sits outside ownership law entirely; Asset in Estonia in practice sets out that route.
Where the founder becomes uncooperative and enforcement stalls, Debtor in Estonia and the deadline covers what happens next.
Verified
Checked against the sources below on 5 June 2025. Primary sources: Directive 2009/24/EC of the European Parliament and of the Council of 23 April 2009 on the legal protection of computer programs (codified version), and Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases. Both set EU-wide minimum protection; national law fills in who owns the right by default.
Frequently asked questions
What is the first step when a founder leaves with the prototype?
Revoke access to the repository, cloud storage and deployment keys the same day, before any conversation about ownership takes place. Evidence decays fastest in the first hours after departure, and access left open is the single biggest reason ownership claims get harder to prove later.
Which deadline is already running?
The clock on evidence, not on a filing date. Commit logs and message threads get deleted, overwritten or archived the longer the departing founder keeps live access, and that erosion starts immediately, not after a formal notice is sent. There is no statutory countdown here; the pressure is practical, not procedural.
Who decides, and on what evidence?
The competent civil court in the company's home jurisdiction decides, based on who created the code or database as a matter of fact — employment status at the time, commit history and any written assignment — rather than on titles or who negotiated the loudest at the cap table.
Related publications
A closely related gap appears with contractors rather than founders, where nothing was ever signed at all; see When freelancers signed nothing in practice for that route.