You Built It in Lovable or Bolt. What Does It Take to Launch for Real?

An AI builder gets you a working app in a weekend. Paying users need more than that. Here is what usually has to be fixed, what you can keep, and what the work costs.

8 min read
Cover for the Lovable and Bolt to production guide: a prototype app screen next to a keep, fix and rebuild list

You described an app to Lovable, Bolt or Base44, and two days later you had one. It has screens, a login page, maybe a Stripe button. Friends tried it and said nice things. Now a real customer wants to sign up, and you've got a bad feeling about it.

That feeling is usually right, and it's fixable. We keep seeing the same request on Upwork: "finish my Lovable app", "connect a backend to my Base44 MVP", one of them with $5,000 attached. This post is what we'd tell those founders before they hire anyone.

What you actually have

You have a prototype that works on the happy path. One user, clean data, nobody trying to break anything. That's worth a lot. You proved the idea can be shown and clicked, and you did it for the price of a subscription.

What you don't have yet is the dull part. Who is allowed to see which data. What happens when a payment fails halfway. Where the backups are. An AI builder won't raise these questions, because you didn't ask and the demo runs fine without them.

Where these apps break

Data that anyone can read. In 2025 a flaw registered as CVE-2025-48757 turned up in apps generated by Lovable. The database rules that decide who sees what were missing, and researchers counted more than 170 live apps where a stranger could pull users' emails, phone numbers and payment details. The founders hadn't done anything unusual. They shipped what the tool gave them. Lovable disputes the report and says each customer is responsible for protecting their own app's data. That's the part to remember: the responsibility is yours.

It isn't one tool's problem either. Veracode ran 80 coding tasks through more than 100 AI models and found a security flaw in 45% of the results.

Logins. Sign-up works. Password reset, email confirmation and "this account already exists" often don't. Roles are the bigger risk. If your app has customers and admins, check whether a customer can open an admin page by typing its address.

Payments. The button charges a card. The app then has to learn that the charge went through, and that message can arrive late, arrive twice or never arrive (six things that break an API integration after launch covers why). Prototypes tend to trust the browser instead, so a refund or a failed renewal leaves the account in the wrong state.

Keys in the wrong place. Secret keys for Stripe, email or an AI service sometimes sit in code that every visitor's browser downloads. Anyone can copy them and spend your money.

No safety net. No backups, no error alerts, no second copy of the app to test changes on. You find out something broke when a customer writes to you.

Code nobody can change. After fifty prompts the app has three versions of the same form and logic copied between screens. Each new prompt fixes one thing and breaks another. This is usually the moment founders start looking for a developer.

What you can keep

What to keep, fix and rebuild in an AI-built prototype

More than you'd think. Nobody should charge you to start again from a blank page without a reason.

  • Keep the screens and the flow. You've already tested them on real people, and they're the cheapest part to carry over.
  • Fix the data rules, logins, payment handling and where the secret keys live. This is most of the work.
  • Rebuild only what can't be repaired. If the data is laid out in a way that can't grow, or the tool won't let you take the code out, that piece gets written again.

One question settles a lot: can you export the code and move the database to an account you own? If yes, a developer can work on what exists. If the app only runs inside the builder, you're renting it.

What it costs

One published breakdown puts a focused "production lift" at $5,000 to $30,000 and an agency rebuild at $25,000 and up. The spread comes from how much has to be rewritten.

Here is how we'd estimate it at our rate of $40 an hour:

  • Audit, 8 to 12 hours, $320 to $480. A developer reads the code, tries to break it, and gives you a list sorted by risk. Do this first whatever you decide afterwards.
  • Hardening, 60 to 120 hours, $2,400 to $4,800. Data rules, logins and roles, payment confirmations, keys moved to the server, backups, error alerts, hosting on accounts you own.
  • Partial rebuild, 150 to 250 hours, $6,000 to $10,000. The screens stay, the back end is written properly. This is the usual outcome for marketplaces and anything with subscriptions.

A full rebuild costs about the same as building the MVP from scratch: a marketplace, line by line, lands at $7,800 to $10,600 for the core, and you can price your own feature list with the calculator below.

When to do nothing yet

If nobody pays you and you don't store anything personal, leave it alone. Keep showing the prototype, keep changing it, and spend the money on finding users. That's the stage where an AI builder is the right tool, and we say so to founders who ask.

The line is simple. The day you take a payment or someone's personal data, the app is a product, and the list above stops being optional.

Three checks you can run today

  1. Open the app in a private window, without logging in, and paste the address of a page that should be private. If it loads, your data rules need work.
  2. Create two accounts. From the first, try to open an order, profile or file that belongs to the second.
  3. Ask the builder where your secret keys are stored and whether you can export the code. Save the answer.

If any of the three worries you, send us the link. We'll tell you whether it needs an audit, a few fixes or a rebuild, and what each would cost.

Questions founders ask us about Lovable and Bolt apps

Investors liked the demo but want to see "real technology". What do they mean?

Usually four things: the code lives in a GitHub repository you own, the database and user accounts sit in a Supabase or similar project in your name rather than inside the builder, someone's checked who can read what, and there's a second copy of the app where a change is tested before it goes live. None of that's visible in a demo, which is why they ask. The 8 to 12 hour audit above produces exactly that list, and a one-page audit report is something you can forward to them the same week.

Which companies can productionize a Lovable or Bolt prototype?

Any studio or freelancer who works with the stack underneath the builder, which for Lovable and Bolt is mostly React on the front and Supabase behind it. Ask two questions before hiring: "Will you work from my exported code or start over?" and "What will I own at the end?" A good answer keeps your screens, moves the data and the keys to accounts you control, and leaves you with a repository and a deploy you can run without them. We do this work, at $40 an hour; so do a few hundred others on Upwork. The two questions matter more than the name on the invoice.

How do I measure usage of my Lovable or Bolt app?

The builders don't give you product analytics, so add it. Two cheap options. First, paste a GA4, PostHog or Plausible snippet into the app's HTML head; most builders allow it, GA4 is free, PostHog's free tier covers a million events a month, and you'll see visits and pages within 24 hours. Second, look at the database itself: the users table tells you sign-ups per week and the last sign-in column tells you who came back. For anything deeper, have a developer log the three actions that matter in your product, such as "listing created" or "payment completed". That's 2 to 4 hours of work, and it's the first thing an investor asks for after the demo.

Can I export the code?

Lovable connects to a GitHub repository and keeps it in sync both ways; Bolt lets you download the project as a zip or push it to GitHub. Base44 and some newer builders are more closed, so check before you buy the next batch of credits. If you can't get the code out, the "keep the screens" option above disappears and a rebuild from the $6,000 line is the only path.

How long does it take?

From the hours above: an audit is 1 to 2 days, hardening 2 to 3 weeks, a partial rebuild 4 to 7 weeks with one developer on it. A prototype that already has paying users is usually in the hardening bucket, not the rebuild one, so plan for three weeks and a bill under $5,000.