The Freelancer's Contract Disadvantage
A company sends you a contract. It's twelve pages of legal language written by their lawyer to protect them, not you. You know you should push back on some clauses, but you're afraid that negotiating will make you look difficult or, worse, cost you the project.
Here's what companies expect: negotiation. Most contracts are written with room to adjust. The clauses that seem non-negotiable often aren't — they're just the starting position. Companies respect freelancers who negotiate because it signals professionalism. The ones who sign everything without reading it signal desperation.
You don't need a lawyer for every contract (though for large engagements, you should have one). You need to know which clauses matter, what's reasonable, and how to ask for changes without creating friction.
The 'Redline Review' Email
Subject: Contract review — a few items to discuss
Hi [Client], Thanks for sending the contract. I've reviewed it and I'm largely comfortable with the terms. I'd like to discuss a few points: 1. [Clause name/number]: [What it currently says, briefly]. I'd suggest [your proposed change] because [business reason, not personal comfort]. 2. [Clause name/number]: [What it says]. Can we clarify [specific ambiguity]? 3. [Clause name/number]: [What it says]. This is standard in some industries but unusual in mine. Would you be open to [alternative]? Everything else looks good. Happy to discuss these on a call if that's easier. [Your name]
The structure matters: lead with 'I'm largely comfortable' (so they don't panic), limit to 3-5 items (so you're reasonable, not difficult), and give business reasons (not 'I don't like this'). Suggesting a call shows flexibility.
Clauses Every Freelancer Should Negotiate
Payment terms: Net 30 is standard but Net 15 is better for your cash flow. Always ask. Kill clauses: 'Payment upon client satisfaction' is a clause that lets them never pay. Replace with specific deliverables and approval timelines. IP ownership: Make sure you retain the right to show the work in your portfolio. Many contracts silently transfer all rights. Non-compete: Push back on any clause that prevents you from working with competitors. A narrow clause is fine. A broad one limits your livelihood.
Scope definition: Make sure the contract specifies what's included. 'All work related to the project' is dangerously vague. 'Deliverables listed in Exhibit A' is specific.
Termination: Both parties should be able to end the contract with reasonable notice. If only the client can terminate, you're in a vulnerable position. Kill-fee for early termination protects your pipeline.
When to Walk Away
Walk away if: they refuse to put payment terms in the contract, the non-compete would prevent you from doing your job, they want all IP rights including portfolio use, or the contract has a 'work for hire' clause that assigns everything you create (even unrelated work) to them during the engagement.
Walk away if: the negotiation itself is hostile. How a client negotiates a contract is how they'll behave during the project. If they're inflexible, dismissive, or aggressive before you've even started working together, it only gets worse.
The confidence to walk away comes from having enough pipeline that no single client can hold you hostage. If you can't walk away, that's not a contract problem — it's a business development problem.
Top comments (0)