There's a clause that shows up in almost every co-founder agreement, gets skimmed by almost every founder, and quietly becomes one of the most consequential pieces of paper a startup ever signs. IP assignment isn't exciting. It doesn't come up in conversations about product or growth or fundraising strategy. It comes up when something goes wrong, and by then the damage is usually already done.
Here's what you need to understand before that happens.
What IP assignment actually means
An IP assignment clause does one thing: it establishes that intellectual property created by founders in connection with the company belongs to the company, not to the individuals who built it. That means code, designs, algorithms, written content, inventions, and anything else with commercial value that comes out of the founding team's work.
Without this clause, the default legal position is murkier than most founders realize. Work created by someone who isn't a formal employee of the company doesn't automatically belong to the company under most circumstances. That gap is exactly what an IP assignment clause closes.
Why this matters more than founders expect
The consequences of missing or vague IP assignment tend to stay invisible right up until they become catastrophic. A few scenarios worth understanding:
A co-founder who built the core product and later leaves the company in bad standing may have a legitimate claim to ownership of that technology if the IP was never properly assigned. At minimum, this creates a negotiation you don't want to be having. At worst, it creates a legal dispute that makes the company unfundable.
Investors conduct IP diligence. Any ambiguity in who owns what will surface, and it will need to be resolved before a round closes. The later you catch this, the more expensive it is to fix.
Acquirers are even more thorough. A company where IP title is unclear or disputed is a company most buyers will walk away from, regardless of how attractive everything else looks.
What a solid IP assignment clause covers
A well-drafted clause should address all of the following:
- Work created during the founder's involvement with the company, regardless of when or where it was made
- Work created using company resources, including time, equipment, or funding
- Inventions related to the company's business, even if developed on personal time
- Prior inventions that a founder brings into the company, which need to be explicitly listed and carved out
That last point is worth dwelling on.
Prior invention disclosures
If a founder brings existing intellectual property into the company, whether that's code written before the company was formed, a patent, a design system, or anything else, it needs to be explicitly listed in a prior invention disclosure schedule attached to the agreement.
Without that schedule, two bad outcomes become possible. The blanket assignment clause may inadvertently transfer ownership of that prior work to the company, which the founder never intended. Or the founder retains it personally and the company ends up relying on technology it doesn't actually own or have a license to use.
Either situation creates a legal problem. The fix is straightforward: list prior inventions explicitly, even the ones that feel tangential or unlikely to matter. The cost of listing something irrelevant is zero. The cost of not listing something relevant can be significant.
Former employer conflicts
This one catches founders off guard more than almost anything else. Many corporate employment agreements contain invention assignment clauses that are written very broadly, sometimes covering work created outside of business hours and on personal equipment if it relates to the employer's business or was developed using any company resources.
If any founder came from a corporate job, a large tech company, or an academic institution before starting the company, it's worth reviewing those prior agreements carefully. The questions to ask are whether there's an invention assignment clause and how broadly it's written, whether there's a non-compete that could create conflicts, and whether any moonlighting policies were in place.
These aren't reasons to panic, but they are reasons to look before you assume everything is clean.
The work-for-hire gap
In the United States, work created by an employee within the scope of their employment is automatically owned by the employer under the work-for-hire doctrine. This gives some founders a false sense of security. The work-for-hire doctrine doesn't automatically apply to co-founders who aren't formal employees of the company yet, which is exactly the situation most early-stage founding teams are in before they incorporate and establish payroll.
An explicit IP assignment clause signed by all founders closes this gap cleanly.
What to watch for in your own agreement
If you're reviewing an existing co-founder agreement, these are the things worth flagging:
- No IP assignment clause at all, which is more common than it should be
- An assignment clause that only covers future work, leaving prior contributions unaddressed
- No prior invention disclosure schedule attached to the agreement
- Vague scope that doesn't define what categories of IP are covered
- Missing assignment of moral rights, which matters more in some jurisdictions than others
The bottom line
IP assignment is a legal hygiene issue. It won't feel urgent until it is, and when it is, it will be urgent in the worst possible context, either mid-fundraise or mid-acquisition conversation, with a clock running and real money on the line.
Get this clause right before meaningful work begins. Have every founder sign it. Attach a prior invention disclosure schedule even if it's mostly empty. It takes an hour to do properly and can save months of legal cleanup later.
This post is for informational purposes only and does not constitute legal advice. Consult a licensed attorney before making decisions about your intellectual property.