How to choose a CRM through a demonstration of your process
Choosing a CRM requires checking how the team will follow contacts, opportunities and tasks day to day. A long feature list does not reveal whether the journey works for your business. Prepare the same scenarios for every option, test taking your data out and compare the cost of the scope you actually need.
By the end, you can:
- Define essential pass-or-fail criteria
- Conduct a useful demonstration
- Test adoption and portability
Define the work the CRM should support
List the sales journey from the first enquiry to the decision and subsequent follow-up. Identify who works at each stage, which information they consult and what next action they need to schedule. Separate sales needs from accounting, stock or technical delivery; these may require connecting another system without turning the CRM into a repository for everything.
In a fictitious example, a maintenance business has three people in sales and two in coordination. It needs to associate several contacts with the same company, track proposals and hand won requests to operations. A contact list without opportunities does not cover the journey; a complex marketing system may add work without resolving handover to coordination.
Separate mandatory conditions from preferences
Choose criteria that prevent intended use if they fail: appropriate permissions, exporting necessary data, essential fields or a demonstrated connection to the system responsible for operations. Request a demonstration and documentation. A logo on an integrations page does not confirm the operations you need exist.
Then identify preferences that can be weighted, such as speed of recording or ease of configuring reports. Microsoft’s implementation guidance recommends matching standard capabilities to needs and considering extension maintenance. Check whether adaptation is supported configuration, custom work or a feature promised for the future.
| Criterion | Evidence to request | Treatment |
|---|---|---|
| Separate access between teams | Test with two distinct roles | Mandatory if the process requires it |
| Export essential relationships | Test file and reconstruction | Mandatory for the planned departure |
| Record the next action | Performed by a team user | Assess effort and clarity |
| Custom report | Build a specific question | Weigh importance and maintenance |
Use the same script in every demonstration
Prepare fictitious data and ask for the journey to be performed rather than just showing prepared screens. Create a company, associate two contacts, open an opportunity, record a proposal and schedule a future action. Then transfer the opportunity to another person and check what changes in access and notifications.
Add an exception: the same contact makes another request, an opportunity reopens or the person responsible is absent. Note steps, ambiguities and interventions by the demonstrator. A function that works only after specialised configuration may be suitable, but that effort should enter the comparison and training plan.
How do you test a CRM for teams selling through WhatsApp?
Use two people and a fictitious enquiry. A bookshop receives a WhatsApp request for thirty copies for an association. The customer requests two proposals, with and without delivery, and agrees to speak again on Thursday. The first person serves them today. The second should be able to resume the matter tomorrow while their colleague is absent.
Open a card in the ContactoIA demonstration and consult the tabs Dados (Data), Conversa (Conversation), Notas (Notes) and Histórico (History). The public demonstration lets you inspect the record in read-only mode. To test saving in the tool you are comparing, use a test environment with fictitious data.
| What to test | What the second person should be able to confirm |
|---|---|
| Who follows the proposal? | In the opportunity data, “Proprietário” (owner) identifies the person responsible. The person who handled the message may be different. |
| What was agreed? | Under “Próxima ação” (Next action), they should read something specific, such as “Prepare both delivery options”. Under “Próximo contacto” (Next contact), they should find the agreed day and time. |
| What has already been sent? | Read the conversation’s last message. An internal note or contact date in the CRM does not send a reply to the customer. |
| Did it pass the test? | Ask the second person to explain without help which proposal is missing, who prepares it and when they should reply. If finding out requires phoning the colleague, record what was missing from the record. |
Test incoming data and the possibility of leaving
Check the difference between person, company, opportunity and activity. Ask how the CRM resolves duplicates, preserves history and relates records. Import a small fictitious sample with two people from the same company and distinct requests. Also check how you correct an incorrect association without deleting history you need to retain.
Export the sample and try to reconstruct relationships outside the tool. HubSpot’s export documentation, for example, distinguishes export options and formats; it serves as a reminder that scope is product-specific. Confirm custom fields, identifiers, associations, notes, attachments and activities. A file with names and emails is not equivalent to taking out an entire sales operation.
Score with evidence and compare the same scope
After applying mandatory criteria, assign weights to the remaining needs. In a fictitious matrix, daily operations count for 40%, data and departure for 25%, integration for 20% and administration for 15%. Scores may run from 0 to 4: absent, insufficient, usable with adaptation, suitable or well demonstrated. Record evidence beside the score.
If an option scores 3, 4, 2 and 3, the weighted result is 3 × 0.40 + 4 × 0.25 + 2 × 0.20 + 3 × 0.15 = 3.05 out of 4. These weights are a choice for this example, not a market benchmark. A high average should never compensate for failure to meet a mandatory condition.
| Cost component | What to confirm in writing |
|---|---|
| Usage | Roles, number of users and included functions. |
| Preparation | Configuration, migration, training and data to clean. |
| Continuity | Support, integrations, storage and changes. |
| Leaving | Export, timescales, assistance and contractual conditions. |
Run a pilot with tasks and completion criteria
Choose a small group representing the real roles. Agree a period and specific tasks without indefinitely duplicating records across two systems. Measure whether requests have a person responsible, a next action and necessary data. Collect observed difficulties; “I liked the appearance” and “I could resume a request without asking for help” are different assessments.
Test a user’s absence, export, error correction and handover of a won opportunity to operations. Do not use the pilot to trigger real campaigns or notifications without preparation. At the end, decide whether to adopt, correct and repeat a limited set of tests, or reject the option. Document the reason and work needed before full use.
- Avoid choosing solely by initial price or number of features.
- Confirm which plan supports each demonstrated function.
- Include the team that will maintain data and permissions.
- Identify who is responsible when an integration stops working.
Record a decision another person can understand
Keep the script, results, commercial conditions and outstanding questions with the decision. This information lets you implement the chosen option and check whether the pilot matches the contracted configuration. If no option fulfils the essential journey, review the process or adaptation needs before adding disconnected tools.
Worksheet for your project
CRM selection worksheet Sales journey and teams involved: Mandatory conditions and evidence of fulfilment: Scenarios used in demonstrations: Criteria, weights and scoring scale: Scores and evidence for each option: Data structure and duplicate rules: Required integrations and person responsible: Export tested, files and limitations: Preparation, usage, continuity and departure costs: Pilot tasks, participants and criteria: Difficulties found and planned resolution: Decision, outstanding conditions and date:
Sources and criteria
Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.
