Freelance Agreement
Freelance contract review before you start work
Freelance contracts often bury the terms that matter most: who owns the work, when you get paid, and how scope changes are handled. Pinnacle flags the clauses that cost freelancers money and time.
Analyze your freelance agreement free →Who should review a freelance agreement?
Every freelancer, contractor, and consultant should review the agreement before starting work — not after delivering the first milestone. Payment terms, IP ownership, and scope language determine whether you get paid fairly and keep rights to your own tools and methods.
Common red flags we catch
- ⚠Work-for-hire language that assigns all IP — including background tools and methods
- ⚠Unlimited revisions without additional compensation
- ⚠Net-60 or longer payment terms with no late fees
- ⚠Broad indemnification making you liable for the client's business risks
Key clauses explained
Work-for-hire and IP assignment
Work-for-hire language means the client owns deliverables from the moment of creation. That's standard for custom client work — but it shouldn't cover your pre-existing code, templates, or general methodologies. Look for carve-outs for background IP.
Payment terms and milestones
Net-30 is common; net-60 or longer puts cash flow risk on you. Milestone payments tied to deliverables are safer than a single payment at project end. Kill fees or partial payment on termination protect you if the client cancels mid-project.
Scope of work and revisions
Vague scope leads to scope creep. The SOW should define deliverables, acceptance criteria, and what counts as a revision vs. a change order. Unlimited revisions without extra pay is one of the most expensive clauses freelancers overlook.
Indemnification
Indemnification makes you responsible for the client's losses from your work. Reasonable caps and mutual indemnification are fair. One-sided indemnification covering the client's entire business risk is not — especially on a small project.
What we review in your freelance agreement
- IP ownership and license grants (exclusive vs. non-exclusive)
- Payment schedule, milestones, and kill fees
- Scope of work and change-order process
- Termination notice periods and payment for work completed
Pre-sign checklist
- ✓Does the client own deliverables but you retain background IP?
- ✓Are payment milestones tied to completed, accepted work?
- ✓Is there a written change-order process for out-of-scope requests?
- ✓Are revisions capped or billed separately after an agreed number?
- ✓Is indemnification mutual and capped to project fees?
Negotiation tip
Propose capping revisions at two rounds per milestone and retaining ownership of pre-existing IP and general methodologies.
Frequently asked questions
Who owns the work product in a freelance contract?
Usually the client, if the contract includes work-for-hire or IP assignment language — which is standard for custom deliverables. You should retain ownership of tools, frameworks, and methods you brought to the project.
What payment terms are fair for freelancers?
Many freelancers use 50% upfront and 50% on delivery, or milestone-based payments. Net-30 after invoice is acceptable for established clients. Avoid 100% payment on final delivery with no kill fee if the project is cancelled.
Should I sign a freelance contract without a lawyer?
For standard projects under a few thousand dollars, many freelancers review contracts themselves or use AI tools to flag issues first — then consult an attorney for high-value or unusual terms. Always read before you sign.
Related guides
Other contract types
Not legal advice. Read our disclaimer.