How to Write a Freelance Contract That Actually Gets You Paid
Most freelance disputes are not about quality. They are about scope that was never written down, payment terms that were assumed, and ownership that transferred before the money arrived.
A freelance contract does not need to be long. It needs to be specific in four places: what you are delivering, what happens when that changes, when you get paid, and who owns the work.
This guide walks through each, with the wording patterns that hold up and the ones that create arguments.
Define scope by deliverable, not by hours
"Design the website" is not a scope. "Five page designs at desktop and mobile, two rounds of revision per page, delivered as Figma files" is.
Write the deliverables as a numbered list, state the revision allowance explicitly, and add a sentence saying anything outside the list is a change order billed at your stated rate. That one sentence prevents most scope creep, because it turns an awkward conversation into an administrative one.
Payment terms that hold
- Deposit up front — 30-50% is standard and filters out clients who were never going to pay.
- Milestone payments on longer projects, tied to deliverables rather than dates you do not control.
- Net 14 or Net 30, stated explicitly. Silence defaults to arguments.
- Late fee: 1.5% per month is the common commercial figure. Check your state's usury rules for consumer clients.
- Suspension right: you may pause work on overdue invoices. Without this, you are contractually obliged to keep working unpaid.
Intellectual property should transfer on payment
The single most valuable clause in a freelance contract is the one saying IP transfers to the client upon receipt of full payment — not on delivery, not on project completion.
Until that point you retain ownership, which means an unpaid client using your work is also infringing it. That is a much stronger position than merely being owed an invoice.
Carve out your pre-existing tools, libraries, and templates. You license those; you do not sell them. And keep an explicit right to display the work in your portfolio unless the client pays for confidentiality.
Kill fees and termination
Clients cancel. The contract should say what happens: all work completed to date is billable, the deposit is non-refundable, and any milestone reached is payable in full.
A kill fee — often 25-50% of the remaining balance — compensates for the calendar time you reserved and cannot resell at short notice. State it as a fixed percentage rather than "reasonable compensation", which invites debate.
Classification: contractor, not employee
For US work, misclassification is the client's risk more than yours, but the contract should support the contractor position: you control how and when the work is done, you supply your own equipment, you may work for others, and you invoice rather than draw a salary.
Some states apply a strict test — California's ABC test being the best-known — and a contract alone will not override how the relationship actually operates. Write it to match reality.
Limit your liability
Cap total liability at the fees paid under the agreement, and exclude indirect and consequential damages. Without a cap, a $3,000 project can theoretically expose you to a claim many times that.
Expect enterprise clients to push back on the cap. A common landing spot is fees paid in the preceding twelve months, with carve-outs for confidentiality breaches and gross negligence.
Draft it in about five minutes
Answer a short questionnaire and the AI produces a state-aware contract you can edit, download, or send for signature. The free tier needs no credit card.
Frequently asked questions
Keep reading
LegalAIContracts provides document automation and AI analysis, not legal advice. Professional review is advisable for high-value or unusual agreements.