Freelance Contract Essentials: Protect Your Business and Get Paid

# Freelance Contract Essentials: Protect Your Business and Get Paid

I talk to freelancers every week who are owed money they'll never see. Not because the client is a scammer — usually because there was no contract, or the contract they had was a one-page joke that didn't cover what actually went wrong.

Here's the thing: a handshake deal works perfectly until it doesn't. And when it doesn't — when the client adds scope, delays payment, ghosts after delivery, or claims they own work you did for someone else — you have nothing to stand on. No contract means no leverage. You're left writing uncomfortable emails and hoping they do the right thing.

I've seen freelancers lose $5,000, $15,000, even $40,000 because they trusted a verbal agreement with someone who seemed great at the start. The client isn't always acting in bad faith. Sometimes they genuinely remember the agreement differently. That's the whole point of writing it down.

This guide covers the 12 clauses every freelance contract needs, the red flags to watch for in client contracts, and when it's worth paying a lawyer. If you're starting a freelance business, this is as important as getting your invoicing process right.

Download the free Freelance Contract Template at the bottom — it includes all 12 clauses with annotations explaining what each one does and how to customize it.

Why Handshake Deals Fail

Let's be direct about what goes wrong without contracts:

Scope creep with no boundaries. You agree to design a website. The client says "oh, can you also do the logo? And write some copy? And set up the email marketing?" Without a written scope, you can't point to anything that says those are separate projects at separate prices.

Payment ambiguity. You think net-30 means 30 days from delivery. They think it means 30 days from when they get around to reviewing it. Four months later, you're still waiting.

Memory is unreliable. This isn't about dishonesty. Two months into a project, neither of you remembers exactly what was said on that first call. You remember agreeing to three rounds of revisions. They remember "unlimited revisions until we're happy." Both of you are being honest about what you remember. You're just wrong.

Power dynamics shift. At the start, the client needs you. They're enthusiastic, responsive, reasonable. After you've done 80% of the work? The leverage shifts. Now they know switching freelancers is painful but possible. Without a contract, you have very little negotiating power when things get tense.

No exit strategy. Projects go sideways. Clients run out of money. Priorities change. Without a contract, there's no clean way to end things. No kill fee. No transition plan. Just awkward conversations and resentment.

The contract isn't about distrust — it's about clarity. The best client relationships I've seen are the ones where both sides know exactly what they agreed to.

The 12 Essential Clauses

These aren't optional. Every single one of these protects you from a real, common problem that freelancers actually experience.

1. Scope of Work

This is the most important clause in your entire contract. Everything else — payment, timeline, revisions — flows from the scope. If the scope is vague, everything else falls apart.

What to include:

• Specific deliverables (not "design work" — instead "homepage design, 5 interior page templates, mobile-responsive, delivered as Figma files and exported assets")
• What's explicitly NOT included (this is just as important)
• Format of final deliverables
• Any dependencies on the client (content, assets, access, approvals)

Example language:

> "Contractor will design and deliver a homepage layout and five (5) interior page templates in Figma format, including mobile-responsive versions. Deliverables include exported PNG/SVG assets. Scope does not include copywriting, development/coding, stock photography, or ongoing maintenance."

The more specific you are, the easier it is to say "that's outside the scope — here's what that would cost as an add-on."

2. Timeline and Milestones

Don't just put a start and end date. Break the project into milestones with specific dates and what triggers the next phase.

What to include:

• Project start date (and what "start" means — after deposit? After receiving client assets?)
• Key milestones with dates
• What happens when the client causes delays (the timeline shifts — this needs to be explicit)
• Final delivery date
• Buffer for review/approval periods

Critical addition: Client delay clause. If the client takes three weeks to provide feedback when the contract allows five business days, your timeline shifts accordingly. Without this clause, you're on the hook for a deadline that's impossible because of their delays.

3. Payment Terms

This is where freelancers get burned the most. Be ruthlessly specific.

What to include:

• Total project fee (or rate structure — hourly, per-word, per-deliverable)
• Deposit amount and when it's due (I recommend 25-50% before any work begins)
• Milestone payments tied to specific deliverables
• Payment method (ACH, wire, check — and who pays fees)
• Net terms (net-15 is better than net-30 for freelancers)
• Currency
• Late payment penalties (1.5% per month is standard)

If you're building out your freelance billing process, check out our complete invoicing guide for the mechanics of actually getting paid on time.

Pro tip: Never start work without a deposit. Period. A client who won't pay a deposit is telling you something important about how they handle money. If they push back, that's a red flag — not a negotiation point.

4. Revision Policy

"Unlimited revisions" is a promise you can't keep and a client expectation you can't manage. Define revisions clearly.

What to include:

