How to choose a CRM your team will use

Choosing a CRM usually starts the same way. Someone writes down five well known names, books three demos and picks the best presentation. Six months later half the team still works in a spreadsheet and leadership asks why the pipeline report does not add up.

The tool is rarely the problem. The order is. If you start with vendors, you compare features. If you start with your own work, you compare whether a tool makes that work easier. The second question is the one you need answered.

Picture a typical B2B team. An account manager keeps customers in Gmail or Outlook, meetings in a calendar and quotes in a shared folder. A sales manager wants to know on Monday which deals will close this month. Marketing wants to send a newsletter to people who opted in. Support wants sales to know about an open complaint before a renewal call. Four people, four questions, one customer.

A good CRM answers those questions without anyone doing the work twice. That means it has to fit your email client, the way you sell and the systems you already run. It also means the people who will use it every day help choose it, not only leadership.

Across more than 150 CRM implementations at Sales Surge, the same patterns keep coming back. Teams pick something too big because they fear having to switch later. Or they pick something too small because it looked cheap, and hit its limits within a year. Or they pick well and set it up badly. This guide covers the first two. For the third, read our guide on rolling out a CRM in phases.

Not sure yet what a CRM does and does not do? Start with what is a CRM and come back here after.

The most common mistake in a requirements list is describing features instead of work. "The CRM must have automations" says nothing. Every CRM has automations. Write what needs to happen instead: "When a deal moves to Quote sent, the owner automatically gets a task to call after three working days."

You can test a requirement written that way. In the demo you ask the vendor to build that one thing. If it takes five minutes, it is a green tick. If it needs a consultant, that tells you something too.

Must have or nice to have

A simple test: could you go live without this and live with it for a month? If not, it is a must have. If yes, it is a wish. Most teams end up with six to ten must haves. Think of email and calendar, the pipeline itself, permissions per role, importing your current data, and the report leadership steers on.

An example of a well written list

Below is a made up example for a B2B services firm with eight sales reps. The point is the format, not the content:

• Must have: email with a customer lands on the right person and deal without manual work.
• Must have: every deal has a value, a stage and an expected close date, and we see totals per stage.
• Must have: a rep sees what they are allowed to see, a manager sees everything for their team.
• Must have: our current contacts and open deals come across without retyping.
• Wish: create quotes from the deal and have them signed online.
• Wish: send a newsletter to contacts who gave consent.
• Wish: a customer portal for support questions.

Notice the difference with "good reporting" and "user friendly". Those two phrases appear on every list and help with no decision at all.

A made up example to show how the sum works. Three tools, called A, B and C, and five criteria from the scorecard. The numbers are invented for this explanation.

• Email and calendar (weight 3): A scores 5, B scores 3, C scores 4. Weighted: 15, 9 and 12.
• Pipeline and deals (weight 3): A 4, B 5, C 4. Weighted: 12, 15 and 12.
• Moving your data (weight 3): A 3, B 4, C 2. Weighted: 9, 12 and 6.
• Reporting (weight 2): A 4, B 3, C 5. Weighted: 8, 6 and 10.
• Cost over three years (weight 2): A 3, B 3, C 4. Weighted: 6, 6 and 8.

Totals: A gets 50, B gets 48 and C gets 48. The gap is small. That is normal, and it is exactly why the scorecard helps. It shows that the decision is not about the total but about one or two rows.

In this example C scores low on moving your data. That risk has a price. If migration takes a month longer, that is a month without a usable pipeline. B scores lowest on email and calendar. So ask the follow up question: is that a hard limit, or is there a workable bridge, such as a BCC address that still gets email onto the record?

The conversation that follows is worth more than the number. Write down which row decided it, which limitation you accept and how you will handle it.

Of all the criteria, this one has the biggest effect on daily use. A sales rep lives in their inbox. If every email has to be copied into the CRM by hand, it does not happen. After three months the timeline is half empty and nobody trusts it.

So the first question in any selection is which email client the team uses. Some tools work best with Gmail and Google Calendar. Others are stronger with Outlook and Microsoft 365. Few are equally far along with both.

Ask each vendor three things:

• What syncs today for your email client? Email on the record, sending from the CRM, calendar in both directions.
• What is on the roadmap, and what can you do in the meantime? A BCC address that sends a copy of an email to the CRM, for example, works with any client.
• What does the CRM pull from your mailbox? All email, or only email with known contacts? That is also a privacy question.

An honest vendor tells you exactly what works and what does not. If your team uses Outlook and the integration is still in development, that does not have to rule a tool out. Weigh it: how big is the difference in daily work, and is the bridge workable for your team? Test it in the trial with real email.

Choosing on the demo

A demo is a performance. The vendor knows the product and shows the smoothest route. That says little about how your rep builds a quote on a Tuesday afternoon. Always have your own scenario shown, then test it yourself.

Wanting everything at once

A CRM that has to serve sales, marketing, service and finance on day one never goes live. Start with the pipeline and email. Switch on the rest when the team is ready. A tool where you enable modules one at a time helps with that.

Leaving users out of the choice

If only leadership chooses, reps experience it as control. Let two or three future users test and give their view real weight. Also read how to get your team to actually use the CRM.

Underestimating the migration

Your current data is messier than you think. Duplicate organisations, people without an email address, deals with a close date two years ago. Plan time to clean up before the switch, not after. The guide on CRM data quality helps.

Looking only at the licence price

The licence is usually the smallest part of the cost. Setup, migration, training and the hours your team loses in the first months count too. Calculate over three years, not one month.

No exit plan

Before you sign, ask how you get your data out. Not because you plan to leave, but because the answer tells you something about the vendor.

A made up example for a team of ten users. The amounts are invented to show the structure, not to compare tools.

• Licences: 10 users times € 40 per month times 36 months is € 14,400.
• Setup and migration: one time € 6,000.
• Training and team hours in the first three months: 10 people times 8 hours times € 60 is € 4,800.
• Adding marketing or service in year two: € 3,600.

Total over three years: € 28,800. The licence is half of it. A cheaper tool that needs twice the setup work is not cheaper over three years. Run this sum for every tool on your shortlist with the real quotes.