NDAs for Startups: What to Include, What to Cut, and When You Don't Need One

Founders reach for an NDA reflexively — before a first investor call, before talking to a potential co-founder, before a sales demo. Sometimes that's right. Often it isn't, and the document gets used as a shortcut for building trust rather than what it's actually for: protecting specific confidential information in a specific relationship.

What an NDA is actually for

A Non-Disclosure Agreement (sometimes called a confidentiality agreement) restricts how the receiving party can use and share information you disclose to them. It's not a substitute for trusting someone, it's not enforceable protection against someone independently building a similar idea, and it doesn't protect an idea itself — only specific confidential information disclosed under it.

When you actually need one

• Sharing genuinely sensitive technical detail — source code, proprietary algorithms, unreleased product specs — with a contractor, potential partner, or acquirer
• Early conversations with a potential co-founder where real strategy and financials get discussed
• Vendor or partnership discussions involving customer data or commercially sensitive terms
• Due diligence conversations with an acquirer or serious investor going deeper than a standard pitch

When you probably don't

• Most investor pitch meetings. Reputable VCs almost never sign NDAs before a first meeting — it's a well-known industry norm, and asking often signals inexperience rather than caution. Investors see too many similar pitches to make NDA-worthy misuse practical or worth their legal overhead.
• Early sales conversations about your product's general capabilities, as opposed to specific technical implementation.
• Hiring conversations before an offer, beyond a standard confidentiality clause in the eventual employment agreement.

One-way vs. mutual

A one-way (unilateral) NDA protects only the party disclosing information — appropriate when only you're sharing something sensitive, like pitching your product to a potential customer. A mutual NDA protects both sides — appropriate for partnership discussions, co-founder conversations, or any exchange where both parties are sharing something confidential.

What a good NDA includes

• A specific definition of confidential information — vague enough to cover what you actually need protected, specific enough to be enforceable
• Standard exclusions — information already public, independently developed, or already known to the receiving party before disclosure
• A defined term — typically one to five years, not indefinite, since indefinite terms are harder to enforce and unreasonable to expect counterparties to agree to
• Permitted use — what the receiving party is actually allowed to do with the information (usually: evaluate a potential deal, nothing more)
• Return or destruction obligations at the end of the relationship or on request

The clause that quietly turns an NDA into something else

Watch for NDAs — especially ones drafted by the other side — that smuggle in non-compete or non-solicit language, or an IP assignment clause, dressed up as "confidentiality" provisions. An NDA should protect information. If it starts restricting who you can hire, who you can do business with, or who owns ideas discussed in the meeting, that's a different (and much heavier) kind of document, and it deserves a second read before signing.

Frequently asked questions

Will investors sign an NDA before a pitch meeting?

Almost never, and asking is often read as a signal of inexperience. Protect what actually needs protecting — proprietary technical detail — later in the process, not the general pitch.

Is a one-page NDA template good enough?

For a straightforward one-way disclosure, often yes. For anything involving IP, co-founder discussions, or acquisition due diligence, it's worth a proper review — those are exactly the situations where a generic template's gaps get expensive.

Does an NDA stop someone from building a similar product?

No. It restricts what they can do with the specific confidential information you disclosed to them — it does not prevent them from independently pursuing a similar idea, especially if they can show they weren't relying on your confidential information to do it.

This article is general information about how these documents and obligations usually work. It is not legal advice on your specific situation, and reading it does not create a lawyer-client relationship. Laws referenced here change — verify current requirements before relying on this for a live decision.