Clausely/Blog/Contract Clauses
Contract Red FlagsMarch 19, 202625 min read

7 Predatory Freelance Contract Clauses That Cost You Thousands (And Exactly How to Negotiate Them)

Real contract language. Real risks. Word-for-word scripts to fight back. This is the guide we wish every freelancer had before signing their first contract.

If you freelance on Upwork, Fiverr, Toptal, or take direct client contracts, there's a good chance you've signed something that cost you money, rights, or both — without even realizing it.

Predatory contract clauses don't announce themselves. They hide behind legal jargon, buried in paragraph 12 of a 20-page agreement. They sound reasonable until you realize that “reasonable revisions” means unlimited free work, or “standard payment terms” means you wait 4 months to get paid.

We analyzed hundreds of freelance contracts across platforms and industries. These are the 7 clause patterns that show up again and again — and that cost freelancers the most money, time, and career flexibility.

For each one, we'll show you what the clause actually looks like, why it's dangerous in plain English, and give you an exact negotiation script you can copy, paste, and send to your client today.

1
Payment

Net-90 or Net-120 Payment Terms

You finish work in 2 weeks. You get paid in 3-4 months — maybe.

What This Clause Looks Like in the Wild

Actual Contract Language

“Payment shall be rendered net-90 from the date of final delivery, subject to Client's review and sole satisfaction with the completed deliverables. Client reserves the right to withhold payment pending resolution of any quality concerns.”

Why This Is Dangerous

Net-90 means the client has 90 days after you deliver to pay you. Net-120 gives them four months. Pair that with "sole satisfaction" language and you're looking at an indefinite delay — they can always claim they're "reviewing."

For freelancers living on project income, this is devastating. You've already paid for software, spent hours, maybe turned down other work. And the money is just... sitting in their accounts earning interest while you wait.

The worst versions tie payment to the client's own client paying them — so if their client is slow, you're the one who starves. This is called "pay-when-paid" and it's banned in construction contracting in many states for a reason.

Exactly What to Say

Negotiation Script — Copy & Send

"I'd love to move forward with this project. I typically work on Net-15 or Net-30 terms, which is standard in the freelance industry. For projects of this scope, I'm happy to offer a milestone-based payment structure — 50% upon project kickoff and 50% on delivery approval, with a 15-day payment window. This keeps the project moving smoothly for both of us. Would that work for your team?"

The Clause Rewritten Fairly

Fair Alternative

“Payment shall be rendered net-30 from the date of each milestone delivery. 50% of the total project fee is due upon contract signing as a non-refundable deposit. Remaining balance due within 15 business days of final delivery acceptance. Late payments accrue 1.5% monthly interest.”

2
IP Rights

Full IP & Copyright Transfer With No Additional Compensation

They don't just own the deliverable — they own your portfolio, your templates, and your future.

What This Clause Looks Like in the Wild

Actual Contract Language

“Contractor hereby irrevocably assigns to Client all right, title, and interest in and to all Work Product, including but not limited to all intellectual property rights, pre-existing materials, tools, methodologies, and any derivative works thereof, in perpetuity throughout the universe.”

Why This Is Dangerous

This clause doesn't just transfer the work you create for them — it transfers ownership of your pre-existing tools, templates, frameworks, and methodologies. That component library you've been building for 3 years? That design system you use across clients? Now it belongs to this one client.

The phrase "derivative works thereof" is especially dangerous. If you build something for Client A using techniques you developed for Client B, Client A could argue they own anything similar you create going forward.

"In perpetuity throughout the universe" isn't dramatic legal language for fun — it means there are zero limits on where and when they can use, resell, or sublicense your work. You can't even use it in your portfolio without their permission.

Exactly What to Say

Negotiation Script — Copy & Send

"I'm happy to assign the rights to the final deliverables created specifically for this project. However, I do need to retain ownership of my pre-existing tools, templates, and methodologies — these are what allow me to do my best work efficiently. I'll include a broad license for you to use the deliverables commercially without restriction. I'd also like to retain the right to showcase this work in my portfolio. This is standard practice for [design/development/writing] professionals. Can I send over my standard IP clause?"

The Clause Rewritten Fairly

Fair Alternative

“Contractor assigns to Client all rights in the final deliverables created specifically under this agreement. Contractor retains ownership of all pre-existing materials, tools, and methodologies, and grants Client a perpetual, non-exclusive license to use them as embedded in the deliverables. Contractor retains the right to display work in their portfolio and marketing materials.”

3
Scope

Unlimited Revisions Clauses

A fixed-price project becomes an open-ended obligation with no end in sight.

What This Clause Looks Like in the Wild

Actual Contract Language

“Client shall be entitled to request reasonable revisions and modifications to the deliverables at no additional charge until the work meets Client's expectations and standards. Contractor agrees to make all requested changes in a timely manner.”

Why This Is Dangerous

"Reasonable" is doing a lot of heavy lifting in this clause — and it's entirely undefined. What's reasonable to you (two rounds of feedback) is very different from what's reasonable to a client who wants to iterate endlessly until they "feel" it's right.

