Build a custom CRM from a prompt: 12 examples by industry

12 ready-to-use prompts, from a quick one-liner to a detailed brief. Copy one into any AI app builder, or click once and Gappsy builds it for you.

What makes a good crm prompt

A CRM prompt works best when it describes how you actually sell. Name what you track (people, companies, deals, jobs or properties), the fields you care about for each, and the stages a deal moves through from first contact to won or lost. Your own stage names, like "site visit booked" or "quote sent", give you a pipeline board that matches your day instead of a generic sales template.

Then describe the follow-up habits you want the CRM to enforce. Who owns each contact, when a reminder should fire, which emails or calls get logged, and what a manager wants to see on Monday morning. If several people use it, say what each role can see and edit. Mention imports too: a spreadsheet of 800 existing contacts is worth stating so the builder adds a CSV import.

CRM prompts, simple to advanced

  1. Freelance designer client list

    I'm a freelance designer and want a simple CRM for my clients. Each contact has a name, company, email, how they found me and notes. I want a list I can search and a follow-up date that shows overdue people in red at the top. Clean, minimal white design.

    Why it works: A follow-up date with overdue people shown first is the one habit a solo freelancer needs, so the build stays small and useful.

    Build this for free with Gappsy

  2. Wedding photographer inquiry pipeline

    I'm a wedding photographer. I want a pipeline board with stages: inquiry, call booked, proposal sent, contract signed, and lost. Each card shows the couple's names, wedding date, venue and package price. I drag cards between stages. Show total booked revenue for each wedding season at the top.

    Why it works: Your own stage names and the fields on each card make the board read like your booking process rather than a generic sales funnel.

    Build this for free with Gappsy

  3. Real estate agent buyer tracker

    I'm a real estate agent in Phoenix. I need a CRM for buyers with budget, preferred neighborhoods, bedrooms, pre-approval status and timeline. I log every showing against a buyer with the property address and their feedback. When a new listing matches a buyer's budget and area, I want it flagged on their profile.

    Why it works: Matching buyers to listings by budget and area is a specific rule the builder can implement, which turns a contact list into a working tool.

    Build this for free with Gappsy

  4. Roofing company lead tracker

    We run a roofing company with three estimators. Leads come in from our website form and phone calls. Each lead has an address, roof type, photos and a stage: new, inspection booked, estimate sent, won or lost. Assign each lead to an estimator, and send them a text when a new lead is assigned. Mobile-first, because estimators use it on site.

    Why it works: Saying estimators use it on site pushes the builder toward a phone-friendly layout with photo uploads front and center.

    Build this for free with Gappsy

  5. Recruitment agency candidate CRM

    I run a small recruitment agency for nurses. I need two linked lists: candidates with their specialty, license expiry date and availability, and hospital clients with open roles. I move candidates through stages per role: submitted, interview, offer, placed. Warn me 60 days before any candidate's license expires.

    Why it works: Two linked lists plus stages per role show the builder that one candidate can sit in several pipelines at once.

    Build this for free with Gappsy

  6. Nonprofit donor relationships

    We are a small animal shelter and want a donor CRM. Each donor has their giving history, total given this year, preferred contact method and notes from conversations. Tag donors as monthly, major or lapsed. I want a list of anyone who gave last year but not this year, so our team can call them before December.

    Why it works: A lapsed-donor list with a clear deadline gives the builder a saved view to build, not just a database of names.

    Build this for free with Gappsy

  7. B2B software sales pipeline

    We sell scheduling software to dental clinics. I want companies, contacts linked to each company, and deals with value, expected close date and stage: demo booked, trial, proposal, negotiation, won, lost. Each rep sees their own deals, managers see everyone's. A dashboard shows pipeline value by stage and deals closing this month. Navy and white, business-like.

    Why it works: Linking contacts to companies and deals to both is the structure B2B sales needs, and naming it avoids a flat contact list.

    Build this for free with Gappsy

  8. Interior design project CRM

    I'm an interior designer. Each client has a project with rooms, budget, style notes and a mood board of uploaded images. I track the stage from consultation through design, ordering and install. Log every email or call with a date. Send me a reminder if a project has had no activity for 10 days. Soft beige and terracotta design.

    Why it works: The 10-day no-activity reminder gives the builder an exact rule for stale projects, so follow-ups do not slip.

    Build this for free with Gappsy

  9. Insurance agent renewals CRM

    I'm an independent insurance agent. Each client has policies with carrier, type, premium and renewal date. I want a renewals view showing everything renewing in the next 45 days, a task list of calls to make, and a note log per client. Let me import my 1,200 existing clients from a spreadsheet with CSV upload.

    Why it works: Mentioning the 1,200-row spreadsheet makes the builder include a CSV import with column matching from day one.

    Build this for free with Gappsy

  10. Agency CRM with email logging

    We are a marketing agency with eight account managers. I want contacts, companies and deals, plus a timeline on each contact that shows every note, call and email. Account managers can paste an email thread into the timeline. When a deal is won, create a client record and a kickoff task for the delivery lead automatically.

    Why it works: Turning a won deal into a client record and a task describes an automation the builder can wire up between two parts of the app.

    Build this for free with Gappsy

  11. Car dealership sales floor CRM

    We run a used car dealership and our sales floor has 12 salespeople. Each lead has the car they asked about, trade-in details, finance status and the salesperson. Leads not contacted within 2 hours get reassigned to the next available person in rotation. The sales manager sees a leaderboard of calls, test drives and sales this month. Store each customer's consent to text.

    Why it works: A 2-hour reassignment rule and round-robin rotation are edge cases that decide whether a busy sales floor actually trusts the CRM.

    Build this for free with Gappsy

  12. Wholesale distributor account CRM

    We distribute specialty coffee and our customers are 300 cafes. Each account has locations, buyers, order frequency and average order size. Reps see accounts that have not ordered in 3 weeks as at-risk. Roles: reps edit their own accounts, managers edit all, finance views only. Weekly email to each rep listing at-risk accounts. Export any filtered list to CSV.

    Why it works: An at-risk rule based on order gaps, plus three clear roles, gives the builder enough to build a retention-focused CRM, not just a sales one.

    Build this for free with Gappsy

