10 Freelance Contract Clauses That Will Screw You (And How to Fight Back)

You got the gig. The client sent over a contract. You skimmed it, signed it, and got to work. Six months later you're in a dispute over who owns the code, why you didn't get paid, or how you somehow owe the client more than they paid you.

This happens because most freelance contracts are drafted by the client's lawyers — and their job is to protect the client, not you. Here are the 10 clauses that cause the most damage, what to look for, and the language you can push back with.

Not legal advice. This is educational content. For contracts involving significant money or risk, consult a licensed attorney.

1. Unlimited liability / uncapped indemnification

What it looks like: "Contractor shall indemnify, defend, and hold harmless Client from any and all claims, damages, losses, costs, or expenses of any nature whatsoever arising out of or related to Contractor's services."

Why it's dangerous: "Any and all" with no cap means a single negligence claim could expose you to liability that dwarfs what you were paid. A $5,000 project with unlimited liability is a $5,000 payday with potentially unlimited downside.

Redline: "Contractor's total aggregate liability under this Agreement shall not exceed the total fees paid by Client in the three months preceding the claim. Neither party shall be liable for indirect, consequential, or punitive damages."

2. IP assignment without a pre-existing work carveout

What it looks like: "All work product, inventions, discoveries, and developments conceived or created during the term of this Agreement — including any tools, frameworks, or methods used in performance — are hereby assigned to Client."

Why it's dangerous: The phrase "including any tools or frameworks" is the trap. If you used your own reusable component library, a design system you've built over years, or an open-source project you maintain — this clause can hand all of it to the client. Courts have upheld assignments this broad.

Redline: "Contractor assigns to Client all work product created solely for this engagement and paid for under this Agreement. Pre-existing intellectual property, tools, frameworks, and open-source work belonging to Contractor are expressly excluded and remain Contractor's sole property."

3. No kill fee (or an unfair one)

What it looks like: Either silence on the topic, or "Client may terminate this Agreement for any reason with 14 days notice. Upon termination, Client shall pay for services rendered to date."

Why it's dangerous: You blocked out six weeks for this project. The client cancels three weeks in. "Services rendered to date" means you get paid for the work you completed — but not for the opportunity cost of turning down other clients. A fair kill fee compensates you for the calendar time you committed.

Redline: "If Client terminates this Agreement without cause after kickoff, Client shall pay: (a) all fees for work completed to date, plus (b) a kill fee equal to 25% of the remaining contract value, not to exceed the total contract value."

4. Auto-renewal with a long notice window

What it looks like: "This Agreement shall automatically renew for successive one-year terms unless either party provides written notice of non-renewal no fewer than 90 days prior to the end of the then-current term."

Why it's dangerous: Miss the window — even by a day — and you're locked in for another year. 90-day windows are deliberately long because clients know most contractors won't notice them. Always set a calendar reminder on the day you sign.

Redline: "This Agreement shall continue on a month-to-month basis after the initial term. Either party may terminate with 30 days written notice at any time."

5. Overly broad non-compete

What it looks like: "During the term and for 24 months thereafter, Contractor shall not perform services for any entity that competes with Client in Client's industry."

Why it's dangerous: If your client is a SaaS company, this clause could prevent you from working with any other SaaS company for two years. That's your entire market. Even if the clause is unenforceable in your jurisdiction, it creates a chilling effect and potential lawsuit threat.

Redline: "Contractor agrees not to solicit Client's customers directly introduced to Contractor by Client during the term of this Agreement. No other restrictions on Contractor's ability to work with other clients are imposed." (Or simply delete the non-compete entirely — many clients will accept this.)

6. Scope creep language

What it looks like: "Contractor shall perform the services described in Exhibit A, as well as any reasonable additional tasks as directed by Client."

Why it's dangerous: "Reasonable additional tasks" is the unlock code for unlimited unpaid work. Clients have a very different definition of "reasonable" than you do — especially at month five of a six-month engagement.

Redline: "Services are limited to those described in Exhibit A. Any additional services must be agreed in writing via a separate change order before work begins and shall be billed at Contractor's then-current hourly rate."

7. NET 60+ payment terms with no late-payment interest

What it looks like: "Client shall pay all invoices within 60 days of receipt."

Why it's dangerous: You're financing the client's cash flow for two months, interest-free. On a $20,000 project, that's a meaningful float — for the client. Large companies routinely pay at 90 or 120 days regardless of what the contract says, unless there's a penalty for late payment.

Redline: "Client shall pay all invoices within 15 days of receipt. Invoices unpaid after 30 days accrue interest at 1.5% per month. Contractor may suspend services if any invoice is more than 30 days past due."

8. Mandatory arbitration with one-sided terms

What it looks like: "Any dispute arising under this Agreement shall be resolved by binding arbitration in [Client's city], under the rules of [expensive arbitration body]."

Why it's dangerous: Arbitration is expensive — filing fees alone can run $1,500–$5,000. For a small freelance dispute, that makes it economically impossible to pursue a legitimate claim. The client knows this. "In Client's city" means you fly to them.

Redline: "Disputes under $10,000 may be brought in small claims court by either party. Disputes above $10,000 shall be resolved by binding arbitration under AAA rules, with proceedings conducted remotely. Each party bears its own arbitration costs up to $2,500."

9. One-sided warranty with no corresponding client warranty

What it looks like: "Contractor warrants that all deliverables will be fit for purpose, free from material defects, and will conform to all applicable specifications for a period of 12 months."

Why it's dangerous: "Fit for purpose" is subjective. "All applicable specifications" is vague if the spec changed (and it always changes). A 12-month warranty on a custom software build is extremely generous — the industry standard is 30–90 days for bug fixes only, not new requirements.

Redline: "Contractor warrants that deliverables will substantially conform to the written specifications in Exhibit A for 30 days following final delivery. Contractor's sole obligation under this warranty is to correct non-conforming deliverables at no additional charge. This warranty does not cover changes to specifications after delivery."

10. Confidentiality with no time limit

What it looks like: "Contractor agrees to hold in strict confidence all Confidential Information indefinitely and shall not disclose it to any third party for any purpose."

Why it's dangerous: Perpetual NDAs are overreaching for most engagements. They also prevent you from listing the work in your portfolio (which many clients forget they've agreed to), discussing general techniques you used, or even mentioning the client's name as a reference. A reasonable NDA has a 2–3 year term and a portfolio carveout.

Redline: "Contractor agrees to hold Client's Confidential Information in confidence for a period of two years following termination of this Agreement. Notwithstanding the foregoing, Contractor may list Client's name and a general description of services in Contractor's portfolio and marketing materials unless Client objects in writing."

The pattern behind all ten

Every clause above transfers risk from the client to you. That's not always malicious — it's often just boilerplate that the client's lawyer drafted to be maximally protective of the client, and no one bothered to negotiate because the freelancer signed without reading.

The good news: most clients will accept redlines on all of these. They want the project done. A calm, professional "I've made a few standard contractor-side edits — let me know if anything is a problem" closes 90% of these negotiations before they start.

The bad news: you have to catch them first, and reading a 20-page MSA for a $3,000 project isn't realistic every time.