It happens more often than the software industry likes to admit. A freelancer goes quiet. An agency closes. The one developer who understood everything moves on. Suddenly the software your business runs on has no one behind it, and you don't even know where it lives.
The panic is understandable. The good news: this is almost always recoverable, and getting unstuck is a big part of what I do.
Step one: take stock of what you have
Before anything else, track down the keys to your own house:
- Where does the code live? GitHub, GitLab, a hard drive, a hosting account, ask everyone who might know. The code is yours; you paid for it.
- Who controls the domain, hosting, and accounts? Your web address, your server, your third-party services, these are yours. Get the logins back or reset them.
- Is anything still running? A live site or app is a working reference, even if you can't change it yet.
You almost always own more than you think you do. The trick is finding it before you rebuild anything.
Step two: bring someone in to map it
Once the assets are in hand, a fresh developer can read the code, figure out how it works, and tell you honestly what shape it's in, what's salvageable, what's risky, and what it'll take to move forward.
That assessment is the whole game. With it, you go from "we're stuck and scared" to "here's the plan." Without it, every next step is a guess. Most projects don't need to be thrown away; they need someone to pick up where the last person left off.
Step three: stabilise before you improve
The instinct is to start fixing things right away. Resist it. First, make sure the system is stable, the hosting is reliable, the backups are working, and nothing is about to fall over. Then get the basics in place: version control you control, a deployment process that isn't a mystery, and a way to test changes safely.
Once the foundation is solid, you can start making improvements, finishing features, fixing bugs, modernising the parts that need it. But stabilisation comes first, because improving a system that might fall over is just building on sand.
The most important thing
The single most important thing after a developer disappears is to act quickly and get the assets in your hands. Every day you wait is a day the system runs without a safety net, and a day closer to the moment where the hosting lapses, the domain expires, or the backups stop working. Move fast, get control, and bring in someone who can read the code and tell you what you're working with. From there, it's a solvable problem.
