Most freelancers treat the contract as a formality — something to sign so the "real work" can start. That instinct is exactly backwards. The contract is the deal. Every dollar you'll be paid, every hour you'll spend on unpaid revisions, and every risk you'll carry if something goes wrong is decided in the document, not in the friendly kickoff call.
The good news: you don't need a law degree to negotiate a fair contract. You need to know which terms reliably hurt freelancers, and you need a calm, collaborative way to ask for changes. This guide covers both — the 12 things worth pushing back on, and how to raise them without souring the relationship before it starts.
Why negotiating is expected, not rude
The single biggest reason freelancers sign bad contracts is fear: fear that asking for changes makes them look difficult, unprofessional, or replaceable. In reality, the opposite is true. Clients who hire freelancers regularly expect redlines. A freelancer who reads the contract carefully and proposes specific, reasonable adjustments signals competence and seriousness. It's the freelancer who signs a one-sided contract without a word who looks green.
Reframe it: you're not "asking for favors." You're aligning the paperwork with the deal you both already verbally agreed to. Almost every negotiation email you send should carry that tone — "Excited to start. A few adjustments so we're aligned and the project runs smoothly."
The mindset: collaborative, specific, prioritized
Before we get to the list, three rules that make negotiation land:
- Be collaborative, not adversarial. Frame each ask as protecting both sides. "A deposit lets me block out the time and prioritize your project" beats "I don't trust you to pay."
- Be specific. Don't say "the payment terms feel risky." Propose exact language: "50% deposit on signing, balance within 15 days of delivery." Specific asks get fast yeses; vague concerns invite pushback.
- Prioritize. Lead with the two or three terms that matter most. If you send back a document with 15 tracked changes, you'll trigger a legal review and a three-week delay. Fight the big battles; let the small stuff go.
Now, the 12 terms.
1. IP that transfers before you're paid
This is the most dangerous clause in freelance contracts, and it hides in plain sight. Look for language like:
"All work product and intellectual property shall become the sole property of Client upon execution of this Agreement."
The trap is the timing. "Upon execution" means the client owns your work the moment you sign — not when they pay. You could deliver a full brand identity, the client owns it, and then they never pay the invoice. You have no leverage because they already own everything.
What to propose instead:
"All work product and intellectual property shall transfer to Client upon Client's payment in full of all fees due under this Agreement. Until such payment, all rights remain with the Contractor."
This is standard, fair, and protects both parties. No reasonable client refuses it.
2. Unlimited revisions
On a fixed fee, "revisions until the client is satisfied" is a blank check written against your time. Watch for:
"Contractor shall provide revisions until Client is fully satisfied."
"Fully satisfied" has no ceiling. Three rounds becomes eight becomes fifteen, and your effective hourly rate quietly collapses from $90 to $15.
What to propose instead:
"This Agreement includes two (2) rounds of revisions. Additional revision rounds will be billed at $95/hour, agreed in writing before work begins."
You're not refusing revisions — you're capping the free ones and pricing the rest. That's a reasonable, businesslike boundary.
3. Net-60 or Net-90 payment terms
Payment timing is cash flow, and cash flow is survival for a freelancer. Net-60 means you finish the work and wait two months to get paid, financing the client in the meantime. Net-90 is worse.
What to propose instead: Shorten the terms and add a deposit.
"50% deposit ($X) due on signing; remaining 50% due within fifteen (15) days of final delivery. Overdue amounts accrue 1.5% interest per month."
If the client's accounting genuinely runs on Net-30, meet them there — but Net-60+ with no deposit is a term to resist hard.
4. No deposit
Related, but worth its own line. Without a deposit, you shoulder 100% of the risk if the client walks mid-project. A deposit isn't just cash flow — it's a commitment test. A client who won't pay 25–50% upfront is telling you something.
What to propose:
"Client shall pay a non-refundable deposit of 50% of the total fee upon signing, before work commences."
5. No kill fee (cancellation compensation)
What happens if the client cancels the project halfway through? In most freelance contracts, the answer is: you get nothing for the work you've done. A kill fee fixes that.
What to propose:
"If Client terminates before completion, Client shall pay for all work performed to date plus 25% of the remaining fee."
6. Uncapped liability and one-sided indemnification
This is the clause that can turn a $5,000 project into a six-figure lawsuit. Look for:
"Contractor shall indemnify and hold Client harmless from any and all claims, damages, and losses arising from the services, without limitation."
"Without limitation" means unlimited personal exposure. If a third party sues the client over a deliverable, you could owe far more than you were ever paid.
What to propose instead: Make it mutual and capped.
"Each party shall indemnify the other for third-party claims arising from its own negligence or willful misconduct. In no event shall Contractor's total aggregate liability exceed the total fees paid under this Agreement."
The liability cap — limiting your exposure to the fees you were paid — is one of the most important protections you can add.
7. Overbroad IP assignment (your reusable tools)
Even a fair "IP on payment" clause can go too far if it sweeps in things you reuse across clients: your component libraries, frameworks, boilerplate, and pre-existing tools. Language like "all work product and related materials" is broad enough to capture your entire toolkit.
What to propose: Carve out your background IP.
"Contractor retains all rights to pre-existing tools, libraries, frameworks, and know-how used in performing the services. Contractor grants Client a perpetual license to use such materials solely as incorporated into the deliverables."
8. Missing portfolio / attribution rights
A full IP assignment plus a moral-rights waiver can legally bar you from showing your own work in your portfolio. For a designer or developer, portfolio rights are marketing oxygen.
What to propose:
"Contractor retains the right to display the work product in Contractor's portfolio and self-promotional materials."
9. Vague scope and no change-order mechanism
If the deliverables are defined as "a website" or "marketing support" with no detail, every ambiguity will be resolved in the client's favor. Worse, if there's no change-order process, the client can add tasks "as needed" for free.
What to propose: Tighten the deliverables list and add a change process.
"Any work beyond the deliverables described in Exhibit A requires a written change order specifying additional scope, timeline, and fees, agreed by both parties before work begins."
10. One-sided termination rights
Watch for asymmetry: the client can terminate "for convenience" at any time with no notice, but you can only terminate for cause after a long cure period.
"Client may terminate for convenience at any time; Contractor may terminate only for material breach with 60 days' cure period."
What to propose: Make it symmetric and paid.
"Either party may terminate for convenience with 30 days' written notice. Upon termination, Client shall pay for all work performed through the termination date."
11. Broad non-compete or non-solicit
A two-year, whole-industry non-compete can lock you out of your own profession after a three-month gig. Non-solicit clauses can be so broad they prevent normal networking.
What to propose: Narrow it drastically — to specific accounts and a short window.
"Contractor agrees not to solicit or directly service the specific Client accounts worked on during this engagement for a period of six (6) months following termination."
12. One-way, perpetual confidentiality
Confidentiality should bind both parties and have an end date. A clause that binds only you, forever, with no standard carve-outs (for information that becomes public) is lopsided.
What to propose:
"Each party shall keep the other's confidential information private for three (3) years following termination, excluding information that is or becomes publicly available through no fault of the receiving party."
Putting it together: the counter-proposal email
Once you know what to change, the delivery matters as much as the content. Don't send back a marked-up PDF with 12 changes — that reads as combative and triggers delay. Instead, send a short, warm email that leads with your top three priorities:
Hi [Client name],
Thanks for sending the agreement — I'm excited to get started. Before I sign, I'd like to align on a few points so the project runs smoothly for both of us:
- IP ownership (§5.1): Happy to transfer full ownership — I'd just like it to transfer on final payment rather than on signing. Standard, and it protects us both.
- Revisions (§3.2): I'd like to define this as two rounds included, with additional rounds billed at my hourly rate. Keeps the timeline predictable.
- Payment (§6.1): Could we do a 50% deposit to kick off, with the balance due within 15 days of delivery?
Everything else looks good to me. Happy to hop on a quick call if easier. Looking forward to working together!
Best, [Your name]
Notice what this does: it's collaborative, it's specific, it references sections, and it caps the asks at three. That's a negotiation a client says yes to.
Know your red lines
Finally, decide in advance what you will not accept, even if the client pushes back. For most freelancers, the non-negotiables are:
- IP transfer before full payment — never accept it.
- Uncapped, one-way indemnification — never accept it.
- Unlimited revisions on a fixed fee — never accept it.
Everything else is a spectrum you can trade on. But those three can genuinely end a freelance business, and no project is worth signing them.
A faster way to catch these
Reading every clause of every contract with this checklist in hand is doable — but slow, and easy to get wrong when you're busy and the client wants an answer today. That's exactly the problem ClauseCatch was built to solve: upload the contract, and in about a minute you get every risky clause flagged, every missing protection detected, and a ready-to-send counter-proposal email drafted for you. It's like having a $500 lawyer read the contract in 60 seconds.
However you do it — by hand or with a tool — the principle is the same: read the contract like it's the deal, because it is. The freelancers who negotiate calmly and specifically don't just avoid bad contracts. They build a reputation as professionals worth working with.
This article is educational and not legal advice. For high-stakes contracts, consult a licensed attorney.