CRM adoption fails for ordinary reasons: the system asks for more than people have time to give, it is awkward on a phone, and nobody in charge uses it either. The fix is three changes, in this order: cut the fields, put the CRM on every phone, and set one rule everyone follows. Training sessions and reminder emails come well after those.
If staff avoid your CRM, they are usually behaving sensibly. They are busy, the system gives them nothing back, and updating it feels like admin done for someone else’s benefit. Change that and the rest follows. Blaming people does not.
Why CRM adoption stalls
Before you change anything, find out which of these is true in your business. Ask three people the same question: “What makes it a pain to update?” Then listen for these.
- Too many boxes. A new contact has twenty fields and eight are mandatory. People type the minimum, or put “n/a” everywhere.
- It lives on a desktop. The work happens in a ute, a treatment room or a car park. If updating means going back to a computer that evening, it will not happen.
- Nothing in it for them. The person entering the data does not get anything out. The owner gets a report. They get more typing.
- Double entry. They update the CRM, and then the calendar, and then a job sheet, and then message the office.
- No one checks. If the owner still asks “so where are we at with the Hendersons?” in the hallway, the CRM is optional.
- Distrust of the data. Records are out of date, so people stop looking, so nobody updates them. It feeds itself.
Most of these are design problems, not attitude problems, and design problems can be fixed.
Fix 1: Fewer fields
This one change does more than any training. Go through every field and ask who looks at it and what they decide with it. If the answer is “nobody” or “might be useful one day”, remove it.
A contact record that works for most service businesses needs about ten things: name, mobile, email, suburb, source, service wanted, estimated value, owner, next action with date, and a lost reason when a job is lost. Our guide to CRM implementation steps has the full reasoning.
Then look at what is mandatory. Make a field required only if the next step genuinely cannot happen without it. A mobile number, yes. A “company size” box on a home owner, no.
Some fields can be filled in for people. Source can be set automatically when a web form comes in. Suburb can come from the address. Every field the system fills itself is one fewer thing a person can skip.
Fix 2: Put it on the phone
If your team works away from a desk, the mobile app is the CRM. Set it up during the first week, on each person’s own phone, and watch them do one real task with it.
The updates that matter most can be made in under a minute from a phone:
- Log a call outcome (“Spoke to her, wants quote after school holidays”).
- Change a stage (Quote sent, Won, Lost).
- Set the next action and date.
- Take a photo or voice note against the record.
Voice notes are underrated. A person who will never type three sentences after a site visit will happily speak them. Check whether your system supports them, and if it does, show it on day one.
If your CRM has a poor mobile experience, that is a legitimate reason it is not being used, and it is worth weighing when you choose or replace one. Our small business CRM comparison looks at how the main options work and who each suits.
Fix 3: One rule everyone follows
Write a single sentence and make it the standard. For example:
If it is not in the CRM, it did not happen.
In practice that means the owner treats the CRM as the only source of truth for follow-up. Weekly sales meetings run from its screen instead of from memory. If someone asks where a quote is up to, the answer is “check the CRM”, and the owner checks it too.
This works because it changes what is useful. Once the meeting is run from the screen, an out-of-date record is embarrassing and an up-to-date one saves a conversation. Nobody has to be policed.
Three supporting habits keep the rule credible:
- The owner uses it first. If you log your own calls, the team sees it is real.
- One place only. Retire the shared spreadsheet, the whiteboard and the sticky notes. Two systems mean none.
- A small, fixed review slot. Fifteen minutes weekly, looking at overdue tasks and stuck quotes. Not a long meeting.
If one person still will not use it
Start by asking, not telling. Sit with them for ten minutes and watch them update a record. The problem is often one thing: a confusing field, a slow login, or a step that duplicates what they already do elsewhere. Fix that and many holdouts come round.
If the system now works and the person still declines, treat it as any other job expectation. Say what you need (calls logged the same day, a next action on every open record), why (so others can cover for them and nothing is dropped), and by when. Check a week later. Do not make an example of anyone in front of the team, because it teaches everyone else to hide the gaps.
Make it useful to the person typing
Adoption improves quickly when the CRM gives something back to the person doing the entering. Ideas that work in small teams:
- A “today” view showing only that person’s tasks, so the CRM is their to-do list.
- A text or email template for a quote follow-up, so writing it takes ten seconds. See how builders follow up quotes for wording that works.
- An automatic reminder when a customer has not replied, so nobody has to remember.
- A booking link, so confirming a time is one tap.
If using the CRM saves a person time, they will use it. If it only produces reports for someone else, they will not.
CRM training that works
The training that works is short, specific and repeated. One long session on a Friday afternoon is forgotten by Monday.
- Thirty minutes, on real records. Each person logs a call, moves a stage and sets a next action, on their own phone, with someone watching.
- A one-page cheat sheet. “After a call, do this. After a site visit, do this. When you send a quote, do this.” Print it, and also keep it where the team chats.
- A five-minute check after one week. Ask what is slowing them down. Fix one thing that day.
- A short introduction for new starters. Otherwise they learn a worse version from whoever sits next to them.
What the owner has to do
Adoption follows what the person in charge does. Open the CRM first thing instead of at the end of the week. Log your own calls from your own phone. When someone tells you about a job in passing, ask them to add it, then look it up together. After a month of that, the team will know the CRM is how things are done here, which no training session can tell them.
How to tell whether adoption is working
Pick two or three signs you can check in five minutes. Do not rely on a feeling.
- Percentage of open records with a next action date in the future. Aim for nearly all.
- Number of records not touched for 14 days.
- Whether a stage change is recorded on the day it happens, or in a batch on Friday.
- Whether the weekly meeting runs from the CRM screen.
These show where it is weak. If one person’s records are stale, it is a conversation with that person, and often about the mobile app or one confusing field. If everyone’s are stale, the system is the problem.
When the answer is to change the system
Sometimes the CRM is simply the wrong shape. Signs: you have already cut the fields, the app is awkward even after set-up, and the same complaint keeps coming back. At that point switching or rebuilding is reasonable. Our custom CRM vs off the shelf guide sets out when each makes sense. CentriWeb does CRM set-up and ongoing support if you want a second pair of eyes, and we will tell you if the tool you have is fine and the habits are the problem.