Someone else built it.
I take it from here.

No. Laravel and PHP are where I have the deepest mileage — ten years of it — so that is what I lead with when someone wants proof. But the job here is reading unfamiliar code and taking responsibility for it, and that skill does not stop at a framework boundary. I work across Node, Next.js and React, Astro, and mobile in Flutter and native. If your stack is genuinely outside what I can be useful in, I will tell you that in the first reply rather than three weeks in.

You should — I do, every day, and it is a large part of why this work is affordable now. But an AI answers the question you ask it, and the expensive problem with inherited software is not knowing which question to ask. It will happily make the change you requested and take out something three files away that nobody told it mattered. What you are paying me for is the judgement in between: knowing what to leave alone, which mess is load-bearing, and which shortcut turns into an outage at month four. If your code is already mostly AI-written, you have felt exactly this.

It is the most common thing landing in my inbox right now, and no, it is not something to be embarrassed about. AI gets you to a working demo faster than any team could, and then the same code hits real users and real data and starts failing in ways it was never shaped to handle — no error handling, no tests, permissions that were never thought through, database calls stacked inside loops. Cleaning that up is ordinary work now. It is usually far cheaper than the rebuild people assume they are facing.

No, and I would rather you did not. Everything runs over written messages — email or WhatsApp, whichever suits you. You get thinking you can re-read, forward to a partner, and hold me to later. It also means the time zones stop mattering. If a call is genuinely the only way through something, we will do one, but it is rare.

Then you are the person this page is for. I have never once opened an inherited codebase and thought less of the owner for it — messy software is the normal outcome of shipping under pressure with whoever was available. I am not going to lecture you about test coverage. I will tell you what it costs to make it safe, and what you can leave alone.

Yes, and it is a lot of what I do. The first step is always the same: work out what is actually there versus what you were told is there. Those two are rarely the same, and the gap between them is usually the reason the project stalled. Once that is written down, finishing it is normal engineering.

Less than you think. Repository access is ideal. A staging login works. Honestly, screenshots and a paragraph explaining what is going wrong are enough for a first read — I can tell you a surprising amount from the outside. You do not need a specification, a budget or a plan; working out the plan is the thing you are hiring me for.

Then I will say so, and I will explain what makes me think it — even though a rescue is the better-paid job for me. Talking someone into repairing software that should be retired buys me one invoice and costs me the reference. There have also been times the right answer was that their existing developer was fine and they needed a second opinion, not a new hire.

You should ask that of anyone you find online, including me. The usual route is a bank transfer against an invoice, arranged so you are never far ahead of the work: the first read costs nothing, an audit is paid when it lands in your inbox, and a sprint is split across its two weeks. If that still feels like a leap, hire me through Upwork instead — your money sits in escrow until you approve what I have delivered, and there is a company between us if it goes wrong. The price for a given piece of work is the same either way; Upwork adds its own fee on your side, and that is what the protection costs.

My Upwork profile

Surat, India — IST, UTC+5:30. I have worked with clients in Canada, the United States and across Europe for years, so overlap is a solved problem: written updates land before your morning, and I keep evening hours when a project genuinely needs the overlap. I take on a limited number of engagements at a time, which is why replies are fast and why I sometimes say no.