I once saw a seven-figure acquisition deal implode on the one-yard line. The acquiring company was doing its final due diligence, and their lawyers found something buried in the startup’s codebase. A single, critical software library, which the entire product was built on, had a license that made it poison. The deal was dead on arrival. The founders walked away with nothing but a very expensive, and very public, lesson.
That’s not some scare tactic. That’s a real story from my time as an investor. And it’s why I’m writing this. As a founder, you’re juggling a thousand things. Marketing, sales, product, hiring—it’s a relentless grind. It’s so easy to think that the little things, like the images you grab for your blog or that open-source library you use, don’t matter. You’re just trying to ship, right? Get the MVP out the door. I get it. I’ve been there.
But here’s the hard truth: those “little things” are landmines. Confused about IP protection? You're not alone. This article is the clear, founder-focused roadmap I wish I had when I was starting out. It’s my no-BS guide to navigating one of the most critical legal areas for your startup, without the fluff and ten-dollar words lawyers love to use.
The “It’s Just a Small Project” Fallacy
Every founder has said it. “We’re too small for anyone to notice.” “We’ll fix it later when we have money.” This is one of the most dangerous mindsets in the startup world. You think you’re flying under the radar, but the internet has a long memory. The code you commit today, the blog post you publish with a stolen image—it’s all archived. It’s a digital paper trail that leads right back to you.
Think about it. You use a copyrighted photo on your landing page. A year later, you’re raising your Series A. The VC’s due diligence team runs a reverse image search. They find the photo on a stock photography site, and your name isn’t on the license. Best case? It’s a red flag that makes you look amateurish and sloppy. Worst case? The original creator has already sent you a demand letter for thousands of dollars in damages, and now you have to disclose a pending legal dispute to your potential investors. Good luck with that.
This isn’t a hypothetical. I’ve seen companies have to pull their products from the market. I’ve seen founders have to pay massive settlements out of their own pockets. Your “small project” is the foundation of your future empire. Don’t build it on quicksand.
Real-World Horror Stories
Let me tell you about a portfolio company—I won’t name names—that built their entire mobile app around a cool, open-source charting library they found on GitHub. It made their data visualizations look amazing. They shipped the product, got traction, and started to get some buzz.
Then the email came. It was from the original creator of the library. The library was under a GPL license, a “copyleft” license. In simple terms, it meant that because they used his library, their entire application was now considered a “derivative work” and had to be open-sourced under the same GPL license. Their proprietary code, their secret sauce, everything. They had two choices: open-source their entire company, or rebuild the app from scratch without the library. They chose to rebuild. It cost them six months of runway and nearly killed the company.
Another time, a founder I know used a song from a popular artist in a promotional video. He thought it was fine because it was just a 30-second clip on social media. The video went viral. A week later, he got a cease-and-desist letter from the record label’s legal team. They demanded $150,000 for copyright infringement. He ended up settling for a fraction of that, but it was still a five-figure check that his early-stage startup couldn’t afford to write.
These aren’t edge cases. This happens every single day.
Images: The Hidden Landmines
Let’s get tactical. Where do you get your images? If your answer is “Google Image Search,” you are playing with fire. Just because an image is on the internet does not mean it’s free to use. Most of those images are owned by someone—a photographer, a designer, a company. Using them without permission is theft.
Here’s a quick breakdown of image licenses, minus the legal jargon:
- Royalty-Free (RF): This is what you want. You pay a one-time fee to use the image multiple times without paying royalties for each use. Sites like Adobe Stock or Shutterstock are full of these. It’s not “free,” it’s “free of royalties.”
- Rights-Managed (RM): This is more restrictive. You license the image for a specific use, for a specific time, in a specific region. It’s more expensive and complicated. Avoid it unless you absolutely need a specific image.
- Creative Commons (CC): This is a spectrum. Some CC licenses let you do whatever you want (CC0 is basically public domain). Others require you to give credit to the creator (BY), or prevent you from using it for commercial purposes (NC), or prevent you from making changes (ND). You have to read the specific license. Don’t just assume “Creative Commons” means “free-for-all.”
Safe Sources for Images:
- Paid: Adobe Stock, Getty Images, Shutterstock. This is the safest bet. The license is clear, and the quality is high. It’s a cost of doing business.
- Free: Unsplash, Pexels, Pixabay. These sites offer photos with their own custom licenses, which are generally very permissive. They are a great option when you’re starting out, but always double-check the terms. Things can change.
Code: The Ticking Time Bomb
The image problem is simple compared to the nightmare of open-source software (OSS) licenses. Using code from GitHub or other sources is a core part of modern software development. But you cannot just copy-paste code without understanding the license attached to it.
Here are the big ones you need to know:
- Permissive Licenses (MIT, Apache 2.0, BSD): These are your friends. They basically let you do whatever you want with the code, as long as you keep the original copyright notice. You can use it in your proprietary, closed-source product without any issues. Most of the popular libraries (like React and a lot of the stuff I invest in) use these licenses for a reason.
- Copyleft Licenses (GPL, AGPL): This is the danger zone. These licenses are “viral.” If you use a GPL-licensed component in your code, your entire codebase may now be considered a derivative work and must also be licensed under the GPL. The AGPL is even more restrictive, applying to software used over a network. This is the license that blew up that deal I mentioned earlier. It’s poison for a commercial startup.
How to Protect Yourself:
- Track Everything: Keep a detailed record of every single open-source library you use. Every. Single. One.
- Use Automated Tools: Services like FOSSA or Snyk can automatically scan your codebase, identify all your dependencies, and flag any license compliance issues. This is not optional. It’s a must-have.
- Have a Policy: Create a clear policy for your engineering team about which licenses are pre-approved (MIT, Apache) and which require special permission (anything with “GPL” in the name).
My No-BS IP Checklist for Founders
Feeling overwhelmed? Don’t be. Here’s a simple checklist. Do this, and you’ll be ahead of 90% of other founders.
- [ ] Image Audit: Do you know where every image on your website, blog, and app came from? Do you have a license for it? If not, replace it now.
- [ ] Code Audit: Are you using an automated tool to scan your dependencies for license issues? Run a scan this week.
- [ ] Create an Asset Policy: Write a one-page document that states your company’s rules for using third-party images and code. Make every employee and contractor read and sign it.
- [ ] Centralize Your Licenses: Keep a folder with the license agreements for every piece of stock photography, every software library, and every font you use.
- [ ] Talk to a Lawyer: Find a good startup lawyer before you need one. Pay them for a few hours to review your IP strategy. It will be the best money you ever spend.
Stop Being Lazy
Look, I’m not a lawyer. This isn’t formal legal advice. This is advice from someone who has been in the trenches, built and sold companies, and seen these mistakes kill dreams. You can’t afford to be sloppy with this. The early days of a startup are about moving fast, but they are also about building a solid foundation.
Ignoring intellectual property is like building a house and not bothering to check if you actually own the land it’s on. It might feel fine for a while. You might even get the walls up and the roof on. But one day, the real owner is going to show up, and they will take everything. Don’t let that be you. Do the work now, or pay for it later. Your company’s life depends on it.
Frequently Asked Questions
Is this guide based on real experience?
Every recommendation in this guide comes from direct experience, either from building and selling my own companies, or from patterns I've observed across 200+ angel investments. I don't write about things I haven't personally tested.
How should I work through this guide?
Don't try to absorb everything in one sitting. Read through once to get the big picture, then go back and work through each section as it becomes relevant to your current challenges. Bookmark it and return to it regularly.
Who is this guide designed for?
This guide is written for founders and operators who want practical, actionable advice rather than theoretical frameworks. Whether you're just starting out or scaling an existing business, the principles here apply across stages.
What if I disagree with some of the advice?
Good. That means you're thinking critically, which is exactly what a good founder should do. Take what resonates, test it, and discard what doesn't work for your specific situation. No advice is universal.