The real trap is "until the work meets Client's expectations." Expectations are subjective. There's no objective standard, no deadline, and no mechanism to resolve disagreements. You're essentially committing to work until the client is happy, however long that takes.

Freelancers routinely report projects that should have taken 2 weeks turning into 2-month marathons because of unlimited revision clauses. You can't take on new work because this project won't end, and you can't bill for the extra time because the contract says it's included.

Exactly What to Say

Negotiation Script — Copy & Send

"I want to make sure you're completely happy with the final result. My standard process includes two rounds of revisions after each deliverable — in my experience, this gives us plenty of room to refine and perfect the work. If we need additional rounds beyond that, I offer them at my hourly rate of $[X]/hr. This keeps the project on track and ensures I can dedicate focused attention to your revisions. Does that sound fair?"

The Clause Rewritten Fairly

Fair Alternative

“The project fee includes two (2) rounds of revisions per deliverable. Each revision round allows for consolidated feedback submitted within 5 business days. Additional revision rounds beyond the included two shall be billed at Contractor's standard hourly rate of $[X]/hr. A revision constitutes changes to existing work; new requirements or features constitute a scope change and require a separate estimate.”

4
Career

Non-Compete Clauses Buried in Freelance Contracts

One project costs you your ability to work in your own industry for years.

What This Clause Looks Like in the Wild

Actual Contract Language

“During the term of this Agreement and for a period of twenty-four (24) months following its termination, Contractor shall not directly or indirectly provide services to, be employed by, or engage with any entity that competes with Client or operates in Client's industry, including but not limited to Client's current and prospective clients.”

Why This Is Dangerous

A 24-month non-compete in a freelance contract is absurd — but it happens more often than you'd think, especially in tech, marketing, and consulting. If you're a freelance web developer and your client is a SaaS company, this clause could block you from working with any other SaaS company for two years.

The phrase "prospective clients" is a landmine. The client can retroactively claim that any company you work with was someone they were "prospecting." It's unenforceable in many jurisdictions, but fighting it in court costs money you probably don't have.

Non-competes are designed for employees with salaries, benefits, and job security. As a freelancer, you have none of those protections but all of the restrictions. Many states (including California) have banned non-competes, and the FTC has proposed a federal ban — but the clauses still appear in contracts regularly.

Exactly What to Say

Negotiation Script — Copy & Send

"I noticed there's a non-compete clause in the agreement. As an independent contractor, my ability to work across the industry is essential to my livelihood — I don't receive a salary or benefits during any restricted period. I'm happy to sign a strong non-disclosure agreement and a non-solicitation clause that protects your specific clients and confidential information. But I can't agree to a broad non-compete that would restrict my ability to earn a living. Could we replace this with an NDA and non-solicitation instead?"

The Clause Rewritten Fairly

Fair Alternative

“Contractor agrees not to solicit or provide services directly to Client's existing named clients (listed in Exhibit A) for a period of six (6) months following project completion. Contractor agrees to maintain confidentiality of all proprietary information per the NDA executed separately. No general non-compete restrictions apply.”

5
Termination

Kill Fee & Cancellation Clauses That Screw the Freelancer

The client can walk away at any time. You eat the cost of work already done.

What This Clause Looks Like in the Wild

Actual Contract Language

“Client may terminate this Agreement at any time for any reason upon written notice. Upon termination, Client shall pay Contractor only for deliverables that have been completed and accepted prior to the termination date. Any work-in-progress, unused materials, or partially completed deliverables shall not be compensable.”

Why This Is Dangerous

This clause lets the client cancel the project whenever they want, but only pays you for work they've formally "accepted." If you're 80% done with a deliverable but haven't hit the acceptance checkpoint? You get nothing for that work.

The worst version is when there's no kill fee at all. You've turned down other projects, blocked off your calendar, maybe even hired subcontractors — and the client just pulls the plug. You're left with lost time, lost income, and lost opportunity cost.

Some contracts go further and require you to hand over all work-in-progress (including unfinished deliverables and research) upon cancellation — for free. So the client gets to benefit from your work without paying for it, and potentially hands it to a cheaper freelancer to finish.

Exactly What to Say

Negotiation Script — Copy & Send

"I understand that circumstances can change and you may need flexibility to cancel. I'd like to add a standard kill fee clause to protect both of us: if the project is cancelled after kickoff, the deposit is non-refundable, and any work completed beyond the deposit is billable at my standard rate. I also ask for [7/14] days notice so I can plan my schedule accordingly. This is standard for projects of this scope — does that work for you?"

The Clause Rewritten Fairly

Fair Alternative

“Either party may terminate this Agreement with fourteen (14) days written notice. Upon termination: (a) Client shall pay for all work completed to date, including work-in-progress, calculated on a pro-rata basis of the total project fee; (b) the initial deposit is non-refundable; (c) Contractor retains rights to all unpaid work. If Client terminates without cause after project kickoff, a kill fee of 25% of the remaining project value applies.”

