Compliance

Non-Compete and NDA Basics for Small Business

What non-competes and NDAs each actually protect, why non-competes are increasingly unenforceable, and when a small business genuinely needs either.

TS
The SimplyPTO Team
Sep 4, 2026 · 5 min read
SimplyPTO

Non-competes and NDAs get used almost interchangeably in casual conversation, but they protect different things, face very different legal treatment, and call for very different judgment about when a small business actually needs either one.

We're not employment lawyers, and this varies significantly by state and is genuinely in flux at the federal level — treat this as the concepts to understand, not a substitute for legal advice before using either document.

What each one actually does

An NDA (non-disclosure agreement) protects confidential information. It prevents someone from sharing trade secrets, client lists, pricing strategy, or other proprietary details — but it doesn't stop them from working for a competitor, doing similar work, or using their general skills and experience elsewhere.

A non-compete restricts where and how someone can work after leaving — commonly a defined time period, geographic area, and type of role they're barred from taking with a competing business. This is a fundamentally more restrictive tool, and it's treated far more skeptically by courts and legislatures than an NDA.

Why non-competes are increasingly hard to rely on

Enforceability of non-competes varies enormously by state. Some states ban them for most employees outright, or only allow them above a certain compensation threshold. Others will enforce a non-compete only if it's narrowly scoped — a reasonable time period, a genuinely limited geographic area, and a role restriction tied to real competitive risk, not a blanket restriction on working in the same industry anywhere. Federal-level rulemaking specifically targeting non-competes has also been active and shifting, which makes this an area where checking current law before relying on one matters more than usual.

The practical implication for a small business: a broad, generic non-compete applied to most or all employees is increasingly likely to be unenforceable where it matters most, and can create real friction and ill will with employees for a restriction that may not even hold up if tested.

When a non-compete might genuinely make sense

A narrow, carefully scoped non-compete is most defensible for a small set of senior or highly specialized roles with real access to competitively sensitive information or relationships — someone who built and owns the primary client relationships in a sales-driven business, for instance, or a senior technical role with access to genuinely proprietary methods. Even then, it should be as narrow as possible: the shortest time period that reasonably protects the actual interest, the smallest geographic area, and the most specific description of the restricted activity — broad, generic language is both more likely to be struck down and more likely to appear designed to suppress ordinary career mobility rather than protect a legitimate interest.

When an NDA makes more sense than a non-compete

For the large majority of roles, an NDA covers the real risk more precisely and with far less legal fragility. If the actual concern is "I don't want this person sharing our client list or pricing with a competitor," an NDA addresses that directly without also restricting where they can work — which is both the less legally contested tool and the one less likely to generate resentment or turn into a recruiting disadvantage.

A simple decision framework

Does this role have access to genuinely confidential information (client data, pricing, proprietary processes)? If yes, an NDA is reasonable regardless of seniority.

Does this role have a level of access or relationships where working for a direct competitor immediately afterward would cause real, specific harm — not just general discomfort? If yes, and only then, a narrowly scoped non-compete might be worth discussing with an employment attorney, checking your state's current enforceability rules first.

Is this a general staff or junior role with no unusual access? A non-compete here is both likely unenforceable in many states and disproportionate to any real risk — an NDA, if any restriction is needed at all, is the more appropriate tool.

What to avoid

A blanket non-compete applied to every new hire regardless of role, which is both increasingly likely to be legally void in many states and a real friction point in hiring, since candidates increasingly ask about and push back on broad non-competes during negotiation.

Vague, overly broad NDA language that tries to define "confidential information" so expansively it covers essentially everything, which can make the whole agreement look overreaching and, in some cases, weakens its enforceability rather than strengthening it.

Using either document as a substitute for genuinely valuable work and fair treatment. Neither an NDA nor a non-compete meaningfully substitutes for the reasons people actually stay — real reasons for retention matter far more day to day than a restrictive agreement signed once at hire and rarely thought about again.

Auditing existing agreements

If your business already has non-competes on file from before current, more restrictive state or federal rules took effect, it's worth a periodic review rather than assuming older agreements remain fully enforceable indefinitely. Law in this area has been genuinely active and shifting in recent years — an agreement that was standard practice when signed may no longer hold up the way it once would, and relying on an outdated agreement without checking creates a false sense of protection that could matter at exactly the wrong moment.

What to do instead of leaning heavily on restrictive agreements

Given how uncertain non-compete enforcement has become in many states, it's worth investing at least as much thought into the things that genuinely reduce the risk a non-compete was meant to address: strong client relationships that are institutional rather than tied to one person, reduced key-person concentration through cross-training, and a well-drafted NDA covering the specific confidential information that actually matters. These measures work regardless of which state's non-compete law applies, and they address the underlying business risk more directly than a restriction on someone's future employment ever fully could.

The short version

An NDA protects confidential information and is broadly useful and enforceable; a non-compete restricts future employment and is increasingly narrow, state-dependent, and hard to rely on except in carefully scoped, genuinely justified situations. Most small businesses need NDAs for roles with real information access, and should use non-competes sparingly, narrowly, and only after checking current state law with an employment attorney.

Frequently asked questions

Are non-compete agreements still enforceable?

Enforceability varies enormously by state — some ban them for most employees outright, others enforce them only if narrowly scoped in time, geography, and role, and a few enforce them fairly broadly. Federal rulemaking on non-competes has also been in flux, so check current law before relying on one.

What's the difference between an NDA and a non-compete?

An NDA protects confidential information — it stops someone from sharing trade secrets or proprietary details, but doesn't stop them from working for a competitor. A non-compete restricts where someone can work after leaving, which is a much broader and more contested restriction.

Does a small business need an NDA?

Often yes, if employees or contractors have access to genuinely confidential information — client lists, pricing, proprietary processes. NDAs are broadly enforceable across states in a way non-competes increasingly are not, and cause far less friction to use.

Should every employee sign a non-compete?

Almost never. Non-competes make the most sense, where enforceable at all, for a narrow set of senior or highly specialized roles with real access to competitive information — applying one broadly to junior or general staff is both often unenforceable and can appear designed to suppress mobility rather than protect a real interest.

Related in Policies & Compliance

Stop tracking PTO in a spreadsheet

SimplyPTO tracks balances, requests, and approvals automatically — with a shared team calendar. Free for up to 10 people, no credit card.

Get started free →