A non-compete tries to stop you from doing similar work, or working for a named competitor, for a set time and region after the contract ends. A non-solicit is narrower: it only stops you from actively pursuing the client's own employees or customers, not from taking any job in the same field. Whether either one actually holds depends almost entirely on which law governs your contract. In the US, enforceability varies sharply by state, with a handful of states banning most non-competes outright and many others enforcing them if the duration, geography, and scope are reasonable. In India, Section 27 of the Indian Contract Act voids most restraints on a lawful profession or trade once the relationship has ended, so a post-termination non-compete rarely survives a direct challenge in an Indian court, though the rule for consultants specifically is less settled than for employees. Non-solicits and confidentiality or NDA clauses are treated more leniently in both systems than a broad non-compete. The clause's exact wording, and the governing-law clause that decides which country's rules apply, matter more than its label.
A clause that sounds absolute on paper, "you may not work for a competitor for 12 months," is rarely that simple once you look at which law actually governs it and what the exact wording restricts. Here is how to read one before you sign, and what you are realistically bound by once a remote contractor role has ended.
What is the difference between a non-compete and a non-solicit clause?
A non-compete tries to stop you from doing similar work or working for a competitor for a set time and area. A non-solicit is narrower: it only stops you from actively pursuing the client's own employees or customers, not from taking a job in the same field.
| Clause | What it restricts | Typical duration |
|---|---|---|
| Non-compete | Working in the same field or for a named competitor | Often 6 to 24 months, by contract |
| Non-solicit | Actively pursuing the client's own staff or customers | Commonly 6, 12, or 24 months |
| Confidentiality / NDA | Sharing or using the client's confidential information | Often indefinite, not time-boxed |
A non-solicit does not usually stop you from working for a competitor outright, and it does not always stop a former client from contacting you first, only from you actively reaching out to solicit them. The exact wording decides which of these a given clause actually is, regardless of what it is titled in the contract.
Can a non-compete actually stop me from working for a competitor?
Whether it holds up depends almost entirely on which law governs your contract. Some US states enforce reasonable non-competes while a handful ban them outright, and the clause's real-world force varies that much state to state, before India's own rules even enter the picture.
US enforceability is a patchwork, not a single rule. California, North Dakota, Minnesota, and Oklahoma have statutory near-bans on non-compete clauses. Most other states will enforce one if it is reasonable in duration, geographic scope, and the specific activity restricted, and courts can sometimes "blue pencil," edit down, an overly broad clause rather than void it outright.
See Fisher Phillips' overview of non-compete enforceability against independent contractors for how US courts weigh contractor status specifically, since being a contractor rather than an employee does not automatically void the clause on its own.
Is a non-compete enforceable against a contractor based in India?
Section 27 of the Indian Contract Act voids most agreements that restrain a lawful profession or trade once the relationship has ended, so a non-compete that only takes effect after you stop working rarely survives a direct challenge in an Indian court, though the rule for consultants specifically is less settled than for employees.
- In-term restraints are treated differently: a restriction that only applies while the contract is active is generally not hit by Section 27, only the post-termination version is.
- Confidentiality and non-solicit clauses are a separate question: these are more likely to survive even where a non-compete is struck down, since they protect specific information or relationships rather than barring an entire line of work.
- The governing-law clause decides which rules even apply: if your contract names a US state's law as governing, an Indian court may look to that state's rules rather than Section 27, and the reverse is also possible.
For the Indian legal basis itself, see iPleaders' explainer on the enforceability of non-compete clauses in India. This is also the least settled area across the sources: none of them specifically address a foreign company's contract with a remote India-based contractor, so a clause unique to your situation is worth a direct read by a lawyer rather than a general guide.
What should I actually check before signing or after the role ends?
Read the governing-law clause first, since it decides which country's default rules apply. Then read the restriction's exact wording to see whether it is a narrow non-solicit or a broad non-compete, and check any separate confidentiality or NDA clause, since that one usually survives even where a non-compete does not.
- Find the governing-law clause. It usually sits near the end of the contract and names a specific US state or India as the law that applies if there is ever a dispute.
- Read the restriction itself, not its heading. A clause labeled "non-compete" that only bars contacting the client's employees and customers is functionally a non-solicit, and the reverse mislabeling happens too.
- Check the duration and scope. An unlimited or multi-year restriction with no geographic limit is far more likely to be struck down, in either country, than a narrow, time-boxed one.
- Separate the confidentiality clause in your mind. Even where a non-compete does not hold up, using or sharing a former client's confidential information is a different, and usually more enforceable, problem.
Want a contract that is clear about this before you sign?
Join the GTMly talent network to get matched with US-facing companies whose contracts are reviewed and clear about what, if anything, applies after the role ends.
Join the talent network →Frequently asked questions
What is the difference between a non-compete and a non-solicit clause?
A non-compete tries to stop you from doing similar work or working for a competitor for a set time and area. A non-solicit is narrower: it only stops you from actively pursuing the client's own employees or customers, not from taking a job in the same field.
Can a non-compete actually stop me from working for a competitor?
Whether it holds up depends almost entirely on which law governs your contract. Some US states enforce reasonable non-competes while a handful ban them outright, and the clause's real-world force varies that much state to state, before India's own rules even enter the picture.
Is a non-compete enforceable against a contractor based in India?
Section 27 of the Indian Contract Act voids most agreements that restrain a lawful profession or trade once the relationship has ended, so a non-compete that only takes effect after you stop working rarely survives a direct challenge in an Indian court, though the rule for consultants specifically is less settled than for employees.
What should I actually check before signing or after the role ends?
Read the governing-law clause first, since it decides which country's default rules apply. Then read the restriction's exact wording to see whether it is a narrow non-solicit or a broad non-compete, and check any separate confidentiality or NDA clause, since that one usually survives even where a non-compete does not.
Related: Moonlighting and exclusivity clauses explained · Quitting a remote US contractor role the right way · Terminated with no notice as a remote US contractor