Short answer: if the way you sell looks like the way almost every business sells, a standard CRM is the best option. If the gap you have is shared by your whole sector, the sensible choice is a sector-specific tool, built once for many. And a custom CRM makes sense when it has to be the foundation of your operations, not just your sales, and you want that system to be yours.
We explain this through two of our own projects, which represent the two paths that aren't standard: DentalCRM Pro, a tool for dental clinics, and the in-house CRM we have developed for a wholesale importer of frozen fish and seafood.
Some context
According to the survey on ICT use and e-commerce in companies by Spain's National Statistics Institute (INE), published on 22 October 2026, in the first quarter of 2026, 33.9% of Spanish companies with 10 or more employees and an internet connection used CRM software. ERP software was used by 60.9%. And having an internet connection is the norm: 98.3% of those companies had one.
In other words, almost twice as many companies have a system to run their operations as have one to manage their customers. Our reading, which is an interpretation rather than a fact: in many businesses, customer information is scattered across the management system, email, a spreadsheet or two and the memory of whoever deals with each customer. Both projects described here grew out of that gap.
There aren't two options, there are three
Conversations about CRM tend to stop at "standard or custom". In practice there are three paths, and choosing well depends above all on one question: is your problem yours alone, or does your whole sector share it?
1. Standard CRM: when your process is like everyone else's
General-purpose CRMs such as HubSpot, Pipedrive or Zoho CRM handle the common case very well: a record for each customer, a pipeline with stages, tasks, reminders and basic reports. They work from day one, with no development, and you pay a per-user subscription.
If your sales fit "contact, opportunity, proposal, close" and your data doesn't depend on another system, start here. You don't need anyone to build anything for you.
2. Sector-specific CRM: when your whole sector has the same gap
Dental clinics use practice management software that handles clinical records, appointments and finances, and also stores treatment estimates. Some, such as Gesden, even let you filter the list of estimates by follow-up actions and their outcome. But they are organised around the patient's file, not around the sale, and follow-up depends on someone pulling that list and working through it.
That gap doesn't belong to one clinic; it belongs to the sector. That's why DentalCRM Pro isn't a custom build for each clinic but a tool built once for all of them:
- A board with estimates organised by status (new, awaiting decision, awaiting payment, won or lost) and the amount stalled at each stage.
- Alerts for estimates with no one assigned, an overdue action, no activity for weeks, or a high value.
- A log of every call, WhatsApp message or email, so anyone on the team knows where each patient stands.
The key decision was not to compete with the clinic's software. DentalCRM Pro is designed to sit on top of it: estimates come in from the system the clinic already uses, and the clinic doesn't change the way it works on the clinical side.
What we learnt: when a problem repeats itself in the same way across a whole sector, nobody should have to pay for a full development project to solve it. Building it once means it can be offered as a monthly product subscription, in this case €29.90 a month, rather than as a project budget.
3. Custom CRM: when the CRM has to be the foundation of your operations
The second case is different. It is a wholesale importer that sells to distributors and wholesalers, and whose products are defined by species, origin, size grade and glaze. The starting point was that commercial decisions were being made with data scattered across Excel, email and the sales rep's head, and that commercial and logistics operations had no system of their own that could grow with the business.
A standard CRM would have covered contacts and opportunities. But what the company needed in one place was something else: customers, orders, margins and stock in a single tool. That is no longer general-purpose CRM territory.
The answer was an in-house CRM with sales, customer, order and margin modules, designed from the outset to grow into a full ERP. It is part of a wider project with this client that includes the website, the brand and marketing, and the underlying idea is for the company to have its own technology base that grows with it, without depending on third parties.
We don't share results figures for this project: we'll publish them once the client has validated them.
What we learnt: a custom CRM is justified when it isn't just a sales tool but the foundation on which operations will be organised. If all you need is to track opportunities, it's overkill.
What they have in common
The two projects are very different, but they share three decisions:
- Start with the process, not the tool. First, understand where information was getting lost; then, decide what to build.
- Grow in phases. In clinics, the practice management software stays where it is and DentalCRM Pro only adds the missing layer. At the importer, the CRM was born with a roadmap towards an ERP, but it doesn't try to be one from day one.
- Build only what's missing. No modules nobody will use, and no features copied from other CRMs just because they "usually come with it".
How to tell which case you're in
Four questions to help you find your bearings:
- Does your sales process fit the stages of a sales pipeline? If so, look at a standard CRM first.
- Is the data that matters already in another system? If it's a typical system for your sector, look for a layer that connects to it before looking for a replacement.
- Is your problem the same as your competitors'? If it is, a sector-specific tool probably exists, or should.
- Do you need the CRM to be the foundation for orders, margins or stock, and the system to be yours? That's where custom development starts to make sense.
What each path costs
Without going into specific prices, each option is paid for differently, and it's worth comparing them over two or three years rather than on the first month's fee:
- Standard: a per-user subscription that grows with your team and the plan you need, plus add-ons and integrations that don't come as standard.
- Sector-specific: a product subscription. The development cost is shared by everyone who uses it.
- Custom: the initial development, plus maintenance and improvements as the business changes. There are no per-user licences, but there's no vendor updating it on its own either.
With custom development there is also a risk worth putting on the table: dependence on whoever builds it. It can be reduced with documentation, with standard technology that another professional can maintain, and by making clear from the start who owns the code and the data.
A note on personal data
Whichever path you choose, you remain the controller of your customers' data. If a provider processes that data on your behalf, Article 28 of the GDPR requires a contract governing that processing.
In a clinic, the bar is higher: a treatment estimate says a lot about a patient's health, and Article 9 of the GDPR treats health data as a special category. Any tool that handles it has to be designed for that from the start.
How we approach it at Isenzo-IA
We build custom CRMs, which is exactly why we almost always start with the opposite question: if a standard or sector-specific tool already solves your problem, we'll tell you in the first session. If not, we define the minimum scope, build it in phases and train your team to use it and develop it further.
You can see DentalCRM Pro in detail on its page. To see how we approach a custom CRM, visit the Custom CRM page. And if you'd rather start by finding out what you need, that's what the diagnosis is for.
Sources
- INE (Spain's National Statistics Institute). Survey on the use of ICT and e-commerce in enterprises. Year 2025, first quarter of 2026. Published on 22 October 2026. Data for companies with 10 or more employees.
- Regulation (EU) 2016/679, General Data Protection Regulation, Articles 9 and 28.
