Skip to content
DT Nova

How to choose a CRM: criteria, a scoring table and questions for vendors

Knowing how to choose a CRM protects a company from a familiar failure: a system the sales team quietly stops using. This guide covers the order of work, the selection criteria, a scoring table you can copy, total cost of ownership, the GDPR checks, when a custom CRM beats an off-the-shelf one, and the questions to ask CRM vendors.

Eurostat counts 28.51% of EU enterprises with ten or more staff using CRM software in 2025, up from 25.83% in 2023, and 14.72% buying CRM as a paid cloud service. The rest run their sales without one.

The short version

  • Describe your sales process before you look at a single product.
  • Choose on daily usability for the people who enter the data.
  • Check the tier you would really buy, not the top tier shown in the demo.
  • Compare five-year cost, migration and admin time included.
  • Make sure you can export everything and leave.

Start with your process, not with products

Write down, on one page, how a customer moves from first contact to paid invoice and repeat order: the stages, who does what at each stage, what information is needed, and which numbers management looks at each week. Then split your requirements into must-haves and nice-to-haves. Keep the must-have list short. A software requirements specification can be short and still do the job.

CRM selection criteria

  1. Process fit. Pipelines, stages and fields that match how you sell, without workarounds.
  2. Usability. How fast a salesperson logs a meeting or updates a deal, on desktop and mobile.
  3. Integrations. Email and calendar, accounting, the website forms, marketing tools, and a documented API.
  4. Reporting. The weekly numbers you steer by, built without exporting to spreadsheets.
  5. Data protection. EU hosting, a data processing agreement, access rights by role, deletion and export for individuals.
  6. Exit. Full export of contacts, deals, activities, notes and files in an open format.
  7. Total cost. Per-user prices, tiers, add-ons and price changes over five years.
  8. Vendor. Support in your language and time zone, product stability and roadmap.

A CRM scoring table you can copy

Score each shortlisted CRM from 1 to 5 per line, multiply by the weight, and add up. Agree the weights first.

CriterionWeightHow to test it
Process fit3Rebuild your real pipeline in the trial
Usability3Two salespeople log a week of real work
Integrations2Connect email, calendar and one key system
Reporting2Build your weekly sales report without help
Data protection2Read the processing agreement and subprocessor list
Exit2Run a full export and open it elsewhere
Five-year cost2Price your real user count and tier
Vendor and support1Open a support ticket during the trial

Use a test account with a small, pseudonymised data set rather than your full customer list until a contract and a processing agreement are signed.

Total cost of ownership

CRM prices are usually per user per month, and the list price is only one part of the decision. Put these lines into one five-year table for each candidate:

  • Subscriptions for every user who needs access, including occasional users.
  • The tier that contains the features you listed as must-haves, such as automation, custom objects or API access.
  • Add-ons for marketing, quotes or extra storage.
  • Implementation, data migration and integrations.
  • Training, and your own admin time each month.
  • Price changes at renewal, and the cost of leaving.

Our CRM development cost guide lays out the same five-year comparison for a custom CRM.

Custom CRM vs off-the-shelf CRM

Off-the-shelf is the right start for most companies with a common sales process. A custom CRM, or a custom layer around a bought one, pays off in a few clear cases:

  • The sales process is unusual: projects, contracts, field visits or bookings that a sales pipeline does not model well.
  • The CRM must be part of other systems, such as an ERP, a customer portal or your own product.
  • Many people need occasional access, and per-user pricing makes that costly.
  • You need the data model and the hosting fully under your control.

The wider method is in our build vs buy software guide.

GDPR and email rules to check

A CRM is mostly personal data. Under the GDPR, the vendor is your processor, so Article 28 requires a contract that binds it to your instructions and requires your authorisation before it brings in other processors. Check that the system can find and delete one person's data (Article 17) and export it in a structured, machine-readable format (Article 20). For email marketing, Article 13 of the ePrivacy Directive requires prior consent, with a narrow exception for your own customers and similar products or services, provided they can object easily each time. A CRM that records consent and objections per contact makes that rule practical.

If the CRM is a cloud service, the EU Data Act also helps at exit: switching charges are being withdrawn and may not be imposed at all from 12 January 2027 (Article 29).

Risks and how to avoid them

RiskWhat prevents it
The team stops using itUsability tested by real users, a short field list, one owner inside the company
Bad data from day oneClean and de-duplicate before migration, not after
Over-customisingChange the process where the product's way is fine
Costs creep upPrice the tier and add-ons you will need in year three
Lock-inFull export tested before signing, API access in your tier

When the off-the-shelf answer is right

  • Your sales process looks like most B2B or B2C pipelines.
  • Per-user licences at your real user count stay acceptable over five years.
  • The integrations you need already exist as standard connectors.
  • You need it working this quarter.

Questions to ask CRM vendors

  1. Which of our must-haves are in the tier we would buy, and which need a higher tier or add-on?
  2. What will we pay over five years for our user count, and how did prices change at the last two renewals?
  3. How do we export all data, including activities, notes and files?
  4. Where is the data hosted, and who are the subprocessors?
  5. What does the API allow, and what are its limits?
  6. How does the system handle consent, objections and deletion requests?
  7. What does implementation include, and who does it?

If your answers point to a CRM built around your process, see our custom CRM development service. Industry pages such as real estate CRM and construction CRM show how the needs differ by sector. Every guide is in the guides library.

Questions people ask

What should we look for when choosing a CRM?

A fit with how you actually sell, ease of daily use for the sales team, the integrations you need with email, calendar, accounting and the website, reporting on the numbers you steer by, full data export, EU hosting options and a clear data processing agreement. Price per user matters, but only over the whole life of the system.

What are the main CRM selection criteria?

Process fit, usability, integrations and API, reporting, data protection and hosting, data export and exit, total cost over five years, and the vendor's support and stability. Weight them before you look at products so the demo does not set the priorities for you.

Should a small business choose a custom CRM or an off-the-shelf CRM?

Most small businesses should start with an off-the-shelf CRM. A custom CRM pays off when the sales process is unusual, when the CRM must sit inside other systems you run, or when per-user licences for many occasional users cost more than owning the software.

How long does it take to choose a CRM?

A focused selection with written requirements, a shortlist of three, scripted demos and a trial with real data usually takes a few weeks. Skipping the requirements step is what makes it take months.

What questions should we ask CRM vendors?

Ask which of your must-haves the product covers in the tier you would buy, what the five-year cost is at your user count, how data is exported, where it is hosted and who the subprocessors are, what the API allows, and how pricing changed in recent years.

Sources