Do You Actually Need an NDA? When to Use One, and When It's Just Theater
Non-disclosure agreements have a reputation problem. Some founders treat them like a magic force field for every conversation. Others wave them off entirely. Both are wrong. An NDA is a specific tool for a specific job, and knowing when to reach for it is half the value.
What an NDA actually does
A non-disclosure agreement is a promise: I'll share sensitive information with you, and you agree not to use it or pass it on outside our relationship. Done well, it gives you a legal remedy if someone misuses what you told them in confidence.
Done poorly, a template you found on Google, signed and filed and never thought about again, it's a prop. It feels like protection. It isn't.
When you genuinely need one
Reach for an NDA when you're about to share information that would actually cause harm if it leaked, with someone who has reason to leak or misuse it:
- Sharing real financials, customer data, or proprietary methods with a potential partner, vendor, or acquirer.
- Hiring contractors or agencies who will see the inner workings of your business.
- Early product or IP conversations with people outside your core team.
When it's just theater
Be honest about the moments an NDA adds friction without adding protection:
- Pitching most investors. Serious investors generally won't sign one, and demanding it signals inexperience.
- Casual conversations where you're not actually revealing anything sensitive.
- Situations you'd never enforce. If you'd never sue over a breach, the NDA is a security blanket, not security.
What a real NDA needs
If you're going to use one, use one with teeth. A serviceable NDA:
- Defines "confidential information" precisely: too broad and it's unenforceable; too narrow and it protects nothing.
- Sets a reasonable time limit.
- Specifies mutual vs. one-way protection, matching who's actually sharing.
- Includes real remedies and a sensible governing-law clause.
This is exactly why I stopped sending clients to random template sites and drafted a clean, plain-language NDA (plus the contractor and service agreements most founders need) into the Founder Foundation package.
The bottom line
An NDA is not a substitute for good judgment about who you share sensitive information with. Use it when the information is genuinely valuable and the relationship genuinely warrants it, and make sure the document itself would actually hold up.
Want attorney-drafted agreements you can use today instead of hunting Google? See the resources. And if you're staring at an NDA someone sent you and aren't sure what you're agreeing to, the free guide will help you read it.
Keep Reading
What I Learned Building a Legal Tech Company as a Solo Founder
The honest version of what it takes to build something new while practicing law, the parts no one puts on LinkedIn.
Independent Contractor vs. Employee: What Founders Get Wrong
Calling someone a contractor doesn't make them one. Getting this wrong can mean back taxes, penalties, and lawsuits.