Let me tell you about the most expensive lesson I ever learned.
A client hired me to build a website. We agreed on £3,200. Shook hands over Zoom. I started working immediately.
Three weeks in, the project was 80% done. Then the client went quiet. No replies. No calls. Nothing.
Two weeks later, they emailed. "We've decided to go in a different direction." That was it. No payment for the work I'd done. No explanation. Just silence.
I had no contract. No signed agreement. No legal ground to stand on.
I never made that mistake again.
Why most freelancers skip contracts
I get it. Contracts feel formal. Intimidating. Unnecessary when the client seems nice.
You think: "We've had three great calls. They're a good person. I don't want to make this weird by sending a legal document."
Here's what I've learned: the contract isn't for when things go well. It's for when they don't. And eventually, they won't.
It's not about trust. It's about clarity. A good contract protects both sides. It sets expectations. It answers the question neither of you wants to ask: "What happens if this goes wrong?"
The clauses every freelance contract needs
You don't need a 20-page document drafted by a lawyer. You need a clear, simple agreement that covers the important stuff. Here's what that looks like.
Scope of work. This is the most important clause. Write exactly what you're delivering. Not vaguely. Specifically.
Bad: "Build a website."
Good: "Design and develop a 5-page responsive website (Home, About, Services, Portfolio, Contact) using Next.js, with mobile-responsive design and a contact form that sends emails to the client's inbox."
The more specific your scope, the fewer arguments you'll have later. Scope creep is the number one reason freelance projects go sideways. A clear scope kills it before it starts.
Payment terms. How much. When. How.
I always require 50% upfront. Non-negotiable. If a client won't pay a deposit, that's a red flag. They're either not serious or they've burned freelancers before.
Spell out the schedule: "50% due before work begins. 50% due upon delivery." Include your payment method. Include your currency. Include what happens if they pay late.
Timeline and milestones. When does the project start? When does it end? What are the checkpoints along the way?
I break every project into 2-3 milestones. Each one has a deliverable and a date. This keeps the project moving and gives the client visibility into progress.
"Milestone 1: Homepage and navigation — delivered by April 5. Milestone 2: Remaining pages — delivered by April 15. Milestone 3: Testing, revisions, and launch — completed by April 22."
Revisions. This one saves your sanity. Define how many rounds of revisions are included. Two is standard. Three is generous. Unlimited is a trap.
"Two rounds of revisions are included. Additional revisions will be billed at £75 per hour."
Without this clause, you'll end up in revision hell. I once had a client request 11 rounds of changes on a logo. Never again.
Kill fee. What happens if the client cancels? This is the clause I wish I'd had for that £3,200 project.
"If the project is cancelled after work has begun, the client agrees to pay for all completed work at the project's hourly equivalent rate, with a minimum of 25% of the total project fee."
This protects you from doing weeks of work and getting nothing. It also makes clients think twice before pulling the plug on a whim.
Intellectual property. Who owns the work? When?
Standard practice: the client owns the final deliverables after full payment. Not before. If they haven't paid, you haven't transferred ownership.
"All intellectual property rights transfer to the client upon receipt of final payment. Until full payment is received, all work remains the property of the freelancer."
This is your leverage. Don't give it away before you're paid.
Confidentiality. Keep it simple. You won't share their business information. They won't share your pricing with competitors. Two sentences is enough.
Late payment penalties. Pick a number. 5% per month is common. The point isn't to make money from late fees. It's to motivate on-time payment.
"Invoices unpaid after 14 days will incur a late fee of 5% per month on the outstanding balance."
The clauses most freelancers forget
The ones above are obvious. These are the ones that save you when things get weird.
Communication terms. How and when will you communicate? I include this now because I once had a client calling me at 11pm on Saturdays.
"Communication will happen via email and scheduled calls during business hours (Monday–Friday, 9am–6pm GMT). Response time: within 24 hours on business days."
Client responsibilities. The project doesn't just depend on you. The client needs to provide content, feedback, logins, brand assets. Put deadlines on their deliverables too.
"Client will provide all page content and brand assets by April 1. Delays in client deliverables will extend the project timeline by an equivalent number of days."
This is huge. If the client takes three weeks to send you their logo, that's not your fault. But without this clause, you'll be the one apologising for the delay.
Portfolio rights. Can you show this work in your portfolio? Get it in writing.
"The freelancer retains the right to display the completed work in their portfolio and marketing materials."
Most clients don't care. But the one who does will care a lot. Get it agreed upfront.
How to send a contract without making it awkward
This is the part everyone worries about. "Won't the client think I don't trust them?"
No. They'll think you're professional. Every serious freelancer uses contracts. If a client pushes back on signing one, that's not a client you want.
Here's what I say: "Before we kick off, I'll send over a quick agreement that covers the scope, timeline, and payment terms we discussed. It protects us both and makes sure we're on the same page."
That's it. No drama. No awkwardness. Just professionalism.
Templates are fine. Just customise them.
You don't need to write a contract from scratch every time. Start with a template. Change the scope, the price, the dates. Keep the rest.
What matters is that it exists, it's clear, and it's signed.
I used to spend 30 minutes writing contracts in Google Docs. Now I use SoloPad — I type the project details, the AI drafts the contract, I review it, and the client signs it right in the platform. Takes about 5 minutes.
But even if you use a basic Word doc, use something. A mediocre contract is infinitely better than none.
The contract isn't the enemy. Ambiguity is.
Every freelance horror story I've heard — scope creep, ghosted payments, endless revisions, stolen work — could have been prevented with a clear contract.
It won't guarantee a perfect project. Nothing does. But it gives you a foundation. Something to point to when expectations don't match. Something that says: "This is what we agreed."
That's worth more than any handshake.
SoloPad generates professional contracts with AI, gets them signed, and tracks payment — all in one place. Starting at £5/mo. Try it free for 30 days.