I almost lost MovieLaLa before it even started.
We were a team of three, working out of a cramped apartment in Palo Alto, fueled by instant noodles and the belief that we were building the future of movie discovery. We had a great idea, a solid team, and a prototype that was getting some buzz. We were ready to raise our seed round.
Then, during a due diligence meeting with a VC, a question came up that made my blood run cold: "Can you show us the IP assignment agreements from your co-founders?"
Silence.
We didn't have them. We were three friends, working together on a passion project. We trusted each other. We thought a handshake was enough.
That one oversight almost cost us the entire company. The VC walked away, and we had to scramble to get the legal paperwork in order. It was a painful, expensive, and stressful lesson. And it's a mistake I see founders make over and over again.
That's why I'm writing this. I want to save you from the same headache. I want to talk about the one document that every founder forgets, but that can make or break your startup: the IP Assignment Agreement.
What is an IP Assignment Agreement, Anyway?
Let's cut through the legal jargon. An IP Assignment Agreement is a simple contract that transfers the ownership of intellectual property from an individual to a company. That's it.
It says that any work you do for the company – code, designs, branding, content, anything – belongs to the company, not to you as an individual.
It sounds simple, but it's incredibly important. Without it, you don't actually own the product you're building. Your co-founders, your employees, your contractors – they could all walk away with a piece of your company's core technology.
Why This is the Hill I Will Die On
I’ve invested in over 200 companies, and I’ve seen this movie play out more times than I can count. A startup is on the verge of a major breakthrough – a big funding round, a partnership, an acquisition. And then, during due diligence, the IP issue comes up.
Suddenly, the deal is on hold. Lawyers are called in. Tempers flare. And in the worst-case scenario, the deal falls apart completely.
Think about it from an investor's perspective. They're not just investing in your team; they're investing in your assets. And your most valuable asset is your intellectual property. If you can't prove that you own it, you have nothing to sell.
This isn't just about fundraising, either. It's about protecting your company from future disputes. What happens if a co-founder leaves on bad terms? What happens if an early employee starts a competing company? Without a solid IP Assignment Agreement, you're exposed.
I remember one of my portfolio companies, a promising AI startup, had to pay a former contractor a seven-figure sum because they never got an IP assignment signed. The contractor owned a critical piece of their core algorithm. It was a costly mistake that could have been avoided with a simple piece of paper.
The Nitty-Gritty: What Goes into the Agreement
An IP Assignment Agreement doesn't need to be a 50-page legal document. A simple, clear agreement is all you need. Here are the key components:
- Invention Assignment: This is the heart of the agreement. It states that any inventions, ideas, or work created by the individual related to the company's business are owned by the company.
- Confidentiality: This clause prevents the individual from sharing the company's confidential information with anyone else.
- Non-Compete: This is a tricky one, and the enforceability varies by state. In California, for example, non-competes are generally not enforceable. But in other states, they can be a powerful tool to prevent former employees from starting a competing business.
- Non-Solicit: This clause prevents the individual from poaching employees or customers from the company after they leave.
The Golden Rule: Sign it on Day Zero
When should you get your IP Assignment Agreements signed? The answer is simple: on day zero. Before you write a single line of code. Before you design a logo. Before you even have a company name.
I know what you're thinking. It feels awkward. It feels formal. It feels like you don't trust your co-founders.
Get over it.
This isn't about trust. It's about good governance. It's about building a solid foundation for your company. It's about treating your startup like a real business, not a hobby project.
Think of it like a pre-nup for your startup. It's a conversation you need to have when everyone is happy and excited about the future. It's a lot harder to have that conversation when things go wrong.
Common Traps and How to Avoid Them
I've seen founders make a lot of mistakes when it comes to IP assignment. Here are a few of the most common:
- The "We'll do it later" trap: This is the most common and the most dangerous. You're busy. You're focused on building the product. You'll get to the legal stuff later. But later never comes. And by the time you realize you need it, it's too late.
- The "It's just a template" trap: You download a template from the internet and have everyone sign it without reading it. The problem is, that template might not be right for your business. It might not be enforceable in your state. It might not cover all of your intellectual property.
- The "We don't need it for contractors" trap: You assume that because you're paying a contractor, you own the work they do. That's not always the case. Unless you have a written agreement that explicitly states that the company owns the work, the contractor may still own the copyright.
My Final Word: Don't Be a Statistic
I know this isn't the sexiest part of being a founder. You'd rather be building product, talking to customers, and changing the world. But this is the stuff that matters. This is the stuff that separates the successful startups from the ones that crash and burn.
Don't be a statistic. Don't be the founder who loses their company over a piece of paper. Get your IP Assignment Agreements in place from day one. It's the cheapest insurance policy you'll ever buy.
And if you're an investor, make this the first question you ask every founder you meet. It will tell you everything you need to know about how seriously they take their business.
Who Needs to Sign an IP Assignment Agreement? Everyone.
This isn't just for your co-founders. It's for anyone who touches your product or business idea. Let's break it down.
- Co-founders: This is the most obvious one, and the most important. You need to have this signed before you do anything else. No exceptions. This ensures that the company owns all the foundational work.
- Employees: From your first hire to your hundredth, every single employee needs to sign an IP assignment agreement as part of their onboarding paperwork. This is standard practice at any serious tech company. At RemoteTeam, this was part of the day-one package for every new team member. It was non-negotiable.
- Contractors and Freelancers: This is a huge one that people mess up all the time. You hire a freelancer to design your logo or write some code. You pay them. You assume you own the work. You're wrong. By default, the creator owns the copyright to their work. Unless you have a written agreement that explicitly transfers ownership to your company, that contractor could come back later and claim ownership of a critical part of your business. Always, always have a contract with freelancers that includes an IP assignment clause.
- Advisors: Even if they're not writing code, advisors are contributing ideas and strategy. Those ideas are intellectual property. Get it in writing.
The Acquisition Lens: Why This Matters for Your Exit
Let's fast forward. You've built an amazing company. You're in talks to be acquired. This is the dream, right? When my first company, MovieLaLa, was acquired by Gfycat, and later when RemoteTeam was acquired by Gusto, the due diligence process was intense. The acquiring company's lawyers go through everything with a fine-tooth comb.
And what's one of the very first things they ask for? You guessed it. The complete set of IP assignment agreements for every person who ever contributed to the product.
If you have a single gap—one former employee who never signed, one contractor you can't track down—the deal can grind to a halt. The acquirer might ask for a significant holdback from the purchase price, a special indemnity, or they might just walk away. They are buying your assets, and if your ownership of those assets is questionable, the value of your company plummets.
Having our paperwork in perfect order for the RemoteTeam acquisition made the process infinitely smoother. It was a clear signal to Gusto that we were a well-run, professional organization. It removed a major point of friction and risk from the negotiation. It’s not just about avoiding disaster; it’s about creating value.
This Isn't About Mistrust, It's About Professionalism
I want to circle back to the awkwardness. It can feel weird asking a friend you're starting a company with to sign a legal document. It feels like you're planning for a divorce before you've even gotten married.
I get it. But you need to reframe it. This isn't about a lack of trust. It's the exact opposite. It's about showing respect for the company you're building together. It's about protecting the value you are all creating. It's a mutual agreement to put the company's interests first.
A real-world conversation sounds like this: "Hey, as we get serious about this, we need to start acting like a real company. The first step is to make sure the company officially owns all the great work we're doing. I've got a standard IP assignment agreement for us both to sign. It protects all of us and the business itself. Let's review it together."
See? It's not a confrontation. It's a collaboration. It's the first of many steps you'll take to build a lasting, valuable enterprise. So please, learn from my near-disaster. Make this the first thing you do. Your future self—and your future investors and acquirers—will thank you.
Frequently Asked Questions
Do all experts agree with this view?
No, and that's fine. The best ideas in business are often contrarian. I share my perspective based on my experience and data, but I encourage you to seek out opposing viewpoints and form your own conclusions.
How has this view evolved over time?
My thinking on most topics has changed significantly over the years. Early in my career, I held many conventional views that experience proved wrong. I try to update my beliefs when the evidence changes.
How can I apply this thinking to my own situation?
Start by identifying the core principle behind the opinion, not the specific example. Then ask yourself: does this principle apply to my context? If yes, test it in a small, low-risk way before going all in.