01 Codebase inspection
02 Modernization workshop
03 Full modernization support
04 Independent technical advice
01 / The situation
Legacy software is rarely just old code. It contains business rules, exceptions, integrations and operating knowledge accumulated over years.
The first job is not to replace it. The first job is to understand where the real constraints and risks are—then make the smallest credible move that improves the situation.
02 / Services
Start with a focused inspection of the code and architecture. Go deeper only when the evidence supports it—from a working session through to full modernization delivery.
01
A focused inspection of the legacy codebase, architecture and delivery constraints. You get an independent view of what is actually holding the system back and what to do next.
Code & architecture review
Risk and constraint map
Practical next-step brief
02
A working session for technical and business leaders to align on the real problem, target outcomes, modernization options and sensible sequence of change.
Shared system picture
Option trade-offs
Phased modernization plan
03
Hands-on support from target architecture through incremental delivery—improving the system without gambling the business on a big-bang rewrite.
Target architecture
Incremental modernization
Delivery & team enablement
04
Independent technical guidance for teams already modernizing—reviewing decisions, unblocking difficult trade-offs and keeping the work connected to business outcomes.
Architecture review
Decision support
Ongoing technical guidance
03 / The entry point
A focused first engagement for organisations that know change is necessary but need a clearer picture before choosing a programme, platform or partner.
Discuss your systemHow it works
We establish what the software supports, why change matters now and where the team feels most constrained.
I review the structure, dependencies, delivery path and technical risks in the context of the business.
You receive an independent view of the risks, available options and the most credible sequence of change.
A useful outcome even if we stop there. The assessment is designed to improve your next decision, not manufacture a larger engagement.
04 / Free resources
Practical tools to help you challenge an idea, frame a project and make a better first decision.
Browse all resourcesUnderstand whether the next step is discovery, stabilisation or active modernization.
Working templateClarify the business pressure, system constraints, risks and first credible move.
Related interactive toolFor the parts of modernization where AI is being considered.
05 / Latest thinking
A rewrite is a business bet, not a technical clean-up. Inspect what the system really carries first.
Read noteThe safest route out of a monolith often begins with boundaries the business already understands.
Read noteModernization plans fail when they promise distant certainty instead of sequencing what the team needs to learn.
Read note07 / About
I’m Jacques van der Merwe. I help organisations understand difficult legacy systems, choose a credible modernization path and deliver change without unnecessary disruption.
My work combines product thinking, software architecture and hands-on delivery. AI is part of that toolkit when it solves a real problem—not the starting assumption.
Use AI for ambiguity. Use code for certainty. Keep people where judgement carries consequence.More about my background
08 / Work together
Start with an independent inspection. You’ll leave with a clearer picture of the codebase, the risks and the most credible next move—whether or not we continue together.
Discuss a codebase assessment