Freelance · Contracts

Do freelancers need a contract? (Yes — the 1-page version)

A practical guide — 5 min read

Short answer: yes — every time, even for small jobs, even for friends. You're not always legally required to have one (a verbal deal can be binding), but a written contract is the only thing that proves what was actually agreed when a client "remembers" the deal differently. And the jobs where freelancers get burned most are exactly the ones where they skipped the paperwork because it "felt like overkill."

You don't need a 20-page legal document. Here are the seven things a simple, one-page freelance contract must cover.

1

The parties and the project

Who's agreeing, and to do what. A one-line description of the project so there's no doubt later about which piece of work this covers.

2

Scope — included and excluded

What's in, and — just as important — what's out. The "not included" list is what kills scope creep before it starts. If it's not written down, it's not agreed.

3

Price and payment schedule

The total, how it's split (e.g. 50% upfront, 50% on delivery), and concrete due dates. A deposit isn't rude — it's standard, and it filters out clients who were never going to pay.

4

When ownership transfers

State that IP and ownership pass to the client on receipt of final payment — not on signature, not on creation. This keeps your leverage until you're actually paid.

5

Revision limits

How many rounds of revisions are included (e.g. two per deliverable), and that further rounds are billed at your hourly rate. "Until satisfied" with no cap is an open door to unpaid work.

6

Termination and a kill fee

What happens if either side walks away: the client pays for work completed to date, plus a cancellation fee if they end it mid-project. Otherwise a cancelled job at 70% done can pay you nothing.

7

A liability cap

Limit your total liability — typically to the fees paid under the contract. This stops a small job from turning into an unlimited legal exposure.

Already been sent a contract? Before you sign, paste it into our free contract red-flag checker → — it flags the risky clauses (IP on signature, Net-60, unlimited revisions) in plain English. No signup, nothing leaves your browser.

The mindset

A contract isn't you being difficult — it's you being clear. Reasonable clients expect one and are reassured by it; the ones who bristle at a fair, one-page agreement are showing you exactly how the project would go. Getting the paperwork right up front is the cheapest insurance in freelancing.

Never sign blind again

If you'd rather have a Claude Code skill read the whole contract and explain every risky clause before you sign, that's /redline — one of 7 in the Claude Code Freelancer Pack.

See the Freelancer Pack — $27

Common questions

Is a contract legally required? Not always — but always use one. It's what proves the deal if there's a dispute.

What must it include? Parties, scope (in and out), price + schedule, IP on final payment, revision limits, a kill fee, and a liability cap.

Even for friends? Especially for friends — that's where the paperwork gets skipped and relationships get damaged.

This is general information, not legal advice. For anything high-stakes, have a lawyer review your contract.