Most founders treat an NDA like a wedding invitation. They collect one, file it, and never read it again.

Then the leak happens. A vendor walks away with your pricing. A freelancer reuses your designs for a competitor. And the beautiful two-page NDA you both signed turns out to be decorative paper. Not protection.

I review NDAs for businesses every month. The mistakes repeat themselves with almost boring regularity. Here are the six that actually cost people money.

First, the basics, because half the NDAs I see get these wrong. India has no separate NDA law. An NDA is simply a contract, governed by the Indian Contract Act, 1872. That is good news — it means your NDA is enforceable in an Indian court like any other contract, provided it has the essentials: offer, acceptance, consideration, and a lawful object. And if the other side breaches it, a court can restrain further disclosure and award damages. The paper has teeth. Only if you sharpened them.

Now the analogy I give every client. An NDA is a door lock.

A lock will not stop a determined thief. Everyone knows that. But when a thief breaks a locked door, nobody asks whether you invited him in. The lock proves you didn't. In a dispute, that proof is everything. An NDA works the same way. It rarely prevents a leak. What it does is convert a leak from "an unfortunate conversation" into a breach of contract with consequences — an injunction, damages, a legal bill the other side has to think about before they talk. Never sign an NDA expecting prevention. Sign it to buy consequences.

Mistake 1: You shared first and signed later. This is the big one. You explained your entire business model over coffee, then sent the NDA the next morning. Legally, information disclosed before the signature is not covered unless the agreement expressly says it covers prior disclosures. Most templates don't. Fix it with one line: "This Agreement covers disclosures made from [date before signing]." Better still — sign first, talk second. Three extra days of paperwork. Zero retroactive anxiety.

Mistake 2: "Confidential Information" means nothing. Half the NDAs I read define confidential information as "all information disclosed." That sounds thorough. It isn't. If everything is confidential, nothing is — because no court can tell what was actually secret. Name your categories: customer lists, pricing, source code, designs, financials, business plans. And build a habit of marking sensitive documents "Confidential" before you send them. Specificity is what makes the lock real.

Mistake 3: You downloaded an American template. I can spot these in ten seconds. References to "work for hire" (a US copyright concept), governing law of California, arbitration in Delaware. An Indian court will not be impressed, and enforcing a foreign-jurisdiction clause against an Indian vendor is a slow, expensive hobby. Your NDA should say: governed by the laws of India, disputes in the courts of your city. One line. Huge difference.

Mistake 4: No survival clause. Your NDA says it lasts two years. Lovely. But does the duty of confidentiality survive after those two years? Without a survival clause — "the obligations under this clause survive termination for three years" — the other party is arguably free to talk the day the agreement expires. I've seen NDAs where the protection died before the relationship did. Two to three years of survival is standard. Write it in.

Mistake 5: Wrong direction. NDAs come in two flavours. One-way: only you disclose, only they stay silent. Mutual: both sides disclose, both stay silent. Founders routinely sign one-way NDAs prepared by the other party while disclosing their own secrets in the same meetings. Your pricing just went out unprotected while theirs is wrapped in cotton wool. If both sides will talk, make it mutual. Always.

Mistake 6: No carve-outs, no clean ending. Two clauses people skip, then regret. Carve-outs — the exclusions. Information that's already public, that the other side developed independently, that they received from a third party without restriction, or that a court orders them to disclose: none of this can fairly be called your secret. Without exclusions, the NDA overreaches and gets harder to enforce. And the ending: when the relationship finishes, the other side should return or destroy your confidential material and confirm it in writing. Secrets with no expiry plan have a way of lingering on old laptops.

Now flip the table. Often you're the one being handed an NDA — by an investor, a large client, a potential acquirer. Before you sign theirs, check these:

  • How long does confidentiality survive? Five years is common; perpetual is aggressive. Negotiate it down.
  • Who else can see your information? "Employees and advisors on a need-to-know basis" is fine. Blanket permission to share with affiliates is not.
  • Does it stop you from working with their competitors? Some NDAs smuggle in non-compete language. Read every line.
  • What's the remedy clause? "Irreparable harm" and injunction language means they can rush to court for a restraining order. Know that before you sign, not after.
  • Is it mutual? If you'll be sharing too, say so and make it mutual.

A final practical note. Keep your NDA short — two to four pages. The twenty-page monsters don't get read, and an unread contract is just a slower way to have no contract. Get it signed before the first real conversation, mark your sensitive documents, and store executed copies where you can find them in a hurry. Which is the entire point. An NDA you can't locate when the leak happens is a lock with no key.

The best NDA is the one you never need to enforce. The second best is the one that makes the other side think twice.