That was the central point of our original guide, and it remains a useful place to start. Before comparing features, get clear about the job you need the system to do.
Start with a real customer journey
Pick a recent enquiry and follow it through your organisation. Where was it recorded? Who responded? What happened when it moved from sales to delivery, or from delivery to support?
Look for the awkward bits: copying details between systems, searching inboxes for a promise, asking a colleague for an update, or maintaining a spreadsheet because the main system does not quite fit. Talk to the people doing that work. Their workarounds are useful evidence.
Turn what you find into a short set of outcomes. For example: every enquiry has an owner; delivery can see what was agreed; customer-facing colleagues can find the latest conversation without asking around. These are more useful selection criteria than a long list of features.
Apply it to your work
Test CRM fit through a real customer journey
- Follow the journey
Use a recent customer example to find the actual need.
- Test the fit
Check the product against that work before committing.
- Plan the change
Decide what information belongs in it and how people will use it.
Test the fit before you buy
Ask shortlisted suppliers to demonstrate your actual scenarios. Give them the same examples so you can compare how each system handles the work.
Look closely at:
- Everyday usability. Can the people who will use it complete common tasks without unnecessary steps?
- Integration. Which information needs to move between systems, in which direction, and who handles a failed transfer?
- Reporting. Can you answer the questions that matter using data the team can realistically maintain?
- Configuration. What can you manage yourselves, and what will need specialist support?
- Full cost. Include migration, training, administration, integrations and ongoing support alongside licences.
- Exit options. Check how you can export your information and what would be involved in moving later.
A polished demonstration is a starting point. A small trial with your own scenarios will tell you more.
Decide what belongs in the CRM
The aim is a dependable shared view of customer relationships. That does not require copying every piece of business information into one application.
Agree which system is responsible for each important record. Define the essential fields, remove duplicates, and decide who keeps information accurate. Check access permissions before migration. Move what you need, and test a sample before committing the rest.
Give ownership to someone who can make decisions about the working process, with technical support where needed. Otherwise every change risks becoming an argument about settings.
Plan the change in people's work
Training should follow the tasks people need to perform. Show a colleague how to hand over a customer or record an agreed next step, then let them try it with support.
Explain what is changing, why it is useful, and where to raise problems. Leave room to improve the setup when real use reveals something the project missed.
Also decide what you want to do with any time saved. Better follow-up, more consistent service and less chasing are sensible goals to test. They should be measured rather than assumed.
A useful first step
Before starting a procurement exercise, write down three customer journeys your CRM must support and the problems in each. Use those journeys throughout selection, implementation and review.
If you need help connecting your customer processes, data and systems, talk to Yopla about where the current setup is getting in the way.
Originally published by Yopla in 2024. Refreshed for the current library.
All insights