What is CRM? Definition, meaning & examples

CRM definition (plain English)

A CRM system is a central database + workflows for everything related to customer relationships: contact data, communication, deals, orders, support history, and segments. The real value: your team sees one truth and can automate follow-ups.

What is a CRM used for?

Six jobs a CRM actually takes over. If none of them sound familiar, you do not need one yet — that is a valid outcome.

1. Deduplicating contacts. Three email addresses belonging to the same person become one record, so history stops fragmenting.
2. Storing conversations. Email, chat, call notes and tickets sit under the same customer, whoever handled them.
3. Guarding follow-up. Every promise gets an owner and a date instead of living in someone’s head.
4. Telling customers apart. Segments based on order behaviour, open complaints or contract value decide who you help first.
5. Making handovers possible. A colleague, a stand-in or a new hire reads the history back instead of interrogating the customer again.
6. Surfacing patterns. Repeat questions, return reasons and customers going quiet only surface when you log them.

What a CRM does not do: sell for you, decide your process, or repair bad agreements. It records what happens and makes visible what does not.

What are the four basic principles of CRM?

The four principles almost every CRM course falls back on come from the IDIC model by Don Peppers and Martha Rogers: identify, differentiate, interact and customise. They describe a sequence rather than software — you cannot personalise what you never recognised.

1. 1. Identify

   Knowing who is reaching out. An address linked to a customer record is a customer; a loose address in an inbox is a stranger. This is the step most often left half-finished: the same person exists three times under three addresses.

2. 2. Differentiate

   Separating customers by value and by need. Someone ordering weekly represents a different stake than a one-off buyer, and a customer with an open complaint has a different need than one with a routine question.

3. 3. Interact

   Recording every contact in one place, whatever the channel. A conversation that starts in chat and ends in email should be one history. Without this step the next one is impossible.

4. 4. Customise

   Adapting treatment to what steps 1 through 3 taught you: a different response window, a different offer, a different tone. Customisation here is not the same as pasting a first name into a subject line.

Other sources count differently — you will also see the four R’s (relationship, retention, referral, recovery) or four pillars such as people, process, data and technology. The sequence stays the same in every variant: know who someone is before treating them differently.

CRM software vs CRM tools vs CRM system

Customer Relationship Management (CRM) in practice

CRM isn’t about “more data”—it’s about better decisions: who needs attention, who’s at risk of churn, which issues repeat, and which segments repurchase. In ecommerce, CRM should connect to support: tickets, chat, and order context.

What does a CRM system deliver?

The gain is rarely “more overview”. It’s in the moments where someone still has to go looking. An agent who opens an email and immediately sees the last order, the open ticket and the earlier complaint doesn’t have to ask what the customer already explained.

A caveat: a CRM won’t fix a messy process. If you log nothing today, tomorrow you’ll log mess — only faster.

Is Excel a CRM tool?

For one person with fifty customers: fine. A spreadsheet with a name, last contact and a note works for years. It breaks on three points, and always in this order.

• The second user. Two people in one file means overwriting, or two versions drifting apart.
• The history. A cell shows the latest state, not what was agreed last month. That’s exactly what you need during a complaint.
• The follow-up. A spreadsheet reminds you of nothing. Promises then live in your head or your inbox.

So switch when you feel that pain, not because a spreadsheet is somehow “unprofessional”. If it still works: keep it.

What is an example of a CRM system?

The best-known names are Salesforce, HubSpot, Microsoft Dynamics 365, Pipedrive and Zoho. They differ less in features than in what they’re built around: Salesforce and Dynamics target large organisations with dedicated admins, HubSpot and Pipedrive target sales at smaller teams, Zoho offers a broad suite at a low price. SamDesk sits elsewhere — customer contact and support as the starting point, not the sales pipeline.

There is no “number one”. There’s a system that fits how your team works. A support team handling questions gains little from a ten-stage sales pipeline, and a sales team gains little from response-time targets.

Which CRM systems exist? Ten well-known names

