A CRM is the path of a deal: who owns it, which status comes next, what cannot be skipped, where the money and the documents sit.
Why a bought system starts to hurt
It is fine while the path is standard: lead, call, invoice. The moment you have your own objects — a site visit, a bill of materials, several legal entities — people open a spreadsheet. The CRM becomes a display. The record lives in Excel.
What to build first
Statuses and transitions, not screens. For each object: fields, who may change them, what is written to history. Then roles. Integrations — mail, phone, the website, the warehouse — come one at a time, after the main loop is the source of truth.
A useful minimum:
- client and contact;
- a deal with a status and an owner;
- a task and a comment;
- a change history;
- one report: how many deals sit on each step.
Example
Equipment supply. A deal is not won or lost. It is a specification, an invoice, a payment, a shipment, an install. Purchasing and installation edit different fields of the same record. A generic CRM hides that in a comment. Your own system shows the step and can block shipment until the invoice is paid, if that is the rule.
Copy the process. Do not copy every module of a large CRM.