A shortlist.
With substance.
Compare three CRM options against the work your team needs to do. Set your priorities, record the evidence and see which requirements still need an answer.
Build your comparisonA high average cannot fix a failed must-have.
- Your requirements. Your weights.
- Unassessed stays unassessed.
- Evidence behind every rating.
- No prefilled vendor rankings.
Loading your comparison…
Weight: 1 = low priority, 5 = high priority. A must-have needs a score of 3 or 4. Leave untested items unassessed. On smaller screens, scroll the comparison horizontally.
| Requirement & priority | Option A | Option B | Option C |
|---|---|---|---|
How the score is calculated
For each option: add weight × rating, divide by 4 × the sum of all requirement weights, then multiply by 100. Results are rounded to whole percentages. Unassessed rows earn no points, but remain in the denominator, so incomplete results are provisional. This does not mean an unassessed feature is unsupported.
“Ready to shortlist” requires every row to have a rating and evidence note, every must-have to score at least 3, and the option name and all requirement names to be filled. Scores are your assessment; this tool does not independently verify the evidence or recommend a vendor. Remove requirements that do not apply equally to all options.
Make the requirement testable.
Replace the starting rows with your own workflow requirements. Give each a weight from 1 to 5. Mark only genuine adoption conditions as must-haves, then use the same definitions for all three options.
A useful row names observable behaviour: “A repeated website submission updates the existing enquiry without creating a duplicate.” A vague label such as “good automation” is harder to assess consistently.
Rate what you can demonstrate.
Use 0 for unsupported, 1 for major gaps, 2 for a workaround, 3 for meets the requirement and 4 for exceeds it. Leave unknowns unassessed. Add the tested plan, result and limitations in the evidence note.
The notes are yours; the tool does not check the underlying claim. Avoid entering confidential client data. The comparison is saved locally in this browser and is not submitted to Meibo’s CRM.
Use the score to ask better questions.
A score is a structured summary of your assessment, not an independent product review. Compare total cost, pilot results and unresolved risks before choosing. Small percentage differences may reflect subjective weights rather than a meaningful product difference.
Export the CSV to keep the ratings, evidence, calculations and must-have status. Browser storage is specific to this origin and browser profile; clearing it removes the saved comparison. The CSV is an export, not an importable backup for this tool.
Before you shortlist.
Can I add my own requirements?+
Yes. Edit the starting six rows, add up to 20 requirements and remove rows that do not apply. Weights and requirements apply consistently to all three options.
Why is my score provisional?+
Some requirements have not been rated. They earn no points while remaining in the total possible points. Complete the assessment before comparing final percentages.
Why does an option fail despite a high score?+
At least one must-have has a rating below 3. The tool keeps that failure visible even if the weighted total is high.
Does ready to shortlist mean we should buy it?+
No. It means every row has a rating and evidence note, names are filled and all must-haves pass your assessment. You still need to verify the evidence, costs and pilot outcome.
Next: read how to choose a CRM, plan the implementation, or review Meibo’s actual plans. This is Meibo’s own decision framework; see our editorial policy.