Do You Need an NDA Before Talking to Investors or Contractors in the US?

At some point, every founder asks the same question before a sensitive conversation: should I get an NDA signed first? The honest answer is that it depends entirely on who’s on the other side of the table, and getting that wrong in either direction costs you something.

Ask the wrong person for an NDA, and you can lose the conversation before it starts. Skip one with the wrong person, and you can lose your idea, your code, or your negotiating leverage.

What an NDA Template Actually Covers

A Non-Disclosure Agreement (NDA) is a contract where one or both parties agree not to share confidential information disclosed during a conversation, negotiation, or working relationship. A solid NDA template covers:

• A clear definition of what counts as “confidential information”
• Who the obligation applies to, one party (one-way) or both (mutual)
• Specific carve-outs, like information that’s already public or independently developed
• How long the confidentiality obligation lasts after the relationship ends
• What happens if it’s breached, and what remedies are available

The details matter more than most founders assume. A vague definition of “confidential information” is one of the most common reasons an NDA fails to hold up when it’s actually needed.

Mutual NDA vs. One-Way NDA

Getting this wrong is a common early mistake. Sending a one-way NDA to a potential partner who’s also disclosing their own confidential information tends to read as one-sided and can slow a deal down before it starts.

Why Most VCs Won’t Sign an NDA

This is the part that surprises first-time founders most, and it’s worth knowing before you send one. Most US venture capital firms have a strict policy of not signing NDAs before a pitch, and pushing the issue can actively hurt your chances of a meeting.

This isn’t because investors plan to steal ideas. Practically, VCs see hundreds of pitches covering overlapping ideas, and signing an NDA for every one would create an unmanageable legal liability if they ever invest in, or have previously heard of, something similar. Reputable investors protect their reputation by not needing your idea badly enough to steal it, and a request for an NDA at the pitch stage is often read as a signal of inexperience rather than diligence.

The practical takeaway: don’t lead with an NDA when raising. Share what’s needed to get investor interest without exposing your most sensitive technical details, and save the NDA (or move to a term sheet with confidentiality provisions built in) for once real diligence begins.

When You Actually Need One

NDAs earn their place in a specific set of situations, not every conversation:

• Before sharing proprietary code, technical architecture, or trade secrets with a contractor or dev shop before a contract is signed
• Before discussing a potential partnership, licensing deal, or acquisition where both sides share sensitive business information
• Before bringing on a potential co-founder who needs to see product details to decide whether to join
• Before sharing financial models, cap tables, or investor lists with a party who isn’t already an investor

Notice what’s not on this list: cold investor outreach, early customer discovery conversations, or public-facing partnership pitches. If the information isn’t genuinely sensitive, or the other party won’t sign one anyway, an NDA isn’t the right tool for the moment.

A Quick Example

A founder shares a working prototype and full technical documentation with a freelance developer to scope out a build, with no NDA in place, just a friendly WhatsApp conversation and a shared Figma file. The developer later builds something similar for another client.

There’s no signed agreement establishing that information was confidential, so there’s little practical recourse. Compare that to a founder who sends a two-page mutual NDA before the first technical conversation. It costs nothing but a signature, and it establishes, in writing, that what was shared was confidential and not to be reused elsewhere.

Neither scenario guarantees good or bad behavior. The NDA just gives you something to stand on if it goes wrong.

Why This Matters More for Cross-Border Founders

If you’re a Nigerian founder engaging with contractors, partners, or investors across borders, a few things make this more important, not less:

Jurisdiction and enforceability need to be specified. An NDA should state which country’s law governs it and where disputes would be resolved. Cross-border enforcement is harder in practice, which makes getting the agreement itself clear even more important.

Informal channels are common, and risky. A lot of early technical and business conversations happen over WhatsApp, email, or a casual call, exactly the kind of setting where nobody thinks to formalize confidentiality until something’s already been shared.

US-based counterparties may expect one as standard practice. Contractors, dev shops, and potential partners based in the US often expect an NDA as a normal first step in a working relationship, and not having one ready can make a founder look less prepared.

Common Mistakes Founders Make With NDAs

• Sending an NDA to investors at the pitch stage, which can cost the meeting rather than protect the idea
• Using a one-way NDA in a two-way relationship, which reads as one-sided and can stall a deal
• Leaving “confidential information” vaguely defined, which weakens the agreement if it’s ever actually enforced
• Treating an NDA as a substitute for a proper contract, like an IP Transfer Agreement, when work is actually being done rather than just discussed

Getting an NDA Template Without the Legal Bill

An NDA doesn’t need a custom drafting engagement every time you need one signed. If you’re incorporating in the US, an NDA template built for founder conversations, contractor scoping, and early partnership talks gives you both mutual and one-way versions ready to send.

It’s part of the same document bank for founders incorporating in the US as our Co-Founder Agreement, Share Vesting Agreement, and IP Transfer Agreement templates, so your founder, equity, and confidentiality documentation all work together as one set.

FAQ

Should I send an NDA before my first investor meeting? Generally no. Most US VCs won’t sign one, and asking can cost you the meeting. Save sensitive technical detail for after there’s real investor interest, and use an NDA once formal diligence begins instead.

What’s the difference between an NDA and a confidentiality clause in another contract? An NDA is a standalone agreement focused only on confidentiality. A confidentiality clause is a section within a larger contract, like an IP Transfer Agreement or Advisor Agreement, that covers the same ground alongside other terms. Either can work, but they shouldn’t be assumed to exist if you haven’t checked.

How long should an NDA last? Most startup NDAs run 1 to 3 years from signing, though information that qualifies as a genuine trade secret can be protected indefinitely under separate trade secret law, regardless of what the NDA itself says.

Do I need a lawyer to make an NDA enforceable? Not necessarily, a clear, properly drafted template covers most standard situations. Where it’s worth getting a lawyer involved is in genuinely high-stakes situations, like acquisition talks or licensing deals involving significant value.

The Bottom Line

An NDA is a useful tool in specific situations, not a default step before every conversation. Know when to use one, know when asking for one works against you, and make sure the one you do send is actually built to hold up if it’s ever tested.

If you’re incorporating in the US and want your confidentiality and founder documentation set up properly from the start, start here.