Knowledge base · processes

How to roll out a CRM people actually use

in short

Sales reps do not fill in the CRM for three reasons: it gives them nothing back, there are more fields than anyone needs, and nobody checks. Laziness has nothing to do with it, people simply stop doing things that carry no consequence. The order that works: decide which reports you need and keep only the fields those reports require, make the required fields technically required, then reconcile ten records against the actual conversations once a week.

The three real reasons

  1. It gives the rep nothing. They spend time and receive supervision. Until the CRM makes their own work easier, it stays somebody else's tool.
  2. Too many fields. Twenty fields get filled in approximately never. Five required ones get filled in.
  3. Nobody checks. A rule nobody verifies quietly stops being followed, and you find out from the reports.

What to do before setup

  1. Write down the reports you will look at every week. Not «analytics», specific numbers.
  2. For each report, write down the fields without which it cannot be built.
  3. Anything that did not make that list does not go into the CRM.
  4. Check which of those fields can be captured automatically: call time, source, payment amount.
What usually survives is five to seven required fields. The rest either fills itself from your phone system and payment provider, or nobody needed it.

What to give the rep in return

  • a stalled-conversation list the system compiles, not the rep
  • a reminder about the customer who never picked up
  • an invoice and delivery note by order number, without assembling them by hand
  • the customer's history in one window instead of scattered across chats

Every one of those saves the rep time. After them, filling in fields stops being a one-way obligation: they put something in and get something out.

How to check without turning it into surveillance

  1. Once a week, pull ten closed records.
  2. Reconcile them against the conversations: does the stated close reason match what actually happened.
  3. More than two mismatches out of ten is a question about the process, not about the person.
  4. Make data quality one modest line in the bonus, not the whole of it.

Signs the rollout failed

  • reps keep a private spreadsheet on the side
  • records get created retroactively at the end of the day
  • half the deals have an empty close reason
  • revenue in the CRM and revenue in the bank differ by more than a tenth

Questions people ask

How many required fields should I keep?

Five to seven. The rest is either captured automatically or needed by nobody.

Should I penalise reps for an empty CRM?

First check whether filling it in gives them anything. Penalties without that produce records written up after the fact.

How long does a rollout take?

Setup takes weeks, the habit takes months. Without a weekly check the habit never forms.

Sources: OpenAI, «From assistance to execution: How enterprises put AI to work» (Enterprise Signals, August 2026) - weekly active enterprise Codex users in sales grew 41x between February and June 2026, against 5x in engineering; lead response speed (Harvard Business Review, Lead Response Management Study, 2025-2026 roundup); touches per closed deal (Gartner B2B Sales Benchmark, 939 companies, 2025); seller productivity (Salesforce State of Sales). Project figures are Double Sales' own measurements on 2026 engagements.
if you need this done in your company

We write the specification from the reports you need rather than from what the software can do, and run the rollout. Part of the build, from $1500 a month.

Book a call