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.
A worked example: two conversations, one NDA
Picture the same founder in two meetings a fortnight apart. In the first, they are sending a product specification — dimensions, tolerances, the bill of materials, the part of the design that took eighteen months to get right — to three contract manufacturers so each can quote properly. Every one of those factories makes similar products for other clients. An NDA here does specific work: it names the documents being shared, limits what each factory may use them for, and gives a contractual hook if a near-identical product appears off that supplier's line next year. All three sign without comment, because at that stage it is simply how the industry operates.
In the second meeting, the same founder emails an NDA to an angel investor ahead of a first thirty-minute call about the market and the idea. The investor declines to sign — not out of bad faith, but because they see a steady stream of pitches in the same sector and cannot contract themselves out of backing an adjacent business later. The call happens anyway, two weeks later than it would have, and the founder has spent their first impression on a document rather than on the pitch.
The difference between the two is not how serious the conversation was. It is what was actually handed over. The factory received a transferable asset it could use without the founder; the investor received a description. And if the worst happened in either case, the route is the same — a claim for breach of contract, brought within six years of the breach under the Limitation Act 1980, in which you must prove the information was genuinely confidential rather than general industry knowledge, that this specific party disclosed it, and that the disclosure cost you money you can quantify. That is a serious argument to run with a specification in hand. With an idea described out loud in a first meeting, it is close to unwinnable — which is another way of saying the second NDA was never going to protect anything.
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.
Common questions
Will an investor sign my NDA?
Usually not, and it is not personal. Professional investors see a large volume of pitches in the same sectors, so signing a confidentiality agreement before a first conversation would expose them to an argument every time they later back something adjacent. Plenty of angel groups and funds have a blanket policy of not signing at first-meeting stage, and asking marks you out as someone who has not raised before. What they will sign is an NDA at due diligence, once there is real interest and you are handing over financials, contracts, supplier terms and customer data. That is the point where confidentiality does an actual job rather than acting as a test of how serious everyone is.
Is my idea protected at all without an NDA?
An idea by itself is not protected in UK law: copyright protects the expression of an idea rather than the idea, and a patent requires something novel and inventive that you have properly applied for. What can protect you without any signature is the equitable duty of confidence, which arises where genuinely confidential information is shared in circumstances that import an obligation of confidence — real, but much harder to rely on than a written agreement. The practical answer is to protect what actually can be protected: register the trademark, control access to source code and technical specifications, and put confidentiality terms into your employment and contractor agreements as standard.
Can I actually enforce an NDA if someone breaks it?
In principle yes, but the practical barriers explain why NDAs deter far more often than they remedy. You have six years from the breach to bring a claim under the Limitation Act 1980, and the remedies are an injunction to stop further disclosure and damages for the loss caused. Both require you to prove three difficult things: that the information was genuinely confidential rather than general industry knowledge, that this specific person disclosed it, and that the disclosure caused you quantifiable financial loss. The third defeats most claims arising from a leaked idea. The costs also fall on you upfront, which is why most breaches end with a solicitor's letter rather than a courtroom.
Can an NDA stop an ex-employee talking about how they were treated?
No, and this is where the law has moved hardest. A confidentiality clause has never been able to prevent a protected disclosure under whistleblowing law, and since 6 April 2026 disclosures about sexual harassment expressly count as qualifying disclosures. The Employment Rights Act 2025 goes further again, voiding any confidentiality term to the extent that it stops a worker speaking about harassment or discrimination, or about how the employer responded to it — expected to take effect in 2027, with narrow 'excepted agreements' where the worker took independent legal advice and genuinely wanted confidentiality. Settlement agreement templates drafted before this need reviewing now, not in 2027.
When is asking for an NDA genuinely the right call?
When you are about to hand over specific, transferable detail that the other side could use without you: a manufacturing specification, a formulation, source code, a customer list, or the financials and contracts an acquirer reads during due diligence. The test is whether they are receiving something they could walk away and use, rather than hearing a description of what you are building. Employees and contractors with hands-on access to proprietary systems should have confidentiality terms in their contracts as a matter of course. If you cannot name the specific document or dataset being handed over, the NDA is protecting a feeling rather than an asset.
