In this article
Step 1 (urgent): recover the access
Before anything else, list everything the project needs to exist, and check who has access to it. The code is useless if you cannot put it online.
- The source code, ideally in a repository (GitHub, GitLab, Azure DevOps), with its full history, not just a copy of the files.
- The hosting: the server or cloud account where the application runs.
- The domain name and the DNS zone.
- The database and its backups.
- The publishing accounts: App Store and Google Play for a mobile app.
- Third-party services: email, payment, maps, text messaging, with their access keys.
- The documentation, even partial, and the mockups.
The most common trap: these accounts are in the developer's name, not the company's. If that is your case and the person still answers, ask for the transfer now, politely, while they are cooperating.
Step 2: check who owns the code
It is a legal question, and the answer often surprises people. In Canada, a computer program is protected by copyright as a literary work (Copyright Act, s. 2). The basic rule: the author of the code is the first owner of the copyright (s. 13(1)). There is an exception for employees: code written in the course of employment belongs to the employer, unless agreed otherwise (s. 13(3)). But a freelancer or an outside firm is not your employee. And the Act states that an assignment of copyright is only valid if it is in writing and signed (s. 13(4)). In other words, having paid for the project does not necessarily make you its owner.
In practice: reread your contract. If it does not provide for a written assignment of the rights to the code, talk to a lawyer before investing more. This article is not legal advice.
Step 3: have what exists assessed
An audit answers a single question: is this code a solid foundation, or a burden? It checks, among other things:
- Does it build and deploy? The project is reinstalled from scratch on a clean machine. If that is impossible, that is the first job.
- The foundations. Technologies still supported, up-to-date dependencies, known security flaws.
- Code quality. Is it readable, organized, tested? Or does every fix risk breaking something else?
- The data. Is its structure sound? Can it be recovered cleanly?
- The gap with the need. What is done, what is missing, and what was misunderstood.
The audit ends with a report in plain language, with a recommendation and an estimate. At AltaCodis, an audit costs $1,500 to $5,000 depending on the size of the project. The first conversation is free: it is used to see whether an audit is needed.
Step 4: continue, repair, or start over
| Decision | When | What it involves |
|---|---|---|
| Continue | The code is sound, features are missing | Document, add tests on the essentials, and resume development |
| Repair, then continue | The base is good but neglected: outdated dependencies, no tests, manual deployment | Stabilize first, before adding anything |
| Start over | The foundations are bad, or the technology is abandoned | Start again, but not from zero: the data, screens, business rules, and mistakes of the first project serve as the specification |
Starting over is not a failure. The first project taught you what you really need, and that is the most expensive thing to discover.
The cost of what comes next depends on the decision and on what remains to be done. Our general ranges are in the guide how much custom software costs in Quebec.
Step 5: a takeover plan in small steps
- Secure: access in the company's name, tested backups, flaws fixed.
- Stabilize: reliable deployment and tests on what is critical.
- Deliver small and often: a first visible improvement within a few weeks, to rebuild trust.
- Document as you go, so it does not happen again.
This is what we do for systems already in production, such as the Taxi Coop iOS and Android apps: we took them over, and we maintain them and keep improving them. See our maintenance and improvement service.
So it does not happen again
- Every account in the company's name, with at least two people who have access.
- The code in a repository you own, updated with every delivery.
- A contract that provides for a written assignment of the rights to the code.
- Regular deliveries you can see and test, rather than a big reveal at the end.
- Minimal documentation: how to install, deploy, and back up.
Our take
An abandoned project can be recovered more often than you would think, as long as you act fast on access. If you are in this situation, start with step 1 today. Then tell us about your project: we will tell you honestly whether it is worth taking over.
Sources
- Justice Canada: Copyright Act (R.S.C. 1985, c. C-42), ss. 13(1), 13(3), and 13(4)
- Justice Canada: Copyright Act, s. 2, definition of "literary work" (computer programs)
Sources checked on November 12, 2026. Programs and prices change, so always check the official page before you decide.