Buyer guide
What should a freelance developer contract include?
In short
A freelance developer contract should state the scope, who owns the code and other deliverables, how and when you pay, what you receive at the end and how either side can stop. Ownership needs particular care: in the US, work made for hire only applies in defined cases and needs signed wording. Have a lawyer in your country review it.
Who is this guide for?
Business owners about to engage a freelance developer who want to know what a sound agreement covers before they ask a lawyer to draft or review it.
A note before you start
This is a checklist of topics, not legal advice and not a template to copy. Contract and copyright law differ by country and sometimes by state. Use this page to know what to ask for, and have a lawyer in your own jurisdiction draft or check the final text.
Scope and deliverables
Describe what is being built or done, what you will receive and how you will decide it is finished. Say what is outside the scope. Most disputes come from a scope that two sides understood differently.
Include the practical items that people forget: source code in your repository, documentation, and the accounts and credentials that the system runs on.
Who owns the code
Do not assume you own what you paid for. The US Copyright Office explains that a work made for hire arises in two situations: when an employee creates it within the scope of employment, or when a specially commissioned work falls into one of nine listed categories and the parties expressly agree in a written instrument signed by them that it is a work made for hire.
The office states that if a work fails to meet these requirements, it is not a work made for hire. Software is not named in that list of nine categories, so a clause saying work for hire is not a safe answer on its own. Ask your lawyer what wording is needed in your country to make sure ownership passes to you.
Also say what happens to code the freelancer already owned or reuses across clients, and to open-source parts, which come with their own licences.
Payment
State the amount or the way it is calculated, when invoices are sent and the payment date. UK government guidance says that when businesses agree a payment date it should usually fall within a set number of days, that parties may agree longer if it is fair to both, and that without an agreed date a payment is treated as late after a default period.
Tie payments to milestones or periods you can check, so you are not paying far in advance for work you have not seen.
Security and quality
If the app handles users' data, say what security you expect. The OWASP Application Security Verification Standard is an open set of security requirements, and OWASP says it can serve as a basis for specifying application security requirements in contracts.
You do not need to adopt all of it. Agreeing on a named level or a short list of requirements is better than saying the software must be secure.
Confidentiality, status and ending the contract
Add a confidentiality clause covering your data and plans. State that the freelancer is engaged as an independent contractor only if that is true in practice: tax authorities look at how the relationship works, not at the label.
Describe how either side can end the contract, what is paid for work done up to that day and what the freelancer must hand over: code, documentation and access.
How do the options compare?
| Topic | Say in writing | Why |
|---|---|---|
| Scope | What is built and what is not | Prevents two different understandings |
| Ownership | Who owns code and deliverables, and how it passes | Work for hire has strict conditions |
| Existing tools | What the freelancer reuses and under which licence | Avoids surprise restrictions |
| Payment | Amounts, dates and milestones | Defines what late means |
| Security | Named requirements for user data | Gives you something to check |
| Ending | Notice, final payment and handover | Protects continuity |
What should I check before I sign?
- A lawyer in your country has reviewed the final text.
- Scope and exclusions are written down.
- Ownership of code and deliverables is explicit and signed.
- Reused or open-source components are listed.
- Payment dates and milestones are defined.
- Security expectations are named, not implied.
- Confidentiality is covered.
- The handover on ending is described.
How pricing works
I quote in writing after a short discovery call, against a written scope. Building an app from scratch? The app cost calculator gives a first range in two minutes.
What else do people ask?
Does paying for the code mean I own it?
Not automatically. Ownership depends on the law and on what is signed. Put it in writing and have a lawyer check it.
Can I use a template I found online?
As a starting list of topics, yes. Have it adapted and checked for your country, because law differs.
Do I need a contract for a small job?
A short written agreement on scope, payment and ownership is worth having even for small work.
What if the freelancer uses open-source code?
That is normal. Ask for a list of the components and their licences so you know the conditions.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.