An example prompt for a CRM

Build a CRM for a small recruiting agency. It needs: contacts, companies and deals, pipelines and stages (kanban), custom fields, activities, notes and tasks, saved views, filters and search and roles, record scope and field-level permissions. Rule that must always hold: store values in a validated jsonb column per entity, indexed with GIN jsonb_path_ops for containment filters, with definitions in custom_field_defs and promotion of hot fields to typed columns by migration when usage proves it. Leave out for now: no email or calendar sync, outbound webhooks or workflow automation in phase 1 (designed for, deferred) and no raw SQL or user-supplied query fragments from the UI, ever.

Replace the first sentence with your own idea. The list of needs stays useful whatever the niche, because it comes from what a CRM has to do.

• Build a customer tracker for a landscaping company. Start with contacts, companies and deals and pipelines and stages (kanban), and add custom fields once those work.
• Build an internal sales pipeline tool for a three-person startup. People should be able to log calls/meetings/notes against records and schedule follow-ups with due dates and assignees.

Forge AI picks a reference architecture from how you describe the app. These phrases point to a CRM: crm, customer relationship management, hubspot, salesforce, pipedrive, zoho crm, sales pipeline and deal pipeline.

• jsonb custom fields with GIN, not EAV or per-field columns.
• Field-level permissions enforced in the query builder, serializer and export.
• Append-only hash-chained audit log written in the same transaction.
• Fractional rank for kanban ordering.

This is a reference design for the category, not a promise that every item is generated today. Built-ins such as email, background jobs, file uploads and search are coming soon, so anything here that needs them is something you add yourself for now.

• Outbound webhooks and a public REST API with scoped keys: needs an outbox, retries and per-key limits; manual export covers phase 1.
• Email and calendar sync (Gmail / Microsoft 365 OAuth): provider review, token storage and sync cost; BCC-to-log covers phase 1.
• Workflow automation engine and duplicate-merge tooling: needs the outbox and run caps first.
• Dedicated search engine (OpenSearch/Typesense): Postgres FTS plus trigram is sufficient.

How detailed should a prompt for a CRM be?

Name the users, the main objects, one rule that must always hold and one thing to leave out. The plan fills in the rest, and you can change it before generation.

Which words tell Forge64 this is a CRM?

Phrases such as crm, customer relationship management, hubspot and salesforce point to this category.

Can I change the app after the first build?

Yes. Describe the change in plain English and Forge AI edits the app; the quality gate checks the code again.

• How to build a CRM
• CRM architecture
• CRM security checklist
• CRM scaling checklist
• Often combined: SaaS dashboard
• Often combined: AI document chatbot
• All app types