Web & Software

How to Choose the Right CRM System: Types, Core Functions and a Practical Selection Process

By ITCM Team · Updated October 2026

A CRM system is software that keeps every customer, lead, deal and conversation in one place so your sales, marketing and service teams work from the same facts. To choose the right one, map how your business actually sells and serves customers, turn that into a written requirements list, then score a short list of products against it in a real trial with your own data. This guide covers the types of CRM, the core functions to look for, a weighted scorecard, Arabic and local requirements for Saudi and Gulf businesses, integrations, total cost, migration, adoption and the red flags that usually predict a failed rollout.

What a CRM system does (in practical terms)

CRM stands for customer relationship management. For the full definition see what is a CRM; here we focus on what the system should do for your team day to day. A good CRM replaces scattered spreadsheets, personal phone contacts, WhatsApp chats and email threads with one shared record per customer, so anyone can see the history before they call.

Whatever the brand, the job is the same: capture every lead, move it through clear stages, remind people what to do next, and show managers what is really happening in the pipeline. If a system cannot do these basics simply, extra features will not save it.

• Contact and company management: one record per customer with history, owner, tags and documents.
• Lead capture: from website forms, phone calls, WhatsApp, email, events and ads, with source tracking.
• Sales pipeline: deals by stage, values, expected close dates and win/loss reasons.
• Activities and tasks: calls, meetings, follow-ups and reminders linked to each customer.
• Quotes and products: price lists, discounts and approvals, often handed to the accounting or ERP system for invoicing.
• Customer service: tickets or cases, response times and escalation.
• Marketing: segments, campaigns and basic email or message automation.
• Reporting: pipeline value, conversion by stage and source, team activity and forecasts.

Types of CRM: operational, analytical and collaborative

CRM products are usually described by three functional types. In practice most modern products combine all three, but knowing which one matters most to you tells you where to look hardest during evaluation.

A field sales team that lives in the pipeline needs operational strength first. A business with many customers and long histories gets more value from analytics. A company where sales, service, projects and finance all touch the same customer needs collaboration features and clean handovers.

Cloud vs on-premise, and off-the-shelf vs custom

Two other choices shape your options. Cloud (SaaS) CRM is hosted by the vendor and paid by subscription; it is fast to start and the vendor handles updates and infrastructure. On-premise or self-hosted CRM runs on servers you control, which gives more control over data location and customisation but makes you responsible for security, backups and upgrades.

The second choice is how much you adapt. Well-known platforms such as Salesforce, HubSpot, Zoho CRM, Microsoft Dynamics 365 and Odoo CRM can be used largely as they come or configured heavily. A fully custom CRM is built around your exact process. The deep dive on that decision, including cost and three-year total cost of ownership, is in our custom CRM development guide, so here is only the short version.

Step 1: map your process and write a requirements checklist

Most CRM projects fail before any product is chosen, because nobody wrote down what the system must do. Spend a few working sessions with sales, service and management drawing how a lead becomes a customer today: where leads come from, who qualifies them, what stages a deal goes through, what approvals exist, and where information gets lost.

Then turn that map into a short requirements list and split it into must-have, should-have and nice-to-have. Keep must-haves genuinely essential; a list of 80 must-haves eliminates every product and helps no one.

• Users and roles: how many users now and in two years, which teams, and who may see or edit what.
• Lead sources and channels: website, phone, WhatsApp, email, social, walk-ins, partners.
• Pipeline stages and rules: stage definitions, required fields, approvals and discount limits.
• Products, quotes and contracts: price lists, quote templates, and where invoices are issued.
• Service needs: tickets, response targets, after-sales follow-up.
• Reports managers need every week, written as actual questions the dashboard must answer.
• Languages, mobile use and offline needs for field teams.
• Integrations: website, email, telephony, WhatsApp, accounting or ERP, marketing tools.
• Data: what you will migrate, how clean it is and who owns it.
• Security and compliance: access control, audit log, backups, data location.

Arabic, RTL and local requirements for Saudi and Gulf businesses

