AI project rescue / direct with Hamza

You started it with AI. I finish it and get it live.

You started it with AI. I finish it and get it live. Send me the project you began in Lovable, Bolt, Cursor, v0, ChatGPT or Replit, whether it stalled halfway or it is built and you don't know how to get it working, deployed and launched.

  • Same-day reply
  • Free audit call first
  • Remote from Casablanca
Started withLovableBoltCursorv0ChatGPTReplit

Start here

Is your project rescuable?

Three quick questions. You get a short starting plan you can send me on WhatsApp or bring to a free audit call.

1Which tool did you start with?

2Where are you stuck?

3What's the goal?

Your starting plan

Answer three quick questions.

Pick one option in each step and your plan appears here, ready to send.

  • Step 1
  • Step 2
  • Step 3

Sounds familiar?

Where AI-started projects usually stall

The AI gets you a convincing first version fast. The last part, where the app has to work for real people, is where most projects stop.

Stuck half-built

Some screens work, others are placeholders, and every new prompt breaks something that worked yesterday.

Auth or payments broken

Sign-up, login, password reset or checkout fail, or only work on the happy path.

Can't deploy

The build fails, environment variables are missing, or you don't know where the app should be hosted.

Database errors

Tables, permissions or migrations don't match what the code expects, and data goes missing.

Works locally only

It runs on your laptop, but not on a real domain, a phone or another person's account.

The AI keeps looping

The same bug comes back after each fix, and the assistant rewrites code without solving it.

Typical cases

Before and after, in plain terms

Generic scenarios that come up again and again with AI-started projects. They describe typical cases, not specific clients.

The booking app that only half exists

Stuck

Calendar screens look done, but bookings are never saved and confirmation emails never send.

Done

Bookings written to a real database, confirmation emails sent, and an admin view to see them.

The SaaS stuck at checkout

Stuck

Stripe test checkout works once, then subscriptions never activate after payment.

Done

Webhooks handled, plans unlocked after payment, and billing tested end to end in test mode.

The app that runs on one laptop

Stuck

Everything works on localhost. Deploying fails on missing keys and a database that only exists locally.

Done

Production database, environment variables set, deployed on your own domain with a repeatable build.

The bug the AI keeps reintroducing

Stuck

Each prompt fixes the login loop, and the next prompt brings it back somewhere else.

Done

Root cause found in the auth flow, fixed once, with a check that catches it if it returns.

What's included

From stalled project to live product

I keep what works in your code, fix what is broken and finish what is missing. You keep full ownership of the code and accounts.

Code audit

I read the repository, run it and write down what works, what is broken, what is unsafe and what is missing.

Fix and finish features

Broken flows repaired and unfinished features completed, including error states and edge cases.

Auth, payments and database

Login, roles, Stripe payments and the database set up properly, with access rules and exposed keys removed.

Deploy to production

Hosting, environment variables, your domain and a build that deploys the same way every time.

Launch checks

Real accounts, real devices and real payments in test mode, checked before your users see it.

Handover

Clean repository, written notes on how it runs and how to change it, and the accounts in your name.

How it works

Five steps, one clear scope

  1. 01

    Send the repo or link

    Share the repository, the AI tool project or a link to what exists, plus a few lines on what it should do.

  2. 02

    Free audit call

    A 30-minute call where I go through what I found and what it takes to get it live.

  3. 03

    Fixed scope

    A written list of what I fix, finish and deploy, agreed before any work starts.

  4. 04

    Build and launch

    I fix and finish the app, deploy it to production and test it with you on the live version.

  5. 05

    Handover

    Code, accounts and documentation handed back, so you or another developer can keep going.

Typical timeline

How long each step usually takes

  1. 1 to 2 daysReview of the repository or link after you send it.
  2. 30 minutesFree audit call, then the written scope within a few days.
  3. 1 to 4 weeksFix, finish and deploy, depending on the agreed scope.
  4. 1 to 3 daysLaunch checks on the live version and handover.

Indicative ranges. The real timeline depends on the state of the code, the features left and how fast feedback comes back.

What I need from you

