Implement a CRM: a practical plan from process choice to the first month

Choose a bounded process and outcome

“Put the whole business in CRM” is not a useful first assignment. Start with a journey such as website enquiry to completed advice. It has a beginning, owner, information requirements and observable result.

Describe current work: where the request arrives, who reads it, where the latest agreement lives and when responsibility changes. Use a normal record and two exceptions. A process that exists only on paper is difficult to automate.

Name an internal process owner to decide field, stage and handover meanings. A supplier can propose configuration but cannot independently decide what “qualified” or “ready for delivery” means for your organisation.

Require concrete deliverables

Verifiable outputs prevent “nearly ready” remaining undefined. A configuration screen does not establish a functioning customer journey.

Validate with actual roles

Have an adviser handle an enquiry, a colleague cover and a planner read the outcome. Use fictional or appropriately selected test data. Include missing details, repeated submissions and a rejected proposal.

Test ordinary user permissions. Microsoft's role documentation distinguishes access and privileges. Include search, documents and export.

Acceptance asks whether staff can do their jobs, the next person understands the record and exceptions can be handled. Assign failures and retest after correction.

Treat migration as its own workstream

Clean and map before final transfer. Salesforce's migration guidance includes validation and user preparation. Upload without user inspection leaves substantial uncertainty.

Agree when the old system stops changing and which active work transfers. Explain count differences. The migration guide provides a mapping and reconciliation approach.

Train work rather than interface tours

Have every employee assess an enquiry, schedule a next action, retrieve a conversation, revise a quotation and report a problem.

Use short instructions covering when, required information, where to record the result and exception handling. Participants must perform the work themselves; watching a presentation does not establish understanding.

Create a clear help route and internal first contact. Repeated questions may expose unclear operating agreements rather than insufficient training.

Launch criteria and the first month

Broaden use when enquiries arrive, tasks are visible, access works and no unresolved primary-process blocker remains. Define who can delay launch and what staff do during recovery.

One possible review sequence is daily exception checks initially, a recurring-issue review after the first full working week and a dossier-based review after a month. This is a suggested cadence, not a guaranteed project duration.

Measure work-related behaviour: active records without owners, missing next actions and incomplete handovers. Login counts alone do not show good customer handling.

Expansion checklist

Add another team, channel or automation when the initial process works consistently and a specific need exists. Reuse definitions where appropriate and identify genuine differences.

Record changes with a problem, example, desired outcome and effect on existing records. Prioritise customer work. Continue with automation selection and team handovers.