How we score
Every list on this site uses the rules below. The Find my best pick panel asks the questions published on that list, then re-applies these scores.
1. Weighted criteria (total = 100%)
| # | Criterion | Weight | What it measures |
|---|---|---|---|
| 1 | Features and fit for the list's niche | 25% | The core jobs for that list, from a checklist of must-haves and nice-to-haves |
| 2 | Pricing and value | 20% | Entry price, cost at a typical team size, free plan or trial, public pricing, add-on traps |
| 3 | Ease of use and onboarding | 15% | Setup, learning curve, templates, mobile app, and ease-of-use notes from reviews |
| 4 | Review sentiment (public) | 15% | G2 and Capterra rating and review volume. TrustRadius or an app store is used only when a list says so |
| 5 | Integrations and ecosystem | 10% | Native integrations for the niche, plus API, Zapier, or Make |
| 6 | Support and reliability | 10% | Channels and hours, documentation, status-page history, and support notes from reviews |
| 7 | Security, privacy, and compliance | 5% | SSO and 2FA, SOC 2 or ISO 27001, GDPR, and niche rules such as HIPAA for therapy tools |
A list may move a weight by up to 5 points if it says why and the total stays 100. The lists on the site currently use the standard weights.
What gets ranked
Each list states the one job a product must do natively to count. A product that fails that gate is not ranked. It can still be scored in an appendix with the reason it was left out.
"Natively" means a built-in feature on the vendor's own pages. A third-party integration counts only when that list says so. The gate does not change the weights.
2. The 0–10 scale
| Score | Meaning |
|---|---|
| 10 | Best in class for this niche; no meaningful gaps |
| 8–9 | Excellent; minor gaps |
| 6–7 | Good; noticeable gaps or trade-offs |
| 4–5 | Adequate; significant limits for this use case |
| 1–3 | Poor; serious gaps |
| 0 | Missing, or not applicable to the niche |
The overall score is the weighted sum of the seven criterion scores, shown to one decimal place. Ties break on review sentiment, then on price.
How each criterion is anchored
- Features: must-haves met, divided by total must-haves, times 8, plus up to 2 points for nice-to-haves.
- Pricing and value: start at 10. Subtract 2 if there is no free plan or trial. Subtract 1–3 for where the price at the list's typical size sits among the other tools. Subtract 2 if the price is not public.
- Review sentiment: take the review-count-weighted average star rating, R, across G2 and Capterra. Only a source with 20 or more reviews counts. Score = (R − 3.0) × 5, capped at 0–10. Subtract 1 if the counted reviews total fewer than 100, or if a count is not published. If no source qualifies, the score is a neutral 5.0 and the table marks it. A rating not read on G2 or Capterra is labeled as a third-party figure. If two snapshots from the same platform disagree, the lower one is used.
- Support: points for channels (chat, email, and phone, up to 3), availability (24/7 = 2, business hours = 1), documentation (0–2), and the review support sub-score (0–3).
3. Sources
Prices, feature availability, ratings, review counts, integrations, and certifications are cited. Vendor pages come first. Third-party sources are for things a vendor cannot report about itself, such as review sentiment, or for a price the vendor page did not publish. Those prices are labeled "Price from third-party source."
Each list shows the date the figures were checked. Prices and ratings are re-checked at least every 90 days.
A price the vendor does not publish is labeled Not published or Price on request. The score does not fill that gap with an estimate. Review quotes are not invented. Whether a company pays a commission does not change a score. See the disclosure.
4. Find my best pick
The panel on a list asks 2–4 questions, then re-ranks the published scores. It does not change the scores stored on the page.
Always asked
- Size: seats, subscribers, technicians, clinicians, or whatever changes the price on that list.
- Budget per month: a hard filter, plus a value re-weight when the list says so.
Optional pool. A list asks at most two of these, and only when they would change the order.
- Top priority: lowest price, most features, easiest to learn, best support, or integrations. The chosen criterion gains 10 points of weight, taken proportionally from the others.
- Must-have integrations: chosen from that list's integrations. Tools without them drop out.
- Must-have feature: chosen from that list's checklist. Tools without it drop out.
- Technical comfort: a simpler setup versus more to customize. This shifts weight between ease of use and features.
- Compliance: HIPAA, GDPR, or SOC 2, when the list asks. Tools that do not offer it drop out.
- Platform: mobile, Windows, Mac, or web only, when the list asks.
The panel applies those filters, recomputes the overall score, and shows the top 3 with a "Why #1 for you" line. If the filters remove every tool, it says so and shows the closest matches.