u/willkode

Here is todays free prompt drop. This time its entire CRM system. Whether you want it to be an internal tool or a SaaS multi-tenant (if so edit the prompt to say that).

Let me know in the comments what my next prompt drop should be. Also I wanted to see if there was any interest in a service where I build complete app foundations, the entire system no UI designing (I'll leave that to you), it will come with a basic design. - Thinking of charging $250-$500 for that. beats paying a partner thousands. LMK.......

THE PROMPT!

Build a complete, production-ready CRM system inside this app.

Before making changes, scan the full app and understand the current structure, routes, layouts, data entities, backend functions, permissions, and existing design system. Then implement this CRM in a clean, modular, scalable way that matches the current app styling unless a dedicated CRM design system is needed.

This is not a simple contact manager. This must be a full CRM platform with role-based access, sales workflows, account management, billing visibility, communication history, reporting, integrations, and admin controls.

==================================================
CORE PRODUCT GOAL
==================================================

Create a complete CRM system for businesses to manage:
- leads
- contacts
- companies/accounts
- deals/opportunities
- tasks
- notes
- activities/timeline
- meetings
- quotes/proposals
- products/services
- invoices and subscriptions
- communication logs
- team management
- reporting
- automations
- integrations

The system must support both internal team workflows and optional customer portal visibility later.

==================================================
ROLES AND PERMISSIONS
==================================================

Create a role-based access control system with at minimum these roles:
- Owner
- Super Admin
- Admin
- Sales Manager
- Sales Rep
- Support Manager
- Support Staff
- Finance Manager
- Marketing Manager
- Viewer / Read Only

Each role must have permission-based access to modules and actions.

Permission model should support actions like:
- view_all
- view_assigned
- view_team
- create
- edit
- delete
- assign
- import
- export
- manage_settings

Permission-controlled modules:
- dashboard
- leads
- contacts
- companies
- deals
- tasks
- activities
- notes
- meetings
- quotes
- products
- invoices
- subscriptions
- reports
- integrations
- automations
- notifications
- users
- roles
- settings
- audit_logs
- custom_fields
- import_export

Protect all routes, UI actions, and backend actions based on role permissions.

==================================================
MAIN APP SECTIONS
==================================================

Create these main sections/pages in the app:

Authentication / entry:
- sign in
- register
- forgot password
- reset password
- invite acceptance
- optional onboarding wizard

Core CRM:
- dashboard
- leads list
- lead detail
- contacts list
- contact detail
- companies list
- company detail
- deals board
- deals list
- deal detail
- tasks list
- meetings/calendar
- activity timeline
- notes
- quotes/proposals
- products/services
- invoices
- subscriptions
- reports

Admin and system:
- team/users
- roles and permissions
- pipelines
- stage settings
- tags manager
- custom fields manager
- automations
- integrations
- sync logs
- notifications
- import/export
- audit logs
- system settings

Use a clean CRM layout with:
- left navigation
- top bar
- dashboard cards
- data tables
- detail pages with tabs
- board view for deals
- modals or drawers for quick add/edit
- filters and saved views

==================================================
DASHBOARDS
==================================================

Create dashboards for different roles where relevant.

Executive dashboard should show:
- total leads
- new leads
- open deals
- won deals
- lost deals
- revenue forecast
- overdue tasks
- upcoming follow-ups
- active subscriptions
- failed payments
- lead source performance
- team activity summary

Sales dashboard should show:
- assigned leads
- deals by stage
- follow-ups due
- tasks due
- recent activity
- close forecast

Support dashboard should show:
- accounts needing follow-up
- recent communication
- overdue client tasks
- billing issue alerts
- account health alerts

Finance dashboard should show:
- active subscriptions
- renewals
- overdue invoices
- failed charges
- payment issues
- revenue summaries

Marketing dashboard should show:
- leads by source
- source conversion
- campaign performance tags
- funnel snapshots

==================================================
DATA MODELS
==================================================

Create robust data models and relationships for the following entities.

Users:
- full_name
- email
- phone
- avatar
- role
- team
- status
- last_login

Roles:
- name
- description
- permissions_json
- is_system_role

Leads:
- first_name
- last_name
- full_name
- email
- phone
- company_name
- website
- source
- source_detail
- status
- priority
- score
- estimated_value
- owner_id
- assigned_to
- next_follow_up_at
- last_contacted_at
- converted_at
- converted_contact_id
- converted_company_id
- converted_deal_id
- notes_summary
- tags

Contacts:
- first_name
- last_name
- email
- phone
- mobile
- title
- company_id
- owner_id
- status
- tags
- lead_source
- address
- city
- state
- postal_code
- country
- linkedin_url
- website
- last_contacted_at

Companies:
- name
- website
- phone
- industry
- company_size
- annual_revenue optional
- owner_id
- billing_email
- billing_address
- shipping_address
- city
- state
- postal_code
- country
- stripe_customer_id
- subscription_status
- account_status
- health_score
- tags

Deals:
- title
- company_id
- primary_contact_id
- pipeline_id
- stage_id
- value
- probability
- forecast_category
- expected_close_date
- owner_id
- assigned_to
- next_step
- lost_reason
- won_at
- lost_at
- source
- notes_summary

Pipelines:
- name
- description
- is_default

Pipeline Stages:
- pipeline_id
- name
- order_index
- probability_default
- is_closed_won
- is_closed_lost

Tasks:
- title
- description
- related_type
- related_id
- assigned_to
- created_by
- due_at
- priority
- status
- completed_at
- reminder_at

Activities:
- related_type
- related_id
- activity_type
- title
- body
- created_by
- activity_at
- metadata_json

Notes:
- related_type
- related_id
- body
- is_pinned
- is_internal
- created_by

Meetings:
- title
- description
- related_type
- related_id
- start_at
- end_at
- owner_id
- attendees_json
- location
- outcome

Quotes:
- quote_number
- company_id
- contact_id
- deal_id
- status
- subtotal
- tax
- discount
- total
- valid_until
- notes
- approved_at
- created_by

Quote Items:
- quote_id
- product_id optional
- name
- description
- quantity
- unit_price
- line_total

Products / Services:
- name
- description
- price
- billing_type
- sku
- active

Files:
- related_type
- related_id
- file_name
- file_url
- file_type
- file_size
- uploaded_by

Tags:
- name
- color optional
- category optional

Record Tags:
- tag_id
- related_type
- related_id

Automations:
- name
- trigger_type
- conditions_json
- actions_json
- active
- created_by

Notifications:
- user_id
- type
- title
- message
- related_type
- related_id
- read_at

Audit Logs:
- user_id
- action
- module
- record_type
- record_id
- before_json
- after_json
- ip_address optional

Custom Fields:
- module_name
- field_name
- field_label
- field_type
- options_json
- required
- active
- order_index

==================================================
CRM MODULE BEHAVIOR
==================================================

Leads:
- create, edit, assign, qualify, tag, score, search, filter
- convert lead into contact + company + deal
- create follow-up tasks
- track source and last contact
- support bulk actions

Contacts:
- full detail page
- related company
- related deals
- notes
- tasks
- communication history
- files
- tags
- search and filters

Companies:
- account detail page
- related contacts
- related deals
- billing data
- notes
- tasks
- files
- activity timeline
- account health score

Deals:
- board view and table view
- drag-and-drop stages if supported
- probability and forecast fields
- expected close date
- next step
- close won / close lost workflows
- lost reason capture
- related notes, tasks, contacts, activity, quote, billing status

Tasks:
- assign users
- due dates
- reminders
- priorities
- linked records
- overdue highlighting
- task completion logging

Activities:
- unified timeline across lead/contact/company/deal pages
- include notes, calls, SMS, meetings, assignments, stage changes, billing events, system events

Meetings:
- create meetings
- link to record
- capture outcome
- create follow-up task

Quotes / Proposals:
- create quote from deal
- add line items
- calculate totals
- statuses like draft, sent, approved, expired
- link quote to deal and company

Products / Services:
- internal catalog for quote creation
- active/inactive toggle

==================================================
INTEGRATION CENTER
==================================================

Create a dedicated integrations section with:
- integration dashboard
- integration detail pages
- status cards
- test connection action
- sync now action
- last sync timestamp
- logs
- error history
- enable/disable toggles

STRIPE integration:
Build a Stripe integration management area that supports:
- connect Stripe account or credentials
- verify connection
- store Stripe connection settings securely
- sync customers
- sync invoices
- sync subscriptions
- map Stripe customers to CRM contacts/companies
- save stripe_customer_id on relevant records
- display invoice status on CRM records
- display subscription status on CRM records
- show failed payments
- show past due invoices
- show renewal dates
- support manual sync
- store sync log history
- create finance alerts for failed payments
- show payment links or hosted invoice links where available

Create supporting data structures for:
- Stripe Customers Sync
- Stripe Subscriptions
- Stripe Invoices

TWILIO integration:
Build a Twilio integration management area that supports:
- connect Twilio credentials
- verify connection
- send outbound SMS from lead/contact/company/detail pages
- store inbound and outbound SMS history
- show message delivery status
- show failed message status
- store Twilio message SID
- create communication timeline entries
- support message templates
- support opt-out status
- store call logs if available
- store Twilio call SID and call status
- notify assigned owner when inbound message arrives

Create supporting data structures for:
- Twilio Messages
- Twilio Calls

Design the integrations area so more integrations can be added later, such as:
- email provider
- Google Calendar
- Google Contacts
- Slack
- webhooks
- Zapier / Make
- Resend
- Mailchimp
- accounting platforms

==================================================
AUTOMATIONS
==================================================

Create a basic automation engine or automation configuration area for:
- new lead created
- deal stage changed
- deal won
- payment failed
- inbound SMS received
- task overdue
- no activity on record for set period
- subscription cancellation pending
- quote approved

Automation actions can include:
- create task
- assign user
- notify user
- log activity
- update status
- create follow-up reminder

==================================================
REPORTING
==================================================

Create reporting views for:
- leads by source
- leads by owner
- conversion by source
- conversion by sales rep
- deals by stage
- won revenue by time period
- lost deals by reason
- overdue tasks by user
- task completion by user
- follow-up performance
- subscription status breakdown
- failed payment count
- invoice aging
- communication volume
- team activity counts

Add filters for:
- date range
- owner
- role
- source
- pipeline
- stage
- tags
- company
- status

==================================================
SEARCH, FILTERS, AND BULK ACTIONS
==================================================

Implement:
- global search
- advanced filters
- saved views
- sorting
- pagination
- export where allowed
- bulk record actions

Bulk actions should support:
- assign owner
- change status
- add tags
- remove tags
- create tasks
- delete where permitted

==================================================
SETTINGS
==================================================

Create settings pages for:
- app settings
- CRM settings
- user profile settings
- roles and permissions
- pipeline settings
- tag settings
- custom field settings
- notification settings
- integration settings
- webhook or API key settings if needed

Global settings should include:
- app branding
- timezone
- date format
- currency
- default lead statuses
- task priorities
- source lists
- default pipeline

==================================================
SECURITY AND AUDIT
==================================================

Implement:
- protected routes
- permission checks on all critical actions
- audit logs for create, update, delete, assignment, role changes, integration setting changes, billing state updates where relevant
- created_by and updated_by tracking
- clear ownership and assignment rules
- prevent unauthorized data access

==================================================
USER EXPERIENCE
==================================================

The UI should feel like a modern professional CRM:
- clean and responsive
- easy to scan
- tables with filters
- board view for deals
- detail pages with organized tabs
- summary cards
- related records panels
- quick action buttons
- clear empty states
- strong admin usability

==================================================
BUILD EXPECTATIONS
==================================================

Do not create placeholders without structure.
Do not create shallow UI only.
Create the full system architecture, pages, data models, relationships, permissions, and logic needed for a usable CRM foundation.

Where deeper integrations require credentials or webhook setup, build the full integration settings UI, data structure, connection testing flow, sync logs, and record linkage so the app is integration-ready.

At the end, provide:
1. a summary of what was built
2. all entities created
3. all pages created
4. all backend functions created
5. all automations created
6. any items that still need manual credentials or API keys
7. any recommended next steps

Yesterday I hosted the Building Client Ready Apps Office Hosts for base44 in their official discord.

I talked about how most users create apps for the audience they are going after, and forget to build the internal systems that they need to actually manage the app. The operations side is normally ignored to a great deal. So! I created the systems for everyone and provided the prompts for free.

Included Systems:

• Admin Foundations
• Billing and Accounting
• Communications and Alerts
• CRM-Style client operations
• Error Tracking and issue monitoring
• Feedback Loop system
• Internal Team Operations System
• Onboarding and retention systems
• Reporting and Visibility
• Support ticket systems and workflows
• User and Client Management

You can find the prompts for all these systems on the app I built for the event.

https://client-ready-apps.base44.app/