Contents6
The CRM is installed, the team has been trained, and three months later deals still live in a spreadsheet, a notebook and everyone’s memory. Management sees resistance to change. That is rarely the right diagnosis: salespeople do a simple calculation, and for them the CRM costs more time than it gives back.
This article from our CRM and customer data section starts from their point of view. Salespeople remain a CRM’s first users, and accurate data comes from serving them, not from watching them.
In short
An empty CRM is a symptom: the tool asks more than it gives back to the people who fill it in.
The recurring causes: double entry, too many fields, vocabulary foreign to the trade, doubtful data.
An adopted CRM gives before it asks: prepared follow-ups, full history, context before a call.
Adoption is built with the salespeople, from configuration onwards, and checked after go-live.
The smallest tool that covers the need is adopted better than the most complete one.
Salespeople’s time comes first
The first argument against the CRM is time, and it is well founded. Salesforce, a CRM vendor, surveyed 5,500 sales professionals in 27 countries for the sixth edition of its State of Sales report:
of salespeople’s time goes on non-selling tasks, such as admin and meeting preparation
only of sales professionals completely trust the accuracy of their organisation’s data
These figures come from a vendor that sells CRMs, and yet they say the same thing as the field: a tool that adds data entry to that share of time will be bypassed. And data people doubt is no longer consulted, so no longer updated.
Why the CRM stays empty
It serves management, not the salesperson
Many CRMs are configured to produce Monday’s report: stages, amounts, probabilities. The salesperson enters data to be seen, and gets nothing out of it for their own work. A tool experienced as an instrument of control gets filled in at the last minute, on Friday evening, and badly.
It asks too much
Every mandatory field is a small tax. Twenty fields to create a deal, half of which serve nobody on the team, and the record stays a draft in the salesperson’s notebook. The rule is simple: a mandatory field must serve a decision someone actually makes.
It does not speak their language
A CRM delivered with its default vocabulary (“lead”, “opportunity”, “account”) forces the team to translate its trade at every entry. An estate agency does not sell “opportunities”; it follows properties, mandates and viewings.
From the field
On Palmora Property, a property listings portal we operate, a property is not a disguised opportunity: properties, areas and referrers are objects in their own right in the Twenty CRM, with business identifiers generated automatically. The team finds its own words there, instead of working around the tool with a spreadsheet.
It makes people enter things twice
The email sent to the customer, then its summary copied into the CRM; the quote made in the billing software, then its amount re-entered in the deal. Every double entry is a reason not to do the second one. Syncing email with the CRM and connections with billing, which lead to a single customer view, remove most of these duplicates.
Its data is unreliable
Three records for the same customer, missing numbers, statuses never updated: the salesperson goes back to their spreadsheet, which they know is right, and the CRM degrades a little more. That circle is broken by a thorough clean-up followed by entry rules, described in our guide to cleaning your CRM data.
What gets a CRM filled in
A CRM for control
Configured for management’s report
Twenty mandatory fields for a deal
The vendor’s vocabulary
Every email and every quote to re-enter
A CRM for work
Configured with the salespeople, for their day
The minimum mandatory, the rest optional
The trade’s words, objects and stages included
Exchanges and invoices that arrive by themselves
The difference comes down to one idea: the CRM must give before it asks. It prepares the follow-up for the unanswered quote, as our guide to sales follow-ups that keep a human tone shows. It shows the full history before a call, unpaid invoices and tickets included. It reminds you of each deal’s dated next action. A salesperson who saves time with it fills it in, because what they put in comes back to them.
Key takeaway
You do not get accurate data by watching the people who enter it, but by serving them with what they enter.
Adoption is built before, during and after
Before, when choosing: the team’s ease with digital tools, its training needs and its habits count as much as the feature list. That is where our own method starts, before any recommendation.
During configuration: two or three salespeople validate the stages, fields and views, in their own words. A “my deals this week” view is worth more than a dashboard they will never open.
After go-live: you check real usage, without policing, with the team. A few questions are enough: how many deals have a dated next action, how many records have no owner, which entries are abandoned halfway. The answers tell you which field to remove, which view to add, which stage to rename. In our offer, these are the follow-up reviews at 30 and 90 days.
The right size of tool
A full ERP chosen for hypothetical needs is adopted less well than a simple CRM that covers the real need: every unused module adds screens, fields and reasons to go back to the spreadsheet. We recommend the smallest tool that genuinely covers the need; our comparison to choose between Twenty, Dolibarr and Odoo starts from team size and the processes to cover.
We have run Twenty in production since early 2025; what gets it adopted, from that use, depends less on the software than on a data model modelled on the trade, as our review of Twenty in production recounts. Dolibarr and Odoo are adopted through the same levers: vocabulary, little data entry, and a tool that serves its users.
A team changing tools also needs to find its history again: our guide to migrating from HubSpot to an open source CRM covers the data migration. The rest of the section covers Twenty as a back office, GDPR in a CRM and automated decisions.
A CRM configured in your vocabulary, with your team trained and follow-up reviews at 30 and 90 days, is our CRM and ERP offer. To talk about your team, write to us.
Frequently asked questions
Should salespeople be required to use the CRM?
A rule helps (“a deal that is not in the CRM does not exist for commission”), but it is not enough: it produces records filled in at the last minute, and badly. The obligation holds when the tool is useful, by preparing follow-ups and showing the history before a call. Start by removing what costs time, then set the rule.
How many mandatory fields should you plan for?
As few as possible: those that serve a real decision, such as the stage, the estimated amount, the dated next action and the owner. Every extra mandatory field slows down deal creation and pushes people to fill in anything to get past it. Other information can stay optional, or arrive by itself through connections with email and billing.
How long does it take a team to adopt a CRM?
It depends on the team, the tool and what it replaces. The first weeks already say a lot: if this week’s deals are in it, with their next action, adoption is on its way. Plan follow-up reviews after go-live, to adjust fields and views with the salespeople rather than waiting for a verdict of failure.
Is a simpler CRM always adopted better?
Not always, but a tool bigger than the need adds screens, fields and menus the team does not use, and each one is a reason to go back to the spreadsheet. The right choice is the smallest tool that covers the real processes, today’s and those you can already see coming, configured in the team’s vocabulary.
Sources
Jim · founder of Brain Plus AI
Also in crm and customer data
Choose and price7 min
Twenty, Dolibarr or Odoo: which one for your team?
Twenty, Dolibarr and Odoo are not in the same category: a pure CRM, a light ERP, a full ERP. Rather than a feature table, here is a decision grid by team size and by process, with what moves you from one level to the next.
Practical guide7 min
Sales follow-ups: automate them, keep the human tone
A forgotten follow-up costs a deal, a robotic one damages the relationship. Let the machine remember and prepare, and the salesperson choose the words and send: the method, the safeguards and the sending rules to know.
Practical guide9 min
Cleaning your CRM data: duplicates, fields and rules
A CRM full of duplicates and empty fields stops being consulted, and every automation or AI plugged into it repeats its errors. The method for a thorough clean-up, then the rules and automatic checks that make it last.