Freelance & Services Agreement FAQ
Answers to the questions freelancers and service providers ask most — what to put in the agreement, when ownership of the work passes to the client, how to price a kill fee, and how to keep scope from drifting. Plain English throughout.
Basics
What is a services agreement?
▾
A services agreement is a contract between a service provider and a client that defines the services to be performed, payment terms, deliverables, timelines, and the rights and obligations of each party. It is the foundation for any professional services engagement.
What is the difference between a services agreement and an MSA?
▾
A services agreement covers a single project. A Master Service Agreement (MSA) establishes general terms for an ongoing relationship, with individual Statements of Work (SOWs) for each project. Use an MSA when you expect multiple projects with the same client.
When do I need a services agreement?
▾
Any time you provide or receive professional services: consulting, software development, marketing, design, accounting, legal, or any other service engagement. Even for small projects, a written agreement prevents misunderstandings about scope, payment, and deliverables.
Key Terms
How should I define the scope of services?
▾
Be specific: list the services to be performed, deliverables with acceptance criteria, milestones and timelines, what is explicitly excluded, and the process for changes (change order procedure). Vague scope definitions are the leading cause of services disputes.
How should I limit liability?
▾
Common approaches: cap total liability at fees paid under the agreement (or a multiple thereof), exclude consequential and indirect damages, carve out exceptions for IP infringement, confidentiality breach, and gross negligence. The cap should reflect the deal economics.
Who owns the work product?
▾
Without an explicit clause, ownership depends on the relationship and jurisdiction. Always include a clear IP assignment clause. Common approaches: client owns all deliverables upon payment, provider retains pre-existing IP with a license granted, or provider retains IP until full payment.
What termination provisions should I include?
▾
Include: termination for convenience with notice period (30-60 days), termination for cause (material breach with cure period), termination for insolvency, wind-down obligations, payment for work completed, and survival of key provisions (confidentiality, liability, IP).
Freelance Work: Scope, Revisions & Getting Paid
What should a freelance contract include?
▾
Eight things cover most freelance work: (1) who the two parties are, (2) the scope — deliverables, what is not included, and how many revision rounds come with the fee, (3) the timeline and any milestones, (4) payment — the rate, the deposit, the invoice schedule, and what happens when an invoice runs late, (5) the moment ownership of the work passes to the client, (6) confidentiality, (7) how either side can end the project early and what gets paid for work already done, and (8) which state or country law applies. Anything beyond that is usually specific to your industry.
Should IP transfer on delivery or on payment?
▾
Tying the transfer to payment is the more common freelance-side choice: ownership of the finished work passes to the client once payment clears in full, and the freelancer holds it until then. Transfer on delivery hands the work over the moment you send it, which can leave you with an unpaid invoice and nothing held back. Either way, name the moment explicitly — a clause saying the client owns all work product without saying when leaves the timing open to argument.
What is a kill fee and how do I write one?
▾
A kill fee is what the client pays if they end the project early for reasons that are not your fault. A common structure has three parts: a non-refundable deposit up front, payment for any milestone already completed, and a set share of the remaining fee — often 25% to 50% — if they cancel after work has started. Write it as a figure or a percentage rather than "reasonable compensation"; vague wording is where these conversations go wrong.
How do I stop scope creep in a freelance contract?
▾
Two clauses do most of the work. First, define what is included and, just as usefully, what is not — a short "not included" list saves more arguments than a long "included" one. Second, add a change-order step: anything outside the agreed scope gets written down, priced, and agreed in writing before it starts. Without that second clause, "just one more small thing" has no natural stopping point.
How many revision rounds should a freelance contract include?
▾
Pick a number and write it in — two or three rounds is typical for design and writing work. Then say what happens after that, usually an hourly rate or a flat fee per extra round. The number itself matters less than having one: "revisions until you are happy" has no end, and neither does the project.
Should I ask for a deposit, and how much?
▾
Most freelance agreements include one. Common splits are 25% to 50% up front with the rest on delivery, or thirds on longer projects — a third to start, a third at the midpoint, a third at handover. A deposit does two jobs: it covers your early hours, and it tells you whether the client can pay before you have done the work.
What can I do about late payment?
▾
Set the terms in the agreement rather than sorting them out afterwards: when the invoice falls due (net 14 and net 30 are both common), a late fee as either a flat amount or a monthly percentage, and the option to pause work until the account is current. In practice the pause clause tends to carry more weight than the fee.
Related Contract Templates
Related FAQs
Ready to Create Your Contract?
Describe your deal in plain English. Three AI agents draft, review, and refine your contract in minutes.
Get StartedAI-generated draft for review. Not legal advice.