Say what you want. Gappsy builds it.

Any design, any feature you can describe. Change anything after by typing. Free to start, no credit card. Describe yours and build it for free.

How to adapt these prompts

  1. Use your real pipeline stage names: Write the stages your deals actually go through, in order, including how they end. "Quote sent" and "site visit booked" make a CRM pipeline board you will use, while "stage 1, stage 2" leaves you renaming columns later.
  2. List the fields that drive decisions: Only name the contact and deal fields you filter or sort by: renewal date, budget, license expiry, territory. Your CRM can always store extra notes, but the fields you mention become the columns, filters and reminders the builder puts first.
  3. Describe follow-up rules in numbers: "Remind me to follow up" is vague. "Flag any lead with no contact in 5 days" or "show renewals due in the next 30 days" gives the CRM a precise rule and a view you can open every morning.
  4. Say who sees whose contacts: In a team CRM, decide whether reps see only their own leads, whether managers see everything, and who can delete or reassign a record. Put these roles in the prompt so the builder sets permissions before your team starts entering contacts.

CRM prompts: questions, answered

Do these CRM prompts work with Lovable, Bolt.new or other AI builders?

Yes. They describe contacts, pipeline stages and follow-up rules in everyday language, so any AI app builder, including Lovable and Bolt.new, can turn them into a working CRM. Swap in your own stages and fields. If you would rather skip the copy and paste, the "Build this for free with Gappsy" button builds the CRM from that exact prompt, free to start, no credit card required to see your pipeline.

Can I import my existing contacts into a custom CRM?

Ask for it in the prompt by mentioning a CSV or spreadsheet import and roughly how many contacts you have. The builder adds an upload screen that maps your spreadsheet columns to CRM fields. Clean up obvious duplicates in the spreadsheet first, since that is easier than merging records after the import.

Why build my own CRM instead of adapting a template?

A CRM you describe yourself starts with your stages, fields and reminders, so there is less to switch off and rename. It works well for businesses with an unusual sales process, like a nurse recruiter or a roofer with site visits. You can keep adding features later by describing them, the same way you described the first version.

Can my CRM send emails or text reminders?

Yes, if you describe them. Say who gets the reminder, what triggers it and when, for example a text to the assigned estimator when a new lead arrives, or a weekly email listing overdue follow-ups. Ask for one reminder at a time and test it with your own phone or inbox before your sales team relies on it.

How should I roll out a new CRM to my sales team?

Build it, add a test login for each role and try it with five or ten real contacts first. Then ask for the changes your sales team notices, such as a missing field or a confusing stage name. Once the pipeline feels right, import the rest of your contacts and agree as a team that new leads only go into the CRM.

More prompts

Start from a ready-made app

How Gappsy compares