Choosing a CRM for a Regional B2B Sales Team: A Requirements List

Most CRM checklists are written for a sales team that works by email, in English, with one currency and a simple pipeline. Many B2B sales teams in Riyadh, Dubai or Cairo work differently. The first contact often arrives on WhatsApp, the customer’s legal name is in Arabic, the deal passes through a consultant, a contractor and a procurement department, the quotation goes through several revisions, and part of the volume is sold through distributors who never log in to anything.

Choosing a CRM on feature lists and demo polish is how companies end up with a system the sales team avoids and management cannot trust. This guide gives you a vendor-neutral requirements list built around how regional B2B sales actually runs, plus the data-location questions to put to every vendor under the Saudi, Egyptian and UAE data protection laws.

Map how you sell before you look at any system

We would write the sales process down on one page before the first demo. Without it, every vendor shows you its own idea of a pipeline, and you end up judging presentations rather than fit. For most regional B2B companies the map includes some version of these stages:

1. Inquiry: WhatsApp message, call, website form, exhibition scan, referral or tender notice.
2. Qualification: is this a real project, who is the end client, who decides, and is there a deadline?
3. Technical stage: site visit, technical submittal, samples, approvals from the consultant.
4. Quotation and revisions: often several versions as scope, quantities or brands change.
5. Tender or pre-qualification, where the deal runs through a formal process with fixed dates.
6. Purchase order, delivery and invoice.
7. After-sales: maintenance contracts, renewals, repeat orders.

Next to each stage, note who does the work (sales, presales engineer, estimator, management, a distributor), which channel they use and which document leaves the company. That page becomes the scoring basis for every vendor. If you cannot agree internally on what “qualified” means, solve that first: a CRM records a process, it does not invent one. When RX became the marketing department for Azeidk, a contracting and electromechanical company working across Saudi Arabia and Egypt, every request was being handled on its own: a post here, a proposal there, an offer on WhatsApp. Part of the fix was a WhatsApp inquiry flow that moves from the first message to a site visit, which is exactly the kind of stage a process map has to name before any system can record it. Our diagnosis of why leads never turn into customers covers the most common break points.

The requirements list

Mark each line Must, Should or Not needed for your business. The third column is what to ask the vendor to show you live, with your own data, not on slides.

WhatsApp: check which product the integration uses

The free WhatsApp Business app is built for a person on a phone. When to move from the app to the Platform is a separate decision; here the point is what the CRM must support once you do. CRM integration runs on the WhatsApp Business Platform, which WhatsApp describes as a way to “integrate with popular back-end systems like CRM and marketing automation platforms”, set up either through a partner or by direct integration. When a vendor says “WhatsApp integration”, ask exactly which product it connects to and who holds the account.

The Platform rule that matters most for the CRM: per Meta’s pricing documentation, free-form replies are allowed only within a 24-hour window opened by the customer’s message, and outside it only approved templates can be sent. So add template management inside the CRM, a visible warning on the window and reporting on message volumes by category; what those messages cost is covered in WhatsApp Business API pricing after the October 2026 changes.

Also ask where opt-in is recorded. WhatsApp’s Business Messaging Policy requires opt-in before you message people and requires you to honour every opt-out request, and the data protection laws below add their own consent rules for marketing. The consent date and source should sit on the contact record, not in someone’s memory.

Arabic: test it, do not take it on trust

“Supports Arabic” can mean anything from a translated menu to full right-to-left layouts. Test what your team will do every day: type Arabic names into every field, search for them with common spelling variants, sort a list that mixes Arabic and English names, and generate a PDF. Check that phone numbers in Saudi (+966), UAE (+971) and Egyptian (+20) formats are matched to the same contact whether they were typed with or without the leading zero, because duplicate contacts quickly destroy trust in CRM reports.

We recommend storing each company’s Arabic legal name and English trading name as separate fields. The legal name is what you will need on contracts and tax invoices; the trading name is what your team calls them.

Where the CRM ends and e-invoicing begins

Decide early which system issues the tax invoice, because all three markets now regulate electronic invoices and the answer changes your requirements.

• Saudi Arabia. ZATCA’s e-invoicing (FATOORAH) generation phase has applied to resident taxpayers since 4 December 2021; the integration phase, under which e-invoicing solutions connect to ZATCA’s systems, has been rolled out in waves since 1 January 2023 (ZATCA).
• UAE. The B2B and B2G e-invoicing system goes live on 1 January 2027 for businesses with revenue of AED 50 million or more, followed by 1 July 2027 for businesses below that threshold and 1 October 2027 for government entities (KPMG). The deadline for the largest businesses to appoint an accredited service provider was extended to 30 October 2026, but the 1 January 2027 go-live was kept (Deloitte Middle East). Check the Ministry of Finance’s current announcements, as dates have moved before.
• Egypt. VAT-registered businesses must submit B2B invoices through the Egyptian Tax Authority’s portal or API, where they are validated and given a unique identifier before they are issued (Avalara, October 2026).

