The demonstration looks convincing: colourful pipelines, automated reminders and a dashboard full of possibilities. Three months later, customer details are still scattered across phones and spreadsheets. The CRM exists, but the team does not trust it as the place to manage work.
Choose a CRM by testing the everyday process it must support. Features matter, but adoption depends on whether people can record useful information, see their responsibilities and move the customer relationship forward without unnecessary administration.
Map one real enquiry from start to finish
Select a recent enquiry and trace what happened. Where did it arrive? Who responded? What information was needed? Who prepared the quotation? What caused a delay? Where was the outcome recorded?
Describe the stages in terms the team understands. “New enquiry,” “needs confirmed,” “quotation sent” and “decision pending” may be more useful than a complicated sales vocabulary nobody uses. Define the evidence required to move between stages.
Record exceptions too: duplicate enquiries, a customer with several projects, a contact changing organisations or a quotation that needs revision. These cases often reveal whether the proposed system fits the business.
Decide the minimum useful record
Identify the fields needed to act: customer or organisation, relevant contacts, requirement, owner, next action and due date. Add other fields only when their purpose is clear.
A form with too many mandatory fields can encourage invented answers or delayed entry. Keep early-stage records proportionate, then collect more detail as the enquiry progresses. Explain who maintains the information and which record is authoritative.
Separate customer facts from internal opinions. Use access controls for sensitive notes and avoid collecting information simply because the software provides a place to store it.
Test the shortlist with your own scenarios
Ask each supplier to demonstrate the same workflow using realistic sample data. Include assignment, reassignment, follow-up, quotation history, lost opportunities and reporting. Test on the devices the team actually uses.
Have frontline staff complete the tasks themselves. A skilled salesperson can make almost any interface look simple. The relevant question is whether your team can repeat the task without coaching.
Check search, duplicate handling, import and export. Understand how you would retrieve your records if the service changed or the business decided to move. Ownership and portability deserve attention before a contract is signed.
Price the implementation, not just the licence
Include configuration, data cleaning, migration, training, integrations and ongoing administration. Identify which useful features require a higher subscription tier or a separate tool.
Ask who will maintain automations and reports after launch. A workflow that only the supplier understands creates a dependency. Document the configuration and retain appropriate administrative access under the organisation's control.
Confirm support arrangements and what happens when an integration fails. A CRM can be available while an important connection silently stops transferring enquiries.
Launch with a small, accountable process
Choose a pilot team and a defined set of records. Agree how the old and new processes will overlap, then set a clear changeover point. Avoid allowing two competing customer lists to remain authoritative indefinitely.
Train people on their actual work, including mistakes and corrections. Review a sample of live records with managers. Missing next actions and inconsistent stages usually require clearer operating rules, not another dashboard.
Measure whether enquiries are assigned, followed up and resolved more reliably. The CRM earns its place when it supports that behaviour and gives management a trustworthy view of the pipeline.
Scope your CRM workflow, migration and implementation with Zero Impulse.




