7 Predatory Contract Clauses Freelance Developers Must Never Accept

What it looks like

"All work product, inventions, developments, and improvements created by Contractor, whether or not during the term of this Agreement and whether or not related to the services, shall be the sole and exclusive property of Client, including any pre-existing intellectual property."

Why it's dangerous

The phrase "pre-existing intellectual property" is the landmine. This clause retroactively claims your reusable libraries, open-source contributions, personal side projects, and any tooling you've built over your career — even code you wrote years before this client existed. Courts have upheld broad IP assignment clauses, meaning you could lose rights to your own code base with a signature.

What it looks like

"The parties acknowledge that all deliverables constitute 'works made for hire' as defined under 17 U.S.C. § 101, and to the extent any deliverable does not qualify as a work made for hire, Contractor hereby irrevocably assigns all rights thereto to Client."

Why it's dangerous

Under U.S. copyright law, a true "work made for hire" by an independent contractor only applies to specific categories (commissioned works in certain media). Software generally does not qualify. The second sentence — "irrevocably assigns all rights" — is the actual weapon: it operates as a full copyright transfer with no carve-outs, no reversion rights, and no compensation for the assignment itself. Combined, these two sentences strip you of all copyright ownership permanently.

What it looks like

"Contractor agrees not to perform similar services, directly or indirectly, for any company operating in the same industry or market segment as Client for a period of 24 months following the termination of this Agreement, in any geographic location where Client operates."

Why it's dangerous

Broad non-competes are unenforceable in California, Minnesota, Oklahoma, and North Dakota — but expensive to litigate everywhere else. "Same industry" clauses for a SaaS dev could mean you cannot work in tech for two years. The geographic scope ("any location where Client operates") effectively makes it global for any company with remote employees. Even unenforceable clauses chill your ability to find work: clients balk at hiring someone under a pending non-compete dispute.

What it looks like

"Contractor shall indemnify, defend, and hold harmless Client and its officers, directors, employees, and agents from and against any and all claims, damages, losses, costs, and expenses (including reasonable attorneys' fees) arising out of or relating to Contractor's performance of services or any breach of this Agreement."

Why it's dangerous

This clause makes you financially responsible for defending the client in any lawsuit — even frivolous ones — as long as the plaintiff can connect the claim to your work. "Arising out of or relating to" is intentionally broad. If a client's end-user sues them over a product you contributed to, you pay for their lawyers. There is no reciprocal indemnification from the client, no cap on your liability, and no carve-out excluding claims caused by the client's own negligence or bad acts.

What it looks like

"To the extent permitted by applicable law, Contractor irrevocably waives all moral rights, including rights of attribution and integrity, in all deliverables produced under this Agreement."

Why it's dangerous

Moral rights — the right to be credited as an author and the right to object to distortion of your work — exist in most countries outside the U.S. under the Berne Convention. A blanket waiver means the client can attribute your code to themselves, strip your name from published work, modify your open-source contributions in ways that damage your reputation, and you have no legal recourse. For developers who contribute to public-facing projects or open source, this can permanently damage professional credibility.

What it looks like

"Contractor agrees to maintain in strict confidence all Confidential Information indefinitely, including after the termination of this Agreement, and shall not disclose such information to any third party without prior written consent of Client."

Why it's dangerous

NDAs without a time limit are generally unenforceable for trade secrets that eventually become public knowledge — but they are still weaponized. A perpetual NDA means you cannot discuss your work in a portfolio, reference the client in a case study, or describe the project in a job interview — ever. It also creates risk if you later work with a client in the same space: anything you learned could be claimed as "confidential" years later. Standard commercial NDAs are 2–5 years; perpetual is a litigation trap.

What it looks like

"Contractor shall perform all revisions, corrections, and modifications requested by Client until Client is fully satisfied with the deliverables. Revisions do not constitute new work and are included within the scope of this Agreement at no additional charge."

Why it's dangerous

"Until Client is fully satisfied" is undefined and infinite. A bad-faith client can request hundreds of revision cycles, deliberately withhold approval, and force you to work for months beyond your estimated scope — all for the original fixed fee. Combined with "at no additional charge," this clause removes any contractual basis for billing extra time. Courts have held that satisfaction clauses can require genuine, not pretextual, dissatisfaction — but proving bad faith in litigation costs more than most freelance contracts are worth.