• Number of revision rounds included (two to three is standard)
• What counts as a "round" (all feedback consolidated into one round, not drip-fed over weeks)
• Timeframe for client to submit revision requests
• Cost for additional rounds beyond what's included
• What counts as a revision vs. a new request (changing the color scheme = revision; redesigning the entire layout = new scope)

Example language:

> "Fee includes two (2) rounds of revisions per deliverable. A revision round consists of consolidated feedback submitted within five (5) business days of deliverable presentation. Additional rounds are billed at $150/hour. Requests that alter the fundamental scope, direction, or concept constitute new work and will be scoped and quoted separately."

5. Kill Fee (Cancellation Clause)

Projects get canceled. Clients run out of money, change direction, get acquired, or just lose interest. You need to be compensated for the time you blocked off and the work you've already done.

What to include:

• Cancellation by client: payment for all completed work plus a percentage of the remaining contract (25-50% is common)
• Cancellation by you: return of payment for undelivered work (minus deposit for work completed to date)
• Notice period required (typically 7-14 days written notice)
• What happens to work completed so far (does the client get it? Only if they've paid for it?)

This clause is the one freelancers skip most often and regret most deeply. A $20,000 project canceled halfway through with no kill fee means you turned down other work for nothing.

6. Intellectual Property (IP) Ownership

Who owns the work? This seems obvious but it absolutely is not.

The default rule (in most states): As a freelancer, you own the copyright to work you create — even if someone paid you for it. This is different from employment, where work-for-hire doctrine typically gives the employer ownership.

What to include:

• When IP transfers (upon final payment is the standard — this protects you)
• What IP transfers (final deliverables only? Or all drafts, source files, unused concepts?)
• License vs. full transfer (sometimes you grant a license to use the work rather than transferring ownership entirely)
• Portfolio rights (you should retain the right to display the work in your portfolio)
• Pre-existing IP (anything you bring to the project that existed before — frameworks, code libraries, templates — stays yours)

Critical protection: IP transfers upon final payment in full. If the client hasn't paid you, they don't own the work. This is your best leverage for collecting payment.

7. Confidentiality (NDA)

Most clients will want some level of confidentiality. That's reasonable. What's not reasonable is a one-sided NDA that restricts you but not them.

What to include:

• What information is confidential (be specific — "all information" is too broad)
• Duration of confidentiality (2-3 years is standard; "perpetual" is aggressive)
• Exceptions (publicly available information, information you already knew, information you develop independently)
• Mutual confidentiality (you keep their secrets, they keep yours — including your rates and processes)

Watch out for: NDAs that prevent you from saying you worked with the client at all. That kills your ability to build your portfolio and get referrals. Push back on this or negotiate portfolio rights separately.

8. Liability Limitation

If something goes wrong with the work you deliver — a website crashes, a design infringes a trademark someone didn't tell you about, copy contains a factual error — how much are you on the hook for?

What to include:

• Cap on liability (typically limited to the total contract value — you should never be liable for more than what they paid you)
• Exclusion of consequential damages (you're not liable for their lost profits, lost business, or downstream consequences)
• Client's responsibility for information accuracy (if they gave you wrong data, that's on them)

Example language:

> "Contractor's total liability under this agreement shall not exceed the total fees paid by Client. In no event shall Contractor be liable for indirect, incidental, consequential, or punitive damages, including lost profits or business interruption."

9. Indemnification

This clause says: if your work causes a legal problem, who's responsible? And if my work gets me sued because of something you did (or didn't tell me), who pays the legal bills?

What to include:

