HOW WE WORK
Methodology
Key Takeaways
- Every guide starts from one job, and the criteria are published before any product is named. - Ranking is fit for that job. A platform placed fourth here can lead a different guide. - Evidence is documentary: public documentation, pricing pages, vendor material and customer reviews. - Nobody pays for placement, and no vendor reads a guide before you do.
How guides are built, what evidence goes into them, and what would get a platform removed from one.
What gets evaluated
Software that sits between customer feedback and a decision: CX platforms, feedback and text analytics, survey and review analysis, and the reporting layers built on top of them.
Adjacent categories that come up constantly and are out of scope: helpdesk software judged as a helpdesk, market research panels, general BI tools, and anything whose customer-experience claim is a marketing label on a different product.
The five criteria
Every platform in a guide is assessed against the same five, in this order.
Fit for the stated job. Does this genuinely serve the use case the guide names? Evidence: product documentation and feature availability by plan.
Depth of underlying analysis. Does it help you understand feedback, or only collect it? Evidence: documentation on taxonomy, tagging and theme building.
Integration coverage. Does it connect to the systems the team already runs? Evidence: published integration directories and API docs.
Pricing transparency. How much can a buyer establish without a sales call? Evidence: public pricing pages and published plan limits.
Manual work left behind. What is still yours to do after the tool has run? Evidence: documentation and customer reviews describing setup and upkeep.
How order is decided
Order follows fit against the job named at the top of the guide. It is not a quality score, and it does not carry between guides.
Where two platforms are close, the tie goes to the one a reader can evaluate without a sales call, because a buyer can act on that.
What evidence is used
Guides are built from public documentation, pricing pages, published integration lists, vendor material, and customer reviews on independent platforms. Where a claim comes from a vendor and cannot be verified elsewhere, the guide says so.
Guides are not based on hands-on use of the products. Everything assessed here can be checked by a reader against the same public sources, which is the point: a ranking you can audit is worth more than one you have to take on trust. Where a criterion cannot be judged from public material, the guide says so instead of guessing.
What gets a platform excluded
Pricing available only under NDA, where nothing about cost can be established publicly. A category claim the product does not support on inspection. Documentation too thin to assess the criteria above.
Exclusion is stated in the guide rather than left silent, so a missing name is explained.
Commercial relationships
Placement and ranking are never sold. No vendor sees a guide before it publishes. Where an affiliate relationship applies to a page, it is disclosed on that page and has no effect on order.
Corrections
Factual errors, material product changes and missing context are all corrected. Send them through the form on the contact page. A correction is reviewed on receipt, and the visible last-updated date changes when the change is material.
When something changes that would alter the ranking. Pricing moves, feature removals and acquisitions trigger a review of every guide the platform appears in.
Vendors can dispute a fact after publication through the contact page, and a supported dispute becomes a correction. Nobody gets to review a guide before it goes out.
Either it does not fit the job that guide names, or it met one of the exclusion conditions above. The guide says which.
Last updated: October 6, 2026