How to Roll Out a CRM Your Staff Will Actually Use

A month after launching the CRM the owner opens a report and sees 40 deals in the system, while the bank statement shows 112 sales. The sales team is tracking clients in notebooks and entering into the CRM only what they were asked about. Formally the system has been rolled out. In practice it has not, and the money spent on it was wasted.

Why people resist

The reason is nearly always the same: the system added work and gave nothing back. A salesperson used to make a call and write a line in a notebook — now they make the call, fill in twelve mandatory fields, create a task, change a status and attach a file. There is less time for selling and the pay has not gone up. The second reason is fear of surveillance: if the first thing the owner said about the CRM was "now I will see who does how much work", resistance is guaranteed. The third is that people do not know what to do with the system in a non-standard situation, and rather than make a mistake they prefer not to enter the deal at all.

The rule for the first two weeks

At launch an employee should face no more than five mandatory fields on a record and no more than four stages in the pipeline. Everything else is optional. Yes, the analytics will be incomplete. But data will exist at all, and you can expand the field set later, once the habit of opening the system has formed. The reverse order — perfect schema first, adoption afterwards — almost never works.

What an employee should get on day one

• A website enquiry pulled in automatically — with the name, phone number and message text, so nothing has to be retyped.
• Correspondence and call history in one place: no hunting through email and messengers.
• A task reminder that genuinely arrives, so nothing has to be held in memory.
• Templates for letters and contracts: what used to take twenty minutes to assemble now takes one.

The manager's role

A rollout fails when the owner does not open the system themselves. If planning meetings run on CRM data, and the answer to "where are we with this client" is only accepted with a link to the record, the habit forms in three weeks. If the manager keeps asking in the chat, the CRM will remain a second, optional place. This is not about staff discipline; it is about where the source of truth in the company lives.

A working six-week plan

Week one — document things as they are: who takes the enquiry, what they do next, where it gets lost. Week two — migrate the customer database and clean the duplicates; we covered the technical side in our piece on moving from spreadsheets to a system. Week three — configure one pipeline and connect the website so enquiries arrive on their own; how that is done on the site side is on the web development page. Week four — role-based training, separately for the sales team and for the manager, 90 minutes each. Week five — run both systems in parallel: the old notebook is still alive, but the data is duplicated. Week six — the old method is switched off, and by this point the CRM needs to genuinely be the more convenient option. Then support begins: for the first two months questions come up every week, and a specific person needs to answer them, not a group chat.

Motivation and the metric

The simplest approach is to tie something financial to the data in the system. Not "a fine for an empty field" but "bonuses are calculated from deals closed in the CRM". Then filling it in is in the employee's own interest. The control metric for a rollout is simple: the share of deals in the system as a proportion of actual sales through the till. Below 90 percent after two months means the rollout did not take, and you need to go back to the question of what exactly people find awkward. If the process is complex and several departments are involved, it is worth designing it on paper in advance — we do this as part of a pre-development audit, and it often saves a month of rework.