Non-Compete vs Non-Solicitation Agreement: What's the Difference

A non-compete and a non-solicitation agreement both show up in the same restrictive-covenant conversation, and they get treated as interchangeable more often than they should be. They are not. A non-compete restricts where someone can work after they leave: it can bar them from taking a job with a competitor or starting a competing business at all, regardless of whether they ever contact a single client or coworker from their old job. A non-solicitation agreement doesn’t care where the person works next. It restricts who they can contact: it bars them from poaching specific clients or specific coworkers, no matter what job they take. A departing employee can join a direct competitor the next day under a non-solicitation agreement, as long as they don’t call the client list or recruit their old team. Under a non-compete, taking that job is the violation, full stop.

The difference matters beyond definitions because the two clauses are enforced very differently. Courts across most states are far more willing to enforce a non-solicitation clause than a non-compete, because it restrains a narrower slice of the person’s ability to earn a living, and that gap changes which document actually protects the business when someone leaves.

What a Non-Solicitation Agreement Actually Restricts

A non-solicitation clause comes in two flavors, and a well-drafted agreement usually addresses both separately rather than lumping them into one sentence. A customer or client non-solicit bars the departing person from soliciting business from, or accepting business from, clients they had material contact with during a defined period before they left, usually the last twelve months of employment. It doesn’t stop them from working with clients they never touched, and it doesn’t stop a client from following them of its own accord if the client reaches out first rather than being solicited, a distinction that matters a lot if the clause ever gets tested.

An employee or coworker non-solicit bars the departing person from recruiting former colleagues to follow them to a new employer or a competing venture they start. This one protects team stability rather than client revenue, and it’s the clause that stops a departing manager from quietly lining up three teammates to join them at the new company before anyone else notices the manager is leaving.

Neither version needs a geographic scope the way a non-compete does, because the restriction isn’t tied to a place. It’s tied to a defined list of people (or a definable category of people, “clients the employee had material contact with”) and it travels with the person wherever they go. That’s a genuinely useful drafting shortcut: a non-solicitation clause doesn’t have to guess at a reasonable mile radius or state boundary, it just has to define who counts as a protected client or employee and for how long after departure the restriction runs.

What a Non-Compete Actually Restricts

A non-compete is a broader ask. It restricts the type of work the person can do at all, for a defined period, usually within a defined geographic area and a defined line of business, whether or not they ever contact a former client or recruit a former coworker. That breadth is exactly why courts scrutinize it more heavily: a non-compete limits someone’s ability to earn a living in their own field, not just their ability to take specific business or people with them.

Because of that scrutiny, non-compete enforceability depends heavily on which state’s law governs the agreement. Non-Compete Agreements: What’s Enforceable State by State covers the full breakdown, but the short version is that a handful of states void non-competes against employees almost entirely, a growing group restricts them to employees above an income threshold, and most other states apply a reasonableness test to scope, duration, and geography.

Why Non-Solicitation Clauses Hold Up Better

A non-solicitation agreement is generally treated as a narrower restraint of trade than a non-compete, which is why it tends to survive in more states, including several where a non-compete against the same employee would be void outright. The reasoning courts give is consistent: restricting who someone can contact leaves them free to work anywhere, in any role, for any employer, including a direct competitor, so it doesn’t raise the same public-policy concern about locking a worker out of their field.

That said, “generally more enforceable” isn’t “always enforceable everywhere,” and the gap has narrowed in at least one important state. California’s Business and Professions Code Section 16600 doesn’t just void non-competes, and California courts have applied the same broad restraint-of-trade rule to employee non-solicitation clauses too, not only customer non-solicitation. A customer non-solicit built around protecting an actual trade secret, a genuinely confidential client list rather than public contact information, can still hold up there under trade secret law even when the contract clause standing alone would not. The practical lesson is the same one that applies to non-competes: check the state before assuming either clause is enforceable, rather than assuming a non-solicitation label alone makes it bulletproof.

Drafting a Non-Solicitation Clause That Actually Holds Up

The same drafting mistake that weakens a non-compete weakens a non-solicitation clause: vague language that sounds protective but gives a court nothing specific to enforce. “Employee may not solicit clients of the Company” doesn’t say which clients, for how long, or what counts as soliciting versus simply being contacted by a client who chose to follow them. A court asked to enforce that language has to fill in the gaps itself, and an overbroad reading is exactly the kind of thing that gets a clause narrowed or thrown out.

The specific version names the protected group, the lookback window that defines who counts, and the exact duration the restriction runs after departure. That’s the difference between a clause a court can actually apply and one that just sounds like protection.

Can You Use Both?

Plenty of employment relationships call for both clauses at once, and they aren’t redundant when they do, because they cover different risks. A sales lead with direct client relationships is the clearest case: the non-solicitation clause protects the specific accounts they managed, and a non-compete, where your state actually enforces one, keeps them from taking their entire skill set and client instinct straight to a named competitor down the street. A software engineer with no client-facing role and no direct reports rarely needs the employee non-solicit at all, and often doesn’t need the non-compete either, since the real risk with that role is a confidentiality leak rather than a poached client list. What to Include in an Employment Contract covers where non-compete and non-solicitation language sits relative to compensation, IP assignment, and termination terms when they’re drafted as clauses inside a single agreement rather than standalone documents.

Building either clause matched to your state’s rules, rather than reusing language written for a different state’s employment law, is what the Non-Compete Agreement generator is built to do. If you’re weighing a non-compete against confidentiality protection instead of a solicitation restriction, NDA vs Non-Compete Agreement covers that separate comparison, since an NDA, a non-solicitation clause, and a non-compete each answer a different question about what a departing employee can do next.

The short version: if the risk is someone taking your clients or your team with them, draft a non-solicitation clause and define exactly who it protects. If the risk is that person working for a competitor at all, regardless of who they contact, that’s a non-compete question, and it comes with a state-by-state enforceability check the non-solicitation clause mostly avoids.