• Client indemnifies you for claims arising from materials they provided (logos, text, images they gave you that turn out to infringe someone's copyright)
• You indemnify the client for claims arising from your original work
• Neither party indemnifies the other for the other party's negligence

Keep it mutual. If a client wants you to indemnify them for everything but won't indemnify you for anything, that's a non-starter.

10. Termination

Different from the kill fee. Termination covers the process of ending the contract, while the kill fee covers the financial consequences.

What to include:

• Termination for convenience (either party can end it with X days written notice)
• Termination for cause (material breach, like non-payment or failure to deliver)
• Cure period (how many days does the breaching party have to fix the problem before termination kicks in — typically 10-14 days)
• What happens after termination (payment for completed work, return of materials, IP status)

11. Governing Law

Which state's laws apply if there's a dispute? This matters more than you think.

What to include:

• State whose laws govern the contract (typically your state, the client's state, or wherever makes sense geographically)
• Whether disputes are handled in that state's courts

Practical advice: If you're in California and your client is in New York, having to fly to New York for a court case adds significant cost and hassle. Try to make it your state, or at least agree on a neutral location.

12. Dispute Resolution

How do you resolve disagreements before they become lawsuits?

What to include:

• Step 1: Good-faith negotiation (30 days to try to work it out directly)
• Step 2: Mediation (a neutral third party helps you find a resolution — cheaper and faster than court)
• Step 3: Arbitration or litigation (binding arbitration is typically faster and cheaper than court, but you give up the right to a jury trial)
• Who pays for mediation/arbitration (typically split 50/50)

I recommend including a mediation step before arbitration. Most disputes that go to mediation get resolved there — and it costs a fraction of what arbitration or litigation costs.

Red Flags in Client Contracts

Sometimes the client sends you their contract. Here's what to watch for:

"Work for hire" language. This means they own everything from the moment you create it — including drafts, concepts, and source files. If you're fine with that, great. But know what you're agreeing to. Many freelancers don't realize this strips them of copyright from day one.

No kill fee or cancellation clause. If the client can cancel anytime without paying for work completed, you're taking all the risk.

"Unlimited revisions." This is a red flag whether it's in your contract or theirs. It means there's no definition of "done."

Non-compete clauses. Some client contracts say you can't work with their competitors for 6-12 months. For a freelancer, this is devastating. You're not an employee — you can't be locked out of your industry. Push back hard on these or negotiate them down to something reasonable (like not working with their direct competitor on a directly competing project during the engagement).

Payment only upon "satisfaction." What does satisfaction mean? Who decides? This gives the client unlimited leverage to withhold payment by claiming they're not satisfied. Tie payment to deliverables, not feelings.

Automatic renewal. Some contracts renew automatically unless you give 30-60 days notice. Make sure you know what you're signing up for.

IP assignment of everything you create "in connection with" the project. This could be interpreted to include your own ideas, tools, and frameworks that you use across clients. Make sure pre-existing IP is explicitly excluded.

Independent Contractor Language

If you're the one being hired, your contract should clearly establish that you're an independent contractor — not an employee. This matters for tax purposes and liability. If you're unclear on the difference, read our 1099 vs W-2 classification guide.

Key language to include:

• "Contractor is an independent contractor and not an employee, partner, or agent of Client."
• Contractor controls how and when work is performed
• Contractor provides their own tools and equipment
• Contractor is responsible for their own taxes (no withholding)
• Contractor may work for other clients simultaneously

Why this matters: If the IRS reclassifies you as an employee, the client could owe back employment taxes, and you could lose your ability to deduct business expenses. The contract language alone doesn't determine classification (the IRS looks at the actual working relationship), but it's an important piece of the puzzle.

When to Use a Lawyer

Not every contract needs a lawyer. But some do.

Use a lawyer when:

• The contract value is over $10,000
• The client is sending you their contract (especially if it's long and full of legalese)
• There's a non-compete or exclusivity clause
• IP ownership is complex (multiple parties, licensing, derivative works)
• You're working with a government agency or large corporation
• You're entering a retainer or ongoing agreement (not just a one-off project)

Skip the lawyer when:

• It's a straightforward project under $5,000
• You're using your own contract template that a lawyer has already reviewed
• The client is a small business or individual with a simple project

Cost reality: A lawyer reviewing a freelance contract typically costs $300-$800. A lawyer drafting one from scratch costs $800-$2,000. Compare that to the cost of a dispute on a $20,000 project with no contract.

Pro tip: Pay a lawyer once to review your template contract. Then use that template for every client, customizing the scope and payment sections. That $500-$1,000 investment pays for itself on the first project.

Putting It All Together

Here's the workflow:

1. Initial conversation — discuss the project, get the details, make sure it's a good fit
2. Send a proposal — outline the scope, timeline, and pricing
3. Client agrees — now send the contract
4. Both parties sign — use DocuSign, HelloSign, or even a simple email confirmation (digital signatures are legally binding)
5. Collect the deposit — don't start work until it clears
6. Do the work — deliver according to the milestones in the contract
7. Invoice per the payment schedule — and follow up on late payments (here's our guide on handling late payments)

The contract should feel like a safety net, not a weapon. The best freelancer-client relationships are ones where neither side ever needs to reference the contract because the expectations were clear from the start.

The Holdings Angle

One thing I see constantly: freelancers manage their contracts well but their money poorly. They collect the deposit, pay for tools and software, cover their own taxes, and at the end of the year they have no idea where the money went.

That's why we built Holdings — free business checking with AI bookkeeping built in. Every payment you receive, every expense you pay, automatically categorized and tracked. When contract payments come in, you can see exactly which project it's from. When tax time hits, your deductions are already organized.

No minimum balance. No monthly fees. 1.75% APY on your balance. $3M FDIC coverage through our partner i3 Bank. It's the banking setup your freelance business actually needs.

---

Download the [Freelance Contract Template](/downloads/freelance-contract-essentials-guide/freelance-contract-template.pdf) — all 12 clauses, fully customizable, with annotations explaining what each one does and how to adapt it to your projects.

— Archer