A non-compete restricts where and for whom someone can work after leaving a job or business relationship, while an NDA (non-disclosure agreement) restricts what confidential information someone can share, regardless of where they work next. Both protect a company's competitive position, but a non-compete limits a person's future employment or business activity, whereas an NDA limits the flow of specific information. Most businesses use NDAs far more freely than non-competes because NDAs face fewer legal restrictions and less scrutiny from courts and regulators.
A non-disclosure agreement is a contract that stops one or both parties from sharing specific confidential information, such as trade secrets, financial data, or product plans. A non-compete agreement is a contract that stops someone, usually a former employee, from working for a competitor or starting a competing business for a defined period after leaving.
The distinction matters because the two documents solve different problems. An NDA governs information. A non-compete governs conduct and employment. A business can share technical details with a contractor under an NDA without ever restricting where that contractor works next. Conversely, a non-compete can stop someone from joining a rival firm even if they never touch a single confidential file while there.
Here's how the two compare across the factors that matter most in practice:
This is where the two agreements diverge most sharply, and where founders and HR leads get into trouble if they assume the rules are the same for both.
NDAs are enforceable across nearly every jurisdiction, provided the information they protect genuinely qualifies as confidential or a trade secret. Courts generally accept that a business has a right to stop the misuse of its private information, so long as the NDA defines that information clearly and the company took reasonable steps to keep it secret in the first place.
Non-competes are a different story entirely. In the United States, enforceability depends almost entirely on state law rather than federal rule. The Federal Trade Commission attempted a nationwide ban on non-competes in 2024, but a federal court permanently blocked the ban in November 2024, ruling the agency exceeded its statutory authority. In September 2025, the FTC voted 3-1 to abandon its appeal and accept the ruling, ending any realistic prospect of a federal administrative ban for the foreseeable future. The FTC formally struck the rule from federal regulations in February 2026 and has pivoted to targeting individual companies whose non-competes it considers unfair, rather than banning the practice outright.
That leaves a genuine patchwork. Some states, including California, Minnesota, North Dakota, Oklahoma, Washington, and Wyoming, ban most non-competes, while others enforce them with significant restrictions or limit them to higher-wage-earning employees. A clause that's routine in Texas or Florida can be void the moment an employee crosses into California.
The UK tells a similar story with a different mechanism. There are currently no statutory restrictions on non-compete provisions in the UK, and under case law, non-competes will only be enforceable if they are no wider than reasonably necessary to protect a legitimate interest and are not contrary to the public interest. That's now under review. In November 2025, the UK government launched a working paper on options for the proposed reform of non-compete clauses in employment contracts, inviting individuals and organisations to submit views until 18 February 2026. The options on the table range from a statutory time cap to an outright ban, though given the amount of work associated with implementing the Employment Rights Act over the next couple of years, non-compete reform is unlikely to land for some time.
NDAs and non-competes aren't substitutes for each other, and relying on just one usually leaves a gap. A senior employee signs an NDA covering pricing models and client data, and separately signs a non-compete that stops them joining a direct rival for twelve months. The NDA travels with the employee wherever they go next. The non-compete controls where "next" can be.
The same logic applies outside employment. When a business is acquired, the buyer typically wants the seller under a non-compete so they can't immediately reopen a competing shop down the road. But the deal also requires sharing financial records, customer lists, and operational data during due diligence, which is exactly what an NDA is built to protect if the deal falls through.
For founders building a team, this is a practical decision rather than a legal formality. A junior hire with no access to strategic information rarely needs a non-compete and a broad one is unlikely to survive a court challenge anyway. A co-founder or senior engineer with access to the product roadmap and customer list is a different case entirely. Seedling's approach to founder and employee agreements reflects this: match the restriction to the actual risk, rather than defaulting to the most aggressive clause available.
One misconception trips up even experienced operators: an NDA that's drafted too broadly can function as a de facto non-compete, even though it was never labelled as one. Academic research argues that confidentiality agreements that go beyond trade secrecy are not harmless, protecting far more information than trade secret law does and prohibiting use as well as disclosure of the covered information.
In practice, this happens when an NDA defines "confidential information" so broadly that it covers general skills, industry knowledge, or publicly available information the employee would inevitably use in any future role. Courts and regulators, including the FTC, have started scrutinising these agreements the same way they'd scrutinise an unreasonable non-compete. Recent FTC enforcement actions against companies using overly broad restrictive covenants (including a 2026 consent order against Rollins, Inc. covering more than 18,000 employees) signal that regulators are watching this boundary closely, even without a blanket federal rule in place.
The practical takeaway: keep NDAs narrow and specific to genuinely confidential information, and reserve non-compete restrictions for roles where the risk of competitive harm is real and provable. A well-drafted NDA that stays in its lane is far more durable than a sprawling one that tries to do a non-compete's job. For growing teams, that distinction is worth getting right before a dispute forces the issue, not after.
Some common questions, answered
An NDA restricts the use and disclosure of defined confidential information, regardless of where someone works next. A non-compete restricts future employment or business activity, such as joining a competitor or starting a competing business for a defined period.
Courts generally accept narrowly drafted NDAs that protect genuinely confidential information or trade secrets. Non-competes face heavier scrutiny because they restrict work and business activity, and their enforceability varies significantly by jurisdiction, with some US states banning most of them and UK courts applying a reasonableness test.
Yes. An NDA can become a de facto non-compete if it defines confidential information so broadly that it covers general skills, industry knowledge or public information needed in future roles. NDAs should therefore be limited to genuinely confidential information, while non-competes should be reserved for roles where competitive harm is real and provable.