Contract vs. Handshake Deal

Short answer: a handshake deal is better than nothing, but it's a bad bet for freelance work. A verbal agreement can be legally binding — but "binding" is worthless if you can't prove what was actually agreed. When a payment dispute or a scope fight happens, a handshake comes down to your word against the client's, and that's a fight you usually lose. A short written contract costs you ten minutes and converts every "we said" into "here's the clause." For anything beyond a tiny favor, get it in writing — every time. Here's what each actually protects, and the minimum terms to lock down.

The single most disputed term is always money. The free Freelance Rate Calculator → helps you set a number you can quote with confidence — and a number you're confident in is one you'll actually put in writing instead of mumbling over a handshake.

Is a handshake deal legally binding?

Often, yes — a verbal agreement can form a valid contract in many situations. But legality isn't the problem. Provability is. If the client later says the price was lower, the scope was bigger, or the deadline was different, a handshake gives you nothing to point to. Courts and even informal disputes turn on evidence, and "we both remember it differently" almost always favors the party who owes you money. A written contract doesn't make the deal more legal — it makes it provable, which is the part that actually protects you.

Contract vs. handshake, side by side

Where handshake deals actually bite you

The trouble almost never shows up at the start, when everyone's friendly. It shows up later:

• The client "remembers" a lower price — and without a number in writing, you're negotiating from zero.
• Scope quietly doubles — "just a couple more tweaks" becomes a second project with no extra pay, because nothing defined where the first one ended.
• Payment drifts — no agreed terms means no late fee, no deadline, and no leverage when an invoice ages out to 60 days.
• The project dies halfway — and with no kill fee or termination clause, you eat the hours you already worked.

Every one of these is cheap to prevent and expensive to fix after the fact. The contract is the prevention.

Quoting the job is the moment to get it in writing. Use the free Freelance Rate Calculator → to lock your real take-home rate first, then put that exact number in a one-page agreement. A price you've actually calculated is a price you'll commit to paper — which is where it protects you.

What about a written confirmation email?

If a full contract genuinely isn't going to happen — a tiny job, a long-trusted repeat client — a confirmation email is your minimum viable contract. After the verbal chat, send a short message: "Confirming what we agreed: [deliverable], by [date], for [$amount], 50% upfront. Reply to confirm and I'll get started." Their "yes" in writing isn't as strong as a signed agreement, but it's miles ahead of a handshake — now the terms exist somewhere you can both read.

That said, the email is the floor, not the goal. For real projects, use an actual contract template — it takes minutes and covers the clauses an email won't.

The minimum terms to always get in writing

You don't need a ten-page legal document. A one-pager that nails these covers the overwhelming majority of disputes:

1. Scope — what you're delivering, and explicitly what's not included.
2. Price & payment terms — the amount, the schedule, and when it's due.
3. Deposit — how much upfront before work starts.
4. Timeline — key dates and what they depend on from the client.
5. Revisions — how many rounds are included before extra charges apply.
6. Termination / kill fee — what happens, and what you're owed, if it ends early.
7. Ownership — who owns the work, and when (usually on final payment).

Defining scope and exclusions in particular is what stops the "just one more thing" problem — see scope-creep pricing and the scope-of-work document for how to write that part well.

How to ask for a contract without killing the vibe

Plenty of freelancers skip the contract because asking feels awkward or distrustful. It isn't — it's professional, and good clients expect it. Frame it as how you work, not as suspicion:

"Great, sounds like a fit. I'll send over a short agreement covering scope, timeline, and payment so we're both clear — once it's signed and the deposit's in, I'll get started."

Notice it's stated, not asked. A contract isn't a favor the client grants you; it's a standard step. Clients who push back hard on any written terms are themselves a red flag — the ones who'll later dispute the deal are exactly the ones who didn't want it written down.

Watch-outs

• Never start work before it's signed. Your leverage is highest before you've delivered anything — once the work's done, the contract is much harder to get.
• A handshake plus a deposit beats a handshake alone — but it's still not a contract. Get the terms written too.
• Verbal changes don't count. If scope or price shifts mid-project, confirm the change in writing the same way you confirmed the original.
• Keep it readable. A short, plain-English one-pager that clients actually sign beats a dense template they stall on.

Put a number you trust into the agreement

A contract is only as good as the price inside it. The $9 Freelance Rate & Tax Calculator spreadsheet nets your income against self-employment tax and expenses so the rate you write into every agreement actually covers your costs and take-home. Want a matching invoice to bill against it? Get the calculator + a clean invoice template in the $14 Starter Pack →

Frequently asked questions

Is a handshake deal legally binding for freelance work?

A verbal agreement can be legally binding in many situations, but legality isn't the real issue — provability is. If a client disputes the price, scope, or deadline, a handshake leaves you with only your word against theirs, which is very hard to enforce. A written contract makes the same deal provable, which is what actually protects you when something goes wrong.

Do freelancers really need a written contract?

For anything beyond a tiny favor, yes. A short written contract takes minutes and prevents the most common and expensive disputes: a client remembering a lower price, scope quietly expanding without extra pay, payment drifting with no agreed terms, and projects ending early with no kill fee. The cost of writing it is trivial compared to the cost of not having it during a dispute.

What's the minimum a freelance contract should include?

At minimum: the scope and what's excluded, the price and payment terms, the deposit, the timeline, the number of revisions included, termination or kill-fee terms, and who owns the work and when. A one-page plain-English agreement covering these handles the large majority of disputes without needing a long legal document.

Is a confirmation email as good as a contract?

It's much better than a handshake but weaker than a signed contract. A confirmation email restating the agreed deliverable, date, price, and deposit — with the client's written "yes" — creates a record both sides can point to. Use it as a minimum for tiny jobs or trusted repeat clients, but for real projects use an actual contract template that covers clauses an email won't.

How do I ask a client to sign a contract without seeming distrustful?

Frame it as your standard process rather than a request: tell the client you'll send a short agreement covering scope, timeline, and payment so you're both clear, and that you'll start once it's signed and the deposit is in. Good clients expect this and take it as a sign of professionalism. Clients who resist any written terms are often the ones most likely to dispute the deal later.