6
Scope

Scope Creep Enablers (Vague Deliverable Language)

"And anything else reasonably related" turns a 10-page project into a 50-page nightmare.

What This Clause Looks Like in the Wild

Actual Contract Language

“Contractor shall deliver a complete website redesign, including all necessary pages, graphics, content updates, and any other elements reasonably related to the project scope as determined by Client. Contractor will also provide ongoing support and adjustments as needed to ensure Client satisfaction.”

Why This Is Dangerous

"All necessary pages" — how many pages? "Graphics" — how many? What kind? "Content updates" — does that mean writing new content or just placing content the client provides? None of this is defined, which means the client gets to decide after the fact.

The phrase "any other elements reasonably related" is a scope creep blank check. Need a logo? That's related. Need social media graphics? Related. Need the site to integrate with their CRM? Also related. Every new request becomes "part of the project" because the contract doesn't draw a line.

"Ongoing support and adjustments" with no time limit or definition means you're on the hook indefinitely. Six months later, the client emails asking you to update their homepage — and points to this clause.

Exactly What to Say

Negotiation Script — Copy & Send

"To make sure we're both on the same page about what's included, I'd like to define the specific deliverables and their quantities in the contract. I'll put together a detailed scope document listing each deliverable, the number of revisions included, and the timeline. Anything beyond that scope we can absolutely discuss — I'll just provide a separate estimate so there are no surprises for either of us. This protects both of us. Can I send over a revised scope section?"

The Clause Rewritten Fairly

Fair Alternative

“Contractor shall deliver the following specific items as outlined in Exhibit A: [list each deliverable with quantity, specifications, and acceptance criteria]. Any work requested beyond the items listed in Exhibit A constitutes a Change Order, which requires a separate written estimate and approval before work begins. Maintenance and support are not included and may be arranged under a separate agreement.”

7
Liability

Liability Clauses That Put All Risk on the Freelancer

If anything goes wrong — even things outside your control — you're on the hook for all damages.

What This Clause Looks Like in the Wild

Actual Contract Language

“Contractor shall indemnify, defend, and hold harmless Client and its officers, directors, employees, and agents from and against any and all claims, damages, losses, liabilities, costs, and expenses (including reasonable attorneys' fees) arising out of or relating to Contractor's performance under this Agreement or any deliverable provided hereunder, regardless of cause.”

Why This Is Dangerous

"Regardless of cause" is the nuclear phrase here. Even if the client misuses your work, modifies it in ways you didn't intend, or if a third party does something wrong — you're still liable. This is called an "unlimited indemnification" and it can expose you to damages far exceeding what you were paid for the project.

As a freelancer, you probably don't have a legal team or errors and omissions insurance. If a client's customer sues because of a bug in software you built, or a typo in copy you wrote causes a compliance issue, this clause means you pay for everything — legal fees, damages, settlements, all of it.

The indemnification is one-sided: you indemnify them, but they don't indemnify you. So if the client gives you copyrighted content to use and you get sued for copyright infringement, you're still on the hook even though it was their material.

Exactly What to Say

Negotiation Script — Copy & Send

"I'm happy to take responsibility for my own work, but I'd like the indemnification to be mutual and proportional. I'll indemnify you for claims directly caused by my negligence or willful misconduct in performing the work. In return, I'd like you to indemnify me for claims arising from materials you provide or modifications you make after delivery. I'd also like to cap my total liability at the amount paid under this contract — this is standard for independent contractors. Shall I suggest some revised language?"

The Clause Rewritten Fairly

Fair Alternative

“Each party shall indemnify the other against claims arising from their own negligence or willful misconduct. Contractor's total liability under this Agreement shall not exceed the total fees paid by Client to Contractor. Contractor is not liable for damages arising from Client's modification of deliverables, Client-provided materials, or use of deliverables in a manner not contemplated by this Agreement.”

The Pattern Behind Every Predatory Clause

Every clause on this list follows the same playbook: shift risk from the client to you, maximize the client's flexibility while eliminating yours, and use vague language that the client can interpret however they want after the fact.

The fix is also the same every time: be specific, be mutual, and set limits. Specific deliverables instead of vague descriptions. Mutual obligations instead of one-sided requirements. Clear caps on liability, revisions, and timelines instead of open-ended commitments.

You don't need a lawyer to negotiate a better contract. You need to know what to look for, and you need the words to push back professionally. That's what this guide — and Clausely — gives you.

Free Contract Analysis

Not sure if your contract is safe?
Scan it in 30 seconds.

Clausely's free contract analyzer flags every predatory clause in your agreement — payment traps, IP overreach, liability bombs — and gives you a word-for-word negotiation script to fight back.

No signup required. Paste your contract and get results in seconds.

freelance contract red flagsUpwork contract reviewpredatory freelance clausesfreelance contract tipscontract negotiation scriptnet-90 payment termsIP clause freelancekill fee freelancescope creep contract