You shipped something. People are using it. And there is a quiet nagging feeling that you do not really know what is underneath. This one is for you, and the short version is that the feeling is reasonable, the situation is common, and it is fixable.
At a glance
You have working software that people use. Twelve months ago that would have required a developer and a budget you did not have.
You also cannot answer questions about it, which is an uncomfortable place to be when it is starting to matter. Both of those things are true at once, and the first one is a genuine achievement.
First: you have not done anything wrong
Let us deal with this bit properly, because it stops people asking for help.
You used a tool that was marketed, accurately, as a way for non-developers to build applications. It worked. You now have something real, built for a fraction of what it would otherwise have cost, and you got to test your idea against actual customers instead of a spreadsheet.
That was a sensible decision. It remains a sensible decision. If there are gaps in what you have, that is not a failure of judgement on your part, it is a property of the tool that nobody mentioned in the marketing.
Developers can be sniffy about this. Ignore them. The people who built nothing because they were waiting for a proper budget are not in a better position than you.
The nagging feeling
It usually shows up around the time the first proper customer arrives, and it sounds like this:
What if someone can see somebody else's data? What happens if a hundred people use it at once? What if it breaks and I cannot fix it? What if the platform changes its pricing, or disappears?
Those are not paranoid questions. They are, more or less exactly, the questions we would ask. The instinct is sound. What is missing is a way to get answers.
How to tell whether you actually have a problem
Some rough signals, in order of how much they should concern you.
Worth checking soon:
- You store anything personal, names, addresses, anything about identifiable people
- Money moves through it
- You have more than a handful of separate customer accounts
- You have never tested whether one account can see another's data
Worth checking, less urgently:
- Things have got noticeably slower as you have added data
- You get occasional odd bugs nobody can reproduce
- You would not know if it broke at three in the morning
- You are starting to hire, or to talk to investors
Genuinely fine for now:
- It is just you and a few friendly users
- No personal data, no payments
- You would happily rebuild it if you had to
If you are entirely in the last group, stop worrying and go and get more customers. That is the actual priority.
The five-minute test you can run yourself
If you do one thing after reading this, do this one.
Make two accounts with different data. Log in as the first, open one of its records, and look at the address bar, there will be a number in it. Now log in as the second account and put that same number in the address bar.
You should be told you cannot see it. If instead you are looking at the first account's information, you have found the single most common serious problem in this kind of software, and you have found it before a customer did.
What this is not
It is not a write-off. This is the assumption we spend most of our time arguing people out of.
The screens are fine. The idea is fine. The business logic reflects a year of you learning what your customers actually need, and none of that is affected by whether the database has the right indexes. What tends to be missing is the invisible engineering underneath, and that can be put in without touching what sits on top.
Starting again is nearly always slower, more expensive, and throws away the most valuable thing you have, which is not the code.
What happens next
Realistically, three options.
Do nothing yet. Legitimate if you are still small and nothing sensitive is involved. Just decide now what would change your mind, so the decision gets revisited rather than forgotten.
Get it looked at. Someone reads what you have and tells you plainly what is there, what is missing, and what actually matters. Days, not months. You end up with a list and the ability to answer questions about your own software.
Get the important bits fixed. Usually a short piece of work following the review, targeting the things that genuinely matter rather than everything a developer would like to change.
We do this specifically for applications built on Lovable, Replit, Bolt and similar: built with Lovable, Replit or Emergent?
None of this is a criticism of the tool you used. It is just the thing this series keeps coming back to: AI is a brilliant typist and a terrible architect. You got excellent typing. The architecture was nobody's job, and that is not your fault.
Want a straight answer about what you have got? Get in touch and we'll tell you, in plain English rather than developer language.
