How to choose a CRM: a practical framework for buyers in Saudi Arabia and the Gulf

Start with your process, not a feature list

The most common buying mistake is comparing vendors' feature grids. Almost every CRM lists deal management, reporting and automation; the differences that matter sit in the details of how your team actually sells. Before you book a single demo, write one page that answers these questions:

1. Who sells and who serves customers? Headcount today and in twelve months, and each person's role.
2. Where do customers come from? WhatsApp, phone, the website, paid ads, exhibitions, referrals.
3. How long is the sales cycle, and how many deals does each rep carry per month?
4. What happens after the win? A project, a delivery, a recurring subscription?
5. Where is the tax invoice issued today, and where should it be issued tomorrow?
6. Which systems must the CRM talk to? Mail, calendar, accounting, telephony.

Send this page to every vendor ahead of the demo and ask them to run your scenario, not their prepared script. How they respond is itself a data point.

Turn needs into requirements you can test

Sort each requirement into must-have (no deal without it), important (decides between finalists) and nice-to-have (pleasant, never decisive). Then write a test for every must-have, because a phrase like “supports WhatsApp” can mean very different things from one vendor to the next.

Arabic: test beyond the translated menus

Many products claim Arabic support; the gap between real and cosmetic support shows in the details. During the trial, check these yourself:

• Coverage: are all screens, settings and system messages in Arabic, or do English strings appear halfway through a task? Is the Arabic clear Modern Standard Arabic?
• True right-to-left: tables, arrows, calendars and drag-and-drop boards should mirror, not just the text.
• Customer documents: generate a quote and an invoice for a customer with an Arabic name and check the PDF for joined letters, correct table direction and readable amounts.
• Bilingual setup data: can pipeline stages and loss reasons carry Arabic and English names so each user sees their own language?
• Arabic search: look up a customer using the common spelling variants of their name, and try compound names.
• Dates, digits and the work week: do you need Hijri dates in documents or reports? Does the calendar treat Friday and Saturday as the weekend? Which digit style do your customers expect?

Ask an Arabic-speaking rep to run a full working day on the system during the trial. Their notes will be more honest than any demo.

WhatsApp: how the connection works and what Meta allows

In Saudi Arabia WhatsApp is often the first channel a customer reaches for, so understand how a CRM connects to it before judging its screens. Systems built for teams usually run on the WhatsApp Business Platform, either directly through Meta or through a solution provider, and that choice affects who owns the number and who pays Meta's messaging charges.

Whatever the vendor, Meta's rules are the same. The WhatsApp Business Messaging Policy lets you contact only people who have given you their number and opted in, and obliges you to honour every request to stop. Each inbound message from a customer opens, or restarts, a 24-hour customer service window: inside it you can reply freely, and outside it you can send only pre-approved message templates. Ask the vendor:

• Is the number registered to our business account or to yours? What happens to it if we leave?
• Who pays Meta's fees, and do they appear on your invoice or are they billed to us directly?
• Does the agent see when the window has closed, and is the agent steered to an approved template?
• Is there a shared inbox with assignment, and can a chat become a deal in one step?
• Where are templates written and submitted for approval, and how do they reach the CRM?
• Are broadcasts supported, and how are opted-out contacts excluded?

E-invoicing: decide where the tax invoice is issued

ZATCA rolled out e-invoicing in two phases: the generation phase from 4 December 2021 and the integration phase from 1 January 2023, applied to taxpayers in waves that ZATCA announces. Integration is more than producing a structured file. Under ZATCA's detailed guidelines, the invoicing solution must be onboarded to the Fatoora platform with a cryptographic stamp identifier; standard tax invoices between businesses are sent for clearance before they reach the buyer, and simplified invoices to consumers must be reported within 24 hours of issue.

So the first question is not “does the CRM support ZATCA?” but “which system will issue our tax invoices?” There are two common patterns:

Personal data protection: questions not to skip

When you keep customer data in a cloud CRM, your business is usually the controller, deciding why and how the data is processed, and the vendor is a processor acting on your behalf. SDAIA's guide to the Personal Data Protection Law states that a controller must ensure the processors it engages comply with the law. Choosing a vendor is therefore part of your own compliance.

