What NDAs actually protect, unilateral vs. mutual, realistic durations, and the real cost of being too protective — many investors and partners simply walk away from founders who require one too readily.
A Non-Disclosure Agreement (NDA) is a contract in which one or both parties agree not to share specific confidential information they learn during a conversation, negotiation, or working relationship.
Why this narrower definition matters: an NDA does not protect an "idea" in the abstract: ideas themselves generally aren't protectable, and courts don't treat vague concepts as confidential information. What an NDA actually protects is specific information you disclose under it: your customer list, your financial details, your product roadmap, your source code, your unreleased designs. If you never share the specific detail, the NDA has nothing to protect, and if you're vague about what counts as confidential, the agreement becomes much harder to enforce if it's ever tested.
Which type fits your situation
| When to use it | Typical scenario | |
|---|---|---|
| Unilateral (one-way) | Only one party is disclosing confidential information | Hiring an employee or contractor who'll see your internals; sharing your product with a single vendor |
| Mutual (two-way) | Both parties are disclosing confidential information to each other | Partnership discussions, joint ventures, M&A due diligence, co-development deals |
Core components of a working NDA
0/5Most NDAs set a confidentiality term somewhere in the 1 to 5 year range for ordinary business information, with 3 to 5 years being the common middle ground for employee, vendor, and partnership NDAs. Genuine trade secrets can reasonably warrant a longer or indefinite term, since a secret formula or process can retain its value for decades if it stays secret.
Why "forever" is often a mistake, not just aggressive: courts have real skepticism toward NDAs that impose perpetual or extremely long confidentiality obligations on ordinary (non-trade-secret) business information, and some states go further: Florida, for example, has a statute that lets a judge simply disregard an "overlong" NDA's stated duration and grant only the protection actually necessary. The practical result is that an NDA written to be maximally protective can end up less enforceable than a reasonably scoped one, because a court asked to enforce it may narrow or void the very terms that made it feel airtight.
This is the mistake founders make most often with NDAs
Requiring an NDA before every casual conversation (a first meeting with a potential partner, an early chat with an investor, a quick call with someone who might refer you customers) signals distrust before a relationship has even started, and it adds real friction to deals that might otherwise move quickly.
Many investors, in particular, simply refuse to sign NDAs as a matter of policy. They see far too many similar pitches to accept the legal exposure of promising confidentiality over an ordinary conversation, and a founder who insists on one anyway often gets quietly moved to the back of the line (or dropped entirely) rather than a real negotiation. The same dynamic shows up with larger corporate partners, who often have a blanket "we don't sign NDAs for exploratory conversations" policy that no amount of pushing will change.
Overly broad NDAs cause a second, subtler version of the same problem: terms that assign you ownership of any related idea the other party ever independently has, or that run for decades, make sophisticated counterparties either walk away or spend real time and legal fees negotiating you down: time that a more reasonably scoped NDA wouldn't have cost you in the first place.
The practical fix: reserve NDAs for situations with a genuinely specific secret at stake (trade secrets, source code, financials in a real M&A conversation, a not-yet-filed patent application) rather than defaulting to requiring one for every meeting. For ordinary exploratory conversations, simply being thoughtful about what you volunteer is usually the better tool.
Find out whether this conversation actually calls for an NDA
Are you about to share something specific and genuinely damaging if leaked: source code, a trade secret, unreleased financials, a not-yet-filed patent?
Quick Check
Why might an NDA with a 50-year confidentiality term actually offer WEAKER protection than one with a 5-year term?
A founder requires every early investor conversation to start with a signed NDA. What's the most likely practical consequence?
Key Terms
Previous
Protecting Your Business Name & IP
Next →
Business Insurance: What It Actually Covers (and Doesn't)
Ask a question about this lesson or share your take.
Loading…