When a software project starts, most of the attention goes to features and design. Ownership and handover are easy to leave for later, and that is when problems appear. A few clear agreements at the start protect your business and make it easier to change developer if you ever need to.
1. Ownership of the custom code
Ask for it in writing: you own the custom code written for your project once it is paid for. This lets you keep using, changing and maintaining the software, with any developer you choose.
Some parts will not be yours to own, such as open-source libraries or paid third-party tools. That is normal. A good developer will list them so you know which licences apply.
2. Access to your accounts
Make sure important accounts are registered in your business’s name, not your developer’s:
- your domain name,
- hosting and cloud accounts,
- app store accounts for mobile apps,
- payment, email and analytics services.
Your developer can be given access to work in them. If the relationship ends, you keep control.
3. Where the code lives
Ask where the code is stored during the project, usually a code repository such as GitHub or GitLab, and make sure you have access to it. Then you can see progress and you always have a copy.
4. What the handover includes
Agree on this before work begins. A useful handover usually includes:
- the source code or project files,
- setup notes explaining how to run and deploy the software,
- a list of accounts, services and licences used,
- a walkthrough with your team.
5. Confidentiality
If you will share sensitive business information, ask for a non-disclosure agreement (NDA) before you share the details. It is a normal request, and a professional developer will not be surprised by it.
6. Support after launch
Software needs care after it goes live: fixes, updates and small improvements. Agree how this works:
- what is covered and what counts as new work,
- how to report a problem and how quickly it will be looked at,
- how support is charged.
Put it in writing so responsibilities are clear on both sides.
7. Changes during the project
New ideas appear once people see the software. That is healthy. Agree how changes are handled: they should be discussed, priced and approved before they are added, so the scope and budget stay clear.
A short checklist
- You own the custom code once it is paid for
- Third-party tools and licences are listed
- Accounts are in your business’s name
- You can access the code repository
- The handover contents are agreed
- An NDA is signed, if needed
- Support after launch is agreed in writing
- There is a clear process for changes
At MojarSoft, you own the custom code we build for you, and the handover and support are agreed before the project starts. If you would like an independent view of an existing project or agreement, our technical consultancy can help, or you can ask us a question directly.