Lovable SaaS Prompts: 15 for Auth, Roles and Billing
Prompt builder · four steps · no account
Step 1 of 4
Which one is closest?
Building something else? Describe it to the AI generator
The gap between a Lovable demo and a SaaS is auth that survives a refresh, roles the database enforces, billing that reconciles and a trial that ends. These 15 prompts specify those four first. The foundation prompt built a workspace with tested invites for 10.4 credits, and this page shows the run, the cost and the order that avoids rework.
By Marco Kohns · Prompts written and run by us
Short answers
Short answers
Where do I start?
SaaS MVP with User Auth, always. Every other prompt here assumes a workspace, three roles and an invite flow already exist.
Pick by situation →What does a run cost?
10.4 credits
Our measured run of the foundation prompt: backend provisioning, sign-in, a tested invite flow and Lovable checking its own output. Two days of free credits plus a bit.
See the credit math →Will Lovable ask questions first?
Four on this run, one at a time: what the SaaS is for, how the first workspace is named, how invites travel, and which of three visual directions fits. None cost extra credits.
Read the run →Does Lovable do payments?
Built-in Paddle or Stripe on Pro and above; your own Stripe account on any plan. The billing prompts here are written for the second path, which is also the one that gives you a webhook.
Both paths, from the docs →15
SaaS App prompts in this category
↳ Copy-paste, free
10.4credits
Measured run, saas mvp with user auth
↳ 72.8 → 62.4 after 0 daily credits
4
Questions Lovable asked first
↳ Before writing any code
64
Upvotes since Jan 2026
↳ One per visitor, self-reported
Data basis: one run of one prompt in a fresh Lovable project in Marco's own workspace, balance read before and after. The other 14 prompts are not run yet and say so on their card. Plan, payment and credit rules from Lovable's docs, checked 22 October 2026.
Find a prompt
Which part of the SaaS are you building?
Cards are sorted by build order. Each says whether we ran it in Lovable, and if not, shows a question mark instead of a guess.
Showing 15 prompts
- Step 1 · Foundation▲ 36
SaaS MVP with User Auth
A multi-tenant SaaS foundation with email auth, a workspace per sign-up, owner, admin and member roles, and tokenized invite links that handle expired tokens.
Run it when: first, in a new project, before any feature that depends on a user.
Measured: 10.4 credits · asked 4 questions firstFull page: builder, run and launch checklistPro version adds the growth-channel instructionsUnlock - Step 1 · Foundation▲ 4
SaaS Teams & Permissions Manager
Team management for an existing multi-tenant app where every role change, removal and ownership transfer re-checks the actor's role in the database and writes a log row.
Run it when: your buyer is a team and the roles have to differ by person.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 2 · Entitlement▲ 1
SaaS Usage Limits & Quotas Manager
Plan-tier limits enforced in each metered server function, failing closed when the counter cannot be read, with usage meters and an 80% warning per feature.
Run it when: before checkout, so the plans sell something the app can tell apart.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 3 · Billing▲ 4
Subscription Checkout Flow
Adds Stripe subscriptions to an existing app, with a signed, idempotent webhook as the only writer of subscription status and a success page that grants no access by itself.
Run it when: entitlements are defined and the app can charge for them.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 3 · Billing▲ 2
Payment History & Billing Pages
A customer billing area that reads invoices from Stripe on every request, shows proration before any plan change, and looks up the customer from the signed-in user.
Run it when: customers need invoices, a card on file and a way to cancel.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - After step 3▲ 1
Promo Code & Discounts Manager
Promo codes validated by one server function for preview and payment, limited to one redemption per account under concurrent checkouts, and re-checked for expiry at payment.
Run it when: checkout works and you want a code that changes the price.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 4 · Lifecycle▲ 2
SaaS User Onboarding Checklist
An onboarding checklist of 3 to 5 steps that tick only when the backend records the matching product event, with dismissal saved across devices.
Run it when: new workspaces stall before the first useful action.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 4 · Lifecycle
SaaS Trial Expiration Flow
A 14-day trial driven by a server-set trial_ends_at: countdown banner, server-refused paid actions after expiry, read-only data and checkout reactivation.
Run it when: trials exist. Trials that never end are the common revenue leak.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - After step 4
SaaS In-App Announcement Banner
Admin-composed in-app banners targeted by plan or behaviour flag on the server, dismissed per user across devices, and removed automatically when expire_at passes.
Run it when: you ship changes users need to hear about inside the app.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Operate▲ 3
Product Feature Toggle Manager
A feature flag system with one server-side evaluation function, fixed precedence from kill switch to percentage, stable hashing on account id, and a logged change history.
Run it when: a feature should reach some workspaces before all of them.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Operate
SaaS Audit Log Viewer
Append-only audit events written by server functions with no update or delete policy for anyone, plus an admin viewer with filters, a detail drawer and CSV export.
Run it when: a customer or an admin asks who changed what.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Operate▲ 4
Product Roadmap Planner
A roadmap board with four stage columns, card order persisted in the database, and a dated public changelog entry each time a card moves to Shipped.
Run it when: customers should see and vote on what is coming.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Signals▲ 5
Lead Scoring System
Rules-based lead scoring where every point traces to a named rule with a timestamp, replayed events never score twice, and reps work a ranked queue.
Run it when: sign-ups outnumber the people who can talk to them.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Signals▲ 1
Customer Churn Predictor
A churn-risk view that scores each account 0 to 100 from weighted named signals, lists the top reasons beside every score, and shows the 10 biggest weekly movers.
Run it when: a month of usage events exists to read.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Signals▲ 1
AI Product Recommendation Engine
Product recommendations with a For you shelf, similar items and a fallback ladder that never shows fewer than 4 items, each card carrying the reason it ranked.
Run it when: there is a catalogue and enough history to recommend from.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock
Building the whole product? The bundle has all 15 as one kit in build order, with every Pro version unlocked, plus 137 more prompts.
See what is in the 152-prompt bundleDisclosure: if you create a Lovable account through links on this page, we may earn a commission. It costs you nothing and does not change what we recommend.
Measured run
We ran the foundation prompt in a fresh project. This is what happened.
▍Context
Build the foundation of a multi-tenant SaaS: users sign up, get a workspace, and invite teammates who arrive in the same workspace with the right role. The target user is a small team adopting a tool together, so the invite must work before anything is polished.
▍Core Features
1. Email and password auth with session persistence across refresh
2. Workspace created automatically on first sign-in, creator becomes owner
3. Member list with three roles: owner, admin, member
4. Invite by email via tokenized link that joins the invitee to the inviter's workspace
▍Access & Session Rules
- Roles are read from the database per request, never from client state
- Protected routes redirect signed-out users to sign-in and return them after
- Sessions persist across refresh and expire gracefully with a re-auth prompt, not a crash
▍Safe-Guard Instructions
- Enforce roles in the database with row-level security as well as in the UI; hiding a button is not access control
- Never accept a role or workspace id from the client on writes
▍Distribution hooks · Pro
Locked. The Pro version adds the growth-channel instructions for this screen.
- 01
Pasted unedited into a fresh project
Build mode, no template, no knowledge file, Marco's own workspace. Default settings.
- 02
Lovable asked 4 questions, one at a time
What the SaaS is for and who the team is; how the first workspace is named; how invites should travel; which of three visual directions fits.
- 03
We answered: a content-planning tool for marketing teams
Three to ten people, workspace name asked at sign-up, copyable invite links only, the first palette. The answers were saved to project knowledge.
- 04
It enabled the backend and built the app
Data and sign-in on the built-in backend, announced before the first table existed.
- 05
It asked permission to test its own invite flow
A throwaway invited teammate signed in through the preview. We allowed it; the join path, the role and the expired link were all checked.
- 06
Balance read: 72.8 to 62.4
10.4 credits for the whole run. Two caveats Lovable raised itself: new accounts confirm by email first, and two test accounts remain in the user list with their data cleared.




