Identify the constraint, not the frustration
A team outgrows a CRM when important business rules cannot be expressed reliably within its configuration and supported integrations. A crowded screen or an unpopular workflow does not automatically justify a custom replacement.
List the workarounds that people repeat: duplicate entry, export-and-reimport, manual permissions, missing status transitions or reconciliation between tools. For each, record frequency, consequence and whether the platform already supports a safer configuration.
Check three remedies in order
- Improve the existing setup: fields, roles, saved views, validation and training.
- Add a bounded integration or specialist interface while keeping the CRM as the record owner.
- Build a custom system when the core workflow and access model remain a poor fit.
| Constraint | Evidence to collect | Possible response |
|---|---|---|
| Too much manual entry | A traced example across systems | Integration before replacement |
| Sensitive records visible too broadly | Role and permission tests | Fix access; investigate product limits |
| Core workflow cannot represent approvals | Written states and transition rules | Extension or custom module |
| Reporting cannot reconcile the source data | Examples of mismatched definitions | Repair the data model first |
Include the cost of ownership
Custom software creates responsibilities for hosting, backups, access reviews, incident response and future changes. A licence comparison that excludes those responsibilities is incomplete. Likewise, a ready-made product may have additional usage, integration or support costs that belong in the decision.
Prove the difficult part first
Choose the workflow that most strongly exposes the current limitation. Build a small proof with representative, sanitised data. Test permissions, exceptions and exportability, not only the happy-path interface.
Write down the conditions under which you would keep the existing CRM. That makes discovery a decision process rather than a sales exercise. M48โs business systems service starts with the workflow and source-of-truth data, not an assumption that every company needs a custom CRM.
A practical question
How do we know a custom CRM is justified?
Document a core workflow that supported configuration and bounded integrations cannot represent reliably. Prove that difficult part with representative data, permissions and exception handling before committing to replacement.