CRM selection guide
Evaluate a CRM by following one case from start to finish
Start your CRM evaluation with a recurring workflow: opening an application, collecting and reviewing documents, contacting the client and changing the adviser. Identify where people search for information or lose track of ownership.
Run the same scenario in each candidate system for comparable evidence. The example below is fictional; use synthetic records and sample files without real client documents or contact details.
Test four actions using the same sample case
Create the record and establish responsibility
Create a synthetic application called Example A in the appropriate branch. Choose an adviser and check the initial stage. Later, find that record again through search or the application list.
Take a document through review
Upload an office-defined sample document, request a correction and upload another version. A file being present, a review waiting to happen and a document being approved should remain distinct.
Record the next action
Add a call task to the application. Record its outcome with an explanation and create a follow-up when needed. Do not assume that completing the task changes the application's workflow stage.
Ask another adviser to check
Have a second authorised team member explain the current position. Can they locate the earlier document version, the revision reason and the open task separately?
Turn observations into a decision record
Mark each step as demonstrated, needs clarification or not met. Record the screen and unresolved question. Distinguish special demonstration actions from the standard workflow available to your team.
In iyely Visa, you can evaluate application records, document review, tasks and the client portal together. Test the client's upload to a prepared document row separately. This is office workflow tracking; it does not produce a decision from an official authority.
- Access: can an adviser reach the branches and actions needed for their work?
- Capacity: does the intended plan fit active users, application volume and stored files?
- Migration: is the method for moving existing spreadsheets and files clear?
- Ownership: who in your team maintains the process and follows up unanswered questions?
Keep unmet requirements visible
Separate available capabilities from future ideas. Clarify the method and scope of any custom integration or bulk migration. Compare current pricing using explicit capacity assumptions; copied prices can become outdated.
Frequently asked questions
Must the demo cover every feature?
Complete your essential case workflow first. Evaluate additional features after the important requirements are met; a long list of unused options is not evidence of fit.
Can we evaluate everything with an administrator account?
Check the adviser's permissions as well. An action available to an administrator may work differently for the role that handles daily casework.
Support your decision with a sample case
Bring unresolved questions from your trial to a demo request. You do not need to send real client documents.