The 5 Contract Clauses That Have Saved Me Over $30,000 in Lost Revenue

The handshake is not the contract

I lost $11,400 in 2017 because a client and I "had an understanding."

The understanding was that I'd redesign their product dashboard over six weeks for a flat fee. The reality was twelve weeks of revisions, two full pivots they called "minor tweaks," and a final payment that never arrived because — and I quote — "the project changed so much it's basically a different scope."

They weren't wrong. And I had nothing in writing that said otherwise.

That was the last time I started work without a signed contract. Not a proposal. Not an email thread. Not a Slack message that said "yeah let's do it." A signed, dated, clause-by-clause document that would hold up if someone with a law degree had to read it.

Here's what I've learned since: most freelancers don't get screwed because clients are evil. They get screwed because the contract was vague, incomplete, or nonexistent. And fixing that doesn't require a lawyer on retainer. It requires knowing which five clauses actually matter.

Clause 1: The kill fee

Every contract needs a cancellation clause. Not "either party may terminate with notice." That's useless. You need a kill fee — a specific dollar amount or percentage the client owes if they cancel after work has started.

My standard: 50% of total project fee if cancelled after kickoff, 100% if cancelled after first deliverable is approved. Non-negotiable.

Why? Because I've blocked out my calendar for you. I've turned down other work. If you pull the plug in week three, I can't retroactively fill those weeks with paying clients. The kill fee isn't punishment — it's insurance against lost opportunity cost.

If a client pushes back on a kill fee, that tells you something. Specifically, it tells you they're already thinking about an exit before the project starts. Walk away.

Clause 2: Revision limits with teeth

"Unlimited revisions" is a phrase that should make you physically uncomfortable. I've seen it in proposals from freelancers who charge $150/hour, which means they're volunteering to work for free after round three.

My contracts specify:

Two rounds of revisions included in the project fee.
Each round defined as one consolidated set of written feedback, delivered within five business days of receiving the deliverable.
Additional rounds billed at my hourly rate, invoiced separately, due net 15.

The key word is "consolidated." Without it, clients send you twelve Slack messages over nine days, each one a new revision, and you're on round seven before you realize it.

I also specify that verbal feedback doesn't count. If it's not in writing, it didn't happen. This isn't because I don't trust my clients' memories. It's because I don't trust anyone's memory, including mine.

Clause 3: The IP transfer trigger

This is the one that trips up designers and developers more than anyone else. Who owns the work?

My answer: I own everything until you've paid everything. Full stop.

The contract language is: "All intellectual property rights transfer to Client upon receipt of final payment in full." Not upon delivery. Not upon approval. Upon payment.

This means if a client ghosts after receiving final files but before paying the last invoice, they're using work they don't legally own. That's leverage. Not the kind you want to use — but the kind that makes the conversation very simple when their accounts payable department suddenly "finds" your invoice.

I've had exactly one client test this. Their lawyer called mine. The conversation lasted four minutes. I was paid within 48 hours.

Clause 4: The scope fence

Scope creep is not a mystery. It's a contract failure. If your contract says "redesign the website" without defining what "the website" means, you've just agreed to redesign whatever the client decides "the website" includes next Tuesday.

My contracts include a scope section that reads like a punch list:

Specific pages or screens, listed by name.
Specific deliverable formats (Figma files, not "designs").
Specific exclusions — what's NOT included.
A change order process for anything outside the listed scope.

The exclusions matter more than the inclusions. I always list at least three things the project does NOT cover, because ambiguity is where scope creep lives. If copywriting isn't included, say so. If responsive breakpoints beyond desktop and mobile aren't included, say so. If QA testing isn't included, say so.

When a client says "I assumed that was part of it," you point to the exclusions list. Assumptions lose. Paper wins.

Clause 5: The late payment escalator

I wrote about invoice recovery recently, but the enforcement starts in the contract, not in the follow-up email.

My payment terms:

50% deposit before any work begins. No exceptions.
Remaining 50% due upon delivery of final deliverables, net 15.
Late fee: 1.5% per month on unpaid balances after the due date.
Work stoppage: All work pauses if any invoice is more than 10 days overdue.

The work stoppage clause is the one with real teeth. Clients who owe you money but still need deliverables will pay fast when the alternative is a frozen project and a missed launch date. Without this clause, you're in the absurd position of continuing to produce work for someone who isn't paying for the last batch.

I've paused work exactly three times in nine years. Each time, payment cleared within 72 hours. The clause works because it exists, not because you have to use it.

The template myth

Someone's going to read this and download a free contract template from a design blog. That's better than nothing, but barely.

Here's what I actually recommend: pay a freelance-focused attorney $500-800 to draft your base contract once. Then use that as your template for every project, adjusting only the scope, timeline, and fee for each client.

$700 for a contract that protects $50,000+ in annual revenue is not an expense. It's the cheapest insurance you'll ever buy. I paid $650 for mine in 2018. It has prevented at minimum $30,000 in potential losses since then. That's a 46x return.

If you can't afford an attorney yet, at minimum include these five clauses in whatever agreement you're using. Even a Google Doc signed by both parties with these provisions is infinitely better than a handshake and a "we're good, right?"

The uncomfortable truth

Good contracts don't make you harder to work with. They make you easier to work with. Professional clients — the ones who actually pay on time and respect boundaries — expect a contract. They're relieved when you have one, because it means you've done this before.

The only clients who resist contracts are the ones you don't want. Let them go find a freelancer who works on trust and vibes. You'll see that freelancer posting about late payments on Reddit in six months.

Trust is a feeling. Paper is a fact. Build your business on facts.