Your AI-built app is 80% done.
I’ll get it across the finish line.

Yes — all of them, plus Claude, Copilot and ChatGPT output. I don’t much care which tool generated the code. What matters is the application underneath it: the architecture, APIs, database, dependencies, and where things are breaking. Lovable and Bolt projects tend to need deployment and backend work; Cursor and Copilot projects more often need the seams between generated pieces checked.

That’s completely fine — “something doesn’t work” is enough to start. Send me the URL, repository, screenshot, error, or whatever you have, and I’ll tell you what else I need. Working out what’s wrong is the first thing I do, not something you have to do before contacting me.

Usually not. Rewriting is the most expensive option and it’s rarely the one the code actually calls for. I’d rather find the specific things that are broken and fix those.

That’s one of the main reasons people come to me. AI is good at generating and modifying code; the problems appear where the generated pieces interact — architecture, state, APIs, databases, authentication, deployment, production environments. Those are exactly the things a model can’t see from inside one file, and exactly what I look at first.

Try the AI once or twice more — sometimes that is enough. If two rounds haven’t fixed it, the model is missing context it can’t get from your description, and each further attempt adds an untested change. That is the point where a developer who reads the code, reproduces the failure and fixes the cause is cheaper than another week of prompting.

You send me what you have and describe what’s going wrong. I go through the application and the code, then come back with what I found, what I’d fix first, and what I’d leave alone. You get that in plain language, not a report you need a developer to interpret.

Yes, and it’s one of the most common reasons people get in touch. "It works locally" is almost always an environment, configuration or build problem rather than a code problem, and those are findable.

It depends on the work, so I don’t publish a price list. After a first look I quote a fixed price for the diagnosis, and any fix is scoped from the findings — so you know the cost before any work begins, and nothing changes partway through.

Less than you’d think. A repository or a deployed URL, some idea of what’s broken, and access to whatever is failing — logs, the hosting dashboard, an error message. If you don’t have all of that, send what you do have and I’ll tell you what else I need.