1. Define the buyer job
Begin with a workflow, owner, users, data, integrations, risk, time horizon, and budget. Product names do not define the requirement.
2. Classify the relationship
A direct comparison covers substantially the same primary job. An adjacent comparison covers overlap without complete substitutability.
3. Use equal evidence requests
Each vendor receives the same scenario, roles, data sample, quantities, integrations, security questions, and assumptions.
4. Normalize cost
Separate licenses, usage, implementation, migration, support, dependent products, administration, renewal change, and exit work.
5. Prefer current sources
Vendor pages, documentation, legal terms, and trust centers support vendor-controlled facts. The buyer confirms the current quote and contract.
6. State the boundary
PR97 does not claim hands-on testing, customer interviews, private pricing datasets, or verified user reviews. The site helps buyers structure their own evaluation.
7. Correct material errors
Public sources change. Send product relationship, source, and pricing-model corrections under the corrections policy.