Before we start

  • Access to the repository or the AI tool project
  • A short description of what the app should do and for whom
  • Access to the services it uses (database, payments, hosting) or permission to set them up in your name
  • One person who can test and answer questions during the build

Tools I work with

The stacks AI tools usually generate

Next.js and React

The default output of Lovable, Bolt, v0 and most Cursor projects, and my main stack.

React Native

Mobile apps for iOS and Android, from a working build to the stores.

Laravel

PHP backends and admin panels, including ones started with ChatGPT.

Supabase

Database, auth and storage, with row-level security set up properly.

Stripe

Checkout, subscriptions and webhooks, tested in test mode before going live.

Vercel

Production hosting, environment variables, preview builds and your own domain.

Extensions

Optional add-ons once it's live

Nothing here is required. Once the rescue is done, these are the extras projects usually ask for next, each scoped separately.

WhatsApp assistant

Answers common questions, takes requests or bookings on your WhatsApp Business number and hands over to a person.

Admin dashboard

A private area to manage users, orders, bookings or content without touching code.

Stripe payments

One-off payments, subscriptions, invoices and webhooks, tested before going live.

Analytics

Event tracking on the actions that matter, so you see where users drop off.

SEO setup

Metadata, sitemap, structured data and fast pages, so search engines can read the site.

Mobile app version

A React Native app for iOS and Android sharing the same backend.

Automations

Emails, notifications, sheet updates and workflows triggered by what happens in the app.

Maintenance

Updates, monitoring and small fixes after launch, so the app keeps working.

Stories

Real projects, from brief to live

Short stories from projects documented on this site. Only what the project pages state, no invented numbers or quotes.

Doc Samad biography page with Dr Abdessamad Benalla on laptop and phone

Doc Samad

The brief
Intimate-care products and professional consultations needed to live in one place, explained clearly and in four languages.
What was built
A Next.js storefront on a Laravel commerce backend, secure Stripe checkout, consultation booking connected to appointment availability, and a private admin.
Where it is now
Live website, with the same journey in French, English, Italian and Arabic.
Open the project
Amana Logistics website with the price calculator

Amana Logistics

The brief
Visitors want to know what a move will cost before they ask, and the team needs every detail to confirm the price.
What was built
A six-step calculator with Dutch address suggestions and a distance estimate, a live price indication, and the full request sent on WhatsApp with a reference number.
Where it is now
Live public website in Dutch and English. The WhatsApp intake assistant runs in a test environment.
Open the project
Jobisque report on laptop and phone

Jobisque

The brief
Professionals need to see how AI affects their day-to-day tasks and which skills to develop next.
What was built
A Next.js product with a Node.js backend and the Claude API: task exposure analysis, human strengths and a practical career roadmap.
Where it is now
Live product with an interactive sample report.
Open the project
Eversa Arabic storefront on laptop and phone

Eversa

The brief
Everyday products for Morocco needed an Arabic-first store that feels natural right to left and works around cash on delivery.
What was built
A custom Shopify theme with reusable Liquid sections, editorial product pages and a cash-on-delivery interface.
Where it is now
Live Arabic storefront.
Open the project

Questions

Before you send your project

Can you finish an app I started in Lovable, Bolt, Cursor or v0?

Yes. These tools mostly generate React or Next.js code, which is my main stack. I look at the repository before saying what can be finished and how.

Do I have to start over?

Usually not. Most AI-started projects have a usable structure. I keep what works and replace only what is broken, unsafe or missing.

My app is built but I don't know how to put it online. Can you help?

Yes. That is part of the service: hosting, database, environment variables, domain and the first deploy, explained so you can do the next ones.

What if the code is too far gone?

The audit call tells you that before you commit to anything. If rebuilding parts is the faster path, you get that in the written scope.

Who owns the code and accounts?

You do. The repository, hosting, database and payment accounts stay in your name, and everything is handed back at the end.

Can you keep working on it after launch?

Yes, if you want. New features and fixes after launch are scoped separately.

Next step

Send me what you started. I'll tell you what it takes to get it live.

Book a free 30-minute audit call or send the project on WhatsApp. You leave with a clear list of what is left, whether or not we work together.