Should a Freelance Contract Have a Non-Compete? Usually No — Here Is Why

Why freelance non-competes are unusual

The premise of a non-compete is that one party — the employer — has invested in another party so substantially that some restriction on competition is needed to protect the investment. The employer trained the employee, gave them access to confidential information, paid them a salary while they developed skills the company funded. A short, narrow non-compete in that context can be a reasonable allocation of risk.

In a freelance relationship, that premise mostly does not apply. You came to the engagement with your skills already developed; the client did not train you. You are working for a fee on a defined project, not earning a salary while you build their proprietary value. You are simultaneously running a business that probably serves other clients in the same space. A non-compete restricting your ability to work with others in your industry effectively asks you to subsidize one client by limiting your business, which is not what either side typically agreed to in the rest of the contract.

When non-competes against contractors are enforceable

That said, non-competes against independent contractors can be enforceable in some states under some conditions. Where they survive scrutiny, courts typically look for the same reasonableness factors as in employment cases: a narrow scope (defined competitors, not the whole industry), a short duration (six months to a year is far more defensible than two-plus years), a limited geography (the area where you actually competed, not nationwide), and a legitimate protectable interest (genuine trade secrets, specific client relationships you developed through this engagement, not general industry knowledge).

A few states make non-competes harder for contractors even than for employees. California’s near-total ban on non-competes (Business and Professions Code §16600) applies regardless of whether the worker is an employee or a contractor. Other states have specific protections for independent contractors, restrictions on assignment, or higher reasonableness bars. So as with employee non-competes, your state of residence (or where you actually work) matters enormously.

How a freelance non-compete can wreck your business

The real problem with a freelance non-compete is the cumulative effect on your business. Suppose you are a designer who takes on a client in the consumer-electronics space. They want a non-compete that prevents you from working for any other consumer-electronics company for a year. If that becomes a habit — every client wants the same restriction — within a couple of years you have non-competes stacking up that exclude you from large parts of your industry, with no compensation to make up for it. Each client has restricted only "their" patch of the market, but together they have shrunk your business to almost nothing.

A freelance non-compete is rarely worth the fee for that reason, unless the fee specifically and substantially compensates you for being out of the market. Without that compensation, the client is getting a real benefit (your time-bounded exclusivity) for free, while you are absorbing real opportunity cost. That is not a fair trade, and recognizing it is the first step to negotiating better.

Non-compete versus non-solicit

When clients ask for "exclusivity" or restrictions on competing work, what they often actually want is a non-solicitation, not a non-compete. A non-solicit prevents you from approaching the client’s customers or employees for a defined period — protecting the specific relationships you developed through the engagement — without barring you from the whole industry. A non-solicit is far more defensible, far more aligned with the client’s real interest, and far less damaging to your business. If a client raises competition concerns, offering a narrow non-solicit instead of a non-compete often satisfies them, because what they actually care about is their specific clients and people, not the whole market.

When a client insists on a non-compete

Some clients will push for a non-compete despite the issues above. When that happens, your options in order of preference are:

• Decline the non-compete entirely and substitute a focused non-solicit; this is the cleanest fix and often acceptable.
• Narrow the non-compete drastically — a short duration (3 to 6 months), a tightly defined list of specific direct competitors, and a geographic limit matching where you actually worked.
• Require compensation — if the client genuinely needs market exclusivity, they should pay for it; ask for a retainer during the restricted period (garden leave equivalent for contractors).
• Carve out pre-existing client relationships explicitly, so anyone you were already working with before this engagement is not affected.
• Walk away if the client insists on broad terms with no compensation; the deal is not worth what it would cost you.

Confidentiality is the protection clients actually need

In many cases, what a client legitimately needs is not a non-compete but a strong confidentiality clause that protects their actual trade secrets and proprietary information. A well-drafted confidentiality clause lasts indefinitely for true trade secrets and prevents you from using or disclosing the client’s specific information — which is what the client actually cares about — without restricting your ability to work in the industry generally. If a client raises competition concerns, leading with a robust confidentiality clause and a narrow non-solicit often gets them what they need without restricting your business.

Watch for "exclusivity" that is really a non-compete

Some contracts dress non-competes up as "exclusivity" clauses — "the contractor will not perform similar services for any other client during the term of this agreement or for [period] thereafter." That is a non-compete, just with a different label, and the same analysis applies. Similarly, "industry exclusivity" or "client exclusivity" clauses are often non-competes by another name. Read for the substance, not the label, and treat any clause that restricts where else you can work as a non-compete that needs the same scrutiny.

The 1099 misclassification angle

A non-compete in a freelance contract also has a misclassification implication. A defining feature of being an independent contractor — under the IRS test, the ABC test, and most state classifications — is that you operate as your own business and are free to work for other clients. A contract that significantly restricts your ability to work for others looks more like employment than contracting, which can push the relationship toward an employee classification regardless of how the contract labels it. So a broad non-compete in a 1099 agreement is doubly problematic: it harms your business directly, and it weakens the contractor classification both sides are relying on. Many sophisticated clients understand this and avoid non-competes in contractor contracts for exactly this reason.

You can use this point in the negotiation. Telling a client politely that a broad non-compete creates misclassification risk for them — not just a problem for you — often changes the conversation, because they care about that exposure. It frames the request to remove the clause as protecting both sides, which is a more productive framing than a one-sided objection.

How to raise it without losing the deal

When you see a non-compete in a freelance contract, approach the conversation collaboratively. The framing that usually works: "I would love to work on this project. The non-compete clause is a problem for me because [specific reason — it would limit my ability to maintain other client relationships, it conflicts with engagements I am already in, etc.]. Could we replace it with a non-solicit limited to your clients, and a strong confidentiality clause? That gives you protection on the things you really care about — your customers and your information — without restricting my broader business."

Most clients respond positively to this framing because it directly addresses their underlying interest. The clients who insist on a non-compete despite a workable alternative are often using a template they have not thought about, and a clear explanation usually unblocks them. The ones who are unmoved by the substantive case are usually the ones to be cautious about more broadly, because the non-compete request was a signal about how they think about the relationship.

The bottom line

A non-compete in a freelance contract is usually a misfit — it applies an employment-relationship tool to an independent-business relationship, often without the compensation that would make the trade fair. When you see one, the right move is almost always to push back: substitute a focused non-solicit, strengthen confidentiality, and explain that what the client actually wants is achievable without restricting your broader business. If you want a fast read on whether a client contract contains a non-compete, an exclusivity clause that functions like one, or other terms that would harm your business, ClauseAudit reviews the agreement in about a minute, flags every restrictive covenant, and tells you in plain English what each one would cost you — so you push back on the right things before you sign.