How do I transfer a Lovable project to my client?

Lovable generates a React app connected to a Supabase backend. To transfer cleanly, you need to move the Supabase project to the client's own Supabase organisation, reconnect the GitHub repository to the client's account, and redeploy to a hosting provider (such as Vercel or Cloudflare Pages) under the client's login. It is easiest to set this up in the client's accounts from the start rather than migrating at the end.

Can a non-technical client manage a site built with an AI builder after handoff?

It depends on the tool. Builders that generate raw code (React, Next.js) require a developer for ongoing changes. Builders like Stunning allow the client to continue editing by describing changes in plain language or by speaking to the AI assistant, which suits non-technical business owners in the Gulf and Egypt who do not have an in-house developer.

What should I include in a website handoff document for a client in Saudi Arabia or the UAE?

Include: domain registrar login and DNS settings; hosting account credentials; database connection details; all third-party API keys (payment gateways such as Moyasar or Tap, registered under the client's own merchant account); VAT registration details for ZATCA e-invoicing if the client is in Saudi Arabia; and the trade licence number associated with any business accounts. Payment and VAT credentials cannot be transferred — they must be set up under the client's own legal entity.

Is Lovable worth it for building client websites?

Lovable is a strong tool for builders comfortable with React and Supabase who want code-level control. For client work, the main challenge users report is handoff: the infrastructure lives in the builder's accounts by default and requires deliberate planning to transfer. If your client project is a standard business system rather than a highly custom application, a no-code builder with simpler ownership may reduce that risk.

Lovable Alternative: Fix the Client Handoff Problem

If you have built something useful in Lovable and then stared at the screen wondering how to actually give it to your client — the domain, the data, the Supabase project, all of it — you are not alone. This is the single most-discussed frustration among Lovable users in public forums, and it is worth addressing honestly before you choose any AI builder for client work.

Why the Handoff Problem Happens

Lovable generates a React application backed by a Supabase database. Both live inside accounts that belong to the builder, not the end client. Many users report variations of the same confusion: the site is live, the client loves it, but ownership of the underlying infrastructure — the database, the hosting, the domain — is tangled up in the developer's own accounts.

This is not a flaw unique to Lovable. It is a structural reality of any tool that provisions cloud infrastructure on your behalf. When the tool does it quietly in the background, the moment of handoff becomes a project of its own: migrating a Supabase organisation, reconnecting a custom domain, transferring GitHub repositories, and explaining to a non-technical client why their new website lives inside someone else's Vercel account.

Users have described workarounds — connecting GitHub and redeploying on Cloudflare Pages, moving the Supabase project to the client's own organisation, or simply leaving everything in the builder's account and hoping the client never asks. None of these is a clean handoff.

A Practical Checklist Before You Start Any Client Project

Whatever builder you use, these steps protect both you and your client from a messy ending.

1. Agree ownership in writing before you build. Decide whose account the domain, hosting and database will sit in. If the client will own it, they should create those accounts on day one.

2. Use the client's accounts, not yours. Where the tool allows it, connect the client's GitHub, their hosting provider login, and their domain registrar from the start. Retrofitting this at the end is far harder.

3. Document every credential and integration. Keep a handoff document: domain registrar login, DNS settings, database connection strings, third-party API keys. In the UAE, Saudi Arabia or Egypt, this often includes payment gateway credentials (Moyasar, Tap, PayTabs, Paymob) and, for Saudi clients, the ZATCA e-invoicing configuration tied to their VAT registration. These cannot be transferred — they must be re-entered under the client's own trade licence.

4. Test the site under the client's domain before final delivery. A surprising number of handoffs fail because an environment variable or API key was hard-coded to a staging URL.

5. Clarify ongoing maintenance costs. If the tool runs on usage credits or a subscription, the client needs their own account and billing method before you walk away.

How Stunning Handles This for Non-Technical Builders

Stunning is an AI builder where you describe what you need — in plain English or spoken Arabic — and it builds a working web app or business system with a real database included. One-click publish, custom domain, and the project sits in your Stunning account from the start.

For client work, the relevant point is transparency: Stunning runs on a single credit balance, and you can see the balance and what it was used on at any time inside your account. There are no hidden provisioning steps in a third-party cloud account that you then have to untangle. The site, the database and the domain are managed in one place, which makes the conversation with a client about what they are receiving straightforward.

Local payment rails — Moyasar, Tap, PayTabs, Paymob, Tabby — connect using the merchant's own credentials, so when a client in Dubai or Riyadh needs to accept card payments or Tabby instalments, those credentials belong to the client's business from day one, not to your Stunning account. The same applies to accounting integrations: Wafeq and Qoyod (both ZATCA e-invoicing compliant for Saudi Arabia) connect under the client's own VAT registration.

If you are building for a client who will eventually manage the system themselves, Stunning's voice assistant Layla means a non-technical owner can continue editing and extending the system by speaking to it — no developer required after handoff.

When Lovable Is Still the Right Choice

Lovable is genuinely strong for builders who are comfortable with React, GitHub and Supabase, and who want maximum control over the underlying code. If your client has an in-house developer who will maintain the codebase, the GitHub sync is a real advantage. If you are building something highly custom — an unusual data model, a complex real-time feature — the code-level access Lovable provides is hard to match with a no-code tool.

The handoff problem is solvable in Lovable if you plan for it from the start: create the Supabase project in the client's own organisation before you connect it, and deploy to the client's own Vercel or Cloudflare account via GitHub. It requires deliberate setup, but it works.

The question is whether your client project needs that level of customisation, or whether a business system — an online store, a booking page, a CRM, a clinic management tool — can be built and handed over more simply.

Choosing the Right Tool for the Job

For most small-business client projects in the Gulf and Egypt — a restaurant's ordering page, a real-estate brokerage's listings site, a clinic's Arabic booking system — the complexity that makes Lovable powerful is also what makes handoff complicated. A builder that keeps the infrastructure visible and in one place reduces the risk of a project ending with an awkward conversation about who owns what.

The best handoff is the one you plan before you write the first prompt. Agree ownership, use the client's accounts where it matters (especially for payments and VAT), document everything, and choose a tool whose infrastructure model you understand end to end.

If you are ready to try a simpler path, describe what your client needs on Stunning and watch it get built — free to start.

Switcher