Nobody starts freelancing because they love paperwork. You start because you can do the work. The contract feels like the part that makes a friendly conversation suddenly cold — so you skip it, send a one-line email, and get to the fun bit.
That works. It works right up until a client decides “one round of revisions” meant four, or that the invoice you sent 60 days ago can wait another 30. At that point the difference between an awkward chase and a clean resolution is a document you wrote in twenty minutes, months earlier.
Here’s the part most advice gets wrong: you do not need a lawyer to write your first freelance contract. You need seven clauses, plain English, and a signature. This is how to put that together, what to charge for, and — because it matters — when a contract is genuinely overkill.
[PLACEHOLDER: nota de experiencia propia — cuántos contratos he firmado como freelancer y el caso concreto en que una cláusula de scope evitó un conflicto.]
What a contract is actually for
Almost every freelancer imagines the contract as a weapon: the thing you wave in court when a client refuses to pay. In practice, suing a client over a $3,000 invoice is a terrible use of your life. The legal remedy is real but rarely worth exercising at freelance invoice sizes.
The contract earns its keep somewhere else entirely — in the conversation you have before the disagreement. When a client says “can you just also do the landing page?”, a scope clause turns a confrontation into a lookup: that’s outside what we agreed, here’s what it costs to add. You’re not saying no. You’re pointing at a document you both signed.
That reframing changes what you optimise for. Your contract doesn’t need to survive a courtroom. It needs to be specific enough that two reasonable people reading it six weeks later agree on what was promised.
The seven clauses that carry the weight
Freelance contract templates float around with 14 sections. Most of them are padding. These seven do the actual work, and if you only ever write these, you are ahead of most of the field.
1. The parties and the dates
Full legal names — yours or your company’s, and the client’s registered entity, not the brand name on their website. Start date, and either an end date or a delivery date. This sounds trivial until you invoice a company that turns out to be three companies.
2. Scope of work
The most important paragraph in the document. List deliverables as countable nouns: “three blog posts of 1,200–1,500 words each,” not “content support.” Then add the sentence that does half the work of the whole contract: anything not listed above is out of scope and quoted separately.
3. Revisions
State the number and what counts as one. “Two rounds of revisions per deliverable; a round is a single consolidated set of comments returned within five business days.” Without that second half, a client sends nine emails and calls it one round.
4. Payment terms
Amount, currency, schedule, and a due date measured in days from invoice. If you take a deposit, say it’s non-refundable and say when work starts (on receipt, not before). If you charge late fees, name the percentage here.
5. Intellectual property
Say when ownership transfers. The standard freelance position — and the one I’d defend — is that IP transfers on final payment, not on delivery. Until then you’ve licensed them nothing. Add a line reserving your right to show the work in your portfolio, unless they buy that right out.
6. Cancellation and kill fee
Projects die. Decide now who pays for the work already done. A common structure: either side can terminate with written notice; the client pays for everything completed to that point, plus a percentage of the remaining fee if they cancel late in the project.
7. Confidentiality
Two sentences is enough for most engagements: you won’t share their non-public information, and the obligation survives the end of the project. If a client sends a 12-page NDA before they’ll even talk, that’s a signal about how they’ll behave later.
What’s deliberately missing: indemnification, limitation of liability, governing law and arbitration clauses. They belong in enterprise contracts, and if a client’s legal team sends you a paper with all of them, that’s the moment to spend money on an actual lawyer rather than guessing.
Scope, written the boring way
Scope creep isn’t malice. It’s ambiguity, compounding. Here’s the same project written two ways.
The version that will hurt you: “Redesign of the marketing website, including all necessary pages and revisions until the client is happy.”
The version that won’t: “Design of five pages (Home, Pricing, About, Contact, one Blog template) delivered as Figma files at desktop and mobile widths. Two rounds of revisions per page. Does not include: copywriting, development, image licensing, or post-launch changes. Additional pages quoted at $X each.”
The second one is longer and less elegant, and it is the entire reason the project ends on time. Notice it defines the work by what it excludes as much as what it includes — “does not include” is the highest-leverage phrase in a freelance contract.
If you’re pricing this stage rather than writing it, the scope and the number are the same conversation: our guide to setting a freelance rate you can defend works through the floor-rate math that should sit behind these figures.
Payment terms: the numbers that decide whether you get paid
Most late payments are structural, not personal. These are the terms worth arguing for, and what they actually do.
| Term | What to write | Why it matters |
|---|---|---|
| Deposit | 30–50% upfront, non-refundable, work starts on receipt | Filters out clients who were never going to pay, and covers your time if the project stalls |
| Payment window | Net 14, or Net 7 for small projects | Net 30 is a corporate default, not a law. Shorter windows are normal for one-person suppliers |
| Milestones | Split anything over ~4 weeks into 2–3 payments | Caps your exposure: the most you can lose is one milestone, not the whole project |
| Late fee | 1.5% per month on overdue balances, or a flat fee | Rarely collected — but it makes the follow-up email a policy rather than a personal complaint |
| Final payment | Due before files transfer and before IP passes | The single most effective clause in the document. Leverage disappears the moment they have the files |
Once the terms are agreed, the mechanics matter too — the invoice has to arrive quickly and land somewhere they can actually pay from. We covered that end of it in how to send an invoice as a freelancer.
Get the free Freelancer Tool Stack
Where to get the document: templates vs software
You have three realistic options, and the right one depends almost entirely on how often you sign new clients.
| Option | Typical cost | Signing included? | Best for |
|---|---|---|---|
| Free template + email | $0 | No (typed name or scanned signature) | Your first few clients, or repeat work with people you know |
| Dedicated e-signature tool (Dropbox Sign, DocuSign) | ~$15–25/mo entry plans [CONFIRM] | Yes, with audit trail | Occasional contracts where you want a clean, legally solid signing record |
| All-in-one freelance platform (Bonsai, Dubsado, HoneyBook) | ~$21–39/mo [CONFIRM] | Yes, plus proposals and invoicing | Signing 2+ new clients a month and already paying for invoicing |
| Word processor + PDF | $0 | No | Perfectly valid; slower, and you lose the “client opened it” signal |
Pricing changes often — check current plans before you commit. [AFFILIATE: bonsai] [AFFILIATE: dubsado] [AFFILIATE: dropbox-sign]
My honest read: if you’re signing fewer than one new client a month, a template and a signed PDF is genuinely fine, and paying $30/month to send two contracts a year is a bad trade. The moment contracts, proposals and invoices start living in three different places, the all-in-one platforms stop being a luxury — that’s the same threshold we hit when comparing proposal software for freelancers, and the tools overlap heavily. The rest of the stack sits in our proposals, contracts and CRM silo, and the wider picture is in the best software for freelancers guide.
Getting it signed without stalling the deal
The most common failure isn’t a bad contract. It’s a good contract that sits unsigned for three weeks while the project quietly starts anyway.
Three things fix that. First, send the contract with the proposal, not after — a signature request that arrives days later reads as a new negotiation. (If you’re building that proposal now, this walkthrough covers the structure.) Second, keep it to two pages; a six-page document goes to whoever handles legal, and you’ve lost a fortnight. Third, never start work on a verbal yes — the deposit and the signature arrive together, and that rule protects you from exactly the clients most likely to test it.
If they want changes, that’s normal and usually fine. Redlines on payment timing or IP transfer, though, are worth holding the line on. Those two are where the money actually lives.
What a contract will not do for you
Being straight about the limits: a contract will not make an insolvent client solvent, will not compel payment without you actually enforcing it, and will not fix a mismatch of expectations you never discussed out loud. A signed document with a vague scope clause is worse than no document, because it gives both sides false confidence.
It also won’t substitute for judgement. If a prospect haggles the deposit, disputes the revision count, and wants IP on delivery before you’ve written a line, the contract has already done its job — it surfaced the client you shouldn’t take.
Who needs this — and who can skip it
Write the full contract if: the project is over roughly $1,000 or two weeks; it’s a new client; the deliverable is something the client will build a business on (a website, a brand, a codebase); or there’s any chance of a third party being involved.
An email confirmation is enough if: it’s a small, fast job for a client who has already paid you reliably; the scope is one countable thing; and payment lands within days. In that case a short email — deliverable, price, date, “reply to confirm” — creates a written record without the ceremony. That is still a contract in most jurisdictions; it’s just a short one.
Get an actual lawyer if: the client sends their own master services agreement with indemnification and liability caps; the work involves personal data at scale; or you’re being asked to assign IP you intend to reuse across clients. A one-hour consultation is far cheaper than the clause you agreed to without understanding.
The version of this that works is the one you’ll actually send. Two pages, seven clauses, plain English, signed before the first deliverable — that’s the whole job.
Get the free Freelancer Tool Stack
The 18 tools that run a one-person business — invoicing, contracts, time, AI writing, automation and money. One checklist, no fluff.
Frequently asked questions
Is a freelance contract legally binding without a lawyer?
Yes. In most jurisdictions a contract needs an offer, acceptance, and something of value exchanged — not a lawyer’s letterhead. A clear document signed by both parties is binding. A lawyer adds value on complex or high-value agreements, not on a standard two-page freelance scope.
Does an emailed agreement count as a contract?
Usually, yes. An email where you set out deliverables, price and timeline and the client replies agreeing is generally enforceable. It’s weaker than a signed document mainly because it tends to be vaguer, not because it’s email.
Do I need an electronic signature tool, or is a typed name enough?
A typed name in a returned PDF is normally sufficient. E-signature tools add a timestamped audit trail showing who signed and when, which matters if a client later claims they never agreed. For most freelance work that’s a nice-to-have rather than a requirement.
How much deposit should I ask for?
30–50% is standard, and 50% is defensible for new clients or projects with heavy upfront work. Clients who refuse any deposit are telling you they intend to keep the leverage — a reasonable business will not blink at it.
Who owns the work if the client never pays the final invoice?
You do, if your contract says IP transfers on final payment. Without that clause the position is murkier and varies by jurisdiction. It’s a single sentence and it’s the most valuable one in the document.
Can I reuse the same contract for every client?
Yes — that’s the point of having one. Keep the seven clauses fixed and change only the scope, dates and fees per project. Rewriting the whole document each time is how details go missing.