A client's contract includes a clause saying you cannot work with any "competing business" for two years after the project ends, and most freelancers either sign it without a second thought or panic and think they have just given up half their future client list. Neither reaction is right, because Indian law treats post-engagement non-compete clauses very differently from how most contracts are written to sound.
Here is what a non-compete clause in a freelance contract actually means in India, what a court will and will not enforce, and what to negotiate instead if a client insists on one.
Post-engagement non-compete clauses are largely unenforceable in India
Under Section 27 of the Indian Contract Act, 1872, any agreement that restrains a person from exercising a lawful profession, trade, or business is void, with narrow exceptions mostly relevant to the sale of a business, not freelance service contracts. This means a clause preventing you from working with a client's competitors after your engagement ends is generally unenforceable in an Indian court, regardless of how firmly it is worded or how long the client's lawyer made it sound.
This is genuinely different from how non-compete law works in many US states, and freelancers who have worked with international clients sometimes assume the clause carries the same weight it would there. It does not. Indian courts have consistently struck down post-termination restraints on trade because the law treats a person's right to earn a livelihood as something a private contract cannot sign away. This guide covers freelance and independent-contractor engagements specifically; employer-employee non-compete disputes follow a related but separate line of case law and are outside the scope here.
What courts will actually enforce, during the engagement
A restriction on working with direct competitors while the engagement is active is a different matter entirely and is generally enforceable, since it is a reasonable protection of the client's legitimate business interest during the time you are actively working for them, not a restraint on your future livelihood. A client asking you not to take on a directly competing project while you are mid-engagement with them is asking for something a court will likely uphold.
The distinction that matters is timing, not the existence of the clause itself. "You cannot work with our competitors while this contract is active" holds up. "You cannot work with our competitors for two years after this contract ends" generally does not, under Section 27. Read every non-compete clause specifically for which of these two it actually says, since contracts are often written broadly enough to sound like the second when a narrower reading might apply.
What clients actually want, and the clauses that deliver it legally
When a client pushes for a non-compete, what they usually actually want is protection against you taking their confidential information or their specific employees and customers to a competitor, not a blanket ban on your entire career path. A confidentiality clause (protecting their proprietary information indefinitely) and a non-solicitation clause (restricting you from actively poaching their specific employees or customers for a defined period) both achieve this and are far more likely to be enforceable than a broad non-compete.
If a client insists on a non-compete despite this, propose swapping it for a strong confidentiality and non-solicitation combination instead, and explain plainly that the non-compete as written is unlikely to hold up anyway, so both sides are better served by clauses that actually protect what the client cares about. Most clients or their lawyers understand this once it is explained, since the goal was never really to stop you from ever working in the industry again. For the confidentiality side of this specifically, see the guide on freelance NDAs in India, which covers what a confidentiality agreement should and should not restrict, including how a non-compete sometimes hides inside an NDA's language rather than appearing as its own clause.
What to actually check before signing
Read the clause for whether the restriction applies during the engagement only or extends after it ends, since that single detail determines whether it is likely enforceable at all. Check the scope: does it name specific competing businesses, or does it vaguely restrict "any business in the same industry," which is broader and harder to justify. Check whether a territory is specified (a restriction covering all of India versus one covering a specific city or client relationship) and whether a duration is stated at all, since an open-ended restriction is even less likely to be upheld than one with a defined end date.
Also check whether the non-compete language is its own standalone clause or buried inside a longer confidentiality or NDA section, since it is common for a non-compete restriction to be worded as part of a "confidentiality and exclusivity" clause rather than labelled clearly on its own. A vague, broad clause is a sign the contract was templated from elsewhere without much thought, not necessarily a sign of bad intent, but still worth pushing back on before signing. For the broader set of clauses every freelance contract should be checked for, see the freelance contract guide for India.
Should you push back, or just sign it anyway
Pushing back on an unenforceable clause before signing is almost always the better move than signing it and assuming it will never come up, since even an unenforceable clause can still create real friction: a client might genuinely believe it holds, threaten legal action based on that belief, or simply refuse to hire you again if you are later found working with a competitor, regardless of what a court would ultimately decide. A short, polite note (something like: "happy to agree to confidentiality and non-solicitation, but a post-engagement non-compete like this typically is not enforceable under Indian law, so I would suggest we adjust it to those two clauses instead") resolves this before it becomes a dispute.
Rinto's contract templates for project work let you send an agreement built around approved, standard clauses like confidentiality and scope, so you are working from a template designed for freelance engagements rather than a client's own boilerplate that may carry unenforceable or overly broad language by default.
Frequently Asked Questions
Are non-compete clauses enforceable for freelancers in India?
Generally not, if the restriction applies after the engagement ends. Under Section 27 of the Indian Contract Act, 1872, any agreement restraining a person from exercising a lawful profession or trade is void, with narrow exceptions unrelated to freelance service contracts. A restriction that applies only during an active engagement is a different matter and is generally enforceable, since it protects the client's legitimate interest while you are actively working for them.
What should I do if a client's contract includes a non-compete clause?
Read it carefully for whether it applies during the engagement or extends after it, and check the scope, territory, and duration stated. If it extends beyond the engagement, propose replacing it with confidentiality and non-solicitation clauses instead, which are far more likely to be enforceable and usually address what the client actually cares about protecting. Most clients accept this once it is explained plainly.
What is the difference between a non-compete and a non-solicitation clause?
A non-compete restricts you from working with a client's competitors, generally unenforceable in India if it applies after the engagement ends. A non-solicitation clause restricts you from actively poaching the client's specific employees or customers for a defined period, which is a narrower, more reasonable restriction and is more likely to hold up in an Indian court since it protects a specific business relationship rather than your entire career path.
Can a non-compete clause be hidden inside an NDA?
Yes, this is common. Some NDAs include non-compete-style language worded as part of a broader confidentiality or exclusivity section rather than appearing as its own clearly labelled clause. Read the full confidentiality section carefully, not just any clause titled "non-compete," since restrictive language can be embedded in wording that looks like standard confidentiality terms at first glance.
Should I sign a non-compete clause even if it is probably unenforceable?
Pushing back before signing is usually the better move, even though the clause likely would not hold up in court. An unenforceable clause can still create real friction: a client may genuinely believe it applies, threaten action based on that belief, or simply choose not to work with you again if a dispute arises. Proposing a swap to confidentiality and non-solicitation clauses upfront avoids this friction entirely rather than relying on the clause never being tested.