A working freelance contract needs just eight clauses: scope, price, payment terms, revision limits, timeline, ownership transfer, a kill fee, and late-payment consequences. You do not need twenty pages of legalese — you need these eight things in plain English, agreed before work starts.

Why most freelance disputes are contract gaps

Almost every horror story — the endless revisions, the vanished final payment, the client who "owns" work they never paid for — traces back to something that was never written down. A contract is not about distrust. It is a shared memory of what you both agreed, written while everyone was still friendly. Here are the eight clauses that carry all the weight.

The eight essential clauses

1. Scope of work

List exactly what you will deliver, in countable units: five pages, three logo concepts, eight articles of up to 1,200 words. Then add one sentence that changes everything: "Work not listed above will be quoted separately." That line is your scope-creep insurance.

2. Price

One number, stated plainly, with what it covers. If the project has phases, price each phase. Avoid open-ended hourly language in fixed-scope projects — mixed models confuse clients and invite disputes about hours.

3. Payment terms

When money moves, and how. The freelancer standard: a deposit before work begins (30–50%), remainder on delivery — and final files released only after final payment. Name the payment method too; the fewer steps between "approved" and "paid," the faster you get paid.

4. Revision limits

State the number of revision rounds included (two is the common standard) and the rate for additional rounds. Define what a "round" is: one consolidated batch of feedback, not a rolling stream of one-line requests.

5. Timeline and dependencies

Give delivery dates — but tie them to the client holding up their end: "Timeline assumes feedback within 3 business days; delays extend the schedule accordingly." Without that sentence, a client who disappears for a month can still blame you for being late.

6. Ownership and usage rights

Say when rights transfer: "Full ownership transfers to the client upon final payment." The last three words are the important ones. Until paid, the work is yours — which is your leverage if payment stalls. Reserve the right to show the work in your portfolio.

7. Kill fee

Projects die — budgets get cut, companies pivot. A kill fee says what happens: "If the client cancels, the deposit is non-refundable and work completed to date is billed at $X/hour." This turns a cancellation from a fight into a math problem.

8. Late payment terms

Give invoices a due date (7–14 days) and a consequence: a late fee, a percentage per month, or paused work on ongoing projects. You may never charge it — the clause exists so the invoice is not treated as optional.

What you can safely skip

  • Pages of boilerplate — indemnification walls of text scare small clients and rarely matter at freelance scale.
  • Aggressive non-competes — unenforceable in many places and hostile in tone.
  • Jargon — "the party of the first part" adds nothing. Plain English is binding too.

If a project is large enough that real legal exposure exists, pay a lawyer for an hour. For everything else, clear beats clever.

Getting it signed without the awkwardness

The smoothest move is to fold the essentials into the proposal itself, so "accepting the proposal" and "agreeing to terms" are the same act. When your proposal states the scope, the price, the revision limit, and the payment terms — and the client accepts by paying a deposit — you have both agreement and commitment in one step. That is the model Tendrly is built on: a branded proposal with one clear price and a one-click Stripe payment link, so the yes and the deposit arrive together instead of drifting apart over a week of paperwork.

One habit that makes contracts work

Refer to the document, out loud, early and casually: "As per the proposal, that would be round two of two." Clients take contracts exactly as seriously as you do. If you treat yours as a live reference, so will they — and you will almost never need to enforce it, because nobody drifts far from a line everyone can see.

FAQ

Is an email agreement legally binding?

In most jurisdictions, yes — a clear offer, acceptance, and payment trail in email can form a contract. A single document is still better because everything lives in one place instead of scattered across threads.

Do I need a lawyer to write my freelance contract?

Not for typical projects. Plain-English clauses covering the eight essentials will prevent the disputes that actually happen. Bring in a lawyer when contract values get large or the client sends you their 30-page master services agreement.

What if a client refuses to sign anything?

That is a red flag, not an inconvenience. A client unwilling to agree to scope and payment terms in writing is telling you how they plan to treat both. At minimum, get the essentials confirmed in email before starting.