Engagement

Legacy Rescue

Systems nobody wants to touch, made safe to change again. Usually eight years old, business critical, understood by one person, and carrying a rewrite proposal that has been declined three times for good reasons.

Free consultation · Reply within 24 hours · You own the code

billing_v2_final.phpdo not touchRESCUEReadTestsChangesafe again
2 to 5 weeksFirst safe change
Rarely the answerRewrites
Tests around the riskStarts with
Planned: noneDowntime
Change stops being scaryOutcome
Who owns what

We take the risk off the codebase.

The job is to move a system from one nobody dares touch to one anybody can. Operations stay with you throughout, because the point is that nothing breaks while we work.

Characterise, then cover, then change. The order is the whole method.
The job
With legacy rescue
If you deployed an FDE
Understanding what you actually need
Ours with you
FDE would
Turning it into a spec
Ours
FDE would
Deciding how the screens work
Ours
FDE would
Choosing the architecture
Ours
FDE would
Writing the code
Ours
FDE would
Reviewing what AI wrote
Ours
FDE would
Getting it into production
Your process
FDE would
Fixing it at 2am
Your rota
FDE would
Six of eight become ours. Nothing changes for the people depending on it.
How we run it

The rewrite is almost never the cheapest option.

A working legacy system encodes years of decisions nobody wrote down. Rewriting throws all of it away and discovers the important parts one outage at a time. We would rather make the existing thing safe to change and then change it.

COMMITS0notes only
01

Two weeks of reading, no commits

Understanding why it does what it does, including the parts that look wrong and are not. Changing code you do not understand is how rescues become outages.

reportsemailssettingsbillingtests where the risk is
02

Tests around the risk, not everywhere

Characterisation tests on the behaviour the business depends on. Not full coverage, which would cost more than the system is worth.

routerOLDNEW
03

Strangle rather than replace

New code takes over one module at a time, with both paths live until the old one is cold. No date on which everything changes.

ZekiLast engineerWhy the cron at 3am?Bank file arrives lateRUNBOOK
04

The last engineer is interviewed, not replaced

The person who knows the system is an asset. We get what is in their head written down while they are still there.

Work we have shipped

Systems we built and still support.

“

Each developer I had worked with from Zeki Experts was talented, efficient, communicative, and self-starting.

SWStuart Washington
Project Manager · Ipsen US
“

Working with the team at Zeki Expert Solutions has been a pleasure. They are professional and efficient.

SSerina
CTO · Volera Himalayan Salt

Tell us what nobody wants to touch.

Book a 30-minute call

See all our work →

Honestly

Sometimes the honest answer is to leave it alone.

Come to us when

Good fit

  • Changes take weeks because nobody is sure what they will break.
  • One person understands it and they are leaving.
  • A rewrite has been proposed and keeps being declined.
  • It runs on something that is going out of support.
We can also help when

Also a fit

  • The system works and rarely changes. We document it and add monitoring so it stays safe.
  • A rewrite has already been decided. We read the code first and plan the move so nothing the business relies on is lost.
  • The process it runs is being retired. We move the data out cleanly and switch it off safely.
Questions

Before you book the call.

Usually not, and anyone who says yes in the first ten minutes has not read it. Rewrites discard undocumented behaviour that turns out to matter, and they run long precisely because nobody knew what was in there. We will say when a rewrite is right, and it is rarer than the industry pretends.

That is the normal starting position. We add characterisation tests that lock in what it currently does, including the bugs, so that any change becomes visible. Correctness comes after safety.

Usually. .NET Framework, older PHP, classic Java and legacy database platforms are routine. Tell us what it is on the first call and we will be straight about whether we have someone genuinely strong in it.

No. A restored copy and read access to logs is almost always enough, and we would rather not hold credentials to a system we are still learning.

Next step

Tell us what nobody wants to touch.

Thirty minutes. Occasionally the right answer is that this system is fine and the money belongs somewhere else, and we would rather say that early.