// full stack developer · since 2003 · tricase, italy · remote
Legacy software grown in layers that nobody dares touch? I modernise it
Legacy software, old but still essential, often turns into a monolith: one single block where every change risks breaking something else. It doesn't get thrown away: it gets modernised one module at a time. I read the existing code, isolate the parts holding you back and rewrite them with AI, checking every line, while the system keeps working. No overnight switchover, no downtime.
30 minutes, no commitment. Written estimate of time and cost within two days.
I map the monolith: what it does, what is needed, what slows it down.
I isolate one module at a time and rewrite it alongside the old one.
I replace with no downtime: the old one stays on until the new one gives the same results.
Marco Panicophp · laravel · vue · aiavailable
23 years of commits · last yearless more
23yearsof development, since 2003
50+ projectswebsites, ecommerce, business apps
10+ major clientsESA, Snam, Edra, Youcanprint
1contactdesign, code and launch
// how I do it
One module at a time, the system never stops
Full rewrites of business software often fail because they take too long, and meanwhile the company still has to work. I modernise in layers: every new piece goes into use on its own, as soon as it is ready.
01 · map
I read code with no documentation
With AI tools I read in a few days code that would take weeks by hand: tables, links between the parts, functions nobody uses any more. The result is a written map and an order of priorities.
c3a9e12Map of the monolith: 180 files read, 23 dead functions, 4 critical modulesweek 1
5f7d0b4First module isolated (invoicing) with tests on real dataweeks 2–4
e9b21c7Second module (orders) in production, old one switched offweeks 5–8
7a4f6d0Rest migrated to PHP 8, one deploy per modulefrom month 3
trueThis is for you if
Your business app works, but every change takes weeks and breaks something somewhere else.
It runs on an old version of PHP or on a framework nobody updates any more, and your hosting provider is asking you to upgrade it.
You want to connect new services (AI, payments, your suppliers' systems) and the current code won't allow it.
falseNot for you if
You want to rebuild everything at once and switch off the old system in a day: it's the surest way to grind to a halt.
The software belongs to a closed vendor and you don't have the code: in that case we're talking about replacement, not modernisation.
Nobody in the company can spend an hour a week trying out the new modules.
// my secret
A monolith is read, not thrown away
Inside business software that has grown over ten years there are ten years of decisions: odd discounts, exceptions for that one client, tax rules that changed. No document tells their story; the code does. With AI I read them in days, not months, and carry them into the new module.
A full rewrite loses these rules and rediscovers them once the software is already in use, one at a time, with angry customers. Working layer by layer, I carry them into the new software one by one.
I domodule-by-module modernisation of business apps and portals; migration from PHP 5/7 to PHP 8 and Laravel; integrations.
I don'tfull rewrites in one go (big bang), software without source code, non-web systems (desktop, AS/400).
business-app-2012 → modules
$ map ./business-app-2012184 files · 52 tables · php 5.6 · 0 testscritical: invoicing, orders, inventory, login$ isolate --module invoicing
✓ 31 tax rules extracted from the old code
$ rewrite --ai --review marco
✓ tests: 96/96 matching the old system on 2024 data
$ replace --switch-off old-invoicing
✓ in production, zero downtime
// ready? start here
Book a free analysis of your project
Tell me what isn't working. I'll tell you whether I can rebuild it, how and how long it takes. If I'm not the right person, I'll say so right away.
130-minute call, by phone or video, whenever suits you.
2Written analysis within two days: what to keep, what to rebuild, time and cost.
3You decide, with numbers in hand. No commitment until then.
// useful answers
FAQ: modernising legacy software
Rewrite everything or modernise module by module?
Modernise module by module, almost always. A full rewrite takes months, freezes changes in the meantime and loses the rules hidden in the code. Module by module, every new part goes into use on its own, the risk stays small and the business never stops. A full rewrite only makes sense if the code is beyond recovery.
How do you understand code with no documentation?
I read it with AI tools that build a map of tables, functions and the links between them in a few days, then I check the critical points by hand and compare them with the people who use the software every day. The result is a written document that stays with you.
Does the business app stay up while you work?
Yes, always. The new module runs alongside the old one on the same data until the results match; only then is the old one switched off. There is no day of downtime and no all-at-once switchover: the people who use the software keep working as before, and the change happens one module at a time.
How much does legacy software modernisation cost?
You pay one module at a time, starting with the one that pays off most. After the free analysis you get a written estimate broken down by module, with timing and priorities, so you decide how much to do and when, without committing to the whole project up front.
Can I keep my current database and data?
Yes. The data stays where it is and the new module reads and writes it just like the old one. If the database structure needs improving, I do it gradually and with test copies, never with a single big transfer over a weekend.