Should You Sign an Investor's NDA? (And Will They Sign Yours?)

There are two versions of this question, and founders often can't tell which one they're in:

1. "Should I sign an NDA the investor is asking me to sign?"
2. "Should the investor sign an NDA I'm asking them to sign?", usually followed by "…because they just refused."

They have almost opposite answers. Let's take them in the order founders actually hit them.

First, the one everyone runs into: the VC who won't sign yours

You're about to pitch. Your deck has your numbers, your roadmap, your secret sauce. Every instinct says: get them to sign an NDA first. You send one. The VC politely declines, and you're left wondering if that's a red flag about them, or about you.

It's neither. Most institutional investors will not sign an NDA to hear a pitch, and their reasons are structural, not sinister.

• They see hundreds of similar companies. A VC evaluating your fintech idea is probably looking at three others this quarter. An NDA that says "don't use confidential information you learn from us" creates a landmine: if they fund a competitor next month, you have a built-in claim that they stole your idea. They can't run their business under that risk across every meeting.
• Signing yours means reading and negotiating yours. Multiply that by every founder who sends one, and it's a legal department's full-time job. Declining is a blanket policy, not a judgment on you.
• It signals inexperience. Fair or not, in the startup world, leading with an NDA before a first meeting reads as a founder who doesn't know the norms. That's a cost you pay before you've said a word about the company.

So the practical answer to "how do I get a VC to sign my NDA" is usually: you don't. But that doesn't mean you pitch with no protection. You protect yourself by controlling what you disclose, not by papering it:

• Lead with the vision, market, team, traction, and product, the things that make you fundable. These are not the things that get "stolen"; execution is the moat, not the idea.
• Hold the genuinely secret material (source code, secret formulas, proprietary algorithms, the actual technical how) for later stages, when interest is real and diligence is underway. That's when an NDA becomes appropriate and investors will often sign one.
• Keep the legal reality in mind: a bare idea, on its own, is very hard to protect. What an NDA and trade secret law actually protect is specific, identifiable confidential information, not a concept in the abstract. Execution is your real moat. So stage your disclosure so the genuinely secret material (the how, not the what) comes out only when there's a signed agreement and real intent.

There's a narrow exception: angel investors, strategic investors, and corporate VCs, especially ones close to your space, are sometimes willing to sign, and there the calculus is different. If someone is both a potential investor and a potential competitor or acquirer, asking for confidentiality before deep disclosure is more reasonable and more likely to be accepted.

Now the other one: the investor asks you to sign

This flips later in the process, and it surprises founders. At some point an investor may hand you an NDA, commonly when:

• They're sharing their information with you (their process, portfolio data, a data room, terms of a structured deal), or
• Diligence goes both ways, or
• You're dealing with a strategic/corporate investor who's also exploring a commercial relationship or acquisition.

Should you sign it? Usually yes in principle, but read it as carefully as any other NDA someone hands you, because an investor's NDA is still a contract drafted to protect them, and a few clauses can reach further than "keep our data room quiet."

What I'd look at hardest in an investor-provided NDA:

• What "confidential information" covers, and in which direction. Is it mutual, or written entirely around their disclosures, leaving what you show them unprotected? If you'll be sharing sensitive material too, a one-way NDA protecting only them is a gap. (See Mutual vs. One-Way NDA.)
• Non-solicitation or "no poaching" language. Some investor and strategic NDAs quietly restrict you from hiring their people or their portfolio companies' people. That's a restrictive covenant, not mere confidentiality. Treat it seriously.
• Non-circumvention clauses. Common in deal and finance contexts: a promise not to "go around" them to their contacts or sources. Reasonable in some deals, overreaching in others. Know it's there.
• IP and "feedback" language. Make sure nothing in the NDA assigns them rights in what you create or a license to your material. An NDA should protect information exchange, not transfer your IP.
• Term, survival, and trade-secret treatment. The same duration questions that apply to any NDA apply here, including whether a fixed term quietly puts a fuse on trade-secret protection. (See How Long Should an NDA Last?.)

None of that means don't sign. It means sign knowingly, and redline what's overbroad, the same standard you'd apply to any counterparty's NDA.

The through-line

The mistake in both directions is treating "investor NDA" as a special category with its own rules. It isn't. When you're trying to get an investor to sign yours, the honest read is that early-stage confidentiality lives in how you stage disclosure, not in a document a VC won't execute. When an investor asks you to sign theirs, it's an NDA like any other, protect-them by default, worth reading for the clauses that reach past confidentiality into your hiring, your contacts, and your IP.

When you're handed an investor's NDA, see what it really says.

If an investor sends you an NDA, you don't have to guess whether it's balanced or whether a non-solicit is tucked inside. Drop it into YayNDA, alongside your own template or our free balanced one, and the tool compares it clause by clause, flags where it protects only them, and surfaces the restrictive-covenant and IP language that doesn't belong in a plain confidentiality agreement. You sign knowing exactly what you agreed to.