Freelance Non-Compete: Should You Sign It?
A non-compete clause asks you to trade away future income for a client who may only need you for eight weeks. Whether that trade is worth it depends on exactly what it says.
What this clause looks like
A freelance non-compete clause restricts who you can work for after — sometimes even during — a project, usually framed as protecting the client's competitive position. A typical version looks like this:
Three things make this version worse than it needs to be: the twelve-month tail after the project ends, the vague "same industry or market" scope (which could mean literally every other client you'd ever want in that space), and "substantially similar to the Services" — which for most freelancers is the entire skillset they market themselves on.
Why it costs you money
Model the real cost before you sign, not after. A freelance copywriter who signs a broad non-compete with one SaaS client can lose access to every other SaaS client for a year — not because any of them are direct rivals to the one who hired her, but because "the same industry" reads broadly enough to cover the whole category she specializes in and markets herself for. If SaaS copywriting is 70% of her pipeline, that single clause can cost more in lost future work than the entire project paid.
The mechanics compound for anyone who works in a niche. Freelancers build expertise by staying inside a lane — fintech design, e-commerce development, healthcare content — and a broad non-compete asks you to abandon exactly the specialization that makes you valuable, for exactly the period after this project when that specialization would otherwise be paying off. The client is asking you to trade your positioning for their peace of mind, on a project that might only run eight weeks.
There's also a legal wrinkle worth knowing: in many US states (California outright bans non-competes for independent contractors in most circumstances; several others restrict them heavily) and in a growing number of other jurisdictions, a broad non-compete against a freelancer is unenforceable on its face. That doesn't make it harmless to sign — an unenforceable clause can still scare off a future client's legal team during due diligence, or cost you the legal fees to fight it even if you'd ultimately win.
Non-compete vs. non-solicit — know the difference
Clients conflate these two constantly, and the difference is the whole negotiation. A non-compete stops you from doing similar work for anyone in the client's space. A non-solicit — much narrower — only stops you from actively pitching the client's specific employees, customers, or named accounts to poach them. A non-solicit protects what the client actually cares about (their team, their book of business) without touching your ability to earn a living in your field. If a client's real concern is you taking their staff or their exact customer list, a non-solicit gives them that protection at a fraction of the cost to you.
The counter-language to send
You don't have to refuse outright — that can read as evasive even when your instinct is right. Instead, name the trade you're actually willing to make. This is the base language FairClause's free check suggests when it flags a non-compete clause:
That's the strongest version — confidentiality protects the client's actual secrets without restricting your income at all. If the client insists on some form of restriction, negotiate down the three dimensions that matter, in this order: scope (narrow it to genuinely competing products, not the whole industry), duration (cap it at three to six months, not twelve), and specificity (limit it to the exact client account or product line you worked on, not "the market"). A non-compete narrowed on all three axes is a very different — and often acceptable — commitment from the one most templates start with.
When it might actually be reasonable to sign
Not every non-compete is worth fighting. A short, narrow one can be a fair trade in specific situations: you're being paid a premium specifically for exclusive access during a product launch window, the restriction is capped at 90 days, and it's scoped to the one or two named direct competitors rather than an entire sector. If the money reflects the restriction — meaning you're being compensated for the exclusivity, not just asked to give it away — it can be a rational deal. The test is whether the clause is proportionate to what you're actually being paid, not whether non-competes are inherently unacceptable.
When to walk away
Treat an unmovable, broad non-compete as a signal about the relationship, not just the paperwork. A client whose legal team won't narrow a twelve-month, industry-wide restriction for a six-week project is telling you they see you as a resource to lock down rather than a specialist to hire for a specific job. That posture tends to show up elsewhere too — in scope creep, in payment terms, in how disputes get handled. If the client won't move on scope, duration, or specificity even after you've explained the actual cost to your business, it's reasonable to decline the project rather than accept a restriction that could outlast the value of having done it.
Frequently asked questions
Are non-competes even enforceable against freelancers?
It varies by jurisdiction and depends heavily on how the clause is written. Several US states restrict or ban them for independent contractors, and courts elsewhere often narrow overly broad ones rather than enforcing them as written. Enforceability isn't a reason to sign a bad one carelessly — you may still face legal costs to establish it doesn't apply, and it can complicate future client relationships regardless of the legal outcome.
What's a reasonable duration if I have to accept some restriction?
Three to six months is a common, defensible range for freelance work — long enough to protect a genuine competitive window, short enough not to meaningfully damage your business. Twelve months or longer is difficult to justify for most short-term freelance engagements and worth pushing back on directly.
Can I negotiate a non-compete into a non-solicit instead?
Yes, and it's often the fastest path to agreement. Explain that a non-solicit — protecting the client's specific staff and accounts — addresses their real concern (someone poaching what's theirs) without restricting your ability to work in your field. Most clients accept this once they see it covers what they actually cared about.
Does signing an exclusivity clause count as the same thing?
It's related but stricter — exclusivity typically bars you from working for anyone else at all during the engagement, not just competitors, and deserves the same scrutiny on duration and scope. See the exclusivity entry in the red flags list for how to narrow that one specifically.
What if the client offers extra pay in exchange for the restriction?
That can make it a fair deal — treat the extra pay as the price of the restriction and check it actually covers what you'd realistically lose in future work from competitors during the restricted period. If the premium is token (a small bump that doesn't come close to covering a year of lost pipeline), the math still doesn't work in your favor.
Check your own contract first. FairClause reads it in your browser, names the clauses that hurt you, and drafts the counter-language for each one. Nothing is uploaded.
Also see: 21 contract red flags freelancers shouldn't sign, unlimited revisions clause: how to push back, pay-when-paid clause: why it's risky, kill fee clauses: what's fair, and how to negotiate a freelance contract.
FairClause is automated pattern analysis and drafting help, not a law firm and not legal advice. Non-compete enforceability varies significantly by jurisdiction. For anything binding, talk to a licensed lawyer where you are.