Legacy systems, kept alive and moved forward.
A working system you can't switch off is not a problem to be replaced overnight. I modernise old business software underneath a running operation — old and new side by side, screen by screen, with the data reconciling the whole way.
How the move happens
No big-bang rewrite.
Side by side, screen by screen
The legacy application keeps serving production while a modern React web app and React Native field app take over one workflow at a time.
The data keeps reconciling
Every invoice, agreement and audit row has to still add up after each step — that is the test, not a green build.
Security and structure retrofitted
Tenant separation, role-based access and proper deployment pipelines added on the way through.
Verified on screen, not on faith
Every change is rendered in a real browser or device and checked before it ships.
Old tech I still read
PHP, CodeIgniter, jQuery, MySQL, Flex and Flash-era systems — I've been building since before most of them were new.
Questions people ask first
Straight answers before the first call.
Should we rewrite from scratch?
Rarely. A rewrite throws away years of business rules nobody wrote down. Replacing the system piece by piece keeps the business running and the rules intact.
Our original developer is gone. Can you pick it up?
Usually, yes. Reading an old codebase to learn how the business actually works is the first step of every modernisation.
How long does it take?
It depends on the system — but because it ships one workflow at a time, you get value from the first screen, not at the end.
Do you work outside the Lower Mainland?
Yes — clients are across Canada and the US. If you are within reach I would rather come to you and watch the operation run; otherwise the work runs over calls and screen shares, the same way the systems are deployed.
