// 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 Panico, freelance full stack web developer
Marco Panicophp · laravel · vue · ai available
GitHub-style commit grid of the last year

23 years of commits · last year

  • 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.

How the analysis works →

02 · layers

I choose where to start

We start from the module that hurts most: the slow one, the one nobody knows how to change, the one blocking integrations. The rest waits its turn.

Book a free analysis →

03 · replacement

I rewrite and replace, with tests

The new module is born with automated tests and runs alongside the old one on the same data. When the results match, the old one is switched off.

The method in detail →
git log --oneline · a typical modernisation
  1. c3a9e12Map of the monolith: 180 files read, 23 dead functions, 4 critical modulesweek 1
  2. 5f7d0b4First module isolated (invoicing) with tests on real dataweeks 2–4
  3. e9b21c7Second module (orders) in production, old one switched offweeks 5–8
  4. 7a4f6d0Rest migrated to PHP 8, one deploy per modulefrom month 3

This 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.

Not 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).

// 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.

  1. 130-minute call, by phone or video, whenever suits you.
  2. 2Written analysis within two days: what to keep, what to rebuild, time and cost.
  3. 3You decide, with numbers in hand. No commitment until then.

No commitment. I reply within one working day.

// 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.