An Arabic CRM is more than translated menus. Check that the interface itself is available in Arabic with proper right-to-left layout, that Arabic names and notes search correctly, and that quotes, emails and PDFs print Arabic text without broken letters. Language support differs between products and sometimes between editions, so test it in the trial rather than trusting a feature page.

If your CRM issues quotes that become tax invoices, remember that in Saudi Arabia invoices must come from a solution that meets ZATCA e-invoicing requirements, and businesses in the integration phase must connect that solution to ZATCA's FATOORA platform. Many companies keep invoicing in a compliant ERP or accounting system and pass the approved quote from the CRM to it. Either way, confirm the full path from quote to compliant invoice; our ZATCA e-invoicing integration guide explains the requirements.

Data location matters too. Saudi Arabia's Personal Data Protection Law, overseen by SDAIA, has been in force since September 2023 and sets conditions for transferring personal data outside the Kingdom. Government entities and regulated sectors may face stricter hosting rules from the National Cybersecurity Authority or their sector regulator. Ask each vendor where your data is stored, whether an in-Kingdom or regional hosting option exists for your edition, and get the answer in writing; if your sector is regulated, check with your compliance team.

• Full Arabic interface with right-to-left layout, not only Arabic data entry.
• Bilingual records where needed: Arabic and English names for companies and contacts.
• Saudi and Gulf phone formats (+966 and others), national address fields and city lists.
• Hijri date display if your customers or contracts use it.
• WhatsApp Business integration if that is where your customers talk to you.
• Quotes in SAR with VAT shown correctly, and a clear handover to a ZATCA-compliant invoicing system.
• Written confirmation of data hosting location and backup location.

Integrations: where most of the value (and effort) sits

A CRM that does not talk to your other systems becomes another place to type the same data. List every system that creates or needs customer data and decide, for each one, which system is the master record and which way data flows.

For each integration, ask whether it is a native connector, a third-party connector with its own fees, or custom work through the CRM's API. Ask about API limits on your edition, because some products restrict API access or call volumes on lower plans. If the CRM must sync with an ERP, define what syncs (customers, products, prices, orders, invoices, payment status) before you sign.

• Website forms and landing pages, with UTM or source tracking.
• Business email and calendar (Microsoft 365 or Google Workspace).
• Telephony or call centre, with call logging and recordings.
• WhatsApp Business and other messaging channels.
• Accounting or ERP system for customers, products, invoices and payments.
• Marketing and advertising platforms for audiences and conversions.
• Single sign-on and user management, if you already use it.

The CRM evaluation scorecard

Once you have two to four candidates, score them on the same criteria with agreed weights. Weights reflect what matters most to your business, so adjust them, but agree them before demos start so the most polished salesperson does not decide for you.

Score each criterion from 1 to 5 based on evidence from the trial, multiply by the weight and add up the totals. A large gap in one critical area, such as Arabic support or a key integration, should rule a product out even if its total is high.

Total cost: look beyond the price per user

Subscription prices change often and depend on edition, billing period and add-ons, so compare quotes you receive in writing rather than published list prices. More importantly, the licence is usually only part of the cost. Setup, data migration, integrations, training and the time someone spends administering the system often add up to more than the first year of licences.

Check which features you need sit in which edition, because automation, advanced reporting, API access and extra storage are often reserved for higher tiers. Ask what happens to the price when you add users or move editions. For a structured three-year comparison of SaaS against a custom build, use the method in the custom CRM development guide rather than guessing.

Run a real trial or pilot

Demos show the vendor's best path; a pilot shows yours. Set up the shortlisted product with your real stages, a sample of your real data and three to five users from different roles, and give it two to four weeks of normal work.

Write test scenarios in advance and score them, for example: a WhatsApp lead arrives, is assigned, qualified, quoted and won; a manager pulls the weekly pipeline report; a customer complaint becomes a ticket and is closed. Record where users got stuck, because that is where adoption will fail later.

