The five clauses that cost freelancers the most money.
After six years of freelance contracts I shouldn't have signed, the same five patterns kept showing up. Here they are — with the replacement language I now push back with.
Every few months a fellow freelancer messages me a contract and asks "is this OK?" And the answer is almost always the same: the part you're worried about is fine. The part that's going to bite you is buried on page four, and reads as standard.
"Standard" for them is "expensive" for you. Below are the five clauses that have personally cost me the most — what they look like, why they hurt, and the language I now copy-paste into every reply.
"Unlimited revisions" — and the soft version that's worse.
The hard version reads exactly like that: "Contractor agrees to provide unlimited revisions at Client's reasonable request." Easy to spot, easy to push back on.
The soft version is the dangerous one. It's usually written as "Contractor will revise the deliverables to Client's reasonable satisfaction" — no number, no cap, just the word "reasonable." There is no reading of "reasonable" that survives an unhappy stakeholder on the client's side. You will get six rounds. You will work two weekends. You will not be paid for either.
The two-day turnaround is the second trap. It sounds reasonable in isolation; it stops being reasonable when paired with no revision cap, because you've now ceded the right to ever take a weekend.
When it matters less: tiny projects with one decision-maker who's signed off on every prior round. Even then, write the cap in. The leverage is in having it on paper.
Net-60 from acceptance, not invoice.
Net-30 is annoying. Net-60 is brutal. The killer is when payment is due not from the date of invoice but from the date of client acceptance of final deliverables.
That word — acceptance — is doing more work than it looks like. The client controls when "acceptance" happens. Every revision round resets the clock. Every "we just need legal to look it over" delay resets the clock. I have personally watched a $8,400 invoice float for 117 days before payment under a net-60-from-acceptance clause that read as innocuous.
The third sentence is the most telling. A contract that explicitly disclaims a late fee is a contract whose drafters expect to pay late. That is, mathematically, an interest-free loan from you to them.
When it matters less: clients with whom you have a long history of on-time payment, or government / regulated entities whose AP cycles are genuinely slow but predictable. Even then, the milestone structure helps both sides.
The IP clause that eats your toolkit.
This is the one I missed the longest. It's almost always presented as standard, and 95% of it is. The 5% that isn't can transfer your entire professional toolkit — your fonts, your design files, your code libraries, your methodology — to one client, on signature.
Read the following slowly:
That middle clause — including all pre-existing materials of Contractor incorporated therein — is the one that assigns your toolkit. If you used a custom Figma library, a code framework you wrote, or even a typeface license you bought, this clause says it now belongs to the client. You can't reuse any of it on the next job without their permission.
The fix is to license, not assign. The client gets full perpetual rights to use your background IP inside the deliverables. They do not get the IP itself.
When it matters less: nothing. There is no version of this where the original clause is fine. Even if you've never reused a single asset across clients, you might want to. License it, never assign.
Uncapped indemnity, howsoever arising.
"Indemnify" means "pay for, including your legal fees, if anyone sues over anything you're allegedly responsible for." The standard freelancer indemnity clause is a one-way obligation from you to the client, often with no cap and no carve-outs.
"Any and all" with no cap. "Howsoever arising" sweeps in things you have nothing to do with. One disgruntled third-party stakeholder + an aggressive corporate lawyer + this clause = you personally owing the client's legal bill, uncapped.
This is the only clause on the list where I have a hard rule. Cap your aggregate liability at fees paid in the prior 12 months. Exclude indirect and consequential damages. If the client refuses, the project isn't worth taking — the unbounded tail risk is mathematically worse than walking away.
When it matters less: never, in my view. Even on a $500 logo, the cost of fighting a frivolous claim under an uncapped indemnity is higher than the project value. The cap is non-negotiable.
Termination without notice, without payment.
Reads as innocuous. Ends careers.
Translate that into plain English: the client can walk away on week four of a six-week engagement, demand your in-progress files, and pay you nothing for the four weeks of work. The final clause — "Contractor shall deliver all work product in progress to Client" — is what makes this asymmetric. They keep the work; you keep nothing.
This pairs nightmarishly with the net-60-from-acceptance clause in §2: if the client never "accepts," they never trigger payment, and now they can also terminate without owing you for the work you did. You are paying them to use you.
When it matters less: very short engagements (under two weeks) where the work-in-progress has minimal value if abandoned. Even then, 14 days notice protects both sides from the awkward "we hate this" silent treatment.
The pattern.
The clauses that hurt you aren't the ones you worry about when you're reading the contract for the first time. They're the ones you skim because the language reads as standard.
It isn't. The drafters wrote a document that is optimal for their client. "Standard" in that document is "expensive" for you. Every clause above is a place where the drafter quietly tilted the balance — and where one paragraph of replacement language tilts it back.
The other thing worth saying: nothing on this list is hostile to ask for. Every contract I've ever negotiated with this language has been signed without drama. Clients with anything resembling a normal procurement process expect freelancers to push back on the indemnity cap and the IP carve-out. The ones who don't expect it — who refuse it categorically — are telling you something important about how the engagement will go.
What clauses am I missing? Send me yours. I'll add the best ones to the next post.
A second opinion on your contract.
$9, sixty seconds.
RedlineBot does this on your actual contract — every clause, every flag, the replacement language drafted for you.