Should I sign this freelance contract?
You typed "should I sign this freelance contract" because something didn't feel right. Maybe the scope is "unlimited revisions." Maybe the IP clause assigns everything you might ever make. Maybe payment is Net 90. This walks through the eight clauses where freelance contracts quietly drain hours, IP, and money, and where the cleanest negotiating moves usually live. We read the boilerplate so you don't have to.
For: freelancers and independent contractors reviewing a project agreement, MSA, or SOW before signing.
Not for: employees with offer letters (see the employment contract guide) or clients drafting freelance forms.
This is contract education, not legal advice. State law and local rules can change.
"Should I sign?" — what that question really asks
It is the question freelancers ask before signing — same question across disciplines, different specific worry underneath. The scope reads as endless. The IP clause asks for everything. The payment terms are 90 days and the deposit is zero. One freelancer online summed up the cost of getting it wrong: "lost $2,300 to scope creep" on a single project, after agreeing to a contract that didn't cap revisions or define done.
Most freelance contract problems aren't about whether the work itself is good. They're about the contract not specifying what good means, when it's done, who owns it, and when you get paid. The same eight or so clauses come up in every "what red flags should I look for" thread, regardless of the discipline.
A quick map of what's in your freelance contract
Project agreements, MSAs, and SOWs all share the same skeleton:
- Parties — your business entity, the client's entity, signing authority.
- Scope of work — deliverables, milestones, what's in scope and what isn't.
- Timeline — start, milestones, final delivery, dependencies.
- Fees and payment — total, schedule, late-payment terms, expenses.
- Revisions — number of rounds, what counts, additional-round pricing.
- Intellectual property — who owns what, when ownership transfers.
- Confidentiality — what's confidential, duration after the project ends.
- Warranties and indemnities — what each side guarantees, who pays if something breaks.
- Termination and kill fee — how either side ends the project, what's owed.
- Liability cap — maximum exposure if a dispute arises.
- Dispute resolution — courts, arbitration, governing law.
If yours is missing scope, payment schedule, or IP language, that's a flag — those gaps usually get filled later in the client's favor.
"Standard" doesn't mean fair
"This is just our standard contract" triggers most "should I sign" threads. Many client templates were drafted by counsel for the client and never reviewed by anyone on the freelance side. They favor the client by default — broad IP, no kill fee, Net 60 or 90 — because no one pushed back when the document was first written.
Two reframes from freelance threads. Contracts are negotiable on most projects worth signing — clients who say nothing is negotiable often mean nothing about scope is negotiable, while payment or IP often are. And the cleanest negotiating posture is positive and specific: "I'm in. I'd like to align on three things before I sign — revisions, payment cadence, and IP." That lands cleaner than a marked-up redline arriving cold.
The 8 freelance-contract clauses where money quietly leaks
None of these are illegal on their face. Each is where a freelance contract quietly converts into hours, IP, or money you didn't price into the deal.
Flag 1Vague or open-ended scope
What it says: "Designer will create marketing assets as needed for the Client's product launch."
Why it matters: "As needed" is the phrase freelancers post about most often when describing projects that ran 3x over estimate. The difference is between a project agreement and an open-ended retainer at no extra pay. Without specific deliverables and a definition of "done," every new request is in scope.
Normal vs. predatory: A clean scope lists deliverables ("3 hero images, 5 social cuts, 1 landing-page design at 1440px"), file formats, source-file ownership, and what's explicitly out of scope. Generic descriptions are the source of nearly every scope-creep dispute.
Flag 2Unlimited revisions
What it says: "Designer agrees to make all revisions necessary to the Client's satisfaction at no additional charge."
Why it matters: "Client's satisfaction" without bounds drops the effective hourly rate 50–80% by the end of a typical project. There is no signal that says "we're done" — only the client's eventual willingness to stop.
Normal vs. predatory: Two or three revision rounds within the project price is common; additional rounds billed at a stated rate. Unlimited revisions inside a fixed time-box is fine; unlimited revisions inside a fixed price is the trap.
Flag 3Aggressive IP assignment
What it says: "Consultant hereby assigns to Company all right, title, and interest in and to all work product, including derivative works, in perpetuity, throughout the universe."
Why it matters: "Throughout the universe" is real boilerplate from many client templates. The trap is that every sketch, draft, and outtake — not just the final deliverables — gets assigned. Your portfolio rights, future-use rights, and ability to repurpose general approaches all live in this clause.
Normal vs. predatory: Reasonable: assignment of final deliverables on full payment, with a license for portfolio use and a carve-out for general tools, processes, and pre-existing IP. Predatory: assignment of every intermediate file with no portfolio rights and no carve-outs.
Flag 4Net 60 or Net 90 payment terms
What it says: "Invoices payable within sixty (60) days of receipt." Or worse, ninety.
Why it matters: Net 60+ is the larger client's free loan from the freelancer. By the time you get paid, you've already spent the money and started a second project. Payment terms longer than 30 days are a financing decision, not a billing one.
Normal vs. predatory: A milestone schedule (deposit on signing, mid-point, final on delivery) protects against the worst of it. Common asks: Net 30, late-payment interest stated in the contract, and a right to pause work on overdue balances.
Flag 5Missing or weak kill fee
What it says: "Either party may terminate this agreement upon written notice, with no further obligation."
Why it matters: This is the one to fix before you start. If the client kills the project two weeks in, "no further obligation" can mean you're paid for nothing. A kill fee defines what's owed if the project ends early.
Normal vs. predatory: A graduated kill fee — often 25% before kickoff, 50% after midpoint, 100% on full delivery — is standard. The exact percentages are flexible; what matters is that an early termination doesn't leave you doing weeks of work for nothing.
Flag 6Work-for-hire that's broader than the project
What it says: "All services performed and deliverables provided shall be deemed 'work made for hire' under U.S. copyright law."
Why it matters: Under U.S. copyright law, only certain narrow categories of work made by non-employees qualify automatically as "work for hire." Where a project doesn't fit, the language sometimes adds a backup assignment to make ownership transfer anyway — which is fine when the assignment matches the deliverables, and a problem when it sweeps in everything you create during the engagement.
Normal vs. predatory: Reasonable: work-for-hire (or backup assignment) on the specific deliverables, on full payment, with a portfolio license. Predatory: assignment of all work product, including derivative works and adjacent material you make for other clients during the period.
Flag 7One-sided indemnification
What it says: "Consultant shall indemnify, defend, and hold harmless the Company from all claims, damages, and expenses arising from the services."
Why it matters: A one-sided indemnity makes the freelancer the legal sponge for everything. The case to watch: ending up paying the legal bills for a dispute you had nothing to do with.
Normal vs. predatory: Reasonable: a mutual indemnity, each side responsible for claims arising from their own breach or negligence, with a cap (often the project fee or a fixed multiple). Predatory: unlimited, one-way, includes consequential damages.
Flag 8Non-compete or non-solicit attached to a freelance contract
What it says: "Consultant shall not provide services to any business that competes with Company for twelve (12) months following termination."
Why it matters: A non-compete on an independent contractor is often legally weaker than the same clause on an employee, but the cost of testing it is the freelancer's. The practical answer is usually: most should be cut, and the ones that remain should be narrow.
Normal vs. predatory: Reasonable: a non-solicit limited to specific clients you actually worked with, for a defined period, paid for separately if it restricts post-engagement work. Predatory: any non-compete or broad "competitive business" language that limits your ability to work in your own field.
How Dang reads your freelance contract in 60 seconds
Every project agreement, MSA, or SOW you upload runs through eight clause-family checks:
- Scope and deliverables — definition specificity, exclusions, change-order language.
- Revisions — round count, definition of a revision, additional-round pricing.
- Payment terms — milestone schedule, deposit, late-payment terms, pause rights.
- IP and licensing — assignment scope, work-for-hire, portfolio license, pre-existing IP.
- Termination and kill fee — notice period, graduated kill fee, deliverable rights.
- Confidentiality / NDA — definition breadth, post-project duration, mutual vs. one-way.
- Indemnification and liability — mutuality, caps, consequential-damages exclusion.
- Restrictive covenants — non-compete, non-solicit, scope and enforceability flags.
You get a plain-English explanation per family, a risk score, and negotiation language calibrated to project size. Your document is processed in memory and deleted after analysis.
What's actually negotiable
More is negotiable than client templates suggest. Most freelance contracts get amended in the first round when freelancers ask cleanly.
Usually negotiable: revision count, payment milestones, late-payment terms, IP carve-outs (portfolio, pre-existing tools), kill-fee structure, indemnification mutuality, non-compete removal.
Sometimes negotiable: total project fee (especially against scope), Net terms (often 30 from a default of 60), liability cap, governing law/venue.
Usually not negotiable: client's signing authority, dispute-resolution forum at large clients, generic confidentiality.
A reasonable ask: "I'm excited to start. Before I sign, I'd like to align on three items — revision rounds, the payment milestone schedule, and the IP carve-out for my portfolio." Better than redlining a draft without warning.
State and federal rules that affect freelance work
Freelance work sits at the edge of contract law and labor classification. A few rules that actually matter:
Worker-classification rules (federal and state)
The IRS and Department of Labor each apply tests to determine whether a worker is genuinely an independent contractor or has been misclassified as one. Misclassification — common in long-running, full-time freelance arrangements with a single client — can trigger back-pay and tax exposure for the client and benefits implications for the worker. State tests vary; California's "ABC test" under Cal. Labor Code § 2775 is one of the strictest.
Freelance protection laws
Several jurisdictions have passed Freelance Isn't Free-style laws requiring written contracts above a stated dollar threshold and prompt payment. New York City's Freelance Isn't Free Act and New York State's Freelance Isn't Free Act are leading examples. Illinois and other states have followed. These laws give freelancers concrete remedies against late-paying clients.
Copyright and "work for hire"
Under U.S. copyright law (17 U.S.C. § 101), only nine narrow categories of work qualify as "work for hire" when made by a non-employee. Outside those categories, a written assignment is the operative transfer mechanism — which is why most well-drafted freelance contracts include both a work-for-hire designation and a backup assignment.
Before signing on a project above a few thousand dollars, check whether your jurisdiction has a freelance-protection law and whether the contract complies.
Frequently asked questions
Should I sign a work-for-hire freelance contract?
It depends on the work. For commissioned project deliverables the client is buying, work-for-hire (or a backup assignment) on the final output is often appropriate. For ongoing creative collaboration or work you might want to repurpose, a license can be a better fit. Only narrow categories of work made by non-employees qualify automatically as "work for hire" — the language matters.
What's a fair number of revision rounds?
Two or three rounds within the project price is common. "Unlimited revisions" is the major scope-creep risk — effective hourly rate routinely drops 50–80% by the end. The clean structure is a stated number of rounds, with additional rounds billed at a stated rate.
How do I get paid faster than Net 60 or Net 90?
A milestone schedule (deposit on signing, mid-point, final on delivery), a stated late-payment interest charge, and a right to pause work on overdue balances. For projects above a few thousand dollars, a 25–50% deposit before starting is the strongest protection.
Should I sign an NDA before discussing a project?
It can be appropriate for confidential projects. Check that it's mutual, covers only what's actually confidential, has a defined term (often two to three years), and doesn't sweep in your general industry knowledge or prior portfolio.
Dang! provides informational contract analysis, not legal advice. For consequential decisions — IP disputes, payment defaults, classification challenges — consult a licensed attorney in your state.