The NDA nobody needed: when contracts protect you, and when they're just theatre

Early on, every meeting started the same way: a printed non-disclosure agreement, slid across the table before a single word about the actual idea was said. It felt professional. It felt like the thing a serious founder does. Two years and a lot of wasted goodwill later, the honest conclusion was that most of those NDAs did nothing except make a few early conversations noticeably more awkward than they needed to be — and that a handful of situations genuinely did need one, which is exactly why it's worth knowing the difference.

Why the instinct feels so reasonable

The fear behind reflexively demanding an NDA is understandable: you've got an idea you believe in, you're about to describe it to a stranger, and the thought of them walking off and building it themselves is genuinely uncomfortable. An NDA feels like insurance against that exact fear. The trouble is that the fear is usually wildly disproportionate to the actual risk, and the document does far less to prevent it than the feeling of having signed something suggests.

The uncomfortable truth about most early-stage ideas

Almost nobody is in a position to steal an idea and execute it better than the person who's already obsessed with it, has already done the early customer conversations, and already understands the specific problem better than anyone else in the room. Ideas, on their own, are genuinely close to worthless — execution, timing, distribution and relentless follow-through are what actually create value, and none of those are things an NDA protects. A potential investor, advisor or early hire who hears a pitch isn't typically weighing up whether to steal it; they're weighing up whether to back it, work with it, or move on. Making them sign paperwork before that conversation even starts signals more insecurity than protection.

An idea described in a fifteen-minute pitch was never the valuable part. The years of execution that follow it are — and no NDA has ever protected those.

Where an NDA is genuinely doing something

This isn't an argument that NDAs are always theatre — there are situations where they earn their place. Sharing genuinely sensitive material with a manufacturer or supplier who needs real technical detail to quote accurately — specifications, formulations, source code — is a legitimate reason, because there's specific, transferable information at stake, not just a pitch. Discussions with a potential acquirer or investor who will see real financials, contracts, or customer data during due diligence also warrant one. And formalising confidentiality with an employee or contractor who'll have hands-on access to genuinely proprietary systems is standard and sensible. The common thread is specific, valuable, transferable information — not a general business idea being described out loud.

The cost of asking for one at the wrong moment

The real cost of an unnecessary NDA isn't legal risk — it's the impression it creates. Experienced investors and advisors see dozens of pitches a month and, fairly or not, an NDA request before an initial conversation reads as a signal of inexperience, because seasoned founders generally understand that the idea isn't the moat. It can also simply slow things down or put people off a conversation entirely — plenty of investors and advisors have a blanket policy of not signing NDAs for first meetings, precisely because they've learned the request rarely reflects genuine risk.

What to actually protect instead

If the fear behind the NDA is real, the more useful response is usually to protect the parts of the business that genuinely can be protected — trademark the name, keep source code and specific technical processes under sensible access control, use proper contracts with anyone who'll have real access to proprietary systems, and simply move quickly on execution rather than treating secrecy as the primary strategy. None of that requires putting a stranger through a legal document before you've even had a conversation about whether working together makes sense.

When to actually ask for one

The honest filter is: are you about to share something specific, technical and genuinely hard to replicate — not just an idea, but the actual mechanics behind it — with someone who has a real reason to need that detail? If yes, an NDA is a sensible, standard step, and nobody serious will be offended by the request. If what's actually happening is a first conversation about a concept, a market opportunity, or a general business plan, the paperwork is very likely protecting a feeling rather than anything real, and it's worth having the confidence to have that conversation without it.

What changed

These days, the NDA only comes out for the situations that actually warrant it — supplier conversations involving real specifications, and due diligence involving real financials. Every other conversation happens on the same trust every other business conversation runs on: the idea alone was never really the asset. Being the person who could actually build it was, and that was never something a signature could protect anyway.

The confidence it actually takes

Dropping the reflexive NDA habit took longer than expected, mostly because it meant sitting with the discomfort of describing an unprotected idea out loud and trusting that it would be fine. It always was. The people worth talking to in the first place were never the ones looking for something to copy — they were the ones deciding whether to help build it, invest in it, or buy it, and none of those decisions were ever going to be made easier by a signature on a document before the conversation had even properly started.