Legacy software modernization for old web applications
Old web software often still runs the daily business. It is also slow to change, hard to host, and understood by fewer people every year. I modernize old applications step by step, and your company keeps working normally while I do. That can be PHP, Laravel, Ruby on Rails or a custom framework.
I'm all in on AI, and it helps most with old code. It reads the code, shows how the parts connect, and writes the tests that were never written. I stay careful, because this software runs your business. I work with companies without their own developer and with teams that want experienced help.
I usually reply within one working day.
What modernization includes
Which parts you need depends on the old system.
Understand what exists
The code, the database, the hosting and the business rules hidden in the code. I write down how the system works, because often nobody knows anymore.
Refactor or rewrite
Most old applications are better repaired than rewritten. A rewrite makes sense when the old system blocks everything. I tell you which applies to yours and why.
Tests first
Before I change old code, I add tests for the parts your business depends on. Then a change can't break them without anyone noticing.
Current versions
Current framework and language versions, maintained packages, and a working development environment with Docker.
Merge and simplify
Two backends in two languages, or three servers where one would do. After merging them, hosting costs less and there is less to maintain.
New hosting and deployments
Automatic deployments, a staging copy for testing, backups that work, and a move to better or cheaper hosting if it helps.
How I work
You don't need to have everything figured out before we talk. An idea, access to the repo, a screen recording or a list of problems is enough. I look at what is there, tell you what I would do and what it costs, and then I build it.
I use Claude Code, Codex and my own agent workflows for reading code, planning changes, writing tests, refactoring and debugging. It is not vibe coding. It is senior engineering with a much faster loop.
AI-first, where old code needs it most
Claude Code, Codex and my own agent workflows read old code much faster than a person alone. They show what depends on what and write the missing tests. I make the decisions and check every change before it goes live.
I stay in control
AI writes a lot of my code. I still make every technical decision, read every change before it ships, and test it. Fast, but meticulous: the speed is only worth something if what goes live is right.
The way you want to work
Some clients want to look at every change before it goes live, others want me to deploy. Some want a weekly call, most prefer written updates. I work well asynchronously, and I still ask the important questions when they come up.
I think like an owner
I still run my own online products. So when I build or fix yours, I think about traffic, conversion, revenue and support as much as about the code, and I tell you when something is not worth building.
Ways to work with me
Fixed price, a flat monthly rate, or hourly. It's always me doing the work, not an agency. If you're not sure, describe what you need and I'll suggest one.
Examples of my work
Old systems I modernized.
From PHP and Ruby on Rails to one Laravel app
Two backends in two languages were expensive and hard to maintain. I moved all the logic into one Laravel application that replaced both. Monthly hosting costs fell from four figures to about $150.
A full rewrite with AI features
An underperforming SaaS got a full rewrite in Laravel and Vue. It also got an AI business name generator, protection against spam signups, and background jobs that keep the app responsive.
Custom PHP framework, no documentation
A business-critical SaaS on a custom PHP framework that nobody had documented. I fixed the urgent bugs, documented the whole application, and set up a Docker development environment.
What clients say
"He also expertly managed a complex upgrade of our core platform (Laravel) to the latest version, ensuring we stay current and secure."
"We work with Vincent regularly on Laravel/Vue projects, both new builds and existing codebases that have grown over the years."
"I've been working with Vincent for several months, and he's one of the most independent developers I've collaborated with."
Questions
Should we refactor or rewrite?
Usually refactor. A rewrite costs more than expected, and the old system knows things about your business that nobody wrote down. When a rewrite is the better choice, I say so and explain why.
Does the software have to stop while you work on it?
No. I work on a copy. The live system keeps running, and we switch over when the new version works.
Our system isn't built with Laravel. Can you still help?
Yes. I have worked with custom PHP frameworks, Ruby on Rails and old CMS setups. Moving to Laravel is only one option.
What if nobody knows how the old system works?
Then I read the code and write down what I find. You end up with documentation you never had.
Will hosting get cheaper?
Often, because a merged and cleaned-up system needs fewer servers. In one project the monthly costs fell from four figures to about $150. I can't promise that for every system.
How do you charge?
Fixed price for a job with a clear outcome, a flat monthly rate for ongoing work, or hourly. Describe what you need and I'll suggest one.
Get a quote
What the system does, what it is built with, and what bothers you most. A few sentences are enough. I'll reply with what I would do first and what it would cost.
If you would rather talk first, book a 30-minute call or email contact@vincentschmalbach.com.