I'll take care of your critical software, even if the people who built it are long gone.

A dependency is losing support, a license change is about to get expensive, or an audit has flagged something your team needs to fix.

I figure out how the system works, make the changes, and leave your engineers able to maintain it.

Valérian de Thézan de Gaussan

I've done this before.

The sole developer left. The platform kept running.

I took over a logistics company's data platform after its sole developer left. I kept it running, fixed existing problems, and delivered new data pipelines.

From two weeks to under an hour.

I refactored a healthcare data-processing tool so a job that used to take two weeks finished in under an hour. I cut the codebase from 60,000 lines to 5,000 and documented it so the team could maintain it.

BATCH PROCESS2 weeks

Brought in to maintain it. First, I had to make it work.

I joined a major international public safety organization to maintain a data platform between project phases. The original team had left, but the platform wasn't ready and users were frustrated. I worked out how it all fit together, fixed the problems, and listened to what users actually needed. Then I reshaped the architecture while keeping the platform available, making changes that had previously been blocked.

Let's talk about your software.

You don't need to know exactly what's wrong.

Leave your details and I'll get back to you within 24 hours.

A few things you might be wondering.

  • What if there's no documentation?

    That's fine. I'm used to investigating unfamiliar code and reconstructing how systems work.

  • What if changing something breaks production?

    I don't change things blindly. I first understand the system, assess the risks, and establish how to verify changes safely.

  • Will this take time away from my engineers?

    As little as possible. I'll need some access and occasional answers, but my goal is to take work off your team's plate, not add to it.

  • What if the problem is bigger than expected?

    That's why we can start with a technical assessment. You'll understand your options before committing to a larger project.

I actually enjoy digging into old code.

Some engineers love starting from scratch. I love understanding what's already there.

I've spent years taking over complex systems, fixing what needs fixing, and avoiding unnecessary rewrites.

But solving the immediate problem is only half the job.

I also document what I've learned, train your team, and make future maintenance easier.

My goal? You won't need me again for the same problem.

The entire stack rests on one little script. Pull the Post-it.

A nod to xkcd #2347

Got a software problem nobody wants to deal with?

Tell me about it. Even if you're not sure what's wrong.

I'll get back to you within 24 hours.

That licensing deadline isn't going away.

Maybe your software still works perfectly fine. But the next licence renewal could cost you ten times more. Or an upcoming security audit could force changes nobody knows how to make.

The longer you wait, the fewer options you may have.

Don't wait until you're forced into an expensive decision.