// full stack developer · since 2003 · tricase, italy · remote

Your developer stopped responding and you're left with a half-finished website?

It happens more often than people admit, and it's not your fault. Here's how we restart: I recover domain, hosting and code, read what's there and tell you within two days what works and what's missing. Then I finish the job, with AI and my own review, in weeks.

30 minutes, no commitment. Written estimate of time and cost within two days.

  • I recover domain, hosting, database and code, even without your old contact.
  • I work out in two days what's there, what works and what's missing.
  • I complete the job and hand over access and code, in your name.
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+ enterpriseESA, SNAM, Edra, Youcanprint
  • 1contactdesign, code and deploy

// how I do it

Access first, then the code, then the work

A takeover succeeds when it's done in order: without access nothing gets touched, without reading the code nothing gets promised.

01 · access

I recover what's yours

Domain, hosting, database, repository, third-party accounts. Where access is missing, I guide you through recovering it from the provider: the domain and the data are in your name, almost always.

How the analysis works →

02 · reading

I read the code without judging it

Whoever came before had their reasons and their deadlines. I measure: what works, what is half-done, what needs redoing. The result is a written list you can show to anyone.

See an example →

03 · completion

I finish it and hand everything over

I complete the missing parts with an AI workflow reviewed by hand, take it live and leave you code, documentation and access. If one day you want to change developer, you can do it in an hour.

The method in detail →
git log --oneline · a typical takeover
  1. d1c4b2eAccess recovered: domain, hosting, database, repositorydays 1–3
  2. 82f0a9cCode review and written list: done, half-done, to redoweek 1
  3. 3e7c5d1Missing parts completed, one demo a weekweeks 2–5
  4. a6b9f04Go-live and handover: code, documentation, access in your nameweek 6

// work examples

Rebuilt projects, real numbers

Projects inherited from other developers and brought to completion, from the problem to the result.

yesvacanze.it
yesvacanze.it: search and APIs for a travel deals portal

travel-deals · laravel · vue · mongodb

yesvacanze.it: search and APIs for a travel deals portal

Full stack on catalogue, Elasticsearch search and supplier API integration, with on-site SEO from day one.

Read the case study →
curapiu.it
CuraPiù: the care home management software I designed and built

care-home-software · web app · ai · qr code

CuraPiù: the care home management software I designed and built

My management software for care homes: QR codes on residents, digital patient records and medication charts, care plans and AI voice dictation. Up and running in 7 days.

Read the case study →
youcanprint.it
youcanprint.it: the frontend of a catalogue with thousands of titles

self-publishing · vue · laravel · mongodb

youcanprint.it: the frontend of a catalogue with thousands of titles

Senior frontend since 2018: search, product pages and on-site SEO of a portal with millions of page views.

Read the case study →

trueThis is for you if

  • Your emails and messages have gone unanswered for weeks and the website or business app is half-finished.
  • You're not sure what you actually have: who holds the domain, where the site runs, where the code is.
  • The project has to go live and you can't afford to start from scratch.

falseNot for you if

  • You want someone to blame whoever came before: I assess the code, not the people.
  • You have no access at all and no invoice or contract: ownership has to be recovered first, then we can work.
  • The work has only been stalled for a day: wait a week and try contacting them again, then let's talk.

// my secret

Taking over well is a skill of its own

In 23 years I've inherited dozens of half-finished projects. The temptation is always to say everything needs redoing. It's almost never true: usually 60% works and the rest just needs finishing with method. First you recover ownership, then you read, then you promise.

With AI, reading unfamiliar code takes days instead of weeks. That's why today a takeover makes more sense than a rewrite.

  • I dotaking over half-finished websites, online stores and web business apps; recovering access, code and data; completion.
  • I don'tlegal expert reports, debt collection, native apps, projects with no recoverable access at all.

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

The questions I get before we start

How do I recover domain, hosting and code if I don't have the login details?

You start from whoever paid: invoices and contracts prove ownership. The domain registrar and the hosting provider have recovery procedures for the owner; the code is often on the server itself. On the first call we make a list and I tell you what to ask of whom.

Can you work on code written by someone else?

Yes, it's most of what I do. I read the code with AI tools and by hand, document it, and complete it without rewriting it all. It doesn't need to be perfect: it just needs to be there, and I'll tell you honestly what state it is in.

What happens if I don't have the source code?

If the website is live, the PHP code is on the server and can be recovered with access to the hosting. If it runs on a closed service (a subscription site builder), content and data are exported and the rest is rebuilt. We work this out in the first analysis.

How much does a takeover cost?

The initial code review is part of the free analysis: in two days you get a written list of what is done, half-done and to redo, with an estimate. Completion is paid in stages, and the first stage is always the one that gets you live.

Should I tell the previous developer?

It's not mandatory, but it's the right thing to do, and often useful: a clear message announcing the change and asking for access and code unblocks more situations than you'd think. I'll help you write it, calmly and without any blame.