Four questions that get a CRM shortlist down to three

There are more than twenty credible CRMs a company here could buy, and a feature matrix will tell you that most of them do most of the same things. That is true and useless. Feature parity is why shortlists built from comparison sites end up as a list of the best-marketed products rather than the ones that will work.

Narrowing is an elimination exercise. Four questions do most of it, and they are worth asking in this order, because each one removes more options than the one after it.

How it usually goes

1. 01Start from the three names everyone has heard of
2. 02Book demos, watch the rehearsed version
3. 03Compare feature grids that mostly agree
4. 04Pick on price, or on who presented best
5. 05Discover the constraints after signature

How it should go

1. 01Start from what the tier your requirements force actually costs
2. 02Check what it has to integrate with, and whether that connector is real
3. 03Weigh the complexity your team will absorb against what it will not
4. 04Ask who can implement and support it here
5. 05Take three to demos, scripted against your own process

1. What does the tier your requirements force actually cost?

Entry prices are close to meaningless, because the requirement that matters is rarely on the entry tier. Single sign-on, API access beyond a low call ceiling, custom objects, sandbox environments and role-based permissions are routinely the things that move a buyer two tiers up the page, and the jump between tiers is usually larger than the difference between vendors.

Price the tier that covers your actual requirement list, for the seat count you will have in year two, over three years. That number bears very little relationship to the one on the pricing page, and it reorders shortlists more often than any other single input.

2. What does it have to talk to, and does that connector exist?

Every CRM has an integrations page. The page is marketing. What you need to know is narrower:

• Does a native connector exist for the specific systems you run, or only for the market-leading product in that category?
• If it runs through a middleware layer, who pays for that layer and who maintains it when it breaks?
• Which system owns the customer record once both are live? Two systems that can both write the same field will eventually disagree, and deciding that in advance is cheaper than discovering it from an invoice sent to an old address.

A connector listed on a marketplace is not the same as one that works at your volume, with your fields, maintained by someone who answers support tickets. Ask for the integration to be demonstrated with your own data shape.

3. How much complexity will the team actually absorb?

This is the constraint most often skipped, and it decides more rollouts than feature coverage does. A powerful platform configured for how management describes the process, rather than how the team actually sells, gets worked around. People keep the real pipeline in their own notes and update the CRM on Friday from memory. The data degrades, the reports stop being trusted, and within a year the tool is a cost with a login page.

The useful question is not which system can model your process. Most can. It is how much configuration the answer requires, who maintains that configuration, and whether the people entering data every day will find it faster than what they do now. If it is slower for them, it will lose, regardless of what it does for the people reading the reports.

4. Who can implement and support it here?

This is the one a global comparison site genuinely cannot see, because implementation capacity is regional and review sites are not.

Several major platforms reach this market through partners rather than through the vendor's own delivery team. Where the partner market for a platform is deep, you have options: you can change partner without changing system, and you can get someone into the building. Where it is thin, you are flying people in, paying for it, and waiting on their calendar every time something breaks.

So shortlist three product and delivery pairs, not three products. Ask for a reference at your size, in this region, with the specific partner who would do your implementation, rather than a case study on the vendor's website.

Where sector requirements come in

Some companies carry requirements that override all four questions, and they should establish that before anything else. Regulated activity in health, financial services and parts of real estate can bring data handling obligations that rule platforms out on their own. Saudi Arabia's PDPL has been fully enforceable since 14 September 2024, the UAE layers a federal regime alongside the separate DIFC and ADGM rulebooks, and a parent company's own policy can impose more than any regulator does.

For most private companies buying a CRM, none of that is the binding constraint, and treating it as one narrows the field for no reason. The way to find out is to ask legal or compliance a single question before you shortlist: what would we need to be able to show a regulator or a large customer about where this data sits? Take that answer into the vendor calls rather than guessing at it in either direction.

What to do this week

• Write the requirement list, then find out which tier each candidate puts those requirements on. Price that tier, not the entry one.
• List the systems the CRM must integrate with, and mark which have a native connector and which need a middleware hop.
• Ask the people who will use it daily what they do today and how long it takes. Any system slower than that has an adoption problem before it launches.
• For each candidate, find out who would actually implement it here, and ask to speak to one of their references at your size.

Where this goes next

Once the shortlist is right, the next trap is comparing the wrong number: the licence is not the cost of the system. And the process around the decision matters more than the shortlist itself: how to buy enterprise software without regretting it.

Shortlisting, running the demos and negotiating without a reseller margin in the way is CRM selection and implementation.

Sources

• SDAIA / Saudi PDPL: full enforcement from 14 September 2024
• UAE Federal Decree-Law No. 45 of 2021 (PDPL); DIFC and ADGM data protection regimes