Non-Compete Clauses for Freelancers: What to Accept and What to Push Back On

Non-compete clauses were built for employees: someone who leaves the company shouldn't immediately work for a direct competitor using what they learned. Freelancers are different. Working for multiple clients, often in the same industry, is the whole business model. A broad non-compete in a freelance contract can effectively stop you working in your niche.

Whether a non-compete is enforceable varies a lot by country and state, and rules keep changing, so don't assume it's harmless just because you've heard they're hard to enforce. Treat it as binding and negotiate accordingly. This is general information, not legal advice.

• Non-compete: you won't work for competitors (or compete yourself) for a period. See the non-compete clause.
• Non-solicitation: you won't poach the client's staff or customers. Usually reasonable. See the non-solicitation clause.
• Exclusivity: you'll work only for this client in a category during the engagement. Reasonable if they pay for it. See the exclusivity clause.

Often what the client really wants is non-solicitation plus confidentiality, and a non-compete was just in their template.

Watch for:

• Vague scope: "any business in the marketing industry".
• Long duration: years after the project ends.
• Wide geography: worldwide, for a local business.
• No compensation: nothing in the fee reflects the work you'll have to turn down.

Ask what they're worried about, then offer a narrower fix:

"I understand you want to protect your product plans. I'd suggest replacing the non-compete with a confidentiality clause and a 12-month non-solicitation of your customers and staff. That covers the risk without stopping me from working in the industry, which is how I serve all my clients."

If they insist on a real exclusivity, price it: "I can agree not to work with named competitors for the duration of the project. That's work I'd be turning down, so it would add [AMOUNT] to the fee."

The client's original:
"For a period of three years after termination, Contractor shall not provide services to any business operating in the software industry."

A narrower counter-proposal:
"During the term of this Agreement and for 6 months after, Contractor will not provide [TYPE OF SERVICE] to the following named competitors of Client: [COMPANY A], [COMPANY B], [COMPANY C]. Contractor remains free to work for any other business."

The second version protects the client against the specific risk they care about (their direct competitors getting the same work), for a limited time, without closing off an entire industry. If the client wants the broader version, it becomes a pricing conversation.

• Signing because "they're never enforced". You don't want to be the test case, and the rules differ by place.
• Arguing in principle instead of offering an alternative. Proposing specific narrower wording usually gets further.
• Ignoring existing clients. Check that the clause doesn't conflict with work you're already doing for someone else.
• Agreeing to exclusivity without extra pay. Turning work down has a cost. Price it.
• Missing a non-compete hidden in the definitions, such as a confidentiality clause that forbids using "any knowledge gained".

Is non-solicitation also a problem? Usually much less so. A limited ban on poaching the client's staff or customers is common and reasonable.

What if the client refuses to change anything? Decide whether the project is worth the work you'd be turning down. Sometimes walking away is the right answer.

"Thanks for sending the agreement. Everything looks good except section 12. As a freelancer, I work with several clients in the same sector, so a three-year industry-wide restriction would effectively stop me working. I've suggested a narrower version below that covers your named competitors during the project and for six months after, plus confidentiality and non-solicitation. Does that address your concern?"

Short, specific, and it ends with a question that invites a yes.

A heavy non-compete often travels with other one-sided terms: unlimited indemnity, IP transferring before payment, no liability cap. Paste the contract into the contract red flags checker to spot them, and read 10 red flags in a client's contract.

Often the simplest move is to propose your own contract, with fair confidentiality and non-solicitation already built in, like the independent contractor agreement. Draft it now with Clinch: describe the job in a sentence, get a clean draft, send one link. Your client signs from their phone without an account, and the deposit is paid in the same step.