What changes
- Someone understands your system again, and it is written down this time
- Changes become possible without holding your breath
- A clear answer on whether to keep it, fix it, or replace it — with the reasoning
The developer who built it has moved on. Nobody knows how the deploy works. There is a server nobody wants to restart. Every change feels like a risk, so changes stop happening.
This is more common than anyone admits, and it is fixable. We start by working out what you actually have — the code, the hosting, the accounts, the parts that are load-bearing — and write it down. Only then does anyone decide what to do about it.
That first pass is one of the places AI has genuinely changed the economics. Reading an unfamiliar codebase used to be billable weeks; a model that can traverse the whole thing at once turns it into days. We still verify what it tells us before you act on any of it — but the survey costs you a fraction of what it did three years ago.
Sometimes the honest answer is that the system is fine and just needed documenting. Sometimes it needs replacing. We would rather tell you the first one is true when it is, and we will say so even though the second pays better.
If this sounds like the problem you have, describe it in an email and we'll tell you what it would take.