Your Lovable app is 80% done.
Who does the last 20%?
The screens are there, the flow works, people have clicked through it. And then it stops: users see each other's data, Stripe works in test but not live, every prompt breaks something that worked yesterday. This page answers three questions honestly: can you finish it yourself, who do you hire if not, and what does it cost.
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.
Where Lovable apps get stuck.
Users see each other's data
Row-level security is off or has a policy that lets everyone through. The most common problem, and the one that goes live unnoticed most often. [How that happens](/blog/gebruikers-zien-elkaars-gegevens-supabase-rls).
Stripe works in test, not live
Live keys, live price IDs and a webhook with its own signing secret. Three things that never existed in the preview. [Why it breaks](/blog/betalingen-werken-in-test-maar-niet-live).
It has to leave lovable.app
Your own domain, your own hosting, your own Supabase. The export to GitHub gives you code, not a working setup. [What exporting involves](/blog/lovable-app-exporteren-en-zelf-hosten).
Every prompt breaks something
Past a certain size the model touches files that were already right, and without meaningful commits there is no way back. [Why that happens](/blog/waarom-breekt-mijn-lovable-app-bij-elke-wijziging).
Keys in the frontend
An API key for OpenAI or Resend in the browser code is a bill someone else runs up. [Where they belong](/blog/api-sleutels-in-de-frontend).
Works locally, not live
Environment variables, redirect URLs for login, a build that behaves differently. [The usual causes](/blog/werkt-lokaal-wel-live-niet).
From stuck to live, without starting over.
Free scan
You send the link or the repository. Usually within two working days you get an honest verdict: keep building, have it finished, or (rarely) start over.
Assessment, if needed
One day of review with a written report: risks worst first and a fixed price per block. Credited in full against the work after it.
Finishing, at a fixed price
Security, payments, hosting, whatever the report says. Your screens and data model stay; I build the foundation underneath.
Handover
Repository, Supabase and hosting on your name, with documentation. You can carry on yourself, with me, or with someone else.
When you can finish it yourself
Not every stuck Lovable app needs a developer. If the problem is a screen that looks wrong, a field that is missing or a flow you want to change, keep prompting. That is what Lovable is good at, and paying someone for it is a waste.
It changes when the problem is below the surface: who can see which data, money that has to arrive, a server that has to keep running. The model can write that code too, but you cannot check whether it is right, and a mistake there does not show up as an error but as a data breach or a missed payment. If you are in doubt whether to keep building or start over, this article walks through it.
Keep going yourself
Layout, copy, new screens, small flows, a prototype only you and a few testers use.
Get help
Real customer data, payments, logins with roles, your own hosting, or an app that breaks with every change.
Fiverr or Upwork, or a developer in the Netherlands
Searching for a Lovable developer mostly turns up freelancers on Fiverr and Upwork. For a quick fix to a screen that can work fine, and the hourly rate is often lower. For the parts above it pays to look at more than the rate.
The questions that matter are the same whoever you pick: whose name is the code, the database and the hosting in, who is liable when customer data leaks, and who signs the data processing agreement your customers are entitled to under the GDPR. Comparing an agency, a freelancer and doing it yourself point by point is worked out here.
| Platform freelancer | Webframer | |
|---|---|---|
| Price | Per gig or per hour, often lower | One fixed price after the scan, known up front |
| Contract | Platform terms, often under foreign law | Dutch contract, Dutch law, Chamber of Commerce registered |
| GDPR | Data often processed outside the EU | EU hosting, data processing agreement as standard |
| Ownership | Transfers on payment, check the terms | Repository and accounts in your name from day one |
| Afterwards | Next gig, possibly someone else | Same person, maintenance if you want it |
What it costs
These are the same fixed prices as on vibecode to production. All amounts exclude VAT. The free scan comes first; most apps need one or two blocks after it, not the whole list.
| Step | What it covers | Price |
|---|---|---|
| Free scan | Ten minutes of looking and an honest verdict: build on or start over. | € 0 |
| Assessment | One day of review. A written report with risks in order and a fixed price per block. | € 600 |
| Taking Stripe live | Live price IDs, webhooks with their own signing secret, the customer portal and a real test payment. | from € 750 |
| Securing it | RLS per table with policies that are right, roles, no keys in the frontend, Supabase advisors clean. | from € 1,500 |
| Moving to your own hosting | From Lovable Cloud or a lovable.app address to your own GitHub, Supabase and hosting, on your own domain. | from € 2,250 |
| Finishing or taking over | What is missing after the assessment: sign-in, roles, payments and going live. | from € 3,000 |
| Into the App Store | Your app as a real app for iPhone and Android, including store submission. | from € 3,000 |
Clients rate me 5 stars on average.
“I am extremely happy with the result of my new website for DoubleStreet Australian Cobberdogs, made by Webframer. From first contact, Webframer radiated expertise and creativity.”
“Webframer helped me enormously with the Veldvisuals website. It is not only good to spar with Bas about building the site, but also in the aftercare and whenever changes have to be made. Recommended!”
“Great to work with. Listens carefully to what we want. When we ask for changes, they are made expertly.”
“Really pleasant to work with and short lines of communication!”
“The website looks great!! Definitely recommended!”
“Excellent! Fast service and good contact!”
Translated from the Dutch originals on Google.
I am Bas Voets. Since 2021 I have been building websites, client portals and business software for small and mid-sized companies, from Hazerswoude-Dorp in the Netherlands. From first call to launch you talk to me, not to an account manager.
Is my Lovable app worthless?
Does everything have to be redone?
What does it cost to have a Lovable app finished?
How long does it take?
Can I keep using Lovable afterwards?
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.
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.
- 01Send a link to your site, your tool or your repository
- 02I look at speed, structure, data and security
- 03Usually within two working days you hear what I would replace and what that costs