Inheritors of a mystery system
The developer left, the documentation never existed, and the business runs on it anyway.
The system the business depends on, that the last vendor abandoned or the author took with them when they left. We audit it, stabilise it, and modernise it piece by piece, without a bet-the-company rewrite.
If one of these sounds like your week, the scope call will be a productive 45 minutes.
The developer left, the documentation never existed, and the business runs on it anyway.
An agency shipped 80% of something and stopped answering the phone.
Nobody touches the old system because nobody knows what breaks.
Fixed price, two weeks, written honestly. Rescue work is a regular part of what we do.
Stop the bleeding first: backups, monitoring and the two or three fixes with the worst risk-to-effort ratio.
Replace components behind stable interfaces, so the business never has a day without a working system.
A typical engagement · Rescue and modernise
The audit maps what actually runs and what it risks. Then we stabilise: backups, monitoring, tests around the scariest paths. Only then do we replace components one at a time behind stable interfaces, so the business never has a day without a working system.
Usually refactor: big-bang rewrites fail at a famous rate. The audit tells you which parts genuinely need replacing and which just need tests and documentation.
That is our normal starting condition. We recover understanding from the code, the database and the users, and write it down as we go.
Yes, and it is credited against a later build if you continue. You can take the audit report to any vendor, including not us.
No obligation. If we are not the right fit, we say so on the call.