Every major CRM platform — Salesforce, HubSpot, Zoho, Dynamics — offers customisation tools at no extra per-feature cost. Custom fields, custom objects, workflow automations, formula fields, custom reports. All included in the subscription. The customisation is free. What isn't free is the cost of operating a sales team on a system that was customised into a state nobody fully understands.
What actually happens when you customise a CRM?
Year one: a sales ops manager adds 15 custom fields, builds 8 workflow automations, and creates a reporting dashboard. Everything makes sense because one person designed it.
Year two: a different person adds 12 more custom fields, changes three automations, and builds a second dashboard because they can't modify the first one without breaking it. Now there are 27 custom fields, two dashboards showing slightly different numbers, and automations that reference fields nobody remembers creating.
Year three: the CRM has 50+ custom fields, 20+ automations with undocumented dependencies, and three dashboards that nobody trusts. The sales team enters data into fields they don't understand because the system requires it. The VP of Sales looks at a dashboard that shows a pipeline number disconnected from reality. Nobody wants to touch the automations because the last time someone tried, three deal stages broke.
This is what free customisation costs.
Why does CRM customisation spiral?
CRM platforms are designed as horizontal tools — they serve every industry, every sales process, every company size. That flexibility means the default setup fits nobody well. Customisation is the response: you bend the CRM to match how your team actually sells.
The problem is that CRM customisation tools are powerful enough to build complexity but not structured enough to manage it. There's no version control on field definitions. No dependency graph showing which automations reference which fields. No impact analysis before you delete or rename something. The CRM gives you a construction set and no blueprints.
Every customisation is rational in isolation. The spiral happens because nobody is tracking the cumulative complexity. By year three, the CRM is a custom application built inside a platform that wasn't designed to be an application development environment. You're paying Salesforce prices for a system that only one person understands — and that person left six months ago.
What does this cost in dollars?
A company paying $80,000/year for Salesforce Enterprise with 40 users is using roughly 20% of the platform's capabilities. The other 80% is features their sales process doesn't need. Meanwhile, they're spending $30,000–$50,000/year on Salesforce consultants to maintain the custom fields, automations, and integrations they've built.
Total cost: $110,000–$130,000/year for a CRM that their sales team actively works around. The reps maintain their real pipeline in a spreadsheet. The managers build their real forecasts in Google Sheets. The CRM is the system of record in theory and a data entry obligation in practice.
When should you build a custom CRM instead?
A custom CRM makes sense when three conditions are true: your sales process has non-standard logic that the CRM can't model without heavy customisation, you're spending more on CRM consulting and maintenance than on the subscription itself, and your team's actual workflow happens outside the CRM (in spreadsheets, in Slack, in their heads) despite the CRM being mandatory.
A custom AI-native CRM built around your sales process costs less per year than a heavily customised Salesforce instance once you factor in the subscription, the consulting hours, the opportunity cost of poor data, and the friction of a tool your team resists using. The breakeven is typically 18–24 months.
What should a CRM actually do for your team?
A CRM should model how your team sells, not force your team to sell the way the CRM was designed. If your sales process has stages the CRM can't represent, if your pricing logic requires a spreadsheet alongside the CRM, or if your team spends more time on data entry than on selling — the CRM is costing you deals, not closing them.
The free customisation was never free. It was a deferred cost that compounds every year. At some point, the cost of maintaining the Frankenstein system exceeds the cost of building the right one. The companies that recognise this earlier spend less overall and get a system their team actually uses.
Building something complex?
Start a project with Madgeek