The developer is long gone. The code might be missing. And the business still runs on that software every single day. You have more options than you think.

We see this constantly: custom software written years ago — by a former employee, a relative, a vendor who’s since disappeared — that quietly became critical. The business grew, the software didn’t, and now new contracts demand things it can’t do. You’ve searched for an off-the-shelf replacement and found nothing, because your requirements are genuinely unusual. Meanwhile, everyone who uses the system is losing patience with it.

The good news: old software is a map

An aging system feels like a liability, but for a rebuild it’s an asset. It’s a working specification of what your business actually needs. Your power users can show us exactly how the system is used — what works, what doesn’t, and what it should do but never did. Whether or not the source code survives, that knowledge dramatically shortens the path to a replacement.

If you have the source code

With code in hand, there are usually three routes:

  • Repair and extend — sometimes the honest answer is targeted changes to the existing codebase, redeployed. Not glamorous, but cheap and fast when the foundation is sound.
  • Extract and rebuild — when the platform is too outdated to keep, we mine the code for its business logic and rules, then use them as the blueprint for a modern system. You’d be surprised how much money that existing code saves you.
  • Modernize in stages — move the riskiest pieces first (often the data layer), keeping the business running while the system evolves underneath it.

If you don’t have the source code

It’s still very workable. We’ve rebuilt systems from printed listings, from half-recovered folders, and from nothing but the running application and the people who use it. The system itself becomes the specification: we document what it does with your power users, then build the replacement against that map.

What happens first

We start with an assessment, not a proposal: where the system stands, what the real risks are (data loss usually tops the list), and which path fits your needs and your budget. Sometimes the answer is a rebuild. Sometimes it’s a repair that buys you three years. We’ll tell you which — and why.

If your business is running on software nobody can update, let’s talk. We’ve probably seen your situation before, and it’s almost never as stuck as it feels. You can also read about how we build and rescue custom software.