A couple of years ago, a potential client called requesting a custom CRM system. He ran an auto parts importing business — six salespeople, a sales manager, an operations team handling customs clearance and distribution to mechanical workshops nationwide. He had ambitious ideas and ambitious plans. My recommendation surprised him.
"I see that your business processes are currently standard, and there is a considerable range of CRM SaaS software providers that can meet your requirements for now. I can accompany you through the implementation process until it is standardized, and when your business processes require more differentiation due to sustained growth, we can evaluate migrating to a custom CRM."
Custom CRM or CRM SaaS: The Foundation
I provided the following justification. Since his processes were standard — and I congratulated him on this, as many small businesses don't have that culture — we were able to map them clearly:
- Lead acquisition through events and phone call campaigns.
- Business opportunity management, generating quotes and different versions of them.
- Customer management and activities: calls, meetings, visits.
- Closing won opportunities through approved quotes.
- Customer support and warranty tracking through ticket management.
- Inventory management (simple: SKU and quantities).
- Reports on approved quotes, new clients by season, and sales funnel.
Most SaaS solutions handle all of that. For inventory, about three specific CRM SaaS providers offer it — but options exist.
Then we moved to the numbers:
- 10 total users (1 sales manager, 6 salespeople, 2 operations, himself)
- ~$50/user/month = $500/month
- Over two years: $12,000
- Estimated time before needing a custom CRM: 2 years
Some might say spending $12,000 on software used for only two years is a poor investment. The answer is simple — most small businesses need cash flow. Paying $500 per month was far more attractive than a large upfront custom build.
Part of our consultancy was ensuring the SaaS CRM actually fit his processes — not the other way around. From experience and pain: asking a SaaS provider to modify their software to adapt to your processes can sometimes be more expensive than building a custom CRM from scratch.
The Unpleasant Surprise
Two years passed. As predicted, the operation grew — and the SaaS CRM started showing its limits:
- Slow resolution of support issues.
- Forms that couldn't be adapted to regulatory or process changes.
- New types of reports that the platform couldn't generate.
- Other operational software that didn't integrate, causing data sync delays.
The natural next step was a custom CRM. But another "consulting" company got to him first — convincing him to implement a packaged version of a globally recognized platform. I'll call it "ELCARO" (for those who understand, few words are needed).
They were an authorized partner. Certified. All the badges. What they were not was a software developer. Instead of adapting the software to the company, they forced the company to adapt to the software — arguing that the processes were already standardized worldwide and the company needed to follow the "ELCARO" methodology.
The project lasted almost a year. They sent Account Managers, Product Managers, Project Managers, Software Integrators, and offshore developers. They delivered — amid frustrations, rescheduled deadlines, and extra charges. It was extraordinarily expensive. And when the system went live, the failures began: broken reports, crashes on data entry. A nightmare you can't wake up from.
Amid the disputes, the consulting firm concluded: "Your company was not ready for a world-class software like 'ELCARO.'" Then they canceled the support contract and left.
Their website still lists my client's company logo under "Clients" and in the "Successful Projects" section.
I found out because the client called me. Between embarrassment and regret, he confessed: they had gone back to paper and Excel, completely abandoned the CRM, and were only using the ERP for basic accounting. He asked me to help him fix it.
The Solution: Custom CRM Development
Two things became clear from this experience:
First: Globally recognized software must be adapted to the local reality and organizational culture of each country. A one-size-fits-all template is not an implementation — it's a forced migration.
Second: A software "consulting" company may hold official certifications and authorized partner status. But if it is not a developer with its own programmers and deep knowledge of the business it's serving, the project will most likely fail.
Detailed Process Assessment
We mapped every screen the CRM would have and how it would interact with the existing ERP and future systems. The client participated actively — providing corrections, suggestions, and envisioning new functionality.
Module-by-Module Development and Testing
As each module was completed, we tested it with real users using real data — verifying that every process was correctly handled before moving to the next.
Go-Live
In just over three months, the client had a fully operational custom CRM — delivering results at a fraction of the cost of the "ELCARO" disaster. A happy and loyal client.
The software was built around the business, not the other way around.
The Takeaway
There is no single right answer — each organization has its own culture and methodology. While many processes are standard, a company's software needs evolve as it grows.
A CRM SaaS may fit well initially. But as the company expands and its processes become more differentiated, a custom CRM becomes the right move in most cases.
Software is like suits. Tailored is always better — once you've grown into needing one. The mistake is ordering a bespoke suit on your first day of business, or worse, forcing yourself into a suit that was never cut for you.