Modernize the system no one dares to change
Your core app still runs, but every change is slow and risky, and the people who built it are long gone. I bring it into the present in steps you can actually ship — without stopping the business that depends on it.
Why the big rewrite is a trap
The instinct is to rebuild it all from scratch. But a two-year rewrite means two years with no new features, a new system that has to match every quirk of the old one before it can go live, and a cut-over weekend where everything happens at once. Most of these projects run late. Some never land.
How I approach it
I keep the old system running and move it across piece by piece. We find a part small enough to rebuild and ship quickly, put the new version in front of real users behind a flag, and only then move the next piece. Each step stands on its own, so value shows up along the way instead of all at the end, and if we need to stop, you're still ahead. Where that old system feeds others, I keep the integrations working as each piece moves.
I've done this from the inside
I spent years in codebases exactly like this — .NET and C#, older VB6, the kind of software that quietly runs a business for a decade. I know the difference between code that's merely ugly and code that's load-bearing, and I treat the second kind with care.
Common questions
Can you work without the original developers?
Yes — that's usually the situation. I read the code and watch the system run to learn how it really behaves, rather than trusting documentation that may be out of date or gone.
Will the business keep running during the work?
Yes. The old system stays live the whole time. I move functionality across in small, reversible steps, so there's no cut-over weekend where everything changes at once.
What languages and stacks do you work with?
Mostly .NET and C#, and Node.js, including older stacks like VB6 and WPF/WinForms. The approach matters more than the language: small steps, kept shippable.
Do I have to commit to the whole thing up front?
No. We start with one piece. If it goes well you keep going; if priorities change, each step already stands on its own.
Have a system you're afraid to touch? Let's look at where to start — 30 minutes, free.
Book a 30-minute call