What Happens to Your Company’s IP If a Co-Founder Walks Away?

Every founding team has a version of this story. Two people sometimes three share a vision, split the work, and build something from scratch. Then, at some point, one of them leaves. Maybe the relationship soured. Maybe their priorities changed. Maybe they just got a better offer. Whatever the reason, the departure itself is rarely the hardest part. What comes after specifically, the question of who owns what is where startups quietly fall apart.

Intellectual property is the invisible architecture of a company. It’s the code, the brand, the product logic, the proprietary methods. When a co-founder walks, they take their memories and their LinkedIn profile. But do they also take their work?

The answer, almost always, depends on paperwork that most founders never signed.

The Default Is More Dangerous Than You Think

Without a formal IP assignment agreement, the legal default in the United States is that the person who creates something owns it. Not the company. Not the other founders. The creator.

This seems intuitive until you realize what it means in practice. If your co-founder wrote the originalcodebase, designed the core algorithm, or developed the trade secrets that your product is built on and there’s no document transferring that ownership to the company they may still own it. Legally. Even after they leave.

Courts have consistently upheld this position. The work was theirs. The company never formally acquired it. In the eyes of the law, the absence of documentation is not an oversight it’s the answer.

Investors know this. During due diligence, one of the first things a seriousVC will check is whether the founding team has properly assigned all IP to the company entity. If a departing co-founder’s contributions exist in a legal grey zone, the entire valuation of the company becomes uncertain. Deals have collapsed over exactly this.

What an IP Assignment Actually Does

An IP assignment agreement sometimes called an invention assignment agreement is a document that transfers ownership of any intellectual property created by a founder (or employee) to the company itself. It covers work done before the company was formally incorporated, work done after, and anything in between.

The scope matters enormously. A well-drafted agreement will specify that all work related to the company’s business including work done on personal time, using personal equipment belongs to the company. This sounds aggressive, and it sometimes is, but it exists for a reason. Startups are often built late at night, on personal laptops, before any formal structure exists. Without capturing that early-stage work, the company’s IP portfolio has gaps.

Mostco-founder agreements, when properly structured, include this clause as standard. The problem is that most early-stage companies don’t get around to properly structuring anything until something goes wrong.

The Vesting Question Nobody Wants to Ask

There’s a related issue that tends to create even more conflict: equity vesting schedules for founders.

When a co-founder leaves after six months with 30% of the company and without a vesting cliff they walk away with a stake that gives them ongoing leverage, board influence, and a financial claim on the company’s future. Combine that with unclear IP ownership, and a single departure can functionally destabilize the business.

Founder vesting typically follows a four-year schedule with a one-year cliff. The cliff means that if someone leaves before the first year is up, they vest nothing. After the cliff, equity accrues monthly. It’s a structure designed to align long-term commitment with long-term reward. But it only works if it was agreed upon at the outset, in writing, by everyone.

Here’s the uncomfortable reality: a lot of co-founders have these conversations in general terms “we’ll split it evenly,” “we’ll figure it out” and never formalize them. Then someone leaves at month fourteen, and suddenly what “counts” as vested is a matter of interpretation, not documentation.

When Things Actually Get Contested

Consider a scenario that plays out more often than the startup world likes to admit. A technicalco-founder builds the initial product, owns the GitHub repository, and wrote every line of code before the LLC was incorporated. They receive40% equity, no IP assignment was ever signed, and they leave after a dispute with the CEOco-founder two years in.

What happens next is a negotiation that the departing founder holds most of the cards in.

They can, in theory, claim ownership of the originalcodebase. They can threaten to withhold licensing rights. They can demand a buyout in exchange for executing an IP assignment retroactively. This isn’t hypothetical bad behavior it’s the logical consequence of a legal structure that was never closed.

The CEO might argueunjust enrichment, or that there was an implied assignment through the nature of the working relationship. Sometimes courts agree with that. But implied agreements are expensive to litigate, uncertain in outcome, and devastating to investor confidence in the meantime. No startup survives that kind of distraction gracefully.

The Practical Moves That Actually Protect You

Getting ahead of this is less complicated than fixing it after the fact. The foundational step is ensuring every co-founder signs an IP assignment agreement before or at the time of incorporation ideally as part of aco-founder agreement that also addresses equity vesting, role definitions, and departure scenarios.

Retroactive assignments are possible and sometimes necessary. If your company has been operating without them, it’s not too late but it requires the active cooperation of every founder, current and former, to execute properly. Former co-founders who’ve already left have no particular incentive to sign. That’s the leverage problem that proper documentation eliminates in advance.

Work-for-hire clauses are another layer of protection. When contractors, consultants, or early contributors build something for the company, those agreements should explicitly state that the work product belongs to the company. Independent contractors don’t automatically lose ownership the way employees do under certain interpretations of the law.

Open-source licensing creates its own subset of complications. If aco-founder used open-source libraries, the licensing terms attached to that code follow the product. If they wrote code and then released it publicly before the company claimed it, you may have a different kind of IP problem on your hands.

What Departing Co-Founders Should Know Too

This conversation isn’t only relevant to the founders who stay. Someone leaving a company has their own IP interests to protect particularly any work they did that predates the founding relationship, any inventions clearly outside the company’s domain, and any creative or technical work they want to retain for future projects.

A thoughtful co-founder agreement will carve out these exclusions explicitly. If you built a side project before the company started, list it. If you have domain expertise you intend to keep using professionally, protect it with a written carve-out. Courts can be sympathetic to overly broad IP grabs by companies, but sympathy doesn’t pay legal fees.

The departure itself should be handled with the same care as the founding. A clean separation agreement one that addresses IP, equity treatment, non-competes where enforceable, and any consulting transitions protects everyone and leaves the company in a legally defensible position.

The Silence Is the Risk

Most founders don’t avoid these conversations because they’re naive. They avoid them because they feel premature, or because raising the topic implies you’re already anticipating the end of the partnership. That instinct is understandable and almost always costly.

The companies that handleco-founder departures cleanly tend to be the ones that had difficult, specific conversations early about ownership, about what happens if someone leaves, about who built what and who it belongs to. Those conversations don’t predict failure. They’re what makes survival possible when circumstances change.