• Individuals' rights: can you fulfil a customer's request to access their data, receive a copy in a readable format, correct it or have it destroyed, without engineering help from the vendor?
• Data minimisation: can you hide sensitive fields from roles that do not need them, and avoid collecting what you do not need at all?
• Retention: can old records be deleted or destroyed once their purpose has ended?
• Accountability: can every change be traced to a named user and a time? Is two-factor authentication available?
• Location and transfers: ask where the data is hosted and on what legal basis, because transferring personal data outside the Kingdom is governed by a separate regulation under the law.
• Exit: will you get a complete, usable export if you switch, and what happens to your data after cancellation?

Do not stop at certification badges. Ask for the documents, read the data processing terms in the contract, and remember that regulated sectors such as healthcare and finance may add rules of their own.

Integrations: ask about data direction, not logo counts

A marketplace page full of logos says little. The integration that matters moves specific data, in a known direction, on a known schedule. For each must-have, ask four questions: what moves, which way, how often, and who fixes it when it breaks?

Test every must-have integration during the trial with your own accounts, not in the vendor's demo environment.

Pricing models and total cost of ownership

The monthly licence price is rarely the real cost. Before comparing, work out a three-year total for each option.

Then add setup and migration fees, the team's training time, any paid middleware the integrations need, VAT and the billing currency. A cheaper licence can cost more overall if every change needs a consultant.

A two-week trial checklist

A free trial is not for browsing screens; it is for proving the must-haves. Here is a two-week plan:

1. 1

   Day 1: real data

   Import 200 real contacts with their custom fields and note how much cleaning the import needed.

2. 2

   Day 2: channels

   Connect a mailbox, the WhatsApp Business number and a calendar, then send and receive real messages.

3. 3

   Days 3 to 7: live deals

   Two reps run their actual deals only in the new system, from first contact to quote.

4. 4

   Permissions

   Log in as a rep and confirm they cannot see what they should not, then log in as a manager and compare.

5. 5

   Reporting

   Ask the sales manager to answer three weekly questions from the system alone.

6. 6

   Documents

   Create an Arabic quote and check it on a phone and as a PDF.

7. 7

   Support

   Send a real question to support in Arabic and rate the speed and accuracy of the answer.

8. 8

   Exit

   Export everything and open the file. Is it complete and usable elsewhere?

A weighted scorecard for the shortlist

Score each finalist from 1 to 5 on every criterion and multiply by the weight. These weights are a starting point; adjust them to your priorities.

How Naffes CRM measures up

Since we publish this guide, it is only fair to apply the framework to ourselves, limits included:

• Arabic: the Naffes CRM interface opens in Arabic, right-to-left. Every translation key in the interface exists in both languages, with automated tests that catch a missing one, and pipelines, stages, loss reasons and lead sources can carry names in both. One known gap: most labels in the web-form builder still appear in English.
• WhatsApp: runs through your own Twilio account. Conversations land in a shared inbox where a rep claims a thread or a colleague assigns it by hand; there is no automatic round-robin. The composer shows the state of the 24-hour window, and approved templates import in one click. There is no direct WhatsApp Cloud API connection, and templates are written and submitted for approval in Twilio, not inside Naffes.
• Access control: four built-in roles plus custom ones, field hiding per role, an audit log of who did what and when, and two-factor sign-in that each user switches on for their own account. Workspace admins cannot enforce it for the team.
• Data and exit: contacts, companies and deals export to CSV or Excel, and the owner can pull the workspace's core tables as one JSON file. That file leaves out attachments, tickets, invoices and emails, so plan to move those separately.
• Pricing: prices are published on the pricing page and billed in Saudi riyals. There is a free plan, and the 14-day full-feature trial asks for no card.
• Limits to know: one currency per workspace, an internet connection is needed to view records, and the mobile experience is an installable web app (PWA) rather than a store app.

If e-invoicing is part of your decision, put us through the same e-invoicing test as every other vendor, and settle which system will issue your tax invoices before you sign. To see how channels come together, read about the unified inbox and WhatsApp CRM, and to understand what you will manage every day after choosing, see our guide to sales pipeline management.

Questions

Sources

1. SDAIA: Guide to the Saudi Personal Data Protection Law for Controllers and ProcessorsAccessed 2026-09-28
2. ZATCA: E-InvoicingAccessed 2026-09-28
3. ZATCA: Detailed Guidelines for E-Invoicing (Version 2)Accessed 2026-09-28
4. WhatsApp Business Messaging PolicyAccessed 2026-09-28
5. Meta for Developers: WhatsApp service messages and the customer service windowAccessed 2026-09-28