For most companies, the cleanest answer is that the CRM handles quotations and the accounting or ERP system issues invoices. In that case the requirement is a reliable handover: the accepted quotation, customer legal name, address and VAT or tax registration number should pass to the invoicing system without retyping. Our guide to quotations and proposals covers the customer details to collect at quotation stage. If a vendor proposes that the CRM issues invoices itself, ask for evidence that the invoicing module meets the rules in each country where you invoice, and confirm with your tax adviser. Check the current rules before you sign; phases and thresholds change.

Data location and transfer: the questions to ask every vendor

A CRM holds personal data: names, mobile numbers, WhatsApp conversations, sometimes ID copies for vendor registration. Many cloud CRMs store or process it outside your country, so cross-border transfer rules can apply. What that means for the vendor contract, in summary (planning notes from the sources linked, not legal advice; confirm with a lawyer):

• Saudi Arabia. Under the PDPL, enforceable since 14 September 2024, transfers abroad need a safeguard such as SDAIA’s standard contractual clauses, and those clauses differ from the EU’s, so an EU-style agreement may not be enough (CMS; Clyde & Co). How the law treats marketing messages is covered in our PDPL direct-marketing guide.
• Egypt. Clyde & Co reports full enforcement of Law No. 151 of 2020 from 31 October 2026, with transfers abroad needing approval from the Personal Data Protection Centre and the data subject’s consent; licences are also required for direct electronic marketing (Clyde & Co, January 2026).
• UAE. Federal Decree-Law No. 45 of 2021 sets the cross-border rules, but an entity in a free zone with its own regime, such as the DIFC, may fall under that instead or as well (UAE Government portal). Ask your lawyer which regime applies to each entity.

Put these questions to every vendor in writing and keep the answers with the contract:

1. In which countries is our data stored at rest, and can we choose the region?
2. Where is it processed, including backups, support access and AI features?
3. Which sub-processors handle our data, and where are they based?
4. Will you sign standard contractual clauses or a data processing agreement that covers Saudi, Egyptian and UAE requirements?
5. How do you support consent records, withdrawal of consent and deletion requests?
6. How quickly will you tell us about a breach? According to Clyde & Co, Egypt’s rules require breaches to be reported to the regulator within 72 hours, so your vendor’s notice period needs to be shorter.
7. Where does WhatsApp message data sit once it reaches your system?
8. Can we export everything and have it deleted when we leave?

On question 7, remember that WhatsApp messages also pass through Meta. Meta offers a local storage option for message content at rest in selected countries, but its documentation states that contact-book data is hosted in Meta’s data centres regardless of that setting, and that message content may be held in data centres outside the selected region for a short period during processing. The CRM’s data location is therefore only part of the picture.

Run a scripted demo with your own scenarios

Vendors demo their strongest flows. Send each shortlisted vendor the same three or four scenarios a week ahead and ask them to run them live. For example, a hypothetical fire-safety distributor might use:

• A WhatsApp inquiry in Arabic arrives at 9pm, is assigned the next morning, becomes an opportunity and gets a bilingual quotation.
• A consultant rejects the specified brand; the salesperson issues revision two with an alternative and the manager approves a discount above the salesperson’s limit.
• A distributor registers a project that a direct salesperson is already quoting.
• The CEO asks for this month’s pipeline by country, source and stage, in one view.

Score each scenario against your process map, then ask two of your salespeople, not only managers, to try the shortlisted system with a copy of real data. Their reaction is a better guide to adoption than any feature count.

What makes the system stick after go-live

A CRM fails less often on features than on habits. Before launch, agree written definitions for each stage and for a qualified lead, decide which fields are mandatory (keep the list short), and set one rule that management enforces: if a deal is not in the CRM, it does not appear in the forecast. Prepare WhatsApp templates, quotation layouts and follow-up messages in both languages before the system goes live, so the sales team finds it faster than its old way of working.

Professional recommendation: the mandatory fields by stage

Hand this table to every vendor as part of the configuration brief. A deal cannot move to the next stage until the fields on its row are filled. Keep it to these few fields; anything else stays optional.

That preparation is mostly sales communication rather than software. At RX Designer, CRM direction and customer-journey mapping sit inside our business solutions and sales enablement work: the process map, the stage definitions and field list above, and the WhatsApp flows, proposals and quotation content a CRM needs to carry. We stay vendor-neutral: the requirements come from your process, not from a product.