Choosing a CRM That Your Sales Team Will Actually Update
Most CRMs fail because the sales team sees them as reporting for managers. Choose and set up one that makes a salesperson's day easier, and the data follows.
The story is familiar. A company buys a well-known CRM (customer relationship management) system, spends months configuring it, trains the sales team and launches it with a clear instruction: every visit, call and opportunity goes in the system. Six months later, the pipeline report shows a handful of active deals, half of them out of date, while the real pipeline lives in each salesperson’s phone, WhatsApp chats and a notebook in the car.
The software usually works. What failed is the deal the company offered its sales team: more admin, in exchange for nothing they value. Choosing a CRM that gets updated means choosing and setting it up from the salesperson’s side first.
Why salespeople stop updating the CRM
- It takes longer than the old way. Logging a visit takes eight fields and three screens. Writing a WhatsApp note to yourself takes ten seconds.
- It gives nothing back. If the CRM only produces reports for the sales manager, updating it feels like reporting on yourself.
- It does not work where they work. Field sales staff visiting customers in industrial areas or across governorates need a phone app that works with weak signal, not a desktop screen they open on Thursday evening.
- It holds the wrong information. Customer records are out of date or duplicated, so salespeople keep their own lists, which they trust more.
- Nobody uses the data. If sales meetings still run from a separate Excel sheet, the message is that the CRM is optional.
Design for both sides of the deal
Managers and salespeople want different things from a CRM. A good selection and setup gives both, with the salesperson’s needs met first because the data comes from them.
| What managers want | What salespeople need in return |
|---|---|
| An accurate pipeline with values and stages | A quick way to update a deal from a phone in under a minute |
| Visit and call activity | Visits logged automatically from calendar or location, not typed twice |
| Customer history in one place | Full history, past orders and open invoices visible before a meeting |
| Forecasts | Reminders for follow-ups so deals do not go cold |
| Quotation tracking | Quotations created from the CRM in minutes, with correct prices |
The right column is where adoption is won. If the CRM helps a salesperson prepare for a meeting, remember follow-ups and send quotations faster, they will open it every day, and the left column takes care of itself.
How to test CRMs before you choose
Vendor demonstrations show the product at its best, using the vendor’s data and the vendor’s scenarios. Instead, run a structured test with two or three shortlisted products and real users.
- Pick three salespeople, including a sceptic. One experienced field salesperson, one office-based or major-accounts salesperson and one who openly dislikes systems.
- Define the five daily tasks. For example: check a customer’s history before a visit, log a visit with a short note, update a deal stage, create a quotation, and set a follow-up reminder.
- Time each task on a phone. Ask each salesperson to perform the tasks on each product’s mobile app, using a trial account loaded with some of your real customers. Count taps and seconds.
- Test in real conditions. Try it in a basement car park or an area with weak signal. Check whether the app works offline and syncs later.
- Check language support. If customer names, addresses or notes are in Arabic, make sure the product handles Arabic text properly in search, display and exports.
- Ask the sceptic last. If the most reluctant person can do the five tasks quickly and sees a benefit, you have a strong candidate.
Integration and setup choices that matter
Several setup decisions have more influence on adoption than the choice of product itself.
- Connect to the ERP (enterprise resource planning) system. Salespeople want to see a customer’s orders, outstanding invoices and credit status. If the CRM cannot show this, they will keep calling finance, and they will see the CRM as incomplete.
- Connect email and calendar. Emails and meetings logged automatically remove a large share of manual entry.
- Handle WhatsApp sensibly. In much of the region, customers prefer WhatsApp. Some CRMs connect to the WhatsApp Business Platform through an approved provider; at minimum, agree how important conversations are summarised in the CRM.
- Keep fields to a minimum. Start with the fields you will actually use in reports and meetings. You can add more later. You can rarely remove them once people are used to skipping them.
- Clean the customer data first. Load one clean, de-duplicated customer list. Starting with poor data damages trust from day one.
An illustrative example: a building materials supplier
Take a supplier of building materials with twelve field salespeople covering contractors across Jordan. Earlier attempts at a CRM failed because it did not show stock or credit status, so salespeople kept calling the office before every quote. In a second attempt, the company chooses a CRM that connects to its ERP, configures a mobile screen showing each customer’s open orders, overdue balance and last three visits, and lets salespeople generate quotations from the app. Weekly sales meetings run directly from the CRM pipeline, with no separate spreadsheet. The data improves because the system is now the fastest way for a salesperson to prepare a quote, and no new rules are needed to get there.
A CRM as a sales tool, not a report
Choosing a CRM successfully means treating it as a tool for the people who sell, with management reporting as a by-product. Test real tasks on real phones, connect it to the data salespeople need, keep it simple and run meetings from it.
Our Enterprise Systems service helps organisations define CRM requirements, run vendor-neutral selection, design integrations with the ERP and plan adoption, so the system you choose becomes the one your sales team relies on.
Related insights
From On-Premises Servers to the Cloud: What Changes for Operations
Moving servers to the cloud is often presented as an IT project. In practice it changes how people work, who is responsible for what, and how…
Dashboards for Clinic and Healthcare Group Managers
Clinic managers juggle appointments, doctors, insurers and cash, often with numbers pulled from four systems by hand. A good dashboard starts with the decisions they make…
Requirements Workshops: Operations, Finance and IT in One Room
Separate interviews produce three wish lists that contradict each other. A well-run requirements workshop turns them into one agreed picture of how the system must work.