Credit math
What 10.4 credits means on your plan
A foundation prompt provisions a backend, auth and a tested invite flow in one message, so it sits at the top of the range we have measured. Lovable bills Build mode on the work done; treat our number as one data point.
| Plan | Daily build credits | One foundation run (10.4) | Unused credits |
|---|---|---|---|
| Free | 5 a day, max 30 a month | Two full days of daily credits plus 0.4 of a third. Two runs this size use 20.8 of the month's 30. | Daily credits do not roll over |
| Pro | 5 a day, plus 100 monthly plan credits from $25 | On a fresh day: 5 from daily, 5.4 from plan credits. In our run the daily 5 were already spent, so all 10.4 came from the plan. | Plan credits roll over, expire after 2 months |
| Business | 5 a day, plus 100 monthly plan credits from $50 | Same split as Pro | Same as Pro |
Lovable's own examples, for scale
- “Make the button gray”
- 0.50
- “Remove the footer”
- 0.90
- “Add authentication”
- 1.20
- Build a landing page with images
- 2.00
Source: Lovable docs, Credits and usage, marked illustrative there. Checked 22 October 2026.
Three ways to spend less
- Run the foundation prompt on a fresh day. Daily credits are spent first. Our run paid all 10.4 from the plan because the day's 5 had gone to another project.
- Answer the 4 questions fully. The answers go into project knowledge, so every later prompt in the category builds on them without restating the roles or the workspace model.
- Decide entitlements before checkout. A checkout built before the plans are defined sells something the app cannot tell apart, and fixing that is a rebuild of two prompts instead of one.
Start here
Which SaaS prompt should you run first?
Pick the sentence that sounds like your project.
Foundation first, then the thing you charge for
- 01SaaS MVP with User Auth · workspace, 3 roles, tokenised invites
- 02SaaS Usage Limits & Quotas Manager · what a plan grants, enforced
- 03Subscription Checkout Flow · the webhook is the source of truth
- 04SaaS Trial Expiration Flow · the trial ends, visibly
Build order
Four steps. Access control before money, money before the lifecycle.
01
Foundation
SaaS MVP with user auth
Protected routes, a workspace and roles read from the database on every request.
02
Entitlement
Usage limits & quotas
Decide what a plan grants before you charge for it.
03
Billing
Checkout · Billing pages
Your Stripe keys as secrets, the webhook as the only writer. Test mode in the preview, live after publishing.
04
Lifecycle
Onboarding · Trial expiry
The first useful action and the day the trial ends.
Anatomy
What each section of a SaaS prompt does
| Section | What it tells Lovable | What you get without it |
|---|---|---|
| Context | Who the team is and what they do together in a workspace | A single-user app with a login bolted on |
| Core features | Auth, workspace, roles, invites, role-gated UI, in that order | Screens before the thing that decides who sees them |
| Access & session rules | Roles read from the database per request, never from the client | A role stored in client state that anyone can edit |
| Screens & states | Inline validation, the member-list skeleton, the empty workspace | The happy path only |
| Build order | Auth and guard, then the role helper, then reads, then invites | Invites that work before the guard exists |
| Safe-guards | Row-level security; hiding a button is not access control | Permissive stubs that pass the preview |
| Before building | Ask questions first, save answers to project knowledge | Guesses about the workspace model |
A one-line prompt gets you
- Login pages with no role model behind them
- A role trusted from the browser
- An invite link that never expires
- Plans the app cannot tell apart
A prompt from this page gets you
- Owner, admin and member, checked in the database
- Tokenised invites with an expiry Lovable tested itself
- Entitlements defined before checkout sells them
- A trial that ends on a date, visibly
Fixes
Where SaaS prompts go wrong, and the line that fixes it
Already built something that works in the preview and will not survive a second user? Paste the fix line into your existing project.
Symptom
Members can see the admin page by typing the URL
Cause: the role lives in client state and the prompt only asked to hide the menu item.
Fix line
Read the role from the database on every request through one server-side helper. Protect the admin routes with it. Do not rely on hiding navigation.
Symptom
The pricing page describes plans the app cannot distinguish
Cause: the pricing page was prompted before entitlements were defined.
Fix line
Define what each plan grants as rows in a plans table, enforce the limits in application code, and make the pricing page read its feature list from those rows.
Symptom
A cancelled subscription still has access
Cause: the checkout only handled the redirect back from the provider, and Lovable's Stripe connector uses no webhooks by default.
Fix line
Write a webhook function for Stripe subscription events, verify the signature, store each event once by its id, and make the webhook the only writer of the subscription status.
Symptom
Trials never end
Cause: a trial_ends_at column exists and nothing reads it.
Fix line
On every request compare trial_ends_at to now. After expiry, block the gated features, show the expired state with one upgrade action, and keep the data readable.
Upvotes
Which SaaS App prompts do builders upvote?
Upvotes since January 2026, one per visitor. SaaS MVP with User Auth is the most upvoted prompt in the whole library and the only one whose Pro version is visible to everyone.
- SaaS MVP with User Auth36
- Lead Scoring System5
- Product Roadmap Planner4
- Subscription Checkout Flow4
- SaaS Teams & Permissions Manager4
- Product Feature Toggle Manager3
The Complete Lovable Bundle
All 15 SaaS prompts in build order, plus every other prompt
Every prompt and kit, every Pro version unlocked. One payment, no subscription.
One payment. No subscription, no renewal, ever.
FAQ
Questions about SaaS App prompts
Can Lovable build a production SaaS?+×
It builds the application layer quickly, and on our run it tested its own sign-up, invite and expired-link paths before reporting done. What it does not do unprompted is enforce entitlements, reconcile billing with the payment provider or end a trial. Those are specified in these prompts because they are where a generated SaaS stops being a product.
Does Lovable have built-in payments?+×
Yes. Lovable's payments docs, read on 22 October 2026, describe built-in Paddle or Stripe for subscriptions and one-time payments on Pro plans and above, with Paddle as merchant of record at 5.0% plus 50 cents per transaction. On any plan you can connect your own Stripe account instead; its key is stored as a secret and the docs say that connector uses no webhooks by default, which is why the checkout prompt here asks for one.
Does Lovable set up row-level security on its own?+×
Partly. The docs say Lovable sets up access rules automatically when it builds features that store user data, and that the policies are read-only in the database view, so a change goes through chat. The docs also warn that server code using the service role bypasses those rules and has to check permissions itself. Every prompt here states the rule it wants, so the generated policy is the one you meant.
Which sign-in methods can a Lovable SaaS offer?+×
Email, phone, Google, Apple, Microsoft and SAML SSO on the built-in backend, per Lovable's authentication docs, plus magic links from the prompt library. The foundation prompt starts with email and password on purpose and adds a provider only after the role model works end to end.
Which of these prompts have been run?+×
One: the foundation prompt, on 26 September 2026, for 10.4 credits with 4 questions asked first. The cards above say which. The SaaS starter kit on the templates page carries the same workspace and role schema with its verification queries executed, which is the proof for the rule pattern the other 14 prompts assume.
Is there a Lovable SaaS template I can clone?+×
These are prompts, which matters more for a SaaS than for a landing page. A template hard-codes a schema and a permission model you then unpick; a prompt generates them to fit the roles and plans you have. Lovable's own SaaS use-case page takes the same route: describe the app, add the backend after the UI walks.
Do I need teams and permissions on day one?+×
Only if your buyer is a team. The foundation prompt already ships owner, admin and member, which is the same three-role model Lovable's prompt library uses for team workspaces. Selling to individuals, defer the teams prompt: a permission model with one role per account adds schema you would migrate later.
What we have not tested yet
- The other 14 prompts in this category. Their cards show a question mark until we run them.
- A checkout run against a Stripe test account, with the webhook received and the subscription status written.
- The built-in Paddle or Stripe path. Priced from the docs on 22 October 2026, not run by us.
- Runs on Bolt, v0 or Base44. Only Lovable runs are ours.
Next run: SaaS Usage Limits & Quotas Manager, the entitlement step the checkout depends on. How we test prompts
Who wrote this
Marco Kohns wrote and ran these prompts. Lovable Prompts is independent and not affiliated with Lovable.
“Try in Lovable” links are affiliate links: we may earn a commission when you create an account through them. The Pro versions and the bundle are our own paid products. Neither decides which prompt we tell you to start with.
Related reading
- backend prompts that enforce roles in the database · The RBAC engine the SaaS prompts assume.
- the SaaS starter kit · Workspaces, roles and RLS, executed and tested.
- the SaaS MVP prompt, annotated and run · Four questions, then a tested invite flow.
- Lovable pricing and credits · Plans read today and what one prompt costs in credits.
- payment webhook and API prompts · Signature-verified, idempotent, reconciled.
- landing page prompts · The capture page that feeds the SaaS.
- Lovable vs Replit · IDE or builder, and what each bills for.
- the app builder guide · The editor, the modes and the Cloud panel.
- the CRM kit · A second tested schema for a SaaS.
- the Lovable prompting guide · Channel first, then the prompt.
- Lovable and Supabase · What Cloud provisioned in the SaaS run.
- app ideas · Fifteen SaaS ideas with the channel each prompt targets.
- SaaS landing page prompt · The marketing page for the SaaS, specified and built.
- SaaS ideas · Fifteen SaaS ideas composed from these prompts, with a billing model each.
- MVP examples, measured · The foundation run as an MVP example, priced.
- build a SaaS · The order to build a SaaS with these prompts, foundation to billing.
- CRM app prompts · A CRM built on the kit's schema, ten briefs with a channel each.
- admin dashboard prompts · The admin side of a product, ten briefs with a channel each.
- Lovable prompt generator · Writes a structured prompt for an idea that matches no library entry.
- the SaaS MVP prompt, with its builder and run · Fill 3 fields, copy, paste; 10.4 credits unedited after 4 questions.
- the bundle · The SaaS prompts with their Pro versions and the SaaS starter kit's SQL.
Other prompt categories
Sources
- Lovable docs: Users and authentication
- Lovable docs: Add payments to your app
- Lovable docs: Stripe connector
- Lovable docs: Database access rules
- Lovable docs: Security best practices
- Lovable docs: SaaS use case
- Lovable docs: Prompt library (roles, team workspaces)
- Lovable docs: Credits and usage
All read on 22 Oct 2026.