You want to change your software supplier. Perhaps they are slow, or too expensive, or they have gone quiet. Then you find the problem. The hosting account is in their name. The code sits in their private account. There is no documentation. Your new supplier cannot even see what they are taking on.
This happens more often than it should. The cost is real. You may face weeks of delay while access is sorted out. You may pay a new team to work out how the system works. In the worst case, you pay to rebuild something you already paid for. Until then, you are tied to one supplier's prices and timescales.
Most of this can be avoided with a few checks before you sign. This article explains what to look for, in plain terms.
What "owning your software" actually means
Ownership is not one thing. It is several things, and you need all of them.
- The code. This is the set of written instructions that makes your software work. You need a full, current copy.
- The legal rights. This is called intellectual property, or IP. It means the legal right to use, change and sell the code. Having a copy of the code is not the same as having the right to use it.
- The accounts. These include hosting (the servers your software runs on), your domain name, app store accounts and the code repository. A repository is the online store where the code lives and every change is saved.
- The data. Your customer records, orders and history. You need to be able to export them in a format another system can read.
- The knowledge. Documentation that explains how the system is built, how to set it up and how to release changes.
If any one of these is missing, you do not fully control your software.
Why control gets lost
Usually nobody plans it. It happens through small, convenient decisions.
A developer sets up the hosting on their own card to get started quickly. The code goes into their company's repository because that is their habit. Documentation is left until "later", and later never comes. The contract says little about IP because nobody thought to ask.
Sometimes the reason is less innocent. Some suppliers keep control on purpose, because it makes you harder to leave. Either way, the effect on your business is the same.
What to check before you sign
Ask these questions before any work starts. A good supplier will answer them clearly and without fuss.
| What to check | What to ask | Warning sign |
|---|---|---|
| IP rights | Does the IP pass to us, and when? | IP stays with the supplier, or passes only on final payment with vague terms |
| Repository | Will the code live in an account we own? | "We will send you the code at the end" |
| Hosting and domain | Whose name and card are the accounts in? | Accounts in the supplier's name |
| Documentation | What documentation is included, and when? | Documentation is an optional extra |
| Data export | How do we get all our data out? | No clear answer |
| Handover | What happens if we move to another supplier? | No handover process described |
A reasonable point to discuss is timing. Some suppliers transfer IP when each phase is paid for. That is fair. What matters is that the terms are written down and clear.
Also ask how you will see progress. If you see working software every week in a staging environment, you know the work is real. A staging environment is a private copy of the system used for testing before anything goes live. Regular access like this makes it hard for problems to stay hidden.
When not owning everything is fine
Full ownership is not always the goal. There are sensible trade-offs.
- Off-the-shelf subscriptions. If you use a tool like an accounting package, you do not own its code. That is normal. What you need is the right to export your data.
- Open-source libraries. Most software is built using shared, free components written by others. You do not own these, but their licences let you use them. Your supplier should be able to list them.
- Licensed components. Some suppliers reuse their own tools across clients. This can save you money. Just make sure the licence lets you keep using them if you leave.
The rule is simple. You should own what is unique to your business, and have clear rights to use everything else.
If you have already lost control
If you are reading this too late, do not panic. Most situations can be recovered. Work through these steps in order.
- Ask for access, in writing. Request admin access to the repository, hosting, domain and any app store accounts. Be polite and specific.
- Check your contract. Look for anything about IP, handover and termination. If it is unclear, take legal advice.
- Back up your data. Export everything you can, while you still can.
- Get an independent review. Ask another team to look at the code. They can tell you whether it is worth keeping, and what risks it carries.
- Move the accounts. Transfer hosting, domain and repository into accounts your business owns.
- Document as you go. Each step should leave behind notes the next person can follow.
Taking over a system someone else built is common work. Our bespoke software practice handles rescues and takeovers, where the first job is to stabilise and document what exists before changing it.
How we approach it at Digitice
We set things up so you never face this problem with us. You own the code and the accounts from day one. Every project ships with automated tests, documentation and a handover. Automated tests are small checks that run by themselves and catch mistakes when code changes.
We do this because it is the right way to work. It also means clients stay because they want to, not because they have to. You can read more about how we work.
Your next step
Take ten minutes this week. List your software systems. For each one, write down who holds the code, the hosting and the domain. If any answer is "the supplier" or "not sure", start there.
If you would like a second opinion on what you find, get in touch and we will talk it through with you.
Questions
Frequently asked questions
If I paid for the software, do I own it automatically?
Not always. Under UK law, the person who writes the code often holds the rights unless the contract transfers them to you. Check that your contract clearly says the intellectual property passes to your business, and when.
What accounts should be in my business's name?
At minimum, your hosting, domain name, code repository and any app store accounts. Your supplier can be given access to them, but your business should hold the main ownership and billing.
Can a new supplier take over software another company built?
Yes, in most cases. The new team first needs access to the code and accounts. They then review the system, fix urgent risks and write the documentation that was missing before making bigger changes.
Is it a problem if my software uses open-source components?
No, it is normal and usually a good thing. Open-source components are shared tools with licences that let you use them. Ask your supplier for a list, so you know what your system depends on.