Where you're starting · Vibe code cleanup

Turn your AI-built prototype into real software.

Lovable, Bolt, Replit, v0 or Cursor got your idea off the ground — and now customers log in and pay. We rework the foundations underneath (security, data, tests) so the app can grow without breaking, and nobody has to relearn the screens they already use.

Who this is for

  • Real customers are paying to use something that started as a prototype, and you hold your breath before every update.
  • A fundraise is coming up, and you know someone will ask whether the code has been reviewed.
  • A weekend project has quietly become something your team relies on every day.
  • You're an agency handing a prototype to a client, and it has to survive contact with them.

Where AI-built apps fall down

AI builders are great at screens. What they tend to skip is the hidden part — the bit nobody notices until it fails. These are the issues we run into most.

Security checked only in the browser

The admin button is hidden from view, but the server never confirms who's making the request. Open the developer tools and anyone can read or change someone else's records.

Secret keys exposed in the frontend

API keys ship to every visitor along with the page — easy to copy, and every call is charged to you.

Database rules missing or too loose

Supabase row-level security (or whatever the equivalent is on your stack) is disabled, or the rules are so broad they block nothing.

No automated tests

Any fresh prompt can quietly undo yesterday's working feature — and the customer usually finds out before you do.

No backups or monitoring

If the site falls over at 3am or the data disappears, nobody hears about it — and there's no copy to bring back.

A data model built prompt by prompt

Tables that duplicate each other, fields doing double duty and records that have drifted apart. Each new feature gets harder to add.

Is your app at risk?

Tick everything that applies. You'll get the same honest verdict we'd give you on a call.

0 of 7 ticked

Keep building for now.

If nobody relies on it yet, rebuilding is money spent too early. Keep learning from your users and come back once real people or real money depend on it.

Ask us about yours →

How vibe code cleanup works, step by step

Step 01

Code review

We go through the code and data, map every screen and flow, and give you a fixed scope, price and timeline before you commit.

Step 02

Foundation plan

Data model, permissions, hosting, backups and deployment — all written up for you to approve before we build.

Step 03

Rebuild in the open

Work happens on a link you can click within weeks, using your real data, while the prototype keeps serving your users.

Step 04

Migrate your users

Accounts, records, files and subscriptions all come across, so nobody signs up twice. The domain and payments switch over in a scheduled window.

Step 05

Go live and hand over

Monitoring, alerts, backups and an automated deploy pipeline are switched on. You receive the code, documentation and every credential.

Four ways to get software built

Each route has its place. Here's how they stack up on the four things that make or break a project.

OptionCostSpeedOwnershipWhen something breaks
A traditional agencyHourly rates or a big retainer, often with no end dateMonths of discovery, design and hand-offsUsually you — sometimes with licences attachedA ticket in somebody else's queue
Off-the-shelf softwareLow to start, then per-seat fees foreverLive today — if it fitsThe vendorWhenever the vendor's roadmap says so
Doing it yourself with AI toolsCheap now, costly to fix laterA demo in daysYou — and every risk that comes with itYou, at 2am
ThoughtOceanFixed-scope sprints, priced before each one startsA working demo in weeks, not monthsYou, outrightThe engineer who built it — in your time zone

Included in every project

Not just promises on a web page — it's all in the proposal you sign. We reply within one business day.

Price agreed up front.Scope and cost are set in writing before work begins. Minor tweaks along the way are on us; anything bigger becomes a separate decision, never a surprise on the invoice.
Post-launch bug fixes included.If something we delivered doesn't behave the way we agreed, fixing it costs you nothing. That's on us, not a new job.
Everything in your name.Code, domain, hosting accounts and data all belong to you. Host it wherever you like, hire whoever you like, and never pay us a licence fee.
A real handover.Code, documentation, logins and a walkthrough for your team. Nothing is locked away in our heads.
No lock-in, ever.Support is optional and month to month — cancel whenever you like. We'd rather you stay because the software keeps improving.

Vibe code cleanup: common questions

What's a 'vibe-coded' app?

Anything built mostly by prompting an AI tool — Lovable, Bolt, Replit, v0, Cursor, Claude Code, Base44, or a Supabase back end wired up the same way. The tool doesn't matter; what matters is whether anyone has checked what it produced.

Will you fix my code or rebuild it?

Whichever the code needs. If the foundations are solid we harden them and carry on. If the data model or permissions are the problem, patching tends to be slower and riskier than rebuilding underneath while keeping the screens. You'll get our reasoning in writing after the review.

Will my users notice a difference?

Only if you want them to. The screens and flows people already know become the spec. Most users simply notice it's faster and stops breaking.

What happens to existing users and data?

They move with you. Accounts, records, files and subscriptions are migrated, tested on a copy first, then switched over in a planned window. The prototype stays live until the new version takes over.

How long will it take, and what will it cost?

We fix both after the code review, because the honest answer depends on what's in there. Since your prototype already answers most of the design questions, it costs less than building from nothing.

Can I keep using AI tools afterwards?

Yes. We set things up so you can keep prompting safely: tests that catch breakages, a review step before anything reaches production, and a structure the tools can follow.

Will I own the code?

Completely. It lives in your repository and your hosting accounts, so you can deploy it anywhere and hire anyone to work on it.

Tell us about your app.

A few lines is plenty. We read every message and reply with an honest take on what we'd do — even when the answer is that we're not the right fit.

[email protected] Aussie team · replies within one business day
Or book a call

Opens your email client with the message pre-filled. We reply within one business day — no obligation, no sales sequence.