Most vibe-coded projects reach us at the same point. The app looks finished, the demo works, and then something stops it going live: logins that break, payments that do not update the account, a security review that came back with a long list, or a developer quote that says start again.
Starting again is rarely the answer. The code an AI tool writes is usually a reasonable shape with a handful of serious gaps. The gaps tend to be the same ones: who is allowed to see what, what happens after a payment, where the keys are kept, and whether the database can change without losing data.
We work through those gaps in order of risk, keep what already works, and hand back code you own, in your own accounts, with notes a future developer can follow.
What is included
A free first look
An hour reading your code and any reviews you already have, then a plain answer: what can be judged from the code, what needs testing, and roughly how many blocks of work it will take to launch.
Sign-in and permissions
Every request checked on the server, so a signed-in user can only see and change their own records. This is the most common serious gap in AI-built apps.
Secrets out of the code
Keys and passwords moved out of the code and out of anything sent to the browser. Any key that was ever committed gets replaced at the provider, because deleting it from the code does not remove it from the history.
Payments that stay in sync
Stripe set up so renewals, failed cards, refunds and cancellations update the account by themselves, not only the first checkout.
A database you can change safely
Proper migrations, tested on a throwaway copy first, plus backups and separate test and live databases so a test never touches a real customer.
Launch and handover
Rate limits on public forms, error logging, the app store or hosting launch, and a short written handover so the next person is not starting from zero.
How we work
- 01
Free first look
You share read-only access to the code. We spend an hour on it and tell you what we found and what it is likely to take. No obligation, and we sign your NDA first if you have one.
- 02
Agree the first block
Work is done in 10-hour blocks. Each block has a named goal and a target date, agreed in writing before it starts, so the scope cannot drift.
- 03
Fix, test, show you
Changes go in as reviewable updates to your own repository, tested before you see them. At the end of each block you get a short note on what was fixed and what is next.
- 04
Launch
Once the serious issues are closed, we take it live, check it on real devices, and stay on for the first round of fixes that real users always find.
Signs your AI-built app is not ready to launch
- Changing a number in the address bar shows someone else's data
- API keys or passwords sit in the code, or anywhere in the git history
- Paying works, but cancelling, renewing or a failed card does not change the account
- The database has been changed by hand, with no record of what changed
- There are no automated tests, so every fix risks breaking something else
- Nobody is sure which accounts (hosting, database, app stores, Stripe) you actually own
Why we fix rather than rebuild
A rebuild throws away the part AI tools are genuinely good at: screens, layouts and the everyday logic. It also means paying for months of work before you can launch.
Fixing in place means the risky parts get rebuilt properly and the rest stays. If the code really is past saving, the first look will say so, and we will tell you before you spend anything more.
The tools we see most
Lovable, Bolt, Replit, Cursor, v0, Claude and ChatGPT, usually on Next.js or React, Expo for phone apps, and Supabase, Firebase or Postgres underneath. If yours was built with something else, send it anyway.
Your code stays yours
The code lives in a repository your business owns, and we work through access you can remove at any time. We do not ask for your passwords and we never need your customers' data to do the work. If you want AI tools kept away from your code, say so and we will work without them.
Frequently asked questions
What is a vibe-coded app?
An app or website built mostly by describing it to an AI tool, such as Lovable, Bolt, Replit or Cursor, rather than writing the code by hand. It is a fast way to get something working. The risk is that nobody has checked the parts you cannot see, like permissions, payments and data.
Do I have to start again?
Usually not. Most AI-built code is a reasonable shape with a few serious gaps. We fix those and keep the rest. If a part is genuinely unsafe to keep, we will say which part and why.
How do you know what is wrong before you start?
The free first look. An hour with the code and any reviews you already have tells us what can be judged from the code alone and what needs a test build, and gives you an estimate of how many blocks it will take.
Why 10-hour blocks instead of one big quote?
Because nobody can price a whole rescue honestly before seeing how the code behaves when it runs. A block is small enough to quote exactly, has its own goal and date, and you can stop after any block.
Will you sign an NDA?
Yes, before the first look if you need one. We also keep the code in your repository rather than passing copies around.
Can you also get it into the App Store and Google Play?
Yes. Store submission is part of our app work, including the developer accounts, listings, privacy declarations and the review back-and-forth.
How much does it cost?
Work is charged from $120 per hour. For a defined project we estimate the hours after a free discovery call and give you a fixed quote, so you know the total before anything starts.
Work in this area
Often paired with
Or see every service we offer.



