Rescue of inherited software
Whoever wrote it for us has vanished, and we do not even have the documentation.
- What we do
- We put the code, the logins and the knowledge of software abandoned by its supplier back in the company's hands.
- How we do it
- We start by finding everything that exists: where the code is and whether it is the version that is running, which servers it runs on, which accounts, domains and services it uses and in whose name they are. What is in someone else's name we help you move into the company's name, wherever the provider of each service allows it, and what cannot be moved we write down. Then we set up a development environment where the software can be changed and tested without touching the one the company uses, and write the minimal documentation: what parts it is made of, how it is installed and how a change is released. In the end, your team or whoever you choose can work on it again.
- What you receive
- An inventory, minimal documentation and a working development environment.
- What changes for you
- The software stops depending on a person who is no longer there. You know where everything is and in whose name; for what is already in your name, you can change a password or renew a domain without tracking anyone down, and making a change to the software becomes possible again.
- What we need from you
- Everything you have, even if it is incomplete: access to the servers, emails with the supplier, contracts, invoices for domains and services; and someone who uses the software every day and knows what it does.
- Who it is for
- Senior management and IT
- How you buy it
- At a fixed price: the price is written down before we start and we give it to you when you ask.
Example use cases
These are examples: they do not describe a real client.
A travel agency in Italy with an office in Argentina, whose booking system was built by a developer who no longer answers
The situation
The booking system was written by a freelance developer, who maintained it for years and one day stopped answering emails. The company does not have the code: he did. The system still runs on a server whose account is in the developer's name, and no one can make the change the Argentine office wants for bookings in pesos.
What we do
We find the code on the server, check that it is the version that is running and store it somewhere in the company's name. We list the accounts and services, and help the company move the server and the domain into its name wherever the provider of each allows it. We set up an environment where the system runs without touching real bookings and write down how it is installed and how a change is released. The change the Argentine office was asking for can now be quoted.
A ceramics maker in Spain with a plant in Peru, whose production application was built by a supplier that closed down
The situation
The supplier that built the application closed down, and the person who knew it went with it. The company has a copy of the code on a disk, but does not know whether it is the latest version, and no one has managed to install it on another machine. When the server at the plant in Peru failed, the application stood still until a technician turned up who remembered how to start it.
What we do
We compare the copy of the code with the application that is running and store the version that really works in the company's name. We set up a development environment where the application is installed from scratch, and write down step by step how it is done, so that the plant in Peru does not depend on anyone remembering. The inventory says which servers, accounts and licences the application uses and in whose name each one is.
Frequently asked questions
What if we do not have the code?
Depending on how the software is built, the code is sometimes on the server where it runs, or in a copy no one remembers. If it does not turn up, the inventory says so, and explains which options are left and what each one involves.
Does the software have to be rebuilt afterwards?
Not necessarily. The rescue leaves the software in your hands and working; if it is worth renewing, you decide later, with the inventory and the documentation in front of you.
What happens with the passwords and the accounts?
We list every account the software uses, with the name of whoever holds it, without copying its passwords. The ones that can be moved into the company's name we help you move; the ones that cannot stay on the list, with what it takes to recover them.