15 SaaS ideas you can build in Lovable, with who pays and how
An app becomes a SaaS when someone pays for it again every month, so each idea here names who pays and the billing model that follows: per seat, flat monthly or by usage. Each one is a product prompt from the library plus the prompts that make it chargeable (sign-in with roles, checkout, limits, trials). Filter by billing model; validate with a landing page first, which cost me 1.8 credits, before paying 10.4 for a foundation.
By Marco Kohns · Upvotes read live from the site's database; Stripe rates read 23 October 2026
5per seat
Teams pay for each person using it.
5flat monthly
One price for the account, whatever the size.
5usage-based
Pay by forms, responses, quizzes or resources.
The ideas
Which SaaS ideas can you build with Lovable?
Each card: the product prompt, who pays, and the prompts to add before you charge.
- Flat monthlyProduct-led Growth
CRM Lite with Contact Management
A lightweight CRM for 2 to 10 reps where email is the duplicate key with a Merge flow, and Today lists overdue follow-ups first every morning.
Who pays: A founder doing their own sales pays to stop losing follow-ups.
The product prompt →To charge for it, add:
- Per seatProduct-led Growth▲ 6
Customer Support Ticketing Tool
A ticketing tool for 2 to 15 agents where web forms and forwarded email become owned tickets, and internal notes sit in a table requesters can never read.
Who pays: A small team pays per agent seat to answer from one queue.
The product prompt →To charge for it, add:
- Usage-basedProduct-led Growth
Survey Builder + Results Display
A survey tool with five question types, one question per screen on a phone, resumable answers, and per-question drop-off counts that show where respondents quit.
Who pays: A researcher or marketer pays per active survey or response volume.
The product prompt →To charge for it, add:
- Flat monthlyProduct-led Growth▲ 2
Booking System (Date + Confirm)
A booking system for a solo service business where a unique constraint on service and start time makes double-booking impossible, and manage links honour the notice rules.
Who pays: A service business pays a flat fee to stop double bookings.
The product prompt →To charge for it, add:
- Per seatProduct-led Growth▲ 1
Kanban Board for Workflow Tracking
A kanban board where moves run through one backend function that checks WIP limits and entry rules, and every transition is recorded for cycle time and aging.
Who pays: A team pays per seat for a board that models its own workflow.
The product prompt →To charge for it, add:
- Flat monthlyNot tied to one channel
Knowledge Base / Help Center
A public help center where every article has an owner and review date, search logs zero-result queries, and a health view lists stale, unhelpful and orphaned articles.
Who pays: A product team pays a flat fee to deflect support email.
The product prompt →To charge for it, add:
- Usage-basedProduct-led Growth▲ 1
Form Builder with Conditional Logic
A form builder with one-level show-when rules, a live Debug preview, and submissions stored with the form version and the fields visible at submit time.
Who pays: Anyone collecting structured input pays by forms or submissions.
The product prompt →To charge for it, add:
- Usage-basedProduct-led Growth▲ 1
Resource Booking Manager
A booking manager for rooms, equipment and desks where a database exclusion constraint on resource and time range blocks conflicts, with per-resource rules and weekly utilization.
Who pays: An office or workshop pays per resource managed.
The product prompt →To charge for it, add:
- Per seatNot tied to one channel
Employee Directory App
An employee directory with sign-in limited to the company email domain, search by expertise tags, and a now-working-on line that expires each quarter and asks for a refresh.
Who pays: An HR lead pays per seat for a directory that stays current.
The product prompt →To charge for it, add:
- Per seatNot tied to one channel
Internal Tool Dashboard Builder
An internal dashboard builder where teams compose widgets from code-reviewed named queries with bounded parameters, and the browser sends only a source name and parameters.
Who pays: An ops lead pays per seat for dashboards without a BI contract.
The product prompt →To charge for it, add:
- Flat monthlyNot tied to one channel▲ 1
Appointment Availability Scheduler
An appointment scheduler that resolves slots from weekly rules and exceptions at request time, books in a transaction that re-checks the slot, and shows invitees their own timezone.
Who pays: A consultant pays a flat fee to replace the back-and-forth.
The product prompt →To charge for it, add:
- Usage-basedProduct-led Growth
Simple Quiz Builder
A quiz builder for scored and outcome quizzes where publishing is blocked until score bands cover the range without gaps, and answer weights stay server-side until submission.
Who pays: A course creator pays by quizzes or takers.
The product prompt →To charge for it, add:
- Flat monthlyCommunity-led Growth
Member Directory with Search
A members-only directory where each profile field has a visibility toggle, search reads only member-visible fields, and contact details stay hidden until a request is accepted.
Who pays: A community pays a flat fee for discovery without exposure.
The product prompt →To charge for it, add:
- Usage-basedProduct-led Growth▲ 1
AI Email Template Builder
An AI email template builder that fills a fixed table-based skeleton from a one-line brief, keeps the footer locked, and blocks export when a merge field is unknown.
Who pays: A marketer pays by templates generated.
The product prompt →To charge for it, add:
- Per seatProduct-led Growth▲ 8
Internal Prompt Library Browser
An internal prompt library where each prompt declares its variables, Copy fills them through a form, and row-level security keeps every workspace's prompts invisible to outsiders.
Who pays: A team running on AI tools pays per seat to share prompts with versions.
The product prompt →To charge for it, add:
The difference
What turns an app idea into a SaaS idea?
Three things the app does not need and the SaaS does: accounts with roles, a way to take money, and a limit the price is attached to.
- 0110.4 credits
Accounts and roles
Workspaces and who can do what, checked in the database. The SaaS MVP prompt. - 02Billing
A way to pay
Lovable's built-in payments on Pro, or your own Stripe account on any plan. Both paths. - 03Per seat, flat or usage
A limit to price
Seats, forms, responses, resources: whatever the price counts is enforced on the server.
| Payment | Fee | Rate |
|---|---|---|
| Stripe, US card, $29 | $1.14 | 2.9% + 30¢ |
| Stripe, international card, $29 | $1.58 | 4.4% + 30¢ |
| Stripe, international + FX, $29 | $1.87 | 5.4% + 30¢ |
| Paddle via Lovable, $29 | $1.95 | 5.0% + 50¢ |
| Stripe, US card, $9 | $0.56 | 2.9% + 30¢ |
| Paddle via Lovable, $9 | $0.90 | flat 10% under $10 |
Measured demand
Which of these SaaS ideas did builders upvote?
Upvotes on the product prompt, read from the site's database at build time. One library's readers; the only demand signal here that was counted.
| Idea | Upvotes |
|---|---|
| Internal Prompt Library Browser | 8 |
| Customer Support Ticketing Tool | 6 |
| Booking System (Date + Confirm) | 2 |
| Kanban Board for Workflow Tracking | 1 |
| Form Builder with Conditional Logic | 1 |
| Resource Booking Manager | 1 |
Before billing
How do you validate a SaaS idea before building billing?
Sell it before you build it: a page, a price and a count of people who said yes.
- 011.8 credits
Landing page with the price
One promise, one form. The email opt-in prompt. - 020 credits
One channel for a week
Send people from where they already are; count sign-ups against visitors. - 034.5 credits
The SaaS landing page
Six sections, the price stated. The SaaS landing page prompt. - 0410.4+
Foundation, then billing
Only once people ask to pay.
Pick the product prompt
Disclosure: 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. Create a free Lovable account
Frequently asked
What makes a good SaaS idea?
Someone who pays again every month for a job that happens weekly, a limit the price can attach to (seats, usage or a flat account), and one channel where those buyers already gather. Every idea on this page names who pays and how.
Can I build a SaaS with Lovable?
Yes: the product prompt, then a foundation with accounts and roles (10.4 credits on my run), then checkout, limits and trials. Lovable's built-in payments need a Pro plan; your own Stripe account works on any plan.
Should I charge per seat, flat or by usage?
Per seat when value grows with each person using it, flat when one buyer pays for an account of any size, usage when value tracks volume such as responses or forms. The limit behind the price is enforced on the server.
How do I validate a SaaS idea before building it?
Put the promise and the price on a landing page, send one channel's people to it for a week, and count sign-ups against visitors. A landing page cost me 1.8 credits; build the foundation once people ask to pay.
What does Stripe charge on a SaaS subscription?
On 23 October 2026 Stripe's US rate was 2.9% + 30¢ per domestic card payment, plus 1.5% for international cards and 1% with currency conversion, and Billing adds 0.7% on pay as you go. Lovable adds nothing.
What we did not publish
- Market sizes or revenue estimates for the ideas.
- A run of each idea's full stack; the foundation and landing page runs are measured, the rest are not.
- Which ideas sold; I have not sold any of them.
Sources
- The prompt library and the site's upvote table, read at build time
- My runs: landing page 2026-07-31, SaaS foundation 2026-09-26, SaaS landing page 26 September 2026
- Stripe US pricing and Lovable payments docs, read 23 October 2026
- Page checked 23 October 2026
Written by
Marco Kohns
Founder of ProtoBites - Venture Growth Studio
Growth PM at a Silicon Valley scale-up (a16z and General Catalyst backed), ex-Techstars where he consulted 13 early-stage startups, Reforge-trained. Every prompt on this site comes out of shipping ProtoBites' own portfolio products.
Related reading
- Lovable SaaS prompts · The fifteen mechanics prompts.
- whole-app prompts with a build order · The product prompts behind the ideas.
- the SaaS starter kit · The foundation as a schema with proof.
- app ideas · Fifty ideas by channel, the wider list.
- SaaS landing page prompt · The validation page, run for 4.5 credits.
- first 100 users · Working one channel.
- Lovable and Supabase · Where the tenancy policies live.
- three prompts and what they built · The foundation run, with screenshots.
- how to build an MVP · One SaaS from foundation to landing page, credits counted.
- build a SaaS · How any of these gets built, foundation to billing.
- CRM app prompts · The CRM idea as ten briefs on the kit's schema.
- admin dashboard prompts · The dashboard idea as ten briefs with data rules first.
- Lovable prompt generator · Writes a structured prompt for an idea that matches no library entry.
- the SaaS MVP prompt page · The foundation every SaaS idea here starts from.