A CRM implementation is eight steps in a fixed order, from writing down the real sales stages to a review thirty days after go-live. This is the procedure, with what each step must produce and the Israeli details that break it: phone formats, Hebrew and consent for marketing messages.
Key takeaways
- Build the pipeline from the sales process you already run, and give every stage an exit criterion someone can check.
- Normalise every Israeli phone number to +972 without the leading zero before import, and store whether it is a mobile.
- Record when, how and in what words each contact agreed to marketing messages, and one opt-out that covers every channel.
- Go live with three automations and four reports, then review at day thirty before adding anything.
Implementing a CRM in a small business takes eight steps in a fixed order: write down the real sales stages, choose the fields, import and de-duplicate the Excel data, connect the lead sources, set up WhatsApp and email with consent recorded, add a few automations and reports, train each role, and review after thirty days.
The order matters more than the software. Each step produces something the next one depends on: fields cannot be chosen before the stages exist, and an import cannot be checked before the fields are fixed. The reasons implementations go wrong are covered separately in why CRM implementations fail; this article is the procedure itself.
What does a CRM implementation include, and in what order?
These are the eight steps. Each one ends with a deliverable, and the next step does not start until that deliverable exists:
- Map the sales stages - a written list of stages, each with an exit criterion and an owner.
- Choose the fields - a short list of mandatory fields and the stage at which each becomes mandatory.
- Import and de-duplicate - one cleaned file, a 20-row test load, then a full load with the row count checked.
- Connect the lead sources - every form and channel writing into the CRM with its source stored.
- Set up WhatsApp and email - messages sent from inside the CRM, with consent and opt-out fields in place.
- Add three automations and four reports - assignment, a follow-up task and a stalled-deal alert; leads by source, conversion by stage, response time and loss reasons.
- Train by role - each person works through their own real records, not a demo account.
- Review at day thirty - a fixed list of checks, and a decision on what to change.
If you have not chosen a system yet, do that first: how to choose a lead management system covers the checks. Where the CRM is one of several systems being introduced together, the wider sequence is in the business systems implementation guide.
Steps 1 and 2: stages and fields from the real sales process
Start from the last ten deals you actually closed and the last ten you lost. Write down what happened between the first contact and the result, in the words your team uses. Those events are your stages. A stage copied from a template ("Qualification", "Discovery") that nobody in the business does is a stage nobody will update.
An example for a small service business that quotes after a site visit:
| Stage | Exit criterion | Field that becomes mandatory |
|---|---|---|
| New enquiry | Someone spoke to the customer | Owner, source |
| Meeting booked | A date is set for the visit or call | Meeting date |
| Quote sent | A quote number exists | Quote amount, expiry date |
| Negotiation | The customer answered the quote | Next action date |
| Won | A signed quote or first payment | Close date |
| Lost | The customer said no, or stopped answering | Loss reason from a fixed list |
Fields follow the stages. Keep the mandatory set small at the start: name, phone, source, owner, stage and next action date. Everything else becomes mandatory only at the stage where it is genuinely known. A field required on the first screen that the rep cannot answer yet gets filled with junk.
Step 3: how do you import Excel data without creating duplicates?
Clean before loading, never after. The full seven-step migration order is in migrating data from Excel into a CRM; what is specific to Israel is the phone number, because it is the field duplicates are matched on.
The Ministry of Communications numbering plan defines the formats a normaliser has to handle:
- Mobile numbers sit in the 05 dialling area and are dialled as 10 digits (050-1234567).
- Geographic landlines use the area codes 02, 03, 04, 08 and 09 and are 9 digits.
- National numbers in the 07 area are 10 digits and are not mobiles.
- From abroad, the number is dialled after 972 without its leading 0, so 050-1234567 becomes +972501234567.
Store the result in one form, +972 followed by the number without the zero, and keep a separate field for the type (mobile, landline, national). The type matters later, because WhatsApp messages go to mobile numbers. Do not try to derive the carrier from the prefix: the numbering plan itself notes that a number may have moved to another provider.
Hebrew needs its own test before the full load. Import the 20-row sample, then check three things on screen: Hebrew names display in the right direction in lists and search, a phone number inside a Hebrew field is not reversed, and an export of the same rows opens in Excel with the Hebrew intact.
Steps 4 and 5: lead sources, WhatsApp and email with consent recorded
Every source - the website form, ad lead forms, WhatsApp, calls - should create or update a CRM record with the source stored on it. A form that still sends an email to a shared inbox is a leak, and the lead it drops never reaches a report.
WhatsApp and email should run from inside the CRM, so the conversation is on the customer record and not on one rep's phone. Before the first marketing message, the consent fields have to exist.
This is a technical description of the rules, not legal advice. Section 30A of the Communications Law (Bezeq and Broadcasts), as added by Amendment 40 in 2008, prohibits sending an advertisement by fax, automatic dialling system, electronic message or SMS without the recipient's explicit prior consent, in writing, including by electronic message or a recorded call. The same section lets the recipient refuse at any time, in writing or through the channel the advertisement came by, and requires the advertisement to state that it is an advertisement (the word "פרסומת" at the start, and in an email in the subject line), the advertiser's name and contact details, and the right to refuse. The current consolidated text may include later amendments. Separately, Meta's WhatsApp Business policy requires businesses to obtain opt-in before messaging people, stating clearly that the person is opting in and naming the business.
In CRM terms, that translates into fields, not a policy document:
- consent date, channel, and the exact wording the person agreed to;
- where the consent was collected (form, call, in person);
- an opt-out date that blocks every channel at once, not only the one it came through.
Step 6: which automations and reports come first?
Three automations cover most of the value at go-live: assign every new lead to an owner and notify them, create a follow-up task when a quote is sent, and alert the owner when a deal has sat in one stage longer than your normal cycle. Longer sequences can wait; how to build them is in automating lead follow-up.
Four reports answer the questions a small business actually asks: how many leads came from each source, what share moves from each stage to the next, how long leads wait for a first answer, and why deals are lost. If a report is not opened in the first month, remove it.
Steps 7 and 8: training by role and the thirty-day review
Train each role separately, on its own records. A rep needs to log a call, move a stage and send a quote; a manager needs the four reports; whoever owns the system needs to add a field and change an automation. A session on a demo account teaches the demo.
At day thirty, check the same list every time:
- How many leads arrived outside the CRM, and from which source?
- Which mandatory fields are filled with placeholder values?
- Which stage do deals stall in, and is its exit criterion clear?
- Is any side spreadsheet back in use?
Fix what the review shows before adding a second process. A day-by-day version of the first month is in the failure-causes article linked above.
Sources
Frequently asked questions
Who should own the CRM implementation in a small business?
One named person inside the business, not the vendor and not a committee. That person approves the stages and fields, decides which requests become changes, and runs the thirty-day review. An outside developer can build the import and automations, but the decisions about how the business sells have to stay with someone who works there.
Should we import all our old Excel data into the new CRM?
No. Import the customers and open deals you will actually work with, and keep the rest in an archive file. Every row you import has to be cleaned, de-duplicated by normalised phone number and checked after the load, so leaving out dormant records is the cheapest way to shorten the import step.
Can we send WhatsApp campaigns to every number we imported?
An imported number says nothing about consent. Section 30A of the Communications Law ties advertising messages to the recipient's explicit prior consent, and Meta's WhatsApp policy requires opt-in before messaging. The CRM should hold, per contact, when and how consent was given, so a campaign can be filtered on it. This is a description, not legal advice.
How many pipeline stages should a small business start with?
As many as the events your deals really pass through, usually five to seven including won and lost. The test is not the number but the exit criterion: every stage needs a condition someone can check, such as a meeting date or a quote number. A stage without one becomes a place where deals sit unnoticed.
When is a CRM implementation actually finished?
When the day-thirty review shows that leads no longer arrive outside the CRM, mandatory fields hold real values, and no side spreadsheet is back in use. Until then the system is installed, not implemented. After that, each further process, such as service tickets or invoicing, is added as its own small project.
Keep reading
Related service
Custom CRM
A CRM built around your pipeline, connected to the tools you already use.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build. I reply within 24 business hours with a few targeted questions, then we walk through it on a free 30-minute call, with no commitment. You come away with a scope, a timeline and a fixed price - or a straight answer that it isn't worth building.