Service · AI-built applications

Your AI-built app works. Let's make it ready for real users.

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.

  • Barcelona · remote EU/US
  • Human code review
  • Reply < 24 business hours

Does any of this sound familiar?

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.

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.

Data migration has stopped you cold

The application is half built, but moving customers, orders or history out of your current ERP or CRM looks impossible without breaking something.

Every fix creates another problem

The AI suggests a different solution each time, none quite fits, and you no longer know which change is safe.

You don't know whether the architecture holds

It works with test data. You have no idea what will happen with real users, permissions, concurrency or volume.

Auth or integrations fail

Login, roles, payments or APIs work halfway, and you can't find the actual cause.

There is no plan after launch

Nobody has defined how to deploy, monitor, back up or fix an error in production.

You don't have to throw away what you've built

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.

  • Review of the code, database and real configuration.
  • Clear priorities: what prevents launch comes first.
  • Changes explained in language you can follow.
  • Documented decisions so you don't depend on me forever.

Technical help where AI-built projects tend to get stuck

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

Rescue and troubleshooting

The problem
The application breaks or stops progressing, and the AI fixes never reach the root cause.
What I do
I trace the full flow, find the source and fix backend, frontend, authentication or integration issues.
What changes
You get a project moving again that looked blocked.
Audit and maintenance

02

Deployment and production launch

The problem
It runs on your machine or in the builder preview, but there is no real environment.
What I do
I set up hosting, domain, SSL, environment variables, database, CI/CD and basic monitoring.
What changes
A stable URL and a repeatable way to publish changes.
See deployment help

03

Database and data migration

The problem
You need to move data from an ERP, CRM, spreadsheet or legacy database.
What I do
I design the mapping, clean and validate the data, run the migration and verify integrity.
What changes
Your data arrives complete and verifiable, not merely copied.
See data migration

04

Technical audit and production readiness

The problem
You don't know whether the code is safe, maintainable or ready for real users.
What I do
I review architecture, permissions, dependencies, performance and tests, then deliver prioritized findings.
What changes
You know what to fix first and what risk you accept by waiting.
See the audit

05

Ongoing maintenance and development

The problem
The app is live, but nobody owns its maintenance or next features.
What I do
I fix bugs, build features, update dependencies and keep an eye on performance.
What changes
A technical partner without hiring a full-time developer.
See maintenance

People who usually need this kind of help

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.

Non-technical founders

You built a first version for your business and need someone to take responsibility for the technical side.

Teams working with AI agents

You use Codex, Claude Code, Cursor or Windsurf and want human review before changes reach production.

Companies replacing an ERP or CRM

You want to move from closed software to your own tool without losing history or workflows.

Products already in production

The app has users, but bugs, performance or integrations are starting to hurt.

Your AI tool isn't the issue; the stack still matters

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.

Tools you may have built with

  • OpenAI Codex
  • Claude Code
  • Cursor
  • Windsurf
  • Lovable
  • Bolt.new
  • Replit
  • v0

Stacks I can review with confidence

  • Laravel / PHP
  • Node.js
  • TypeScript
  • React
  • Vue
  • Next.js
  • Nuxt
  • Astro
  • PostgreSQL
  • MySQL
  • SQLite
  • Supabase
  • Redis

Infrastructure and services

  • Vercel
  • Netlify
  • Railway
  • Render
  • DigitalOcean
  • Docker
  • GitHub Actions
  • Nginx
  • Stripe
  • REST APIs

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.

Production engineering, not another layer of AI

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.

Read the full technical case

A short process from being stuck to a technical decision

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.

  1. 01

    Tell me what you've built

    What the app does, which tool you used, where it runs and what is blocking you. No technical report needed.

  2. 02

    I review the real state

    I look at code, database, configuration and scope, then tell you what I see and what I can't guarantee.

  3. 03

    We define the path

    Priorities, scope and next step in writing. If I'm not the right person, I say so.

  4. 04

    I fix, deploy or migrate

    Every delivery is tested and explained; nothing ends at “it should work now”.

  5. 05

    We decide what follows

    I can stay on maintenance or leave documentation and a plan for your team to take over.

What people usually ask before getting in touch

Can you help with an application built entirely with AI?

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.

Do I need to understand programming to contact you?

No. Tell me what the application does and where it breaks. Translating that into a technical problem is my job.

Can you work with Codex, Claude Code, Cursor or Lovable?

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.

My app works locally but won't deploy. Can you fix that?

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.

Can you migrate data from my current ERP or CRM?

Yes, if I can export the data or access it with authorization. The work includes mapping, cleaning, validation and import, not just copying rows.

Can you review AI-generated code?

Yes. I review readability, security, permissions, error handling, dependencies and tests. The result is a prioritized report, not a promise that everything is perfect.

Can you get my application ready for real users?

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.

Can you take over an existing application?

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.

Do you maintain and improve the software after launch?

Yes. It can be occasional maintenance or an ongoing collaboration, depending on what the application needs.

Do I have to start from scratch?

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.

I don't know which technology my app uses. Is that a problem?

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.

Do you work remotely with international clients?

Yes. I work remotely from Barcelona with companies in Spain, the EU and the United States, in Spanish or English.

Tell me what you've built and where you're stuck

No technical brief needed. With four details I can understand the starting point and tell you whether I can help.

What helps to include

  • What the app does and who it is for.
  • Which tool you used (Codex, Claude Code, Cursor, Lovable…).
  • Where it runs today and what exactly fails.
  • Whether you have a repository, domain or code access.
  • What you want to achieve: deploy, migrate, review or maintain.

Please don't share passwords, API keys or production credentials in the form. If access is needed, we arrange it securely afterwards.

Tell me what you need

Name, email, reason and message are enough. I reply within 24 business hours, and if there is an NDA we sign it before sharing details.

0/500
Availability