How to build a CRM
Follow these steps in Evonx to a working CRM repository with leads, accounts, opportunities, and activities you can preview and ship.
Step-by-step
Define your sales model
List stages, required fields, and roles before prompting so the schema matches how your team sells.
Start from the CRM template
Open the CRM template in Evonx or describe entities explicitly if you import an empty repo.
Model core entities
Create leads, accounts, opportunities, and activities with relationships and ownership fields.
Add pipeline views
Ask for kanban by stage, filters by owner, and activity timelines on account pages.
Wire notifications
Integrate email or Slack alerts for stage changes and overdue tasks using Resend or Slack webhooks.
Preview and review
Run preview environments, validate permissions, and merge via pull request when satisfied.
Outcome
A working CRM repository with leads, accounts, opportunities, and activities you can preview and ship.
Related resources
FAQ
What should I define before writing CRM code?
Lock the sales motion first: lead sources, pipeline stages, and who owns each activity. The guide walks entities before UI so screens stay coherent.
How does this guide relate to the CRM template?
The guide is instructional sequencing. The CRM template is the structured product starting point inside Evonx—use both without swapping keyword intent.
When should I import GitHub instead of greenfield?
If a CRM already runs in production, import the repository and apply the same entity checklist to your existing schema rather than regenerating from zero.
Build production software with Evonx
Start from a template or connect an existing repository. Evonx helps you ship real applications with preview, evolution threads, and pull-request delivery—not disposable demos.