Before you start a CRM project

Map the process first

Write down the path from first contact to paid invoice and repeat business: who handles each step, what information they need, what they decide, and where that information lives today, whether in Excel, WhatsApp, a notebook or the accounting system.

Lead sources. Website forms, phone calls, WhatsApp, Facebook and Instagram lead ads, walk-ins, referrals.
Stages. Name them the way the team talks, and give each one an exit condition: “quote sent”, not “in progress”.
Handoffs. Sales to operations, operations to billing. This is where most information gets lost.
Exceptions. Cancellations, returns, quotes that change after approval. If the system cannot handle the exception, people go back to the spreadsheet.

Data sources and cleanup

List every place customer data lives today, and choose one source of truth per field. Billing details, for example, usually belong to the accounting system.
Choose the key that identifies a customer. In Israel it is often the mobile number, so store numbers in one format (+972…) rather than a mix of 050-… and 972….
Remove duplicates before the import, not after.
Keep required fields to a minimum. Every mandatory field slows data entry and fills up with placeholder values.
Record marketing consent and where it came from. Israel’s Privacy Protection Law and the anti-spam section of the Communications Law (section 30A) both apply to the data you hold and the messages you send.

Who uses it, and on what device

Field sales work on phones. If updating a deal takes more than a few taps on mobile, it will not get done.
Office and operations staff work on desktops with many records open, and need fast search, filters and bulk actions.
Managers need reports and alerts, not data entry screens.
Language matters: Hebrew, Arabic and English interfaces, right-to-left layout, and search that finds names written in more than one script.

Spend time with the people who will use it every day. Adoption is the project; the software is the means.

Integrations

WhatsApp. Use the official WhatsApp Business Platform (Cloud API), not unofficial tools that put the number at risk of being blocked. Conversations attach to the customer record, and messages sent outside the 24-hour customer service window use approved templates.
Website forms and lead ads. Forms post straight into the CRM with the source and UTM parameters. Meta and Google lead forms connect through their APIs instead of manual exports.
Accounting or ERP. With Priority, SAP Business One or an invoicing service, decide which system owns customers, products, prices and invoices, and which way each one flows.
Email and calendar. Google Workspace or Microsoft 365, so meetings and correspondence appear on the record.

For each integration, write down the trigger, the direction, the fields and what happens when it fails. Integrations fail silently unless someone designs the error path and decides who gets alerted.

Permissions

Decide who sees which customers: their own, their team’s, or everyone’s.
Limit export and bulk delete to a few roles. An export is the easiest way for a whole customer list to leave the company.
Protect sensitive fields such as margins, ID numbers and payment details at field level.
Keep an audit log of changes to records and settings.
Remove access on an employee’s last day, as part of the leaving process.

Decide the reports up front

List the numbers management looks at every week, then work backwards to the fields that have to be captured for them:

Conversion by lead source requires a source on every lead.
Time to first response requires a timestamp on the first reply.
Revenue per salesperson requires deals linked to invoices.

A report that depends on a field nobody fills in will be wrong, and people stop trusting the system.

Migrating history

Decide what moves. Active customers and open deals in full. Closed history can move in summary or stay in a read-only archive.
Map old to new. Old statuses to new stages, old fields to new ones, and what happens to values that have no home.
Run a trial import. Ask users to check their own accounts. They will spot problems no one else would.
Cut over cleanly. Make the old system read-only, run the final import, and keep the old data accessible for reference.

Roll out in phases

Phase one. Core records and the pipeline for one team, replacing their spreadsheet completely.
Phase two. Integrations that remove manual entry: forms, WhatsApp, accounting.
Phase three. Automation and reporting, once the data is reliable.

Train each role on its own data, and name one internal owner who decides on changes. Set a date to switch the old tool to read-only; running two systems in parallel invites double entry. After a few weeks, look at which fields stay empty and which steps get skipped. They show where the design does not match how people work.

Off the shelf, customised or built

An off-the-shelf CRM such as HubSpot, Salesforce, Zoho or monday.com fits when your process is close to standard. Configure it, do not fight it. A custom or heavily integrated system makes sense when the process itself is what sets you apart, when the CRM has to work closely with operations or ERP, or when per-user licensing does not fit how your team is structured.

Either way, the groundwork above is the same, and it is what a reliable estimate should be based on.

Where we fit

We map processes with the people who do the work, then build or integrate the system: CRM, WhatsApp through Engage or the Business Platform, website forms, and accounting or ERP connections. The mapping is useful even if you end up choosing an off-the-shelf product.

Talk to an engineer