CRM software: don't compare — filter before the demo
The five filter gates that help you choose a CRM system based on your work, not on a feature list.
In this article
Why every CRM software comparison starts in the wrong place — and why the filter is written before the demo
You enter a CRM software demo, and the salesperson shows a sales dashboard, reports, automations and a WhatsApp connection. Everything looks organized. Later you discover that the salesperson still keeps track in a notebook, that support does not see the promises that were made, and that accounting receives messages in text messages.
The problem is not necessarily the product. The decision started in the wrong place: with a list of features instead of a description of the work. Before you ask to see a system, write down how a lead enters, who handles it, what information must be kept and what happens when the normal scenario goes wrong.
In an accounting firm in February, an initial inquiry can quickly become a client file, a document task, a clarification question and a handoff to another team. A system that excels at sales but does not keep this context will create another screen, not organizational memory.
That is why the model here is the CRM filter. Every software passes through five gates before a demo is scheduled: process, data, permission, integration and cost of ownership. If it fails at one gate, the demo will only make it harder for you to give it up.
Anyone who wants to understand the basics before writing can read What is CRM and why it is not just sales software. Here the question is more practical: does the system fit your work, also when a new employee joins, a client returns or an unexpected exception occurs?
What is CRM software in an Israeli business: not Excel, not WhatsApp, not a shared email inbox
CRM software is the work layer that connects people, clients, processes and decisions. It is not just a list of contacts, a message inbox or a deal board. A useful CRM system shows what is known about the client, what has already been done, what is missing and who is responsible for the next step.
In a clinic with two reception stations, an inquiry can arrive from a form, a phone call or a WhatsApp message. If every channel is kept in a different place, the employee at the second station does not know whether a reply has already been given, whether an appointment has been set or whether a previous commitment exists.
Excel can hold a list. WhatsApp can hold a conversation. A shared email inbox can hold inquiries. None of them on its own defines who is allowed to see information, when a stage moves forward, which data is missing and what will happen if an employee leaves.
In a CRM for a small business there is no need to copy a corporation's structure. You need to define the few processes that repeat every day and make sure they do not depend on one person's memory. Sometimes a simple system with precise fields is preferable to a broad platform that no one updates.
The CRM Filter: The Five Gates Every Software Must Pass
The filter replaces the question "which system is best?" with five test questions. Software enters the list of candidates only if it passes all of them on paper, before any presentation.
| Gate | What is checked | The question that decides | What breaks without it |
|---|---|---|---|
| Process | Stages, responsibility and exceptions | What is the next step and who performs it? | Inquiries get stuck between employees |
| Data | Entities, fields and history | Where is every detail stored and for how long? | Duplicate information and manual searching |
| Permission | Access, editing and export | Who is allowed to see or change? | Exposure of information and uncontrolled changes |
| Integration | Connections and information flow | What enters and what leaves automatically? | Copies, mistakes and duplicated work |
| Cost of ownership | Use, change and exit | What will be required after launch? | An expensive system that is hard to maintain |
In a vehicle service center, the temptation can be to choose based on a pretty app and lead management. The filter will demand different answers: how the reason for returning to the garage is recorded, who sees the service history and what happens when a payment fails.
The order matters. There is no point checking WhatsApp integration before you have decided which event should trigger it. There is no point comparing the price of a CRM system before you know how many users, processes and changes will be inside.
Gates 1 and 2: Mapping the customer lifecycle and the data model — what is stored, where and why
The first gate defines the customer's movement; the second defines the material that accompanies it. Together they answer four questions: what happened, to whom, when and who is responsible now.
In a small brokerage office, the path does not end at "new lead." It can move to a fit call, a suitable property, a viewing, an offer, negotiation, a deal or a loss. Every stage has transition conditions. "A call was made" is not necessarily a sufficient condition for moving to an offer.
Mapping the lifecycle
Write the stages in the employees' language, not the supplier's language. For each stage define:
- What brings a record into this stage.
- What information must be completed before the transition.
- Who is responsible for the next action.
- What counts as success and what counts as a stop.
- What happens if the customer does not respond, comes back after a period or asks to speak with someone else.
A lead that arrived from a website form is not necessarily a customer. A person who has approached before is not necessarily a new lead. Decide whether an additional inquiry updates the existing record, creates a new event or opens an additional opportunity under the same customer.
The data model
Define the entities before the fields. Usually you will need to distinguish between a person, a company, a lead, a deal, a service, a task, and a document. In a business that sells to several role holders at the same company, the contact person and the company are not the same record.
For each field, specify the type of information and the reason it exists. A phone number should be stored in a uniform format. A source of inquiry should be a closed choice if you want to compare sources. A loss reason should be mandatory when a deal is closed without success.
Separate information the user enters from information the system creates. A record's creation date, status change, and the last user who worked on it should be created automatically. Otherwise you cannot know whether the information is up to date or who changed it.
Also ask where the history is stored. A general note is not a substitute for a date, an action type, a responsible party, and a link to a document. In the customer card of a cleaning company, you should see the inquiry, the quote, the service coordination, and the problem discovered later in the same sequence.
Gate 3: core processes — sales, service, operations and retention, and where organizational memory breaks
The process gate examines what happens between departments. A CRM system fails when it documents each team separately but does not manage the moment when responsibility passes from team to team.
In an insurance agency, the salesperson can promise a check, operations can request documents, and service can receive a question about the policy. If the promise stays in a private conversation, the customer will have to tell it again.
Sales
Define a source of inquiry, an owner, a stage, a next action, an action date, and closing conditions. If a lead can stay "in treatment" without a task, you do not have a real stage but a folder.
Check what happens with an unanswered contact attempt, a duplicate inquiry, and a sale of several services to the same customer. Do not settle for the question of whether there is a sales funnel. Ask to see how the system prevents a deal without a future action.
Service
Define how an inquiry is opened, who classifies it, which team it is routed to, and what closes it. A call opened on WhatsApp, in a phone call, or in an email should reach the same place if it requires handling.
Determine which details must appear before closing a call: the description of the fault, the employee's action, the customer's response, and whether follow-up is required. Otherwise the report will show closed calls without teaching you anything.
Operations and Maintenance
The handover from sales to operations should be an event with conditions, not a general announcement. Define the documents, contacts, requested date, and commitments that must be on the record before work begins.
In an ongoing service, define a checkpoint before renewal, handling of a customer who did not use the service, and an alert about a missing document. A business that manages renewals from a personal calendar will discover the risk only once the customer has already approached somewhere else.
The most important scenario is the exception: an employee on vacation, a customer who changes their number, a deal opened by mistake, a failed payment, or a request sent to the wrong team. If the requirements document does not describe what happens then, the demo is not testing your system.
Anyone planning an implementation can go over CRM implementation: why projects fail and how to succeed, especially around responsibility, data, and user adoption.
Gate 4: Israeli integrations — WhatsApp, phone system, invoices, payments, website, and forms
A good integration is not "there is a connection." It defines an event, a direction, fields, an error, and ownership. A WhatsApp CRM integration should answer what enters the record, who sees the conversation, and what happens to an unrecognized number.
In a treatment clinic with local campaigns, a lead can arrive from a form, a call, or WhatsApp. Decide in advance whether the system merges by phone number, which source is kept, and what is created when a similar record exists.
Check whether the connection uses the official interface, how the conversation history is stored, and when it is permitted to send a proactive message. Define templates, approvals, error messages, and escalation to a representative.
Israeli numbers require consistency. If the same customer appears once with a local prefix and once in international format, the system may create a duplicate. Ask to see the merging process, not just the chat window.
Phone system
Define incoming call identification, dialing from the record, summary documentation, and a link to the recording if this is permitted and appropriate for your policy. Decide who is allowed to listen and what appears in the timeline.
Invoices and payments
Write down what information passes to the invoicing system, which document number returns to the CRM, and what happens when the production fails. In payments, define the difference between an attempt, an approval, a failure, and a refund.
Website and forms
Define which fields, campaign source, and landing page link enter. Determine what happens when the form is submitted again, when a phone is missing, or when the message arrives outside operating hours.
Do not ask only "is there an API." Ask who maintains the key, how a version change is carried out, where an error is logged, and who receives a task. A connection without failure handling is an automatic copy of a problem.
Gate 5: The true cost of ownership — licenses, implementation, training, changes, and exit
The price of a CRM system is only one component of the cost. The real cost includes licenses, setup, data cleanup, connections, employee training, customizations, maintenance, and the way you will export the data if the engagement ends.
In a law firm, a low license price does not help if every field change requires the vendor, every additional user changes the structure, and case transfer is done manually. Examine the work around the software, not just its screen.
Ask for a quote that separates between:
- User license, permissions, and storage.
- Requirements document, setup, and data migration.
- Connection to each external system.
- Training for employees and managers.
- A change after go-live.
- Reports, automations, and integration maintenance.
- Data export, the format, and when it can be performed.
Ask what you can change yourselves and what requires the vendor's work. Ask for an example of a field change, a stage change, and a permission change. A vague answer here will later show up as an unexpected cost.
Also check the customer data: can it be exported, in what structure, and what remains with the vendor. With us, the customer's data belongs to them and can be exported for 30 days after the engagement ends. The software itself is ours.
Present all costs over the same time horizon. A system that looks cheap at the start can be expensive once you add training, duplicate cleanup, connections, and changes that the activity requires.
The requirements document to copy: the sections you send to vendors — the page itself is the template
The document you send does not need to be technical. It needs to force you to decide and allow the vendor to propose a solution based on the same picture. Copy the following sections into a working document and fill them in in your own words.
1. The business and the goal
- What the business sells, to whom, and through which channel inquiries arrive.
- Which process you want to manage better.
- Where the work gets stuck today.
- How you will know the system is useful after go-live.
2. Users and permissions
- Which roles will work in the system.
- Who sees all customers and who sees only personal assignments.
- Who is allowed to edit, export, delete, or change settings.
- What financial, personal, or operational information needs to be restricted.
3. Customer lifecycle
- What the stages are from the moment of inquiry until the end of service.
- What the entry and exit conditions of each stage are.
- Who is responsible at each stage.
- What happens when the customer does not respond, returns, or changes a request.
4. Entities and fields
- Which records are required: person, company, lead, deal, service, task, and document.
- Which fields are mandatory and at which stage.
- Which values will be in a closed list.
- What information is created automatically.
- What the identifier is that prevents duplication.
5. Core processes
- How a lead is captured and what its next action is.
- How a deal moves from sales to operations.
- How a service ticket is opened and who receives it.
- How renewals, collection, credits, and returning customers are managed.
- Which exceptional scenario must be checked before approval.
6. Integrations
- Which systems connect: WhatsApp, phone system, website, invoices, and payments.
- What goes in and what goes out in each connection.
- How an existing record is identified.
- What happens when the connection fails.
- Who receives an alert and who is responsible for fixing it.
7. Reports and control
- Which questions management needs to answer every week.
- Which reports are required by source, employee, stage, service, or loss reason.
- Which exceptional records should appear.
- Who is allowed to see each report.
8. Past data and exit
- From which files and systems the information comes.
- Which duplicates need to be cleaned before the transfer.
- Which information must be kept as history.
- In which format the data can be exported.
- Who performs the export and what happens at the end of the engagement.
9. Acceptance questions before going live
- Can a lead be opened from every channel and assigned correctly.
- Can the entire history be seen in one card.
- Does an employee without permission see only the information allowed to them.
- Does a status change create the right task.
- Is an integration failure logged and does it reach a responsible person.
- Is it possible to produce a report without manually collecting data.
This is your requirements document. There is no need to start from a list of screens. You start from decisions the business is not prepared to leave to chance.
Off-the-shelf system vs custom development: how the filter decides the choice
An off-the-shelf system is suitable when your process resembles the process the product already manages, and the gaps can be defined without bypassing the system. Custom development is suitable when the process that differentiates you is the core of the work, and not a side addition.
In a real estate agency with a simple sales process, an off-the-shelf system can suffice. In a company that manages several types of service, approvals, documents, charges and exceptions on the same customer card, point adjustments can turn into a cumbersome structure.
Decide according to the five gates:
- If the process passes without a major change, off-the-shelf is a natural candidate.
- If the data model requires entities that do not exist, check the price of the bend.
- If the permissions are exceptional, check whether they are supported or only "possible in development".
- If the integrations are the heart of the business, check who controls the flow of information.
- If the changes are expected to be frequent, compare the cost of dependency over time.
Also CRM software in Hebrew is not only a question of menus from right to left. Check fields, system messages, templates, dates, phone numbers, documents and support for the workflow of an Israeli team.
An expansion on the difference is in Custom CRM or SaaS? The question is not price. The question is change. The choice is not ideological. It is the result of the gap between the filter and what the system knows how to perform without bypasses.
How to send the document to vendors and compare proposals without falling for a polished demo
Send every vendor the same document, ask for an answer according to the same sections, and do not allow a demo to replace a written answer. A serious proposal will show what is supported, what requires adaptation, what will be done through an external connection, and what is not possible.
Ask every vendor to demonstrate three of your scenarios: a lead that arrives twice, a deal that moves to operations with a missing detail, and a payment that fails after a proposal was sent. These are scenarios that reveal more than a clean sales sheet.
Compare in your own table the five gates, not the number of features. Next to each section write "exists", "requires change", "depends on a connection", or "not supported". Do not let "it can be built" count as a complete answer.
Ask who enters the data, who approves it, who handles a fault, and who can change the process. Also ask how training for a new employee looks, how responsibility for records is transferred, and how the data is exported if you change direction.
Before signing, demand an acceptance document that describes a tested result: a treated lead receives a task, a restricted user does not see sensitive data, a WhatsApp message is linked to a record, and the report shows what was defined. That is how a demo becomes a test, not a presentation.
For a broader comparison of categories and use cases you can read recommended CRM system for an Israeli business — full comparison. Do not choose according to where the software looked most impressive. Choose according to the gate where it was clearest.
If the filter points to processes that cross sales, service, documents, and automations, custom CRM for a business can concentrate them in one customer card. The alcyone14 team builds and operates tailored systems with CRM, automations, WhatsApp AI, dashboards, and documents, and starts with you from one process that is stuck.
Frequently asked questions
What is a free CRM software in Hebrew?
A free CRM software in Hebrew is usually a limited version of a customer management system, with limits on users, automations, connections, or reports. It can suit testing work habits, but check in advance whether the data can be exported and what will happen when you need WhatsApp, permissions, and more complex processes.
How do you create a CRM system?
You start by mapping the process, data, permissions, and integrations, and only then choose whether to configure an existing system or develop a tailored system. A good document describes stages, required fields, responsibility, exceptions, and acceptance conditions, and not only screens and features.
What is the price of a CRM system?
The price of a CRM system depends on licenses, number of users, implementation, data transfer, integrations, training, and changes after launch. To compare correctly, ask for a proposal that separates each component and also check the cost of maintenance and the option to export the data.
What is a CRM?
A CRM is a system that centralizes the information and actions around customers, deals, service, and operations. The difference between a useful CRM and a list of contacts is that the system manages responsibility, stages, permissions, and follow-up actions.
Is a CRM system also suitable as a CRM for a small business?
Yes, provided it starts from the processes the business actually runs and does not load on the structure of a large organization. For a small business, it is worth choosing few clear fields, a next action for every inquiry, and permissions that are easy to maintain.
