CRM implementation checklist for SMEs

1. The sales process is on one page — stages, entry and exit criteria, owners, handovers — and signed off by the owner and the salespeople before anything is configured. 2. The fields are chosen: for each record type, the few that the process needs at each stage, marked required or optional; anything not used in a decision is left out. 3. Stages and pipelines are named as the team speaks — if you sell two very different things, two pipelines, not one with twelve stages. 4. Roles and permissions: who sees what, who can edit what, who can delete — with the owner able to see everything and delete nothing by accident. 5. Data is gathered and cleaned before migration: the customer list from accounts, the contacts from phones and inboxes, the open deals from notebooks — deduplicated, with owners assigned, in one spreadsheet that matches the fields chosen in check 2.

Check 5 is where the time goes, and skipping it means launching a CRM full of duplicates that the team learns to distrust in a week.

6. Configure the process first — pipelines, stages, required fields, task types — and nothing else; the automations and dashboards come after the basics are used. 7. Integrate the enquiry sources: the website form, WhatsApp Business, email capture, the call-tracking number — tested by sending a real enquiry through each and finding it in the CRM with its source. 8. Migrate the cleaned data, into a test environment first, and have the champion open twenty records at random and check them against the source. 9. Configure the two owner views — this week’s pipeline, and overdue follow-ups by person — and the salesperson’s morning list. 10. Pilot for a fortnight with the champion and one more salesperson on real deals, and fix what they find: the field nobody fills, the stage that means two things, the view that is wrong. 11. Train everyone in two half-days, on their phones, on the five daily scenarios — log a call, set a follow-up, move a deal, handle an assigned enquiry, find a customer — with the process page beside them, and the champion in the room.

Train after the pilot, not before; the pilot changes what is trained.

12. Go live on a Monday with the rule that from today every enquiry and every deal exists only in the CRM — notebooks and threads are closed, and the weekly pipeline meeting runs from the CRM screen. 13. Adoption is measured weekly for the first quarter: deals with a next action, activities logged per person, enquiries assigned within the standard — and the owner reads it, not to punish but to see who needs help. 14. Governance: one person owns fields and stages and changes them only through a request, so the system does not drift into sixty fields by month six; a monthly data check for duplicates and dead deals. 15. Support: who the team asks when something does not work — the champion first, the vendor second — with a response expected within the day. 16. Improvement: a monthly half hour on what the team wants changed, and one automation added a month once the basics run — lead assignment, a follow-up sequence, a stale-deal flag — each tested before it is switched on.

Checks 12 to 16 are the difference between an implementation and a launch. Most SMEs do 1 to 11 and stop.

The mistakes: configuring before the process is written; sixty fields on day one; migrating dirty data; launching on everyone at once with a webinar; automations before the basics; the owner never opening it; no champion; and declaring victory at go-live. A safeguard: at go-live, the owner opens the CRM on a phone and finds this week’s pipeline in under a minute — if not, it is not ready.

It worked if, at ninety days, every enquiry has an owner and a next action, the weekly meeting runs from the screen, the owner trusts the pipeline number, and the team has asked for changes rather than for a way round it. This is the CRM implementation work we do — the process and fields, the cleaned migration, the integrations, the pilot, the training on phones, and the first quarter of adoption measurement and improvement — and the free audit starts by checking which of the sixteen your last implementation skipped.