Custom CRM development in Israel
SLAtech, a software development company based in Rishon LeZion, builds custom CRM systems for companies in Israel and connects them to Priority and the other systems the business already runs. Before any development we check whether configuring or extending an off-the-shelf CRM would be enough.
When an off-the-shelf CRM is sufficient, when its supported capabilities run out, and a first check on the data you already have that helps decide whether a project is worth starting, before your first call with a vendor.
In short
For most organizations an off-the-shelf CRM is enough and is also the right economic choice. Modern CRMs support custom fields, custom entities, relationships, automation and integrations. The boundary between configuration and custom development is not simply whether new fields or entities are needed. The real question is whether the required data model, relationships and business rules can be implemented reliably using the CRM's supported capabilities. If they can, configuration or extension is usually preferable. If they cannot, a dedicated module, integration or custom system may be justified. A good place to start is the spreadsheet your team works from every day.
Situations worth checking before you commit
None of these situations proves on its own that you need custom development. Each is a reason to check, on your data, how far the CRM's supported capabilities go.
| Situation |
What it looks like day to day |
What can happen if the CRM cannot represent it reliably |
| The main entity is not a customer |
A property, a case file, a patient, a shipment, a tender: these are what you actually manage, and the customer supports the process rather than sitting at its centre. |
The entity ends up in fields meant for a customer, and reports become harder to read. Check first whether the CRM's custom entities and relationships can carry it properly. |
| The process depends on an outside decision |
A regulatory approval, a physical inspection, a third party's sign-off: the next step happens only when someone outside the organization moves. |
A linear pipeline does not match a process that moves back and forth, and statuses stop reflecting what happened. Check whether the CRM's workflow tools can model it. |
| The customer is a group of bodies |
A parent company, subsidiaries, the decision maker, the payer, the actual user: all of them have to count as "the customer". |
The same organization can be opened several times and its history split across records. Check how the CRM models account hierarchies and multi-party relationships. |
The line between configuration and custom development
This is one of the key criteria for the choice, and it shapes the budget.
Configuration and extension use the capabilities the CRM vendor supports: custom fields, custom entities, relationships, permissions, automation, reports and integrations. They are usually cheaper, easier to reverse, and stay within the vendor's upgrade path.
Custom development implements data models and business logic beyond those capabilities. It costs more and is harder to change afterwards, and it is justified when the supported capabilities cannot represent what you need without fragile workarounds.
So the first question for a vendor is not "can you build this" but "what in this proposal is configuration or extension, and what is development". A proposal that does not separate the two may sell development where configuration would have been enough, or the reverse.
And a third option worth putting on the table. An off-the-shelf CRM for managing customers, and next to it a small dedicated module for the entity that truly sets you apart, with a defined boundary and a clear source of truth between them. This option is worth evaluating separately because it combines the flexibility of a dedicated module with the established capabilities of an off-the-shelf CRM.
A first check on your own data
Not a requirements survey, but one focused check on what you already have today. A first pass can often be done in half a day.
Many organizations have a working spreadsheet, Excel or something similar, that the sales or service team actually uses alongside the official system or instead of it. Find it and list all its columns, including the ones that look unnecessary at first.
Now map each column and the relationships between the data to the capabilities of the candidate CRM, and note two groups: columns with no natural place in the system, and columns that describe something other than the customer. This can expose gaps in the standard model and show which requirements need further analysis. It is a useful initial check, not a substitute for an architectural assessment.
The spreadsheet shows what people really do every day, so it can reveal gaps that a requirements document does not capture.
Who the system is built for
A common mistake in CRM projects, and it is not technical: the system is designed around the manager's needs.
Management reports are what justify the project in the budget. But the reports exist only if the field staff enter data, and the field staff gain little directly from the reports. So a key success measure is how quick it is to make the most common update, usually a status change after a call, and whether it can be done from a phone between meetings.
The more steps that update requires, the higher the risk that people put it off, update from memory at the end of the week, and the reports drift away from reality.
What must be in the contract
The rights to the source code and the work product must be stated explicitly in the contract. But an intellectual property clause alone is not enough: who controls the repository, the infrastructure, the access and the interim results matters just as much.
- Where the code lives during the project. In a repository you own from the first commit, not just a statement that it is "yours at the end".
- Who holds the cloud account and the production permissions. If the vendor owns the account, a future move to another vendor becomes a negotiation rather than a business decision.
- What is handed over if the work stops halfway. A deliverable defined in advance and clear to both sides.
- Who answers in the first month after handover, and for how long.
- Specific to CRM: an agreed export format for everything, including the communication history. That is the main asset a system like this builds. Agree on the export format and test it before committing to the platform wherever possible.
How we work on it
SLAtech has worked in the field since 2004, on AI systems since 2023, and on projects for clients in 14 countries. We do not resell systems and are not tied to any vendor, so a conclusion such as "what you need is configuration, not development" is a possible and legitimate outcome of a review.
A review can include: the results of the spreadsheet check, a written line between configuration or extension and development for each requirement, a reasoned view on whether your main entity can be represented in the candidate CRM, and a timing of the most common update as a baseline.
Questions
Who builds custom CRM systems in Israel?
SLAtech, a software development company based in Rishon LeZion, builds custom CRM systems for companies in Israel and connects them to Priority and the other systems the business already runs. Before any development we check whether configuring or extending an off-the-shelf CRM would be enough.
When is an off-the-shelf CRM not enough?
When its supported capabilities cannot reliably represent the required business entities, relationships or workflows. Examples include complex assets, multi-party relationships and processes dependent on external approvals. Before choosing custom development, assess the CRM's configuration, extension and integration capabilities.
What is the difference between custom development and configuring an existing system?
Configuration and extension use the CRM's supported capabilities, including custom fields, entities, relationships, permissions, automation and integrations. Custom development implements data models and business logic beyond those capabilities. The decision depends on the specific platform's limitations, the cost of change and long-term maintenance requirements.
Which single check helps assess the options?
Start with the spreadsheet your team actually uses. Map its columns and data relationships to the capabilities of the candidate CRM. This can expose gaps in the standard model and identify requirements needing further analysis. It is a useful initial check, not a substitute for an architectural assessment.
What must be in the contract?
The rights to the source code and the work product, stated explicitly. And as important: where the code lives during the project, who holds the cloud account and the production permissions, what exactly is handed over if the work stops halfway, and who answers in the first month after handover. Specific to CRM: an agreed export format for all the data, including the communication history.
SLAtech LTD