Free audit · Lovable, Bolt, Cursor, v0, Replit, ChatGPT
You built the app with AI. I will tell you for free if it is ready for customers.
I look at the code, the data, the accounts and the payments. Then I tell you in plain words what is solid, what needs rebuilding and what it would cost to take it to production. The audit does not commit you to anything.
- 17 years of software: frontend, backend and mobile
- 10 products of my own, with real payments, accounts and data
- I work with AI agents every day, so I know where they slip
- Reply within one working day
Where these apps usually get stuck
AI tools write code that works in a demo, fast. The problems show up when real people arrive with real data. These are the ones I look for first.
- 01
Keys in plain sight
Keys for the database, payments or AI end up in the code that runs in the browser, where anyone can read them.
- 02
Data that is not yours
Access rules are missing, so a signed-in user can read or change other people’s data.
- 03
Works for one, not for a hundred
Pages that load the whole database at once, with no paging, no cache and no indexes.
- 04
Every change breaks something else
Code generated in layers, with no tests, that neither the person nor the AI fully understands any more.
- 05
Payments and emails only in test
Unverified webhooks, payments that never confirm, emails that land in spam.
- 06
No safety net
No backups, no error log, no test environment separate from the one customers use.
What I check
Six areas, in the order in which they can do the most harm.
Security
Keys and passwords, access rules, sign-in, what is visible from the browser.
Data
Database structure, backups, what is lost if something fails, GDPR.
Accounts and roles
Who can see and do what, invitations, password reset.
Payments and integrations
Stripe or another processor, webhooks, emails, outside services.
Code and structure
Whether a developer can carry it on, what needs rewriting and what stays.
Hosting and costs
Where it runs, what it costs per month at 10 and at 1,000 users, what happens at a traffic peak.
What you get
- A written report in plain words, without needless jargon.
- What is solid and stays as it is.
- What must be fixed before customers arrive, in order of risk.
- What can wait until after launch.
- An estimate of time and cost to reach production.
- A 30-minute call where I walk you through the report.
If you want me to take the app further, you get a fixed price. If not, the report is yours and any developer can use it.
How it works
- 01
You write to me
The link to the app and what it should do. A few lines are enough.
- 02
You give me read access
An invitation to the repository on GitHub or GitLab, read-only. Or you show me the app on a call.
- 03
You get the report
I walk you through it on a call and answer your questions. You decide afterwards, with no rush.
Please do not send me passwords or API keys by email or through the form. Invite me with read-only access and remove it after the audit. If you want, I sign a non-disclosure agreement before I look at the code.
Questions
Why is it free?
It is the first step, just like the free call for my other projects. If you want to continue after the audit, you get a fixed price. If not, we stop there.
Which tools and technologies?
Lovable, Bolt, Cursor, v0, Replit, ChatGPT, Claude, or code written by a freelancer. On the technical side: React, Vue, Supabase, Node.js, PHP and Laravel, MySQL and PostgreSQL.
Do I have to rebuild everything?
Not necessarily. The point of the audit is to keep what works and rebuild only what is risky.
How much do the fixes cost?
It depends on what I find. You see the estimate in the report before you decide anything. Small changes start at €150.
Ask for the audit
Tell me where the app is and what got stuck. I reply within one working day.
Please do not send me passwords or API keys by email or through the form. Invite me with read-only access and remove it after the audit. If you want, I sign a non-disclosure agreement before I look at the code.