Ask the BattleTested Lawyer: Do I Really Need 3 Different NDAs?

Ask the BattleTested Lawyer

Every week, founders bring me the questions they're actually Googling at 1 a.m. This week it was NDAs — specifically, why one isn't enough, and how a founder with a "good" NDA still lost his entire backend. I've litigated these cases on both sides of the table. Here's how the conversation went.

Do I really need more than one NDA? Isn't one enough?

You need three, and using the wrong one — or none at all — is one of the most expensive mistakes I've watched founders make. Most founders own one NDA. Some own none. Using a single NDA for every situation is like using one key for your house, your car, and your safe. The reason you carry different keys is the same reason you need different NDAs: they protect different things, in different directions, against different risks. A document built for one situation will be wrong for the other two. Each of the three points a different way — one protects you while you talk, one protects a two-way exchange, one protects you from the people already inside your business. One key can't open three different locks.

Which NDA do I use when I'm pitching an investor?

The Founder's Disclosure NDA — that's the one you use when you're the one talking and the other side is listening. Pitching an investor, showing a manufacturer your product, walking a partner through your model. The protection runs one direction, toward you, and it should be written in your favor, with the assumption that something will go wrong, because it sometimes does. It defines your idea broadly, bars the other side from using it or building it, and keeps them from circling around you to your people. Sign it before a single word of your idea leaves your mouth. And remember who you're usually talking to: an investor at your level or above, with the resources to act on what you showed them. If you only master one of these, master this one — the pitch is where ideas get taken.

What about when I'm exploring a partnership and we're both sharing sensitive info?

Then a one-directional NDA is the wrong tool for that room. When both parties are about to share — a partnership, a joint venture, an acquisition conversation — you want a Mutual NDA. A one-sided agreement signals you want protection without offering any, and a sophisticated counterparty will push back. A mutual NDA protects both sides, which is exactly what makes the other party comfortable enough to actually open up. The biggest mistake here is signing whatever the other side sends you without reading their definition of confidential information. If their definition is narrow and yours is broad, your protection isn't equal. Define what each side is bringing to the table, so there's never a fight later over whose information it was in the first place.

What protects me from a contractor or freelancer stealing my work?

The Inside-the-Tent NDA — and this is the one founders forget, which makes it the most dangerous gap. Your contractor, your freelancer, your VA, your designer, your systems person, your first hire — these people don't just hear your idea. They live inside your business. They see the client list, the pricing, the processes, the proprietary systems, the financials. I call the insiders the challengers, one of the five enemies every business faces, and they're dangerous precisely because you trust them. This NDA protects everything they see, not just what you tell them. And it should carry two more provisions: a non-solicitation clause so they can't walk out and take your clients or your team, and an IP assignment so everything they build for you actually belongs to you, not to them.

I heard you tell a story about a founder who had a good NDA and still got burned. What happened?

He did everything right — with the wrong document. He had a solid disclosure NDA and used it faithfully with every investor. He felt covered. Then a contractor who'd built his entire backend left, took the code, and started selling a competing version. The disclosure NDA he'd been so proud of said nothing about work product and nothing about a contractor's obligations. Wrong key, wrong lock. The right document — an inside-the-tent agreement with an IP assignment — would have made that code his, full stop. The lesson isn't that he had a bad NDA. It's that he had the right NDA for the wrong situation. Protection isn't one document you buy once and forget. It's matching the right agreement to the person sitting across from you, every time.

What actually makes an NDA hold up in court?

Match the document to the moment, and make it specific. Start here: not everything you call confidential is actually protected. Under the trade secret rules, information is only protected if it has economic value from not being public and you took reasonable steps to keep it that way. That second part destroys people. Reasonable steps means at least having an NDA in place before you share. Hand a judge the wrong NDA for the dispute, or no NDA at all, and it doesn't matter how serious you were. Beyond that, the three good ones share traits: each defines confidential information by named category instead of leaving it vague; each spells out what the other side can and can't do, not just that they should keep quiet; each sets a real term and a real consequence; and each is written to be read by a judge, not just signed and filed in a drawer. If your definition is the vague "all information shared between the parties," a court will throw it out as too broad. Named categories win. Vague language loses — and in court, the burden is on you.

So what should I actually own?

Three documents, each for its own job. The Founder's Disclosure NDA, for when you're pitching and disclosing. The Mutual NDA, for two-way conversations with partners or buyers. And the Inside-the-Tent NDA with IP assignment and non-solicitation, for contractors, freelancers, and early hires. Own all three and you stop forcing one document to do three jobs it was never written for.

Want to legally bulletproof your business, for free? Start with the free Legal Risk Report and find your blind spots in minutes.

About the Author — Karam Nahas, The BattleTested LawyerTM. A 20-year courtroom veteran who has handled over $1 billion in deals and real litigation, Karam founded Legally BulletproofTM to give entrepreneurs the same legal defense systems big companies use — without big-law prices.

Ready to lock it down? Visit the Contract Library — every contract comes with the training and a 20-year lawyer inside your business, starting as low as $197, and it’s constantly updated and customized.

Educational content, not legal advice.