Claude is excellent at inventing an interface. It is less excellent at giving that interface a database, auth, and a URL your team can bookmark. Lovable (and similar app builders) is the other half: it ships. Used together, a non-engineer can go from "we need a tool for X" to a working internal app in an afternoon.
I use this pairing for internal tools, not public consumer products. The standard is: will an agent in the field actually click this twice? If no, delete it.
Who does what
| Claude | Lovable |
|---|---|
| Clarify the job, users, edge cases, copy, information architecture | Generate the app, host it, hook a backend, auth |
| Write the spec as if a contractor will build it without you | Implement the spec, iterate on UI |
| Review the result like a skeptical operator | Fix what the review found |
The spec Claude should write first
Do not open Lovable with "build me a CRM." Open Claude and produce a one-pager:
# App spec User: [role], on [phone or desktop], in [how many minutes]. Job to be done: [one sentence]. Screens: 1) 2) 3) Data we store: [fields]. Data we must never store: [PII rules]. Happy path: [click-by-click]. Failure: [what happens if the API is down]. Empty state: [what they see on day one]. Done means: [a test a stranger could run].
That spec is the prompt. Paste it into Lovable. When the first preview appears, do not immediately ask for more features. Walk the happy path. Write down every moment you hesitated. Those hesitations are the second prompt.
The loop
- Claude writes / updates the spec.
- Lovable implements.
- You click like a tired user, not a proud builder.
- Claude turns your notes into a punch list with priority 1 / 2 / 3.
- Lovable only gets priority 1 until those are gone.
Skipping step 3 is how you ship AI slop: extra screens, gradient soup, three ways to do the same thing.
Backend without becoming a developer
Use Lovable's default backend (or Supabase) for anything that must persist: waitlists, simple CRMs, request forms. Rules I don't violate:
- No secrets in the frontend. Ever.
- Don't store more personal data than the job needs.
- One table until you can explain why you need two.
- If money or medical data is involved, stop and get a real engineer.
When to graduate to Claude Code
If you need custom integrations, a design system that matches this site, or five people committing to the same repo, move the project to Claude Code. Lovable is the factory for v1. Claude Code is the factory for v2 when v1 is already earning its keep.
The method is the same as everything else on this site: specify, ship something small today, delete what nobody uses.