Notes for owners · CRM, automation and RevOps
Getting a sales team to adopt a new CRM: the first sixty days
A sixty-day plan for CRM adoption that starts with one view, one rule and a manager who runs every sales meeting from the screen. Includes what to do with the person who refuses.
The GullySales team · Updated 17 Oct 2026 · 5 min read

On this page
The CRM has been bought and loaded, and the real record is still the senior salesperson's notebook. It is adopted when the sales meeting is run from it and nobody argues with what it shows. Reaching that in two months is realistic if you ask for very little at first. Give each person one view to open every morning, set one rule about what must be entered, and ask the manager to stop collecting updates by message. The long field list can wait.
Days 1 to 10: one saved view per person
Skip the tour of every screen. Set up a single saved view for each salesperson: their open deals, sorted by next-action date, oldest first. That is the only screen they need to learn this fortnight.
Sit with each person for about twenty minutes and load their real customers, not sample data. A salesperson who sees their own accounts on the screen tends to see the point before the sitting ends. One who sees "Test Company Ltd" learns that this is training, not work.
Keep the fields to those you will actually read: name, number, need, stage, next action, next date. If you cannot say which meeting reads a field, leave it off. A form of twenty fields teaches people to fill two and skip the rest.
Days 11 to 30: one rule, and a person who checks it
Pick one rule and hold it. A good first one is that every deal carries a next-action date and the date is never in the past. It is easy to state, easy to check, and it makes the view useful. Add nothing until this one holds.
Each morning, for ten minutes, one named person looks at the overdue list and says in plain words what is there: "four overdue". No blame. A rule nobody checks teaches people that it can be ignored.
Expect a messy first week. People enter dates simply to turn the red off, and the dates are fiction. Treat that as information about which deals have no real next step, and ask what the step is.
Days 31 to 60: the manager works only from the screen
This stretch decides everything and depends on one person, the sales head or the owner. From day thirty-one a deal is discussed in the meeting only if it is in the CRM. A deal that lives in a notebook gets no time, no support and no decision on a discount.
Stop collecting updates by WhatsApp and phone. If you want to know about a deal, open it. If it has no history, ask its owner to write it up after the meeting and say why. A meeting from the screen runs roughly like this:
- Clear the overdue view first, by giving each deal a date or closing it.
- Read the deals that moved to quote since last time.
- Take the largest open deal and ask for one decision on it.
- Close by checking who owns the next action on every deal discussed.
A CCTV and security installer in Madurai
Here is an invented example. An installer of CCTV and access-control systems in Madurai, with a showroom counter, two field executives who visit builders and apartment associations, and an owner who took updates in a WhatsApp group. The group was where deals lived, and it scrolled away every evening.
Their first attempt failed the usual way. Everyone was told to enter everything, the owner kept asking in the group anyway, and entries stopped after about three weeks. The second time they set one view per person and one rule, no deal without a next date. The owner stopped answering deal questions in the group, with one warning: a deal that was not in the system could not get a special rate from the owner.
One field executive called this unfair for a fortnight, then started logging calls from the car. The group went quiet. The other executive kept a paper diary and entered deals only after each meeting, so six weeks in about a third of the deals were still going in late. The owner treated that as a habit to fix rather than a pass, and entered their own deals too, including the large one with a housing society, so the rule could not be called one-sided.
When one person will not use it
Ask what they are protecting. Sometimes it is a customer list they brought with them and fear losing. Sometimes it is plain weariness with another tool. Both can be talked about openly. Ask for the minimum: new enquiries logged the same day and quotes entered with a date. Then run the meeting from the screen. If their record is thin, the meeting is thin for them alone, which is feedback no argument can answer.
If they still refuse once the meeting depends on it, that is a management matter, not a software one. Do not exempt your best seller. The exemption is read by everybody.
Reasons to wait
Do not begin if the sales process is not written down. A CRM stores a process; it does not invent one. If stages are vague, settle them first, using stage names and exit rules. The post on why employees do not use the CRM lists the other causes in more detail.
Do not start in peak season either. Pick a quieter stretch and keep the first sixty days free of other changes, or people will blame the CRM for everything that goes wrong.
Agree the rules above with the owner before anyone is trained. The rest of our sales work sits under sales.
Choose tomorrow's view and rule
Write down the one view each person will open tomorrow and the one rule you will check. CRM adoption and training is the service that sets both up with your team, and tell us what you need is how that starts.








