Non-disclosure agreements are one of the most misused documents in early-stage startups. Some founders send them to every person they speak to — which signals inexperience and creates friction with exactly the people they're trying to impress. Others never use them — which leaves genuinely sensitive information unprotected. Knowing when an NDA is appropriate and when it isn't is a foundational skill for any founder.
Why investors almost never sign NDAs
Venture capital firms and angel investors speak to hundreds of companies every year. Many of those companies are working on similar ideas — that's simply the nature of innovation cycles. An investor who signs NDAs before initial conversations would be permanently restricted from funding any company in a space where they'd heard a pitch.
Asking an investor to sign an NDA before an initial meeting is a red flag. It signals that the founder doesn't understand how the investment community works, and it creates an unnecessary obstacle to a relationship you want to build.
The protection for most startups at the early stage isn't legal — it's execution. Ideas are not rare. The ability to execute on an idea faster and better than anyone else is. If your competitive advantage can be completely destroyed by someone hearing your pitch, you need to reconsider whether you have a competitive advantage.
When NDAs are absolutely appropriate
Contractors and service providers who will be given access to your proprietary systems, source code, customer data, or business strategy should sign an NDA before that access is granted. This is standard practice and professional service providers expect it.
Potential hires being given detailed technical or commercial information during a late-stage interview process should also sign an NDA. While most candidates are acting in good faith, the information shared in advanced hiring discussions — product roadmaps, unreleased features, financial projections — is genuinely sensitive.
Strategic partners, potential acquirers, and enterprise clients in extended procurement processes frequently exchange confidential information under mutual NDA. In these commercial contexts, an NDA is expected by both sides and signals that the negotiation is being treated seriously.
Mutual versus one-way NDAs
A one-way NDA protects information flowing in one direction — typically from the disclosing party to a recipient. A mutual NDA protects both parties' confidential information and is appropriate when both sides will be sharing sensitive material.
For most contractor and service provider relationships, a one-way NDA (disclosing your information to the contractor) is sufficient. For partnership or M&A discussions where both organisations are sharing strategic information, a mutual NDA is more appropriate.
Mutual NDAs are also used in employment contexts where the candidate is disclosing confidential information about a current employer — though this is less common and requires careful drafting to avoid unintended obligations.
What a startup NDA should include
An effective startup NDA should clearly define what counts as confidential information, how it can be used, how long the obligation lasts, and what happens if confidential information is required to be disclosed by law.
The definition of confidential information is the most important clause. Too narrow, and it doesn't protect what you need it to. Too broad (attempting to make everything confidential), and it becomes unenforceable. A well-drafted definition covers information disclosed in connection with a specific purpose and marked as confidential, plus categories of information that are obviously sensitive by their nature.
Duration matters too. A perpetual NDA is difficult to enforce. Three to five years from the date of disclosure is a standard and enforceable duration for most startup purposes.
Use NDAs purposefully rather than reflexively. The right NDA at the right moment protects your business. The wrong NDA at the wrong moment damages relationships before they start.