6 Freelance Contract Provisions That Cost Freelancers Money
Freelance · 6 min read · Published 2026-05-28
Freelancers are often so eager to win work that they accept unfavorable contract terms without pushing back. The result is delayed payments, IP you thought you owned, and scope that expands without additional pay. These six provisions are where most of that money is lost — and all of them are negotiable.
1. Net-60 and Net-90 payment terms
Payment terms dictate how long a client can wait before paying you. Net-30 (payment due 30 days after invoice) is the standard that most freelancers accept. Net-60 or Net-90 is common in enterprise contracts — but it's a significant cash flow problem for individual freelancers.
What you should know:
• Net-60 means you may complete work in week one and not see payment until week 11 or later
• Clients use long net terms to manage their own cash flow at your expense
• The longer the net term, the higher your effective price should be
How to push back:
• Propose Net-15 or Net-30 as your standard
• For large projects, negotiate milestone payments (e.g., 30% on signing, 30% at midpoint, 40% on delivery) rather than a single payment at the end
• Add a late payment interest clause: "Invoices unpaid after the due date shall accrue interest at 1.5% per month"
A client insisting on Net-90 is telling you something about how they treat vendors. Factor that into your pricing accordingly.
2. No kill fee
A kill fee (also called a cancellation fee) is what the client pays you if they cancel the project after work has begun. Without one, you have no protection if the client changes direction, loses budget, or simply ghosts you mid-project.
What a reasonable kill fee looks like:
• 25–50% of the remaining project value if cancelled after the project starts
• 100% of the current milestone if cancelled mid-milestone
• A clear definition of what constitutes "cancellation" (vs. a pause or scope change)
Many clients will accept kill fee provisions because they understand project abandonment has a real cost to the freelancer. The negotiation isn't about whether a kill fee exists — it's about the percentage and trigger conditions.
Include in your contract: "If Client cancels the project after work has commenced, Client agrees to pay a cancellation fee equal to [X]% of the remaining project value, payable within 14 days of cancellation."
3. Work-for-hire clauses without carve-outs
Work-for-hire clauses assign ownership of everything you create for the client to the client. This is often appropriate — but standard work-for-hire language is frequently overbroad.
The problems:
• A broad assignment may cover your pre-existing code, design elements, templates, or frameworks that you use across multiple client projects
• If you've already licensed your tools or boilerplate to other clients, assigning them to a new client could create conflicting obligations
• Some work-for-hire clauses include "future developments" related to the work — these are almost always too broad
What to negotiate:
• Add a carve-out for "Contractor's pre-existing IP, tools, and frameworks, listed in Exhibit A"
• Specify that the client receives a license to use your pre-existing IP in the delivered work, but doesn't own it
• Retain portfolio rights: the right to show the work in your portfolio and promotional materials
For creative freelancers especially, your portfolio is your business development engine. Protect your right to show your work.
4. Vague scope definitions
Scope creep — where the client requests more work without additional compensation — is the number one freelancer complaint. It happens because the scope of work in the contract is too vague to establish clear boundaries.
Compare these two scope descriptions:
• Vague: "Design a website for Client's business"
• Specific: "Design a 5-page website (Home, About, Services, Blog, Contact) with 2 rounds of revisions per page, delivered as Figma files"
The vague version leaves everything open to interpretation. How many pages? How many revisions? What format? Every ambiguity is a potential disagreement.
Best practices for scope definition:
• List specific deliverables (number of pages, screens, or pieces of content)
• Specify the number of revision rounds included
• Define what "complete" looks like (what triggers final payment)
• Add a change order provision: "Any work outside this scope will be quoted and approved in a separate Change Order before work begins"
5. Unlimited revision clauses
"Unlimited revisions" is a marketing pitch, not a contract term — unless your contract actually says it. But some client contracts include language that effectively creates unlimited revision rights:
Watch for phrases like:
• "Contractor will revise work until Client is satisfied"
• "Work shall be revised to meet Client's reasonable requests"
• "Deliverables shall be subject to Client approval, with additional revisions as needed"
All of these give the client open-ended revision rights at your expense. A single unclear sentence can turn a week of work into a month of back-and-forth with no additional pay.
What to use instead: "This agreement includes [X] rounds of revisions per deliverable. Additional revision rounds are available at Contractor's standard hourly rate of $[X]."
6. Confidentiality clauses that restrict your portfolio and referrals
Confidentiality clauses in freelance contracts are reasonable — clients have legitimate interests in protecting their business information. But overly broad confidentiality terms can prevent you from doing things essential to running your freelance business.
Look for clauses that:
• Prohibit you from identifying the client in your portfolio without written permission
• Prevent you from listing the client as a reference
• Prohibit mentioning that you've worked with the client at all
• Cover information so broadly that your process, methodology, or general learnings are included
What you should negotiate:
• A specific carve-out allowing you to identify the client in your portfolio and proposals (without disclosing confidential project details)
• Permission to list the client as a past client for reference checks
• A clear definition of "confidential information" that excludes general skills and learnings
Some clients have legitimate reasons for restricting public attribution (stealth startups, sensitive industries). If that's the case, consider charging a premium for the restriction — it has real business value you're giving up.