CRM App Prompts for Lovable: 10 Briefs on a Tested Schema
Prompt builder · four steps · no account
Step 1 of 4
Which one is closest?
Building something else? Describe it to the AI generator
A CRM asked for in one sentence is a contacts table with a login and no rule about who may change what; the day a second person joins, records get overwritten. These 10 briefs are written to a schema that already exists and was proven: shared reads, owner-only writes, a with-check clause that stops a member from stealing a record. This page shows the schema, the daily loop the briefs build, and what the first run will record.
By Marco Kohns · Prompts written and run by us
Short answers
Short answers
Where do I start?
Run the Lightweight CRM kit's schema and verification queries first, then the contacts and companies brief. Nothing else works without those tables.
Pick by situation →What does a run cost?
? credits
Not measured for a CRM brief yet. The closest measured run, the SaaS foundation that built roles checked in the database, cost 10.4 credits; a brief on an existing schema should cost less because the tables already exist.
See what we do know →Shared or private CRM?
Shared by default: every signed-in team member reads every record, only the owner writes. For per-person isolation, change the select policies to owner_id = auth.uid() before running anything else and re-run the verification queries.
The kit's model →My CRM already exists
Then check whether the client sends owner_id and whether notes can be edited. Both are the common failures, and the fix lines below correct them without a rebuild.
Fix lines for live apps →10
CRM App prompts in this category
↳ Copy-paste, free
0of 10
Prompts from this category run in Lovable
↳ Next run: Contacts and Companies with Dedupe
3runs
Measured so far across the library
↳ 1.8 to 10.4 credits each
0
Upvotes since Jan 2026
↳ One per visitor, self-reported
Data basis: no brief run on a CRM project yet; every card says so. The policy claims come from the Lightweight CRM kit, whose six verification queries were executed, two of them as a second user. Credit figures from the three measured runs elsewhere in the library. Docs and the Lovable use-case page checked 22 October 2026.
Find a prompt
Which part of the CRM 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 10 prompts
- Step 1 · Foundation
Contacts and Companies with Dedupe
The contacts and companies layer of a lightweight CRM, where a matching email or company name shows before saving and owner_id comes from the database default.
Run it when: first, on the kit's schema, before any other brief.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 1 · Foundation
Pipeline Board with Stages You Define
A deal pipeline board where one server function owns every stage change and appends a stage_history row, with amber and red badges for stuck deals.
Run it when: contacts exist and deals need stages you define, with a history row per move.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 2 · Daily loop
Activity Timeline That Takes Seconds to Write
An append-only activity timeline on the CRM's notes table, with a composer that saves on Enter and a company feed that merges every contact's notes.
Run it when: people should log a call in seconds, or they will not log it.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 2 · Daily loop
Follow-Up Reminders and a Morning Digest
Dated follow-ups on contacts and deals with a Today view, inline snooze, a Gone quiet list after 14 silent days, and a daily digest email.
Run it when: deals go quiet because nobody owns the next step.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 3 · Inputs
Public Lead Form Writing Into the CRM
A public lead form that writes into the CRM's leads table insert-only, captures UTMs on the server, and queues each lead for a member to accept or discard.
Run it when: the marketing site should feed the pipeline without copy-paste.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 3 · Inputs
CSV Import with Mapping and Dedupe Preview
A CSV import for CRM contacts and companies that marks every row Create, Match existing or Skip before writing, and undoes a batch while no record has notes.
Run it when: an old spreadsheet has to come in without duplicates and with an undo.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 4 · Team
Team Roles and Reassignment
Owner, admin and member roles for the CRM, with admin-only reassignment that requires a reason and records from, to, by and why on every record.
Run it when: a second person joins and records change hands.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 5 · History
Pipeline Reports from Stage History
CRM reports computed by database views over stage history, deals, notes and follow-ups, where every chart has a table view from the same query.
Run it when: a month of stage history exists and a partner asks for a funnel.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 5 · History
Stage Playbooks: Tasks Created on Entry
Stage playbooks that create a deal's tasks inside the stage-change transaction and record a reason whenever a deal moves forward with required tasks open.
Run it when: every deal should be worked the same way at each stage.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock - Step 5 · History
Win-Loss Reasons and a Quarterly Review Page
Closing a deal requires a reason enforced in the stage-change function, and a quarterly page groups closed deals by reason and lost-to competitor with a copyable summary.
Run it when: a quarter of closed deals exists to learn from.
Not run yet · credits ?Pro version adds the growth-channel instructionsUnlock
Building the whole CRM? The bundle has all 10 as one kit in build order, with every Pro version unlocked, plus 142 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
No CRM brief has been run yet. This is what the first run will record.
▍Context
Build the contacts and companies layer of a lightweight CRM for a founder or a team of up to ten doing their own sales. The app's backend already has companies, contacts and notes tables with row-level security from the Lightweight CRM kit; do not recreate them. The one job: adding a contact takes ten seconds and never creates a duplicate.
▍Data Rules
▍Core Features
1. Add contact: name, email, company (typeahead over existing companies, create on the fly) and one optional note, saved with Enter
2. Dedupe on entry: an existing email or a near-identical company name shows the match with Open, and Create anyway as a secondary action
3. Contact page: details, company link, note timeline, owner, last touched
4. Company page: its contacts, open deals count and the combined note timeline
5. Search across names, emails and company names using the kit's full-text index, opened with Cmd+K
▍Safe-Guard Instructions
- Never include owner_id in an insert or update payload from the client
- Do not weaken a policy to make a query work; if a write is denied, fix the write
▍Distribution hooks · Pro
Locked. The Pro version adds the growth-channel instructions for this screen.
- 01
A fresh project in Marco's own workspace, backend enabled
Balance read and screenshotted first. The kit's schema.sql run in the SQL editor, then verify.sql as user A and as user B, expecting the two theft queries to fail.
- 02
The brief pasted unedited, in Build mode
Its Context line says the tables exist and must not be recreated. Its Before Building line should make Lovable ask about the team size and the sales motion.
- 03
Every question recorded, with the answer given
On the SaaS foundation run the same closing line produced 4 questions and a self-tested invite flow. The count goes on the card.
- 04
The rule pattern checked, never assumed
The foundation run reported roles checked in the database on every read and write. The CRM run repeats that check as a second user against contacts, which is what the kit's queries 3 and 4 do.
- 05
Rounds counted until the Core Features list is met, or 5
Each follow-up verbatim: a recreated table, a policy weakened to pass a query, a dedupe that merged silently.
- 06
Balance read again
Credits before minus after, to one decimal, daily credits counted first. Then the row goes into the runs file this page reads.
Credit math
What a CRM brief is likely to cost, from the runs we have
No figure for a CRM brief yet. The nearest measured run provisioned a backend and roles for 10.4 credits; a brief that builds on tables the kit already created does less work, and Lovable bills Build mode on the work done.
| Plan | Daily build credits | The nearest measured run (10.4) | Unused credits |
|---|---|---|---|
| Free | 5 a day, max 30 a month | Two days of daily credits plus 0.4 of a third, if a brief costs what the foundation did. Running the kit's SQL in the editor costs no build credits. | Daily credits do not roll over |
| Pro | 5 a day, plus 100 monthly plan credits from $25 | 5 from the day's credits, the rest from plan credits, on a fresh day | 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
- “Add authentication”
- 1.20
- Build a landing page with images
- 2.00
- A Plan mode message
- 1.00 plus research
- Running schema.sql in the SQL editor
- 0.00
Source: Lovable docs, Credits and usage (illustrative) and Plan mode; the SQL editor is under More > Database > Manage. Checked 22 October 2026.
Three ways to spend less
- Run the kit's SQL yourself. The schema and the verification queries go into the SQL editor, which costs no build credits. The brief then starts from tables that exist and policies that were proven.
- Tell Lovable not to recreate the tables. Every brief's Context line says so. Without it, the model builds a second contacts table and the policies you verified protect nothing.
- Answer the questions about the team. Team size and sales motion decide the schema extensions. An answer costs nothing; a guess costs a second build message.
Start here
Which CRM brief should you run first?
Pick the sentence that sounds like your project.
A working CRM for one person, in four briefs
- 01Contacts and Companies with Dedupe · dedupe at entry, ownership from the database
- 02Pipeline Board with Stages You Define · one function writes stage, nothing else
- 03Activity Timeline That Takes Seconds to Write · Enter to save, last touched derived
- 04Follow-Up Reminders and a Morning Digest · a today view and a digest
Build order
Five briefs deep. Foundation, loop, inputs, team, history.
01
Foundation
Contacts · Pipeline
On the kit's schema. Dedupe at entry, stage changes through one function with a history row.
02
Daily loop
Timeline · Follow-ups
The append-only timeline and the today view. The reason anyone logs a call.
03
Inputs
Lead form · CSV import
Insert-only from outside, one undo batch per import.
04
Team and history
Roles · Reports · Win-loss
Reassignment through a function; reports from views once history exists.
Anatomy
What each section of a CRM brief does
| Section | What it tells Lovable | What you get without it |
|---|---|---|
| Context | Who sells, the speed rule, and that the kit's tables exist and must not be recreated | A second contacts table with no policies |
| Data rules | Ownership from the database default, shared reads, owner-only writes, one company per contact | owner_id in the insert payload, so anyone creates records as anyone |
| Core features | Read paths before the add form, the add form before edit and delete | An edit screen on records that cannot yet be listed |
| Screens & states | The first-visit empty state, the dedupe match state, a save failure that keeps typed values | A blank page and a silent duplicate |
| Safe-guards | No policy weakened to pass a query; dedupe never merges silently | A select policy loosened because a page showed nothing |
| Before building | Ask about team size and sales motion, save the answers | A schema extended for a team you do not have |
A one-sentence CRM prompt gets you
- A contacts table with a login and no ownership rule
- Notes that can be rewritten
- Reports computed in the browser from one page of rows
- A duplicate for every re-entered lead
A brief from this page gets you
- Ownership the client cannot set
- An append-only timeline
- A funnel from a view anyone can re-run
- A dedupe decision shown to the person, never made for them
Fixes
Where CRM prompts go wrong, and the line that fixes it
Already built a CRM that works for one person? Paste the fix line into your existing project.
Symptom
Anyone can create records as anyone
Cause: owner_id arrives in the insert payload from the client.
Fix line
Set owner_id to default to auth.uid() in the database and remove it from every insert the client sends. Add a with-check clause to the update policies so owner_id cannot be changed by a member. Show me a query as a second user that is refused.
Symptom
A note was edited and the history is gone
Cause: the notes table has an update policy, so the timeline is a document, not a record.
Fix line
Remove update and delete policies from notes. Corrections are new notes that reference the old one. The timeline renders both, newest first.
Symptom
The second person overwrote the first person's deals
Cause: a shared CRM was prompted with no rule about who writes.
Fix line
Every signed-in team member reads every company, contact and deal. Only the owner updates or deletes their own. Reassignment happens only through an admin function that writes a history row with who, what and when.
Symptom
The funnel changes every time it is opened
Cause: reports are computed in the browser from whatever page of rows was loaded.
Fix line
Create a database view for the pipeline funnel with a date range parameter, computed from stage_history. The reports page reads only from that view and shows the range it used.
The Complete Lovable Bundle
All 10 CRM briefs 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 CRM App prompts
Do I need the CRM kit to use these prompts?+×
The briefs assume its three tables and policies, so yes for the first one: run schema.sql and verify.sql from the Lightweight CRM kit in the SQL editor under More > Database > Manage before pasting the contacts brief. The prompt is free; the schema and verification files ship in full with the bundle. Without the kit, tell Lovable to create the same three tables with the same rules, and run the verification queries yourself before building further.
Does Lovable build CRMs on its own?+×
It has a CRM use-case page and a two-part video on building one, and its prompt library has an entry for CSV import and export on a contacts table. None of them states an ownership rule, which is where a generated CRM fails the day a second person joins. The docs do say Lovable sets up access rules automatically when a feature stores user data; the briefs state the rule so the generated policy is the one you meant.
Is this a shared or a private CRM?+×
Shared by default: every signed-in team member reads every record, and only the owner writes. That is the kit's choice because a sales team that cannot see each other's pipeline is not useful. For per-user isolation, change the select policies to owner_id = auth.uid() before running anything else and re-run the verification queries.
Which of these prompts have been run?+×
None of the 10 on a CRM project yet. The rule pattern they encode was run: the SaaS foundation prompt built roles checked in the database for 10.4 credits, and the kit's schema executes with its six verification queries passing, two of them as a second user. The first CRM run gets the same ledger as every other run on this site.
Can the digest and welcome emails send on the free plan?+×
Not per Lovable's prompt library page: app emails need a paid plan and a verified email domain. The follow-up and lead form briefs say so and deliver the digest as a page until both exist, so the first build does not fail silently.
Why do eight of ten briefs target B2B sales?+×
Because a CRM's users are the sales channel. The Pro variants add the mechanisms a founder selling by outreach needs: a LinkedIn paste path, shareable pipeline summaries, follow-up sequences, a team activity page. The two others serve email marketing and organic search, where the lead form and the digest live.
How does this differ from the SaaS prompts?+×
The SaaS category is the machinery for charging strangers: workspaces, checkout, limits, trials. This category is one product. A CRM sold as a SaaS runs the SaaS foundation first and these ten inside a workspace; a founder's own CRM runs the kit and these ten and never needs billing.
What we have not tested yet
- All 10 briefs in this category. Their cards show a question mark until we run them.
- The kit's schema created by Lovable from the brief alone, against the kit's SQL, queried as a second user.
- The CRM Lite one-prompt version on the app builder page against the first two briefs here, with credits compared.
- Lovable's own CRM video prompt, for what it produces without data rules.
Next run: Contacts and Companies with Dedupe, on the kit's schema. How we test prompts
Who wrote this
Marco Kohns wrote these briefs and the kit, and ran the foundation prompt they build on. 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
- CRM kit · The schema, policies and verification queries the briefs assume.
- Lovable SaaS prompts · The machinery for selling the CRM as a product.
- whole-app prompts with a build order · CRM Lite, the one-prompt version.
- landing page prompts by traffic source · The page the lead form belongs on.
- Lovable and Supabase · The with-check clause the kit relies on.
- Lovable security · What the scans prove and what only a query does.
- SaaS ideas · The CRM as a chargeable product.
- build a SaaS · Foundation, schema, proof, billing.
- first 100 users · The outreach channel eight of ten briefs serve.
- free build kits with tested RLS · The four kits, counted.
- admin dashboard prompts · The sibling category: roles, an audit log, and view-as-user.