At some point in the early life of almost every startup, someone will suggest you need an NDA. Sometimes they are right. Sometimes what they actually mean is a non-compete, or a non-solicitation agreement, or some combination of all three. The terms get used loosely, and that looseness creates real gaps in protection.
Here is what each document actually does, when you need it, and where founders most commonly get this wrong.
What an NDA does
A non-disclosure agreement, or NDA, is a confidentiality contract. It prevents the person who signs it from disclosing information you have designated as confidential. That is the entire purpose. It does not prevent someone from competing with you. It does not prevent them from hiring your employees. It only restricts what they can share with others.
NDAs come in two forms. A mutual NDA protects both parties, which makes sense when two companies are sharing sensitive information with each other, such as during partnership discussions or due diligence. A one-way NDA protects only the disclosing party, which is appropriate when you are sharing sensitive information with someone who is not sharing anything confidential in return.
For early-stage startups, the most common use cases for NDAs are conversations with potential hires before an offer is made, discussions with vendors or contractors who will have access to proprietary systems or information, early investor conversations where you are sharing non-public financial or product details, and partnership or integration discussions with other companies.
What an NDA does not do
This is where founders most often get into trouble. An NDA does not prevent someone from building a competing product using only their own knowledge and independently developed work. If a potential hire signs your NDA, learns about your product in an interview, declines the offer, and then builds something similar using what they already knew before talking to you, the NDA does not give you recourse. It only applies to information they learned from you that was clearly designated as confidential.
NDAs are also limited by what you can actually prove. If you share your roadmap with a potential partner under NDA and they later build a competing feature, proving that they used your confidential information rather than arriving at the same idea independently is genuinely difficult.
What a non-compete does
A non-compete agreement restricts someone from working for a competitor or starting a competing business for a defined period of time and within a defined geographic or market scope. Unlike an NDA, a non-compete is not about information. It is about activity.
Non-competes are most commonly used in employment agreements, co-founder agreements, and acquisition deals. The logic is straightforward: if you are paying someone or giving them equity, you want some assurance that they will not immediately take what they have learned and use it directly against you.
The enforceability problem
Here is the part that surprises most founders. Non-competes are not enforceable everywhere. California does not enforce them against employees at all, with very limited exceptions. Several other states have significantly restricted their use in recent years, and the Federal Trade Commission has been moving toward broader restrictions on non-competes at the national level.
Even in states that do enforce non-competes, courts will scrutinize the scope and duration. A non-compete that prevents someone from working in any technology company anywhere in the world for five years is not going to hold up. A non-compete that prevents a senior engineer from joining a direct competitor in the same market for one year has a much better chance.
If you are using non-competes in your founder agreements or employment contracts, the clause needs to be tailored to your jurisdiction and drafted with enough specificity to be defensible.
Non-solicitation agreements
A non-solicitation agreement is narrower than a non-compete and generally more enforceable. It prevents a departing founder or employee from recruiting your team members or approaching your customers for a defined period after they leave.
Non-solicitation clauses are worth including in both co-founder agreements and employment contracts. Losing a key employee who then recruits three more people on the way out is a real risk, and a non-solicitation agreement gives you a legal basis to push back.
What most early-stage startups actually need
For most founding teams at the early stage, the priority is threefold. First, a mutual NDA for substantive conversations with outside parties before any formal relationship is established. Second, IP assignment and confidentiality obligations in your co-founder agreement, which function as a more targeted and enforceable form of protection than a standalone NDA. Third, non-solicitation clauses in both your co-founder agreement and any employment agreements you issue.
Non-competes are worth including where they are enforceable and where the scope is reasonable, but do not rely on them as your primary protection. They are harder to enforce than most founders expect and will not substitute for clear IP assignment and confidentiality provisions.
A note on asking everyone to sign NDAs
Some founders ask every investor, advisor, and potential hire to sign an NDA before any conversation. This tends to backfire. Experienced investors almost never sign NDAs before an initial meeting, and asking them to do so signals that you do not yet understand how early-stage fundraising works. The information you share in early investor conversations is generally not protectable anyway, and the relationship cost of the ask is usually not worth it.
Save NDAs for situations where you are sharing genuinely sensitive technical or commercial information with someone who has a real reason to receive it.
This post is for informational purposes only and does not constitute legal advice. Consult a licensed attorney before drafting or relying on any confidentiality or non-compete agreement.