Problem first. Platform second.
Choosing the platform first usually means spending the rest of the project defending it. The operating requirement, the ownership and the integration needs come before any shortlist.
Name the problem in operating terms. What decision or task is failing, and what would working look like on a normal day? Then look at what is already there: the systems, the data people trust, and the tools they quietly work around. A new platform that cannot see that estate, or that needs its own copy of it, adds a reconciliation job.
Decide who will administer it once the project team has left. Security and governance sit in the same decision: access, retention, exceptions and the record of what changed. So does adoption. A tool the site team will not use does not become the system of record, however well it scored in a demonstration.
Only then compare platforms. The question is fit. Can this product meet the requirement, join what already exists, and be run by a named owner? A preferred product is a hypothesis to test, not the requirement itself.