Most sales teams do not avoid the CRM because they are lazy. They avoid it because every update costs time they would rather spend with clients, and they rarely get anything back for the effort. Too many required fields, the same details typed twice, a slow screen on a phone and a system that seems built for managers rather than for the people who sell are the usual causes. The fix is not another reminder from the sales manager: cut the fields to what drives a decision, capture data where it is created, run a short weekly clean-up, show each rep what the CRM does for them and make an update as easy as sending a message. Below we cover what research says about selling time and data quality, what an empty CRM costs, the fixes that work in any company and where an assistant that understands plain language fits in.
How much of a salesperson's week actually goes to selling?
Less than half. In the seventh edition of Salesforce's State of Sales report, based on a survey of 4,050 sales professionals in 22 countries in August and September 2025, reps said they spend 40% of their time selling and 60% on non-selling work such as data entry and prospecting. The survey is global and does not cover Egypt or the Gulf, but most sales managers in the region will recognise the pattern.
The number of tools makes it worse. In a Gartner survey of 1,026 B2B sellers run in early 2024, half said they were overwhelmed by the amount of technology their job requires, and overwhelmed sellers were 45% less likely to attain quota. When the CRM is one more screen in a long list, it is the first one to be skipped. We looked at the wider cost of clicking through screens in our article on the hidden time cost of dashboard clicks.
Why do salespeople avoid updating the CRM?
The reasons are similar in almost every company.
- Too many fields. A deal form with dozens of boxes turns a quick note into a chore, so reps fill the minimum and guess the rest.
- Double entry. The details already exist in an email, a chat or a quote. Typing them again feels like paperwork, because it is.
- No visible benefit. If the CRM only feeds a management report, the rep sees the cost and none of the return.
- It feels like surveillance. When the CRM is mostly used to count calls, reps log whatever keeps them out of trouble.
- It is slow where the work happens. Selling happens on the phone and at the client's office, not at a desk.
- Nobody owns the data. If no one is responsible for duplicates and dead deals, no one fixes them.
| Barrier | What the rep experiences | What the company loses |
|---|---|---|
| Too many required fields | Every update takes too long | Updates are delayed, guessed or skipped |
| Double entry | The same details typed twice | Records lag behind real conversations |
| No visible benefit | The CRM serves the manager, not the rep | Low use and a pipeline nobody trusts |
| Used for policing | Logging feels risky | Activity logged to look good, not to be accurate |
| Desktop habits | Hard to update between meetings | Notes stay in phones and notebooks |
| No data owner | Duplicates and stale deals pile up | Reports that need cleaning before every meeting |
What does an empty or messy CRM cost managers?
The cost lands on the people who rely on the data. In Validity's State of CRM Data Management in 2025, a survey of 602 CRM users and stakeholders in the US, the UK and Australia run by a data quality software company, 76% said less than half of their organisation's CRM data is accurate and complete, and 37% said they had lost revenue as a direct result of poor data quality. Trust follows quality. In Salesforce's previous State of Sales edition, published in 2024, only 35% of sales professionals said they completely trust the accuracy of their organisation's data.
At the scale of large organisations, Gartner research from 2020 found that poor data quality costs at least $12.9 million a year on average. A mid-sized company in Cairo, Riyadh or Dubai will lose far less in absolute terms, but the losses take the same shape:
- Forecasts you cannot use, because deal stages and close dates are out of date.
- Follow-ups that never happen, because the note lives in one person's phone.
- Handovers that start from zero when a rep leaves and takes the client history with them.
- Meetings spent on status instead of decisions.
- AI and automation that cannot help, because any tool that reads the CRM is only as good as the records inside it.
If you are still deciding which system should hold client data, our guide to CRM vs ERP explains what each one is for.
How can you tell if your CRM has an adoption problem?
You do not need a survey. Pull a few checks from the CRM itself:
- Open deals with no next step or next date. Each one is a follow-up waiting to be forgotten.
- Clients with no activity in the last month. Some are fine. Many are quietly slipping away.
- Deals whose expected close date has passed but which are still marked open.
- Duplicate companies and contacts, often the same client typed once in English and once in Arabic.
- Fields that are almost always empty. Either they do not matter or the form hides them.
- The gap between the CRM and reality. Ask each rep for their top deals and compare with what the CRM shows.
Run these checks once to find your starting point, then every month. The trend matters more than the first result.
Which fixes actually get a team using the CRM?
Cut required fields to what drives a decision
For every required field, ask who uses it and for which decision. If nobody can answer, make it optional or remove it. A short form that is always filled in beats a long form filled with guesses. Keep only a handful of fields required at each stage, such as client, value, stage and next step date.
Capture data at the source
Every detail should be typed once. Send website enquiries straight into the CRM as leads, log calls and emails automatically where your CRM supports it, create the client record from the quote and import exhibition contacts in one batch instead of by hand.
Show reps what the CRM does for them
Give each rep a view that answers their own questions: who to call today, which quotes await a reply, which clients have gone quiet. Run the sales meeting from the CRM instead of slides, and recognise the rep whose pipeline is accurate, not only the one with the biggest number.
Make updating as easy as sending a message
The closer an update is to the way reps already communicate, the more often it happens: a mobile screen where logging a call takes a few taps, a standard short format for meeting notes or a way to forward an email into the client record. If updating takes longer than messaging a colleague, it will be skipped. For more on AI in follow-ups, see AI in sales: from manual follow-ups to a smart pipeline.
What does a weekly CRM hygiene routine look like?
Client data decays: people change jobs, numbers change and deals stall. A small weekly routine keeps the CRM useful without a painful clean-up every quarter. Keep it short enough to survive a busy week.
| When | Task | Who |
|---|---|---|
| Start of the week | Review open deals with no next step and add one | Each rep |
| Every day | Log calls, meetings and quotes on the same day | Each rep |
| Midweek | Merge duplicates and fix obvious errors in new records | Sales coordinator or CRM admin |
| End of the week | Update or close deals whose close date has passed | Each rep, checked by the manager |
| End of the week | Review clients with no contact in a month and plan follow-ups | Sales manager with the team |
| Monthly | Repeat the adoption checks and remove fields nobody uses | Sales manager |
How does Amrak handle this?
Amrak is HBS Group's AI assistant that works inside the systems a company already has, including its CRM. Staff type a request in plain Arabic or English and Amrak carries it out through a connector HBS builds for the company's own sections and rules, using MCP, an open standard for connecting AI assistants to business systems that we explain in what MCP is. For CRM adoption, that changes a few things:
- Ask the CRM instead of searching it. A manager can ask which clients have not been contacted in a month, or for a summary of yesterday's work, without building a report.
- Follow-ups drafted for you. "Draft follow-ups for clients not contacted in a month" is one of the example commands on our Amrak page. Amrak prepares the messages and the rep reviews them.
- Messages to clients always wait for approval. Nothing goes to a client until someone approves it. Deleting records and changing prices are treated the same way.
- Updates in a sentence. Depending on the commands agreed in your command map, a rep can describe what happened in plain words and Amrak prepares the change to the client record.
- Permissions still apply. A rep may update their own clients without being able to change prices.
- Every action is logged: who asked, when and what changed.
Every request follows five steps: Amrak understands the request, checks the person's permissions, prepares the full change, asks for approval if the action is sensitive, then completes the task and logs it. The data stays in your CRM, Amrak reads only what a request needs, and there is no migration and no system to replace. The full walkthrough is in how Amrak works, sales commands are in our commands by department and the safety model is in how to let AI act safely in your systems.
Amrak does not fix a CRM full of fields nobody needs, so the steps above still come first. What it removes is the distance between the rep and the record, so that updating and asking feel like part of the work.
Where should you start this week?
- Run the adoption checks above and write down the results.
- Make optional, or remove, every required field nobody can justify.
- Connect one data source first, usually the website form or quotes.
- Agree the weekly routine with the team and put it in the calendar.
- List the pipeline questions managers ask every week. They are the first candidates for plain-language requests.
To see whether the effort pays off, measure before and after, as we describe in how to measure AI ROI.
If your team keeps the real pipeline in their phones and the CRM is always a week behind, book a free discovery session with our team. We will look at your CRM with you and show what your team could ask it and get done in plain Arabic or English. See how Amrak works and book your session.