A top 10 ranked by “best” does not exist, because the answer changes per team. What does exist is a list of systems you will meet on almost any shortlist, together with what each one is built around. Read it as a sorting list, not a ranking.

The top 5 that lands on nearly every shortlist

Ask ten companies which CRMs they evaluated and these five come back nearly every time. That says something about market reach and marketing budget, not about which one is best for you. So the third column mainly tells you when to rule each one out.

These five share one trait: they are designed around selling. If your day is driven by inbound customer questions, a support-first option such as SamDesk is the fairer comparison.

Ten names you will meet on any shortlist

1. Salesforce — the reference for large organisations. Almost everything is configurable, which is exactly why you need someone to administer it.
2. HubSpot — sales and marketing in one suite, popular with growing teams. Entry is light; cost climbs once you stack hubs.
3. Microsoft Dynamics 365 — the logical pick when your organisation already runs on Microsoft and CRM and ERP need to sit close together.
4. Zoho CRM — a broad suite at a low price. Many modules, which means deciding which ones you will not switch on.
5. Pipedrive — built around the sales pipeline. Strong when deals are the work, thin as soon as support is the work.
6. Freshsales — the CRM in the Freshworks family, attractive if you already run Freshdesk for support.
7. Odoo — open source, with CRM as one module beside stock, invoicing and webshop. Attractive if you want one package, heavier to configure.
8. Teamleader — a Dutch-Belgian player combining CRM, quotes and invoicing for SMBs and agencies.
9. SuperOffice — a Northern European vendor with CRM and service combined, common in B2B services.
10. monday CRM — CRM on top of a work-management platform. Flexible to shape, but you build what comes standard elsewhere.

The most-used CRM is a different question from the best one. Market overviews usually name Salesforce as the largest vendor, with Microsoft, HubSpot and Zoho behind it. For a team of five that tells you little: those figures are dominated by enterprise contracts that have nothing to do with how you handle your inbox.

Which free CRM systems are there?

Several vendors offer a free entry tier — HubSpot, Zoho and Bitrix24 among them — and Odoo can be self-hosted as open source. Limits and terms change regularly, so check them with the vendor before you put customer data anywhere. On a free plan, watch three things in particular:

• The user count. Free often stops exactly where your second colleague starts.
• The export. Can you pull out contacts and history in one go? If not, free is a one-way street.
• The integrations. Connections to your shop or inbox usually sit just above the free line — and that is exactly where the gain lives.

Looking for a free starting point for customer questions rather than for sales? See the free ticket system and free helpdesk software.

CRM or ERP: what’s the difference?

In short: a CRM looks outward, an ERP looks inward. The CRM covers the customer relationship — conversations, tickets, agreements, follow-up. The ERP covers operations — stock, purchasing, invoicing, accounting and sometimes HR.

Most companies eventually need both, but rarely at the same time. If the pain is customers slipping away or questions going unanswered, start with the CRM. If it’s stock that doesn’t match or invoices going wrong, the ERP comes first.

What does a CRM system look like in practice?

Three situations you’ll meet in almost any shop or service business, and what the CRM actually does there.

Which CRM features does a support team actually need?

• One customer view: contact + orders + tickets + conversations
• Workflows: ownership, SLAs, escalations, follow-ups
• Segmentation: VIP, return risk, churn signals
• Knowledge + templates: consistent replies, less repetition
• Measurement: FRT/TTR/CSAT + retention (not just “activity”)

What types of CRM exist? (operational / analytical / collaborative)

CRM implementation in 14 days (without a months-long migration)

1. Days 1–3: data model (contact fields), tags, basic segments.
2. Days 4–7: integrations (store + inbox), templates, workflows (ownership + SLA).
3. Days 8–14: dashboards + QA: measure FRT/TTR/CSAT and retention signals.

Moving existing customer data? See our guided CRM migration.

SamDesk vs classic CRMs (where support feels the difference)

Many CRMs (think HubSpot/Salesforce/Pipedrive) are built for sales. In ecommerce support, you need something else: order context next to the conversation, ticket history, and templates/workflows that reduce response times.

FAQ: what is CRM?