A first-time founder heading into pitch meetings often assumes the same rule applies as any other business conversation involving sensitive information: get an NDA signed before you say anything real. Then the request goes nowhere. A partner at an institutional fund declines politely, an associate says “we don’t sign those,” or the meeting simply never gets scheduled because the ask itself read as a red flag. This isn’t one investor being difficult. It’s close to universal practice at institutional venture firms, and understanding why changes how a founder should actually prepare to pitch.

Why Most VCs Won’t Sign a Pre-Pitch NDA

The core reason is volume. A single active fund can review hundreds or thousands of pitches a year across a handful of partners, and a meaningful share of those pitches land in the same handful of categories: another vertical SaaS tool, another consumer app, another infrastructure play with a similar wedge. If a fund signed an NDA before every first meeting, it would be creating a standing legal obligation tied to every idea it hears, in categories where it may already have a portfolio company, may be actively evaluating a direct competitor the same week, or may simply choose to pass and fund something similar six months later built by a different team. An NDA turns each of those ordinary outcomes into a potential breach claim, and no fund’s legal team wants that liability sitting against a document a partner signed in a ten-minute intro call.

There’s a reputational layer underneath the legal one. Venture is a small, relationship-driven industry, and a fund that develops a reputation for taking ideas from pitches it passed on doesn’t survive on deal flow for long, because founders talk to each other and to the same lawyers before every fundraise. That informal accountability does more day-to-day work than a signature would, and it’s a large part of why institutional VCs treat “we don’t sign pre-pitch NDAs” as standard practice rather than something they need to justify meeting by meeting. Angel investors and family offices are occasionally more flexible, since they’re writing fewer checks and not managing the same portfolio-conflict exposure, but even there, a signed NDA before a first conversation is the exception, not the norm.

Fiduciary duty is the last piece. A general partner owes a duty to the fund’s limited partners to explore the best opportunities in its stated thesis, and a stack of pre-pitch NDAs would constrain exactly that: the fund couldn’t freely discuss, compare, or pass on ideas across similar companies without checking each one against a confidentiality obligation first. None of this means investors are careless with what they hear. It means the protection founders get isn’t contractual, and it’s worth knowing what actually is protecting them before walking into the room.

Three reasons institutional funds decline a pre-pitch NDA Volume of pitchesacross similar ideas Reputation amongfounders and lawyers Fiduciary duty tolimited partners

Figure 1: Why institutional venture funds treat a pre-pitch NDA as a non-starter.

What Protects Founders Without a Signed NDA

Trade secret law does real work here, and it runs independently of any contract. Information that is genuinely secret (not publicly known or easily discoverable), has economic value because it’s secret, and has been protected by reasonable measures on the founder’s own side, qualifies for trade secret protection under state law and the federal Defend Trade Secrets Act regardless of whether the person who heard it signed anything. The catch is that “reasonable measures” is doing the load-bearing work in that definition, and it’s a standard the founder controls, not the investor: sharing a fully open cap table, unreleased source code, and unfiled technical detail in a first meeting with no internal access controls or disclosure log undermines a later trade secret claim more than a missing NDA does.

For anything genuinely patentable, filing a provisional patent application before the first substantive pitch is worth the modest cost and short timeline it takes. A provisional filing gives a founder a filed legal right independent of any confidentiality promise, and once it’s on record, disclosing the underlying idea to investors doesn’t forfeit anything the way it would for an unfiled invention. It’s a narrower tool than an NDA (it only covers what’s actually patentable, not the business model or the go-to-market plan), but for the subset of startups built around a defensible technical mechanism, it’s the strongest protection available and it doesn’t depend on anyone else’s signature at all.

The last piece is less legal and more practical: most of what a founder is nervous about sharing isn’t actually the moat. A market thesis, a general product direction, even a rough go-to-market plan, are cheap to hear and expensive to execute, and an investor who passes on a pitch has essentially no use for the idea without the founding team behind it. The genuinely protectable material, proprietary technical mechanisms, named customer data, unreleased code, is a much smaller slice of a typical pitch deck than founders initially assume, which is exactly what shapes how disclosure should be staged across a fundraise.

Three protections that work without a signed NDA Trade secret law,with reasonable measures Provisional patentbefore the pitch Staged disclosure,not full disclosure

Figure 2: Protections a founder keeps without a signed NDA. Source: state trade secret law and the Defend Trade Secrets Act.

What to Share, and When

What to disclose, and when

Pitch deck stageDiligence stage
Market size, business modelShare fullyAlready shared
Revenue and unit economicsDirectional rangesFull detail, data room
Proprietary algorithm or source codeDescribe, don't discloseNDA-gated walkthrough
Customer names and contractsAggregate or anonymizedNamed, under NDA
Cap table and prior investorsNot needed yetFull detail, data room

The pattern here is staging, not withholding. A pitch deck should give an investor everything they need to decide whether to take a second meeting, market size, the problem, the model, traction in directional terms, without handing over the specific technical or customer detail that would let a competitor replicate the product without doing the underlying work. That detail belongs in the data room, opened selectively once a firm has shown real interest, ideally after a partner meeting rather than before a first call. If the underlying idea is described accurately enough at the deck stage, most serious investors don’t need the deeper material to make a first-round decision anyway.

When a Narrower NDA Is Worth Asking For

There are real situations later in a fundraise where an NDA is a reasonable ask and gets a different response than it would at the pitch stage. A lead investor’s technical diligence team asking to walk through unreleased source code, a deeper look at a proprietary algorithm, or access to a live production system is a case where a narrow, single-purpose NDA scoped to that specific material is a normal request, not an unusual one, especially once a term sheet is in hand or close to it. The same logic applies to sharing named customer contracts or data containing personal information as part of legal or commercial diligence: scoping confidentiality to that specific data room, for that specific diligence window, is far more likely to get signed than a blanket NDA covering the whole relationship.

The direction of these narrower agreements is almost always one-way rather than mutual, since the founder is the party disclosing real secrets and the investor typically isn’t sharing anything comparably sensitive back. If it isn’t clear which structure fits a given diligence request, Mutual NDA vs One-Way NDA covers how to match the type to the relationship. If a lead investor’s team needs a narrow agreement before reviewing source code or a customer dataset, our NDA generator builds a one-way agreement scoped to that specific material, rather than the broad, catch-all confidentiality language that makes a fund’s legal team hesitate in the first place.

Once a term sheet is signed, confidentiality usually stops being a standalone document altogether and becomes a clause inside the term sheet or the eventual investment agreement itself, covering the terms of the deal rather than the underlying business. If it’s not obvious whether a given relationship still needs a separate NDA at that point or just a confidentiality clause folded into the main agreement, NDA vs Confidentiality Clause walks through how to tell the two apart.

Building Disclosure Discipline Into the Fundraise

Unstructured disclosure
  • Full deck with all financials sent to any warm intro
  • Assume a verbal request to 'keep this confidential' holds up
  • No record of who has seen the data room or when
Staged disclosure
  • Teaser-level deck first, technical and customer detail held back
  • Source code and unfiled IP withheld until real diligence starts
  • Data room access logged so a leak traces back to one party

None of this requires treating investors as adversaries. It requires treating disclosure as something to sequence deliberately rather than something to hand over all at once and hope a signature or a verbal promise covers the gap. Most of a pitch deck is safe to share broadly because it’s cheap to hear and hard to act on without the team behind it; the smaller slice that would actually hurt if it leaked, proprietary technical detail, named customer data, unfiled IP, is exactly the material worth holding back until a firm has earned real access, and it’s the material a narrow NDA is built for once that point arrives.