Support
Bringing a prototype
A working prototype from Lovable, Bolt, Cursor, or Replit is a real head start, and we take them seriously. It is also usually not the thing you can put in front of paying users yet. Here is how that conversation goes.
What do you need from me to look at it?
Access to the repository or an export, the list of accounts and services it touches, and an honest map of what is real and what is mocked. That last one saves the most time.
Tell us who the users are and what they are supposed to do. We can read the code, but we cannot read the intent behind it.
What will you keep, and what will you rebuild?
More survives than founders expect. The interface thinking and the data model usually hold up, because those came from you understanding your own problem.
What usually gets rebuilt: authentication, how secrets and keys are handled, and anything that runs in the background. AI builders are good at producing something that works when one friendly person clicks through it, and less good at the parts that only matter when strangers show up.
What problems do you usually find?
The same short list, over and over, and none of them mean you did something wrong.
- Authentication that can be bypassed, so one user can reach another user data
- API keys and secrets committed into the repository
- Missing row-level security, meaning the database itself does not enforce who can read what
- No tests, so there is no way to know whether a change broke something
- No error monitoring, so failures in production are invisible until someone complains
Do I need to stop using the AI builder while you work?
No. Keep building, on a branch. Nothing reaches production without passing the automated checks and a review from us, which is the same rule we hold ourselves to.
The full policy is on the code and accounts page.