01 · inventory
I measure what's really there
I read the code and the database, try what works and note what doesn't. In two days you have a written list: done, to finish, to redo.
How the analysis works →// full stack developer · since 2003 · tricase, italy · remote
A project that was started and never finished can almost always be recovered: I pick up the code and data that exist, finish what's missing with AI, checking every line, and take it live in 2-8 weeks. The work you've already paid for doesn't go to waste.
30 minutes, no commitment. Written estimate of time and cost within two days.
23 years of commits · last yearless more
// how I do it
A stalled project has value: the decisions made, the screens built, the data collected. First I measure it, then I finish only what's missing.
01 · inventory
I read the code and the database, try what works and note what doesn't. In two days you have a written list: done, to finish, to redo.
How the analysis works →02 · plan
Many projects stall because they tried to do everything. Together we decide what it takes to go live and what can wait for version 2.
Book a free analysis →03 · completion
I write the missing parts with AI and check them line by line: a third of the time it would have taken when the project stalled, with the experience of a senior developer.
The method in detail →// my secret
When a project stalls, whoever paid for it thinks everything is lost. Usually it isn't: the screens, the way the data is organised, the rules of your business are already there, written in the code. I read them, keep them and complete them.
With AI, the cost of finishing the missing parts is a fraction of what it was a few years ago. That's what makes a project possible today that was too expensive to finish back then.
$ inventory./project-202261% done · 27% to finish · 12% to redo keep: screens, data model, order rules $ plan--first-version 9 features to go live, 6 in the backlog $ complete--ai --review marco✓ 38 screens finished, 3 weeks✓ tests: 140/140 passed $ go-live--domain --data ✓ live, week 7
// ready? start here
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.
// useful answers
Yes, almost always. A project stalled for two or three years needs the components it uses and its PHP version updated, but the screens, the database and the rules of your business remain valid. In two days the analysis tells you how much can be recovered and how much needs rewriting.
Everything that works is recovered: the way the data is organised, the steps of the work, the screens. Only what is broken or too outdated gets rewritten. How much can be saved depends on the project: I tell you in the written list from the analysis, item by item, together with the estimate.
Less than it would have cost when it stalled: I complete the missing parts with AI, reviewing every line, and that cuts the time to a third. The exact figure comes with the free analysis, in a written estimate with timeline and what is left out.
The code (even in a compressed file), access to the database or a copy of it, access to domain and hosting, and any documents that exist: quotes, screens, emails. It doesn't all need to be in order. If something is missing, on the first call we work out together how to recover it, step by step.
Then I keep the database and the rules of your business and rewrite the code with AI, starting from what was there: it is still faster and cheaper than a brand new project. It happens, for example, with very old versions of PHP or with frameworks, the foundations software is built on, that are no longer updated.
// other situations
// legacy monolith
modernised piece by piece →
// developer not responding
I take over the existing code →
// overpriced software subscription
I replace it with software you own →