Help · From prototype to production

From Lovable prototype
to a real website.

You built something in an evening that looks good. The problem is not your idea, it is the distance between a demo and something you dare hand to customers: your own domain, speed, findability, safe data and code someone else can take over.

Vibecode naar productie
0:00 / 0:00

In half a minute I show what almost always sits below the waterline in a project like this: everyone can reach all the data, payments that only work in the demo, and an environment that does not run outside the tool.

Recognise it? Send your link. The first opinion costs you nothing.

Sound familiar

A demo is not a website yet.

01

It runs on their domain

As long as your site sits on a subdomain of the tool, you build neither brand nor SEO. Moving to your own domain is more than a DNS record if the environment around it does not move with it.

02

Google cannot find it

Everything is rendered in the browser, without titles, structured data or a sitemap. Technically it works, but to search engines the page barely exists.

03

Slow on mobile

Uncompressed images and far too much JavaScript. On a phone over 4G, half your visitors leave before anything appears.

04

Editing content costs a prompt

Every text change goes through the tool. Without a CMS you depend on the underlying subscription for every comma.

05

Forms and email

Enquiries do not arrive, end up in spam or nowhere. Without properly handled email, revenue quietly leaks away.

06

You cannot leave

No repository, no documentation, no export that runs anywhere else. If the subscription stops, your site stops.

How it works

From demo to something you can sell.

01

I look at what you have

Send the link or the export. I judge what is usable: design, copy, structure and data model. That opinion costs you nothing.

02

Design and copy stay yours

What works, we keep. Usually the design is the best part of your prototype and the problem sits in the layer underneath.

03

Rebuilt in Next.js

Server-side rendered, with a CMS so you edit copy yourself, meta text and sitemap for Google, optimised images and forms that land neatly in your inbox.

04

Live on your own domain

Domain connected, SSL sorted, analytics set up privacy-friendly and the old URLs cleanly redirected. The code sits in your GitHub.

What you end up with
  • A site on your own domain, findable in Google
  • Fast load times on mobile
  • A CMS you manage content with yourself
  • Forms and email that arrive
  • Code in your GitHub, no subscription holding your site hostage

The first opinion costs you nothing: send me the repository or a link and I will tell you honestly whether building on beats starting over.

Frequently asked questions
Can my design from Lovable be preserved?
Yes. In most cases I take the design over one to one and rebuild the technology underneath. If you want to use the opportunity to sharpen the design, we do that in the same step.
What does taking a prototype to production cost?
A website takes two to three weeks. If there is an application behind it, with logins or payments, it is four to six weeks and correspondingly more work. Either way you get a fixed number before we start.
Does this apply to Bolt, v0, Replit or Framer too?
Yes, same story. It is not about the tool, but about the step from demo to something that may go live, is findable and stays transferable.
Can I still use my AI tool afterwards?
For prototypes and new ideas: absolutely. I see them as a sketchbook, not a production environment. The distinction between those two is exactly what costs most people money.
How long does the move take?
For a website usually two to three weeks. If there is already a clear design and the copy is ready, it can be faster.
How do I connect a custom domain to my Lovable site?
Inside Lovable you can point a custom domain at it; your site then keeps running on their hosting and stays dependent on your subscription. The other route is exporting to your own hosting, after which domain, DNS and code are all in your name. For anything customers rely on I recommend the second, precisely because a cancellation then does not mean an offline site.
How do I export my Lovable project to GitHub?
Lovable connects to your GitHub account and writes the project to a repository that is yours. That puts the code in your hands, but not yet a working setup outside it: environment variables, build settings and database migrations are usually missing. That last part is exactly what finishing the build is about.
Where is the best place to host an exported project?
For React or Next.js, Vercel works most comfortably, with Supabase for the database. I put both accounts in your name and you pay the supplier directly, with no markup through me. If everything has to stay inside the EU, we pick the region accordingly.
Will my site be more findable after the move?
That is one of the reasons to do it. An AI prototype is usually a browser app: one address, one title, little for Google to read. During the move every page gets its own URL, title, description and place in the sitemap, and structured data is added. That makes indexing possible; rankings after that still depend on your copy and your competition.
Let's build

Tell me what you
want to build.

A half-hour call. You get an honest answer about what it costs, how long it takes and whether building it is smart at all.

Free · no obligation

Have your current site or tool scanned

You do not have to want to buy anything yet. Send what you have and I will tell you honestly what I would keep, what I would replace and whether that is worth the investment. Including when the answer is that you are better off doing nothing.

The scan is a first impression, not a security audit.

WhatsApp
0:00 / 0:00
  1. 01Send a link to your site, your tool or your repository
  2. 02I look at speed, structure, data and security
  3. 03Usually within two working days you hear what I would replace and what that costs
Vibecode naar productie
0:00 / 0:00
From Lovable prototype to a real website · Webframer