Nobody decides to outgrow their CRM. It happens gradually: a custom field here, a Zapier rule there, and eventually a spreadsheet that the team trusts more than the system of record.
The tell is not the number of customisations. It is where the truth lives. When the answer to "what is the current state of this deal?" is in a shared sheet rather than the CRM, the CRM has already stopped being a CRM.
Four signals worth acting on
None of these are fatal on their own. Three together usually mean the configuration path has run out.
- A shadow spreadsheet exists and is more accurate than the system.
- Onboarding a new hire requires explaining which fields to ignore.
- A process change requires a consultant rather than an afternoon.
- Reporting is exported and reassembled before anyone can read it.
What building actually costs
A custom system is not automatically more expensive. Licence fees for a large team, integration middleware and consultancy hours compound; a well-scoped internal system is a one-off build plus maintenance.
The real cost difference is responsibility. Off-the-shelf means somebody else decides the roadmap. Custom means you do — including the parts you would rather not think about, like backups and access reviews.
The middle path
The most common good answer is not all-or-nothing. Keep the off-the-shelf product for what it does well, and build the one process that is genuinely specific to your business as a system beside it, connected through an integration layer you control.
That keeps the surface small, and it makes the decision reversible — which is worth more than being right first time.
We wrote this because we had to solve it. See what we built or tell us what you're working on.