# When to hire a developer for your AI-built app

> Signs your Lovable, Bolt or Replit app has outgrown the AI builder, what a developer should do first, and the questions to ask before you hire one.

By Tommy Pham · 2026-11-14 · https://tommydev.web.app/blog/hire-developer-vibe-coded-app

**Short answer:** keep building with AI while you're still finding out whether people want the product. Bring in a developer when real users or real money arrive: you're about to take payments, store other people's personal data, publish to the app stores, or the AI keeps breaking one feature while fixing another. A good developer starts by reading your code and reporting what's risky. They shouldn't open with "we need to rewrite everything".

This is part of my [production checklist for vibe-coded apps](/blog/vibe-coded-app-production-checklist).

## Do you actually need a developer yet?

Probably not, if:

- You're testing an idea with a handful of friendly users.
- Nothing stores personal data beyond an email.
- No money changes hands inside the app.
- The AI builder can still make the changes you ask for without breaking other things.

AI builders are very good at this stage. I've built with Lovable, Bolt, Replit and Base44 myself, and for a prototype they're faster than writing code by hand. I compare them in [this guide](/blog/lovable-vs-bolt-vs-replit-vs-base44-vs-v0).

## What are the signs it's time?

| Sign | Why it matters |
|---|---|
| You're adding payments or subscriptions | Webhooks, refunds and failed payments need careful server code |
| Users' personal data is in the database | You need working access rules, like [Supabase RLS](/blog/supabase-rls-vibe-coding) or Firebase rules |
| The AI fixes one bug and creates two | The codebase has grown past what the tool can hold in context |
| You need iOS or Android apps | Store review, signing and in-app purchase rules ([App Store](/blog/expo-app-store-submission), [Google Play](/blog/pwa-to-google-play-twa)) |
| You're paying a lot in AI credits per change | A developer can be cheaper per fix once the app is large |
| A customer or investor asks about security | You need someone who can explain what's in the code |
| You want to move off the builder's hosting | Export, environment variables and a real deploy ([guide](/blog/export-lovable-app-deploy)) |

## What should a developer do first?

An audit before any building. In my experience, a useful first pass on an AI-built app covers:

1. **Access control.** Can user B read user A's data? Are the database rules real?
2. **Secrets.** Are any private keys in the frontend bundle or git history? ([How to check](/blog/api-keys-frontend-security))
3. **Payments.** Are webhooks verified? What happens when a payment fails or is refunded?
4. **Deploys.** Is there a staging copy, or does every change go straight to users?
5. **Data safety.** Are there backups, and has anyone tried restoring one?
6. **The worst parts of the code.** Which files are so tangled that every change there is risky?

The output should be a short written list, ordered by risk, that you can understand without being a developer. Then you decide what to fix.

## What should you ask before hiring?

- **"Can you look at my repo and tell me what you'd fix first?"** You want specifics about *your* code, not a generic pitch.
- **"Have you worked with this stack?"** Lovable and Bolt apps are usually React + Vite, with Supabase or the builder's built-in backend. Replit and Base44 apps differ. Hire for the stack you have.
- **"Will you keep the code I already have?"** A rewrite is sometimes right, but it should be a conclusion from reading the code, not an opening offer.
- **"Will I own everything?"** Code in *your* GitHub, hosting and database in *your* accounts, keys you control.
- **"How will I see progress?"** Small pull requests or regular deploys to a preview URL beat a big reveal at the end.
- **"Can I keep using the AI builder afterwards?"** Often yes. Many founders keep prototyping in the builder while a developer hardens the risky parts.

## Freelancer, agency or a full-time hire?

| Option | Good fit when |
|---|---|
| Freelancer | You need an audit, a set of fixes, or a feature built, with one person who reads the whole codebase |
| Agency | You need design, development and project management together, at a larger scope |
| Full-time hire | The product has traction and needs continuous development |

Many projects start with a freelancer for the audit and the risky fixes, and hire full-time later.

## FAQ

### Should I rewrite my vibe-coded app from scratch?

Usually not at first. Most AI-built apps can be made safe by fixing access rules, moving secrets server-side and cleaning up the worst files. Decide on a rewrite only after someone has read the code.

### Can a developer keep working in Lovable or Bolt?

Yes. Both sync with GitHub, so a developer can work in the code directly while you keep using the builder. Agree on who edits what, so you don't overwrite each other.

### How long does an audit take?

It depends on the size of the app. Ask for an estimate after the developer has seen the repo, not before.

### What do I need to share?

Access to the GitHub repo, a test login for the app, and read access to the database and hosting dashboards. Never share your own passwords. Invite the developer as a team member instead, so you can remove their access later.

---

I do this kind of work: audits, fixes and features for apps that started in an AI builder. My background is production apps on the web, iOS and Android ([see my work](/#work)). Hire me through Upwork or reach out in the contact section below.