# How do I hand a Lovable site over to a client? - URL: https://getroomi.com/guides/how-to-hand-a-lovable-site-over-to-a-client - Updated: 2026-10-20 Show it first, and hand it over when the deal is done. Before then, send the client the site in a room, on mock data, with a link for each person. After it, move the Lovable project to a workspace the client owns, or transfer its ownership, and hand over the repository and the domain with it. This guide is for an agency or a freelancer who has built a client’s site in Lovable. It covers showing the site before it is theirs, the two ways Lovable lets a project change hands, and what has to go with it. [Sharing a Lovable app with a client](https://getroomi.com/guides/how-to-share-a-lovable-app-with-a-client) covers the showing in more depth, and [Roomi for Lovable](https://getroomi.com/share/lovable) has the steps. ## Why not hand it over straight away? Because once the project is theirs, so is your work, whether or not the deal goes ahead. Until then, a room lets the client try every part of the site without owning any of it. It also tells you who opened it and when, which is the moment to call. Handing over is the last step, not the pitch. While the project is yours, you can keep changing it as they comment, and every round is one more reason to talk. [How agencies share work in progress](https://getroomi.com/guides/how-agencies-share-work-in-progress) covers those rounds. [Pitch with a working prototype, not just a deck](https://getroomi.com/guides/agency-pitch-working-prototype-not-just-a-deck) covers the pitch itself. ## How do I show the site before it’s theirs? Put it in a room on mock data, and send each person at the client their own link. A newer Lovable project runs as a container demo, on a paid plan; an older one runs as a static demo, on every plan. Lovable can also invite people to a published app, who must log in. - **A newer project.** A Lovable project made since 13 May 2026 needs a server, so on Roomi it runs as a container demo, on Pro or above. - **An older project.** An older Lovable project, built with React and Vite, builds to static files, so on Roomi it is a static demo, which runs on every plan, Free included. - **Its data.** A Lovable app on Roomi runs on sample data, never on its live Lovable Cloud backend. Every demo runs on mock data, and a container demo has no internet to reach one. - **Lovable’s own option.** On Lovable’s Free and Pro plans, up to 10 invited people per project can open a published app set to invite only. Each logs in with the invited email address to see it. Each person at the client gets their own link, so their visits are filed under their name. [Giving each client their own demo link](https://getroomi.com/guides/how-to-give-each-client-their-own-demo-link) shows how, and [Roomi against Lovable](https://getroomi.com/compare/lovable) sets the two ways side by side. ## How do I transfer a Lovable project to a client? There are two ways, both in the project’s settings. Move the project into a workspace the client owns, which they invite you to first. Or transfer its ownership, to someone in your workspace or, on some Lovable plans, straight to the client’s own account. Either way, check who pays from then on. ### Move it to the client’s workspace A Lovable project can be moved only to another workspace you belong to. Its direct collaborators are removed unless you choose to keep them, and the destination workspace pays for its usage from then on. Its access setting resets to that workspace’s default. 1. **The client makes a workspace of their own** in Lovable, and invites you to it. You can only move a project to a workspace you belong to. 2. **Open the project’s settings**, choose **Move workspace**, and pick the client’s workspace. 3. **Decide about collaborators.** People invited directly to the project are removed unless you choose to keep them. 4. **Tell the client what changes.** From the move on, their workspace pays for the project’s usage. 5. **Check who can open it.** The project’s access setting changes with the move, so look at it again in the client’s workspace. ### Transfer its ownership A Lovable project’s ownership can pass to an owner, admin or editor of its workspace. On Business and Enterprise, it can also pass to a Lovable account outside the workspace, which accepts a transfer request. - **To the client’s own account**, where your plan allows it, choose **Transfer ownership** and enter the email address of their Lovable account. They get a request, and the project is theirs once they accept. - **Otherwise**, the new owner has to be someone in your own workspace. For a client, moving the project into their workspace is usually the simpler route. ## What else has to go with it? The code, the domain and the data. Hand over the repository the project syncs with, by transferring it on GitHub. Move the custom domain, if the site has one. And ask Lovable what happens to the project’s Cloud backend and its data before you move it, because its help does not say. - **The repository.** On every Lovable plan, Git sync keeps a project in step with a repository on GitHub, GitLab or Bitbucket. Downloading the code once, as a zip file, is on the paid plans. A GitHub repository can be transferred to another account or organisation, with its issues, pull requests and history, and links to its old address redirect. A personal account has a day to accept, and the original owner stays on as a collaborator. - **The domain.** Lovable’s Pro plan includes custom domains and unlimited lovable.app addresses, and removes the Lovable badge. The domain’s registration is with whoever registered it, so move that, or its records, as well. - **The backend and its data.** Lovable’s settings page does not say what a move does to the project’s Lovable Cloud backend, its data or a connected domain. Ask Lovable before you move a live site. ## A handover checklist 1. **Your test accounts and sample records** are out of the live project. 2. **Keys you have used are rotated.** [Is it safe to send a client an AI-built app?](https://getroomi.com/guides/is-it-safe-to-send-a-client-an-ai-built-app) has the checks. 3. **The repository is transferred**, and the client can open it. 4. **The domain points where it should**, under the client’s control. 5. **The client signs in with their own login** and sees the project in their workspace. 6. **Who pays is agreed**, now that their workspace pays for usage. ## What happens to the room afterwards? It stays yours. The room was your pitch, not their product, so it never goes to the client. Once the real site is live, revoke the links or pause the room, and everything each person did stays on record. Or keep it, with the client’s permission, as work to show the next one. - **Revoke a link** from the Links tab. It stops working at once and cannot be undone ([sharing](https://getroomi.com/docs/sharing)). - **Pause the room** from the project’s Settings. Every link then opens a short page saying it is paused, and the same links open the room again if you resume it ([running a room](https://getroomi.com/docs/running)). Put the site in a room, send each person at the client their own link, and hand the project over when they say yes. ## Questions people ask ### Can I transfer a Lovable project to a client’s own account? Yes: join a workspace the client owns, and move the project into it. A Lovable project can be moved only to another workspace you belong to. Its direct collaborators are removed unless you choose to keep them, and the destination workspace pays for its usage from then on. Its access setting resets to that workspace’s default. ### Does the client need a paid Lovable plan? It depends on what the site uses. Lovable’s Pro plan includes custom domains and unlimited lovable.app addresses, and removes the Lovable badge. After a move, the client’s workspace pays for the project’s usage, so check its plan covers what the site needs. ### Should I hand it over before they pay? That is for your contract to say. A room lets them try every part of the site first, without the project becoming theirs until you hand it over. ## Sources - Lovable: [docs.lovable.dev/features/publish](https://docs.lovable.dev/features/publish), checked 19 October 2026 - Lovable: [docs.lovable.dev/features/projects/settings](https://docs.lovable.dev/features/projects/settings), checked 20 October 2026 - Lovable: [docs.lovable.dev/tips-tricks/external-deployment-hosting](https://docs.lovable.dev/tips-tricks/external-deployment-hosting), checked 12 October 2026 - GitHub: [docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository), checked 20 October 2026 - Lovable: [lovable.dev/pricing](https://lovable.dev/pricing), checked 12 October 2026 ## About the author **[Kaz Kato](https://getroomi.com/about)**, Co-founder & CTO, Roomi. Kaz co-founded Roomi with Tesh, whom he has built with since 2017: two startups that failed, one venture studio that didn’t, and an exit. More at [katosan.co.uk](https://katosan.co.uk). ## Related guides - [How do you share a Lovable app with a client and know if they opened it?](https://getroomi.com/guides/how-to-share-a-lovable-app-with-a-client) - [Should an agency bring a working prototype to a pitch, not just a deck?](https://getroomi.com/guides/agency-pitch-working-prototype-not-just-a-deck) - [How do you pitch a website to a client?](https://getroomi.com/guides/how-to-pitch-a-website-to-a-client) - [How do I give each client their own private demo link?](https://getroomi.com/guides/how-to-give-each-client-their-own-demo-link)