• Use real but limited data, and agree how test data will be removed afterwards.
• Include at least one sceptical user, not only enthusiasts.
• Test on mobile phones in the field, not only on a desktop in the office.
• Test one critical integration end to end.
• Test exporting your data, so you know you can leave if you need to.

Data migration and adoption

Migration is where hidden effort lives. Clean the data before you move it: remove duplicates, standardise phone numbers and company names, decide which old records are worth bringing, and map every old field to a new one. Do a trial import, check it with the people who own the data, then plan the final cut-over for a quiet period.

Adoption needs as much planning as the technology. Name an owner for the CRM inside the business, train each role on its own daily tasks, and make the CRM the only source for pipeline reviews and reports so people have a reason to keep it updated. Start with the essentials and add automation once people are using the basics every day.

Red flags when choosing a CRM

Some warning signs appear again and again in failed CRM projects. If you see several of them, slow down and ask more questions before you sign anything.

• No written requirements, so the choice is driven by demos and sales pressure.
• The vendor will not run a trial with your data or your scenarios.
• Arabic support is promised but cannot be shown working in right-to-left in the actual product.
• Key features or API access sit in an edition far above the one you were quoted.
• No clear, written answer on where data is hosted and backed up.
• No full data export, or export only through paid services.
• Long contract lock-in with steep price increases at renewal and no exit terms.
• Customisations promised by a partner with no examples, no documentation and no plan for upgrades.
• Management expects the CRM to fix a sales process that nobody has defined.

When a custom CRM makes more sense, and how ITCM can help

If your evaluation keeps ending in workarounds, or the products that fit cost more over three years than building, a custom CRM may be the better route. Typical signals are unusual processes such as real estate units, project-based sales or multi-company structures, heavy integration needs, or strict data location requirements.

ITCM can help you write the requirements, run a neutral comparison, or design and build a custom CRM in stages. Every service starts from $100, bigger builds are quoted per project, the price is agreed first and there is no advance payment: you pay after you have seen and reviewed the work. You can start with a free initial consultation.

Frequently asked questions

What is the main function of a CRM?

The main function of a CRM is to keep all customer information and interactions in one shared system so teams can manage leads, follow up on deals, serve customers and report on performance from the same data instead of separate spreadsheets and inboxes.

What are the three types of CRM?

The three common types are operational CRM, which runs daily sales, marketing and service work; analytical CRM, which turns customer data into reports, segments and forecasts; and collaborative CRM, which shares customer context across departments and channels. Most modern products combine all three.

Is there a CRM in Arabic?

Yes. Several major CRM platforms offer an Arabic interface with right-to-left layout, and custom CRMs can be built bilingual from the start. Support varies by product and edition, so test the Arabic interface, search and printed quotes during a trial before you decide.

How long does it take to choose and set up a CRM?

For a small or medium business, requirements, shortlisting and a pilot typically take a few weeks, and setup with migration and training can take from a few weeks to a few months depending on integrations and data quality. These are typical ranges and vary with scope.

Should a CRM issue invoices in Saudi Arabia?

It can, but any tax invoice must come from a solution that meets ZATCA e-invoicing requirements, including FATOORA integration for businesses in the integration phase. Many businesses issue quotes in the CRM and invoices in a compliant ERP or accounting system connected to it.

Cloud or on-premise CRM: which is better?

Cloud CRM is faster to start and the vendor handles infrastructure and updates. On-premise or self-hosted CRM gives more control over hosting and data location but makes you responsible for security, backups and upgrades. Choose based on your data location needs, IT capacity and budget.

What is the difference between CRM and ERP?

A CRM manages customer-facing work such as leads, deals, service and marketing. An ERP manages internal operations such as accounting, inventory, purchasing and HR. Many businesses use both and integrate them so customer, order and invoice data flow between them.

Related reading & services

• Custom CRM development services
• Custom CRM development guide (build vs buy, cost)
• What is a CRM?
• ZATCA e-invoicing integration guide
• Custom software vs off-the-shelf
• Odoo vs custom ERP

← All articles