It works in preview, not in production
The app runs on your machine or inside the builder, but deployment fails on environment variables, database access, domains or permissions.
Service · AI-built applications
I review, fix, deploy and maintain applications built with Codex, Claude Code, Cursor, Lovable, Bolt, Replit or v0. No default rewrite, and no need for you to read the code.
The starting point
You're not the only one here. AI has made the first version much faster to build; the trouble starts when that version has to carry a real business.
The app runs on your machine or inside the builder, but deployment fails on environment variables, database access, domains or permissions.
The application is half built, but moving customers, orders or history out of your current ERP or CRM looks impossible without breaking something.
The AI suggests a different solution each time, none quite fits, and you no longer know which change is safe.
It works with test data. You have no idea what will happen with real users, permissions, concurrency or volume.
Login, roles, payments or APIs work halfway, and you can't find the actual cause.
Nobody has defined how to deploy, monitor, back up or fix an error in production.
The approach
An AI-generated application can be a perfectly valid starting point. The problem isn't that a machine wrote it: it's that nobody has reviewed the decisions underneath.
My work starts by understanding what you have, what works and where the risk sits. From there I propose the shortest route to a stable product: keep what is sound, fix what blocks you, and document what your team needs to know.
I won't promise to rescue any codebase unchanged. If part of it needs to be rebuilt, I explain why and what the alternatives are before touching anything.
AI speeds up the first version. Engineering decides whether that version can carry a business.
What I can do
You may need one of these or several. The first conversation is for understanding the real state and deciding what is worth doing first.
01
02
03
04
05
Who it's for
You don't need an engineering team or a technical diagnosis. I work with internal platforms, ERP/CRM systems, booking tools, customer portals, SaaS products and industry-specific management software. I only need access to the project and an explanation of what you want it to do.
You built a first version for your business and need someone to take responsibility for the technical side.
You use Codex, Claude Code, Cursor or Windsurf and want human review before changes reach production.
You want to move from closed software to your own tool without losing history or workflows.
The app has users, but bugs, performance or integrations are starting to hurt.
Tools and technologies
I can work with projects built through different agents and app builders. Before taking the work I review the code, access and architecture to see whether I can genuinely help.
This does not mean I accept any project or any stack. If I cannot access the code or the architecture won't let me take the work on responsibly, I tell you before we start.
Why me
You won't be talking to someone whose only skill is asking a model for changes. I've spent five years maintaining Laravel/PHP/Vue applications in production, owning database, API, frontend, deployment and observability.
15k
req/min at peak
A real campaign with high traffic and windows that did not allow mistakes.
99.9%
campaign uptime
Monitored operations and incident response during the peak.
118 ms
API p95
Deliberate work on caching, queues and queries to hold latency.
5+
years in production
Product, agencies and international clients with code in the wild.
How it works
No filler meetings and no free audit promised up front. First I understand the project; then we decide whether there is work and how to do it.
What the app does, which tool you used, where it runs and what is blocking you. No technical report needed.
I look at code, database, configuration and scope, then tell you what I see and what I can't guarantee.
Priorities, scope and next step in writing. If I'm not the right person, I say so.
Every delivery is tested and explained; nothing ends at “it should work now”.
I can stay on maintenance or leave documentation and a plan for your team to take over.
Frequently asked questions
Yes, as long as I can access the code and review how it is built. The fact that AI generated it doesn't rule it out; what matters is whether the architecture and data let me work on it.
No. Tell me what the application does and where it breaks. Translating that into a technical problem is my job.
Yes. They are different tools, but the starting point is the same: review the repository, the environment and what was generated. I can also work with Bolt, Replit, v0 or Windsurf projects.
It's one of the most common cases. The cause is often environment variables, database access, permissions, DNS or differences between development and production. I diagnose it and leave a reproducible deployment.
Yes, if I can export the data or access it with authorization. The work includes mapping, cleaning, validation and import, not just copying rows.
Yes. I review readability, security, permissions, error handling, dependencies and tests. The result is a prioritized report, not a promise that everything is perfect.
I can review and fix the technical blockers I find: authentication, data, deployment, backups, monitoring and errors. The decision to launch is still yours and also depends on the product and the business.
Yes, after reviewing it. I don't take on maintenance for code I haven't been able to assess, because I would end up promising something I can't deliver.
Yes. It can be occasional maintenance or an ongoing collaboration, depending on what the application needs.
Not by default. Keeping the existing work is usually the first option if the code and data allow it. If part of it needs rebuilding, I explain why before doing it.
Not for the first conversation. With the URL or repository I can identify the stack. If you don't have code access, we can also review the alternatives.
Yes. I work remotely from Barcelona with companies in Spain, the EU and the United States, in Spanish or English.
Contact
No technical brief needed. With four details I can understand the starting point and tell you whether I can help.
What helps to include
Please don't share passwords, API keys or production credentials in the form. If access is needed, we arrange it securely afterwards.
Related help
Related service
From preview to a stable URL: hosting, domain, SSL, database, CI/CD and monitoring.
Related service
Mapping, cleaning and validation to move your company history into a custom application.
Related service
Code, permissions, performance and tests reviewed; ongoing maintenance after launch.