AI fixes one thing and breaks another.
You’ve spent hours or days circling the same problem and every new prompt creates a new edge case.
I help founders get AI-built apps finished, fixed and ready for real users — without starting over.
Senior engineer · 13 years in production software · Based in Portugal (EU)
Sometimes another prompt isn’t the answer. That’s usually where I come in.
You’ve spent hours or days circling the same problem and every new prompt creates a new edge case.
Payments, customer data and private accounts are involved. That’s when “it seems to work” stops being enough.
The product has users. You want to keep moving fast without gambling with production.
If the same problem keeps coming back, another prompt probably isn’t going to solve it. I find out why it’s happening and fix that.
back to the first prompt
with a test behind it
I don’t open with a rewrite or a retainer. We start with the smallest piece of work that can actually move things forward.
You’ve got one thing blocking you. I get into the code, trace the problem and help get it out of the way.
You can’t tell whether the app is safe to put in front of people. I go through it and tell you what I found, what I would fix, and in what order.
Sometimes it’s not one bug anymore. A few things are tangled together and patching them one by one isn’t working. That’s what Rescue is for.
After a Rescue, someone watching the things that break quietly: a bad deploy, a failed payment, a backup that stopped running.
A senior engineer in your corner while you keep building: review before you ship, and a straight answer when you don’t know whether something is safe.
I’m building small apps with the same AI tools founders use, to run the checks I’d want before trusting one in production. The card beside this is the format. The first result isn’t in yet, and the label stays on until it is.
Usually not. Rebuilding is the last option, not the default recommendation.
Yes. I’m not here to take the product away from you. If you can keep building it yourself afterwards, that’s a good outcome.
For hands-on work, usually yes. We can talk first, before you share anything sensitive.
Then I’ll tell you that. I’d rather send you back to Cursor than invent work you don’t need.
Send me the app and tell me what’s been giving you trouble. I’ll have a look and tell you how I’d approach it, even if the answer is just “keep building”.