Should I Make Investors Sign an NDA Before They Hear My Pitch?

“Am I about to hand my idea to someone who could steal it?”

That thought is common for first-time founders before an investor meeting.

The instinct is understandable. But asking the wrong person to sign an NDA at the wrong time can create more problems than it solves. You could either overshare sensitive information or make an investor question your understanding of the fundraising process before the meeting even begins.

What Does an NDA Actually Protect?

A Non-Disclosure Agreement (NDA) is a contract requiring someone to keep specified confidential information from being disclosed or used improperly.

But an NDA has limits.

It does not prevent someone from independently developing a similar idea. It also cannot undo the damage if sensitive information has already been widely shared.

That makes the most important protection surprisingly simple: Be careful about what you disclose and to whom.

Why Most VCs Won’t Sign One

Venture capital investors hear hundreds of startup pitches. Many companies operate in overlapping markets or use similar technologies.

If an institutional investor signed an NDA before every pitch, it could create unnecessary legal exposure whenever the firm later invested in another company pursuing something similar.

Because of this, most institutional investors have policies against signing NDAs before an initial pitch.

Asking a VC to sign one before a first meeting can therefore be interpreted as a sign that the founder is unfamiliar with standard fundraising practices.

It can also slow down or end the conversation before you have even presented the company.

That does not mean investors never sign NDAs.

It means the timing and information being shared matter.

When Does an NDA Actually Make Sense?

There are situations where requesting an NDA is reasonable.

The key is that you are no longer having a standard introductory pitch. You are sharing specific confidential information with a counterparty that has a legitimate reason to receive it.

Examples can include:

• Unfiled patent details or proprietary algorithms.
• Source code or detailed technical architecture during due diligence.
• Sensitive customer or user information during a partnership evaluation.

A targeted NDA can be particularly appropriate when you are deep into discussions with a potential commercial partner or acquirer and need to provide information that cannot reasonably be included in a public-facing pitch.

The agreement should match the specific relationship and information involved.

Your Pitch Deck Should Do Most of the Protecting

The strongest protection during an initial fundraising conversation is often what you choose not to disclose.

Your general pitch deck should focus on your vision, market, traction, business model, and other information investors need to evaluate the opportunity.

You can hold back highly sensitive technical details, unfiled patent information, proprietary specifications, and other information that does not need to be disclosed at the early stage.

This lets investors understand the business without giving them unnecessary access to your most valuable secrets.

Common Founder Mistakes

• Sending a boilerplate NDA before a first VC meeting: Founders may believe a generic NDA demonstrates professionalism and protects the pitch. With institutional investors, it can have the opposite effect. Many VCs will not sign pre-pitch NDAs, and the request may signal inexperience or cause the investor to deprioritize the meeting.
• Putting sensitive information into a widely circulated deck: Founders sometimes include detailed technical specifications, unfiled patent information, proprietary processes, or customer data and assume an NDA will solve the problem. But investor materials can circulate internally, and an NDA does not undo exposure after information has already been distributed.
• Using one NDA for every relationship: Investors, employees, vendors, and commercial partners have different risks and negotiating dynamics. Investors generally do not sign NDAs before pitches. Employees typically need confidentiality obligations in their employment agreements, while vendors and partners may require targeted protections when they receive proprietary information.

10-Minute NDA Self-Check

Before sending confidential information, ask:

• Am I about to disclose unfiled patent details, source code, or proprietary technical specifications?
• Am I speaking with an institutional investor who is only evaluating my initial pitch?
• Have I kept the most sensitive technical information out of my general pitch deck?
• If I am using an NDA, does it match the specific relationship and information being shared?
• Do my employee agreements already contain appropriate confidentiality protections?
• Would requesting an NDA at this stage likely slow down or end the conversation?

If the conversation is only an introductory investor pitch, an NDA may create more friction than protection.

Bottom Line

An NDA is a tool for a specific type of confidential conversation, not a shield that needs to surround every startup pitch.

Most institutional VCs are unlikely to sign an NDA before an initial meeting. That does not mean you should expose your most sensitive information. Instead, keep the initial pitch focused on what investors need to evaluate your company and reserve highly confidential technical, customer, or intellectual property information for situations where a targeted NDA makes sense.

The goal is not to hide your business. It is to disclose the right information to the right person at the right stage.

Want to Know Which Legal Protections Actually Matter Before You Start Pitching?

Schedule a free 30-minute call with our team to discuss your needs and concerns. 

Book here: Initial Consultation with Primum Law Group