Fifteen CRM best practices for data, pipeline, process and team, plus a daily and weekly routine for using a CRM well, from setup to the Monday review.

Migaru5 min read

The CRM best practices that matter most come down to one idea: the CRM should describe what is really happening with every customer, and the team should be able to trust it without checking. That means capturing conversations automatically rather than by memory, keeping the structure small, moving deals on evidence, and running the team’s meetings from the CRM itself.

The fifteen habits below are grouped by what they protect: the data, the pipeline, the process, and the team.

Data

  • 1. Capture, don’t type. Connect email, calendar and calls so that every conversation lands on the right record by itself. The conversations nobody logged are the biggest gap in most CRMs.
  • 2. Match on email and domain. People by email address, companies by website. It is what keeps one company from becoming three records.
  • 3. Keep fields few and choices fixed. Add a field only when you will report on it or act on it, and use pick lists rather than free text wherever the answer can be counted.
  • 4. Merge duplicates as they appear, on a schedule, rather than in a cleanup project once the forecast stops adding up. See CRM hygiene.

Pipeline

  • 5. Define every stage by what the buyer has done. “Agreed budget and timeline”, not “sent proposal”. See sales pipeline stages.
  • 6. Give every open deal a next step and a date. A deal without one is waiting for something nobody has written down.
  • 7. Keep close dates honest. A close date that has passed is a decision to make: move it with a reason, or close the deal.
  • 8. Record why deals are lost. Loss reasons are the cheapest research a sales team can do, and the first thing to look at when the win rate drops.

Process

  • 9. Write down the rules of the road: how quickly a new lead gets a reply, when a quiet deal is reviewed, and what a handover to customer success includes.
  • 10. Automate the reminders, not the relationships. Let the CRM remind you a follow-up is due, or draft it, and decide yourself whether and what to send. See CRM automation.
  • 11. Turn promises into tasks. Whatever someone said they would send or do on a call belongs on the record with an owner and a date, not in a notebook.

Team

  • 12. Name one owner for the CRM, who decides fields and stages and says no to the field nobody will fill in.
  • 13. Run meetings from it. The pipeline review, one-to-ones and the forecast come from the CRM. If they come from a spreadsheet, the team learns the CRM doesn’t matter.
  • 14. Give every role something back: a brief before a call, a list of who is owed a reply, a dashboard of their own. A CRM that only takes gets avoided.
  • 15. Review it every quarter. Remove the fields nobody uses, merge stages nobody tells apart, and check the numbers still answer the questions you bought the CRM to answer.

How to use a CRM day to day

Best practices stick when they are a routine. A seller’s, in a CRM that captures its own activity:

  • Start of the day: the meetings ahead and their briefs, replies owed, and tasks due.
  • Before each call: the account’s history, who you’ve spoken to, and what was promised last time. See sales call preparation.
  • After each call: check the summary and the tasks it created, move the deal if the buyer did something that moves it, and set the next step.
  • End of the day: anything waiting for your approval, such as suggested changes and drafted follow-ups.
  • Every Monday: deals closing this month, deals past their close date, deals with no conversation in two weeks, and new deals without a next step.

A manager adds the team view on Monday: pipeline by owner, what slipped last week, and which deals need help. CRM dashboards has examples for each role.

Best practices Migaru keeps for you

Several of these Migaru does by itself. It builds accounts and contacts from your mail and meetings and files each conversation on them (1), matching people by email address and companies by web domain (2), and flags likely duplicates about every half hour for you to merge (4). Each pipeline’s stages carry their own definitions, which are what it reads when it suggests a deal has moved (5), and a deal’s empty close date is filled from what a call or proposal said, with a later change suggested for you to approve (7).

Promises from calls and email become tasks with owners (11), and once you turn it on, a follow-up is drafted when one comes due and waits in Review for you to approve into your own drafts (10). A brief is written before every external meeting (14), and the agent answers questions about the pipeline by counting your records, so the Monday review can start from a question rather than a spreadsheet (13).

Frequently asked questions

What are CRM best practices?

Capture email, meetings and calls automatically; match people by email and companies by domain; keep fields few; define pipeline stages by what the buyer has done; give every deal a next step and an honest close date; record loss reasons; name an owner for the CRM; and run the team’s meetings from it.

How do you use a CRM effectively?

Make it a routine: check briefs and replies owed at the start of the day, read the account before each call, update the deal and next step after it, approve suggested changes at the end of the day, and review the pipeline every Monday from the CRM rather than a spreadsheet.

How often should CRM data be updated?

Continuously, which in practice means automatically: email, meetings and calls should reach the CRM as they happen. Deal stages, next steps and close dates should be checked after every customer conversation and reviewed weekly.

What are the most common CRM mistakes?

Depending on people to log every conversation, adding too many required fields, stages that describe the seller’s activity rather than the buyer’s, close dates nobody updates, no owner for the system, and forecasting from a spreadsheet instead of the CRM.

What should be in a CRM workflow?

A trigger, such as a deal changing stage or a lead arriving from a form, and the actions that follow it, such as assigning an owner, creating a task with a due date, or drafting a follow-up for review. Good workflows automate reminders and record-keeping, and leave judgement calls to people.

See what Migaru does with your customer record.