Freelance contract essentials: the 9 clauses that protect your invoice

Why freelancers lose money on contracts

Most freelancers lose money not because they undercharge, but because they don't have a contract that says when and how they get paid. The hourly rate matters far less than the payment terms, the scope definition, and the kill fee. A $150/hour freelancer with a leaky contract earns less, on average, than a $90/hour freelancer with a tight one.

Clause 1 — Scope, version-locked

The scope section needs to reference a specific version of the brief — "as described in Exhibit A, version 1.2 dated 5 March". Anything outside that version triggers a change order. Without a version lock, scope creep is invisible until it's too late. The Freelancers Union publishes a good model scope clause.

Clause 2 — Deposit and milestones

Standard freelance terms: 30–50% deposit before work begins, milestones at 50% delivery and final delivery, with payment due net 14 from invoice date. "Net 30" is for employees and large vendors — freelancers should not finance their clients' cash flow.

Clause 3 — Kill fee

A kill fee is what you get paid if the project is cancelled before completion. Standard ranges: 25% if cancelled in the first quarter, 50% at midpoint, 75% if more than three-quarters done. Without a kill fee, a client can pull the plug after 80% of the work for 0% of the money.

Clause 4 — Late-payment interest and chasers

Include statutory interest (in the UK, 8% above base rate under the Late Payment of Commercial Debts Act 1998; in India, 2% per month under the MSMED Act for qualifying small businesses) and a clause permitting reimbursement of debt-recovery costs. Most clients pay faster when they read those words.

Clause 5 — IP transfer on payment, not on delivery

The default rule in most jurisdictions is that the creator owns the copyright until they assign it. Use that. Your contract should say IP transfers to the client upon receipt of full payment. Until then, you have a real lien on the work and a real reason for them to pay.

Clause 6 — Portfolio and credit rights

Reserve the right to use the work in your portfolio and to be credited as the creator unless the client buys the credit rights for a defined fee. This is standard in design, photography, and writing — and surprisingly negotiable in software.

Clause 7 — Revisions, capped

"Two rounds of revisions included; additional rounds billed at hourly rate." Without this, the third round of revisions is psychologically free for the client and unpaid for you. Capping protects both sides.

Clause 8 — Liability cap equal to fees paid

Your liability for any single project should never exceed the fees the client paid for that project. Without a cap, a single bug in your code or a typo in a contract could in theory expose your personal assets. This is the most-skipped clause in freelance contracts and the most important.

Clause 9 — Termination for non-payment

If the client misses two invoices in a row, you can suspend work and terminate the contract with no further obligation. Combine this with the IP-transfer-on-payment clause and you have a real enforcement mechanism.

The one-page freelance contract

All nine clauses fit comfortably on one page in 11pt type. If your contract is longer than that, you're probably copying corporate boilerplate that doesn't apply to a two-person engagement. Run your next contract through ContractScan AI to spot which corporate clauses you can safely delete.