Notes for owners · CRM, automation and RevOps
Why employees do not use the CRM
Salespeople stop updating a CRM when it costs them time and gives back nothing, so fix the fields, the phone experience and what the data gets used for.
The GullySales team · Updated 15 Sept 2026 · 6 min read
On this page
Salespeople stop updating a CRM when it takes time out of their day and gives them nothing back. That is the whole answer, and it is a management and design problem rather than a discipline problem. Too many compulsory fields, a version that is unusable on a phone, data that is only ever used to question them in the Monday meeting, and no visible benefit to the person typing. Fix those four and adoption usually recovers without a single additional training session.
The real reasons, in the order they occur
It costs time and returns nothing. A salesperson finishing a site visit at six in the evening has twenty minutes of typing ahead of them. If nothing they type makes tomorrow easier, they will not do it.
Too many fields. Someone added forty fields because the data might be useful. Now every record takes eight minutes and most fields are empty, which makes the whole system look neglected.
It does not work properly on a phone. Field sales and clinic reception live on phones. If the mobile version cannot log a call in three taps, the log happens on paper and never arrives.
The data is used against them. When the only use of the CRM is a manager reading out activity counts in a meeting, the system becomes a surveillance tool and people enter the minimum that keeps them out of trouble.
Nobody trusts what is in it. Duplicate companies, three spellings of the same customer, leads assigned to someone who left. A salesperson who cannot find their own customer stops looking.
No stage definitions. If nobody agreed what the quotation stage means, everyone guesses, the reports are wrong, and the team learns that accuracy does not matter.
The owner does not use it. If the managing director asks for pipeline by WhatsApp and accepts the answer, the CRM is officially optional.
What the salesperson has to get out of it
| What they need | What it looks like | What it replaces |
|---|---|---|
| Their day planned for them | A phone screen listing today's calls and visits, in order | A notebook and memory |
| Never losing a follow-up | Reminders created automatically when a lead arrives | Sticky notes and guilt |
| Faster quotations | A quotation generated from the record with GST fields | Twenty minutes in a spreadsheet |
| Customer history in one place | Last order, last complaint, last price given, on one screen | Scrolling WhatsApp before a call |
| Credit for their work | Their enquiries and orders visible and attributed | Arguments about who brought the lead |
| Cover when they are away | A colleague able to pick up a live deal | A customer calling and nobody knowing anything |
When two or three of those are true, the typing stops feeling like paperwork. That is the whole of CRM adoption.
The fixes that actually work
Cut the fields. Go through every field and ask who uses it and for what decision. Most SMEs can remove half. Make four or five compulsory, no more: contact, requirement, stage, next action date, and source.
Make the phone version the primary one. Test it yourself by logging a call while walking. If it takes more than three taps, the design is wrong.
Give the data back. Start the weekly meeting with the CRM's own list of untouched leads and stuck quotations, and use it to offer help rather than to accuse. Send each salesperson their own numbers before the meeting so nobody is surprised in front of others.
Agree the stage definitions in one sitting with the people who sell, in their words, and put them on one sheet on the wall.
Clean the data once, properly. Merge duplicates, fix owners, delete records with no phone number. Adoption cannot recover on top of a dirty database.
Name an owner for the system. One person, half a day a week, who notices when a rule breaks or a field stops being used.
Make the rule simple and apply it to everyone. A deal that is not in the CRM is not forecast, not supported and not paid on. Including the owner's own deals.
What does this look like in practice?
For example, a building materials distributor in Bengaluru with nine salespeople covering contractors, builders and retail counters. It had implemented a CRM eighteen months earlier, and the sales manager was spending most of Monday chasing people for updates that arrived as WhatsApp voice notes.
Looking at the configuration explained it. There were thirty-four fields on the lead form, eleven of them compulsory, including two that required information a salesperson could not know on a first call. The mobile app had never been set up, so everything had to be typed on a laptop in the evening. And the only report anybody ever saw was a call count, read out on Monday.
The fix removed things. Compulsory fields went from eleven to five. The mobile app was set up and every salesperson logged a call on it during a single training hour. The Monday meeting was changed to open with the list of leads nobody had touched and the quotations open for more than thirty days, with the manager asking what help each one needed. Two weeks later the salespeople were entering visits from the field, because the reminder list was saving them the evening's recall. No new software was bought.
What to do next
Sit with your two most reluctant salespeople for half an hour each and ask them to log a real lead in front of you, on the device they actually carry. Count the taps and the fields, and watch where they hesitate. That half hour will tell you more than a training programme, and the fixes are usually removals rather than additions. If you would like the configuration, the stage definitions and the reporting reviewed together, tell us what you need.
