How we score

How we score CRMs

How bestCRM scores each CRM — explicit criteria, weights by vertical, and public sources only. No lab tests, no paid rankings.

Updated September 26, 2026

bestCRM is an editorial comparer for the US/English market. Scores do not come from blind tests, mystery shopping, or vendor-private data. They come from what each product claims on its official pages, read against the yardstick for that segment — system sizing and financing in solar; listings, portals, leasing, and messaging in real estate; inbox, official API, and pipeline in the WhatsApp vertical; what the permanent $0 plan already includes on free plans; charts, insurance billing, and patient messaging in clinics; matters, deadlines, fees, and client messaging in legal; enrollment pipeline, tuition, and family outreach in education.

That has a clear limit — and we would rather say it out loud than fake precision. If you want to decide well, use these profiles to show up at the demo with the right questions, not to skip the demo.

What goes into the score

Each CRM gets a 0–10 score on six axes. The math is the same across the site. The name of each axis changes with the segment, because the pain changes.

In solar energy the axes are proposal generator, financing, post-sale and monitoring, native messaging, price, and learning curve. Proposal and credit weigh more than messaging and price: a pretty pipeline with zero kW sold loses points on purpose.

In real estate the same slots become inventory and proposal, mortgage credit, leasing and post-sale, native messaging, price, and learning curve. Inventory and messaging weigh more than credit — a lot of brokerages live on rentals, and the lead lives in text and phone. Credit stays on the yardstick because, when it is real, it shortens the sale.

In WhatsApp (the dedicated Meta channel vertical) the same slots become pipeline in chat, official API, automation and campaigns, multi-agent inbox, price, and learning curve. The inbox weighs more: without conversation inside the product, the rest is spreadsheet CRM with a phone on the side. Browser extensions, web sessions, and a sibling product from the same brand count as missing. Meta’s per-message fee stays out of the price score.

In free plans the same slots become pipeline on free, automation on free, email and reporting, messaging on free, free-plan ceiling, and learning curve. Ceiling and automation weigh more: this vertical asks what you already get without paying. A 7-, 14-, or 21-day trial does not count. A feature the rate card only unlocks on a paid plan counts as missing. Marketplace messaging channels also count as missing.

In clinics the same slots become charting and care, insurance and billing, patient relationship, messaging and confirmations, price, and learning curve. The chart weighs more: a schedule without a clinical history pushes the visit back onto paper.

In legal the same slots become matters and deadlines, fees and billing, relationship and intake, native messaging, price, and learning curve. Matters and deadlines weigh more: a pretty pipeline with zero docket work loses points on purpose. A client portal alone does not earn the messaging flag; native two-way SMS or WhatsApp API on the matter/contact does.

In education the same slots become enrollment and admissions pipeline, tuition and billing, retention and re-enrollment, family outreach, price, and learning curve. The enrollment pipeline weighs more: a generic sales board with zero campus visit, application, or term loses points on purpose. The US stack is more sliced than a typical all-in-one school CRM — higher-ed enrollment CRM, private-school SIS, and tuition management are often different products, so sibling SKUs do not earn native flags. Family outreach means native SMS/messaging (or WhatsApp API) on the candidate or family record — not email-only or portal-only tools.

Native messaging (US yardstick)

Outside the dedicated WhatsApp vertical, the messaging axis is not Meta-only. Native SMS or an in-product messaging inbox on the lead/contact/patient/matter card counts. WhatsApp Business API also counts. Marketplace apps, Zapier, browser extensions, website chat buttons, one-way reminder blasts, and sibling SKUs do not.

The dedicated WhatsApp ranking stays Meta-specific on purpose: that vertical compares WhatsApp inboxes and official API products.

The overall score

The overall score is a weighted average. Each vertical’s weights sit in the sidebar on this page and on the ranking. A generic CRM enters the same ranking as the vertical tools. The score shows what the product is — not a “satisfaction index.”

A score is not the same thing as a feature

Besides scores, each profile has a has / does not have feature list. The rule is conservative: we only mark “has” when the feature ships in the product. Marketplace integrations, third-party apps, or “you can do it with Zapier” count as does not have. The score captures perceived quality in the sources; the feature flag captures presence only.

What we don’t do

We do not invent pricing. If there is no public rate card, the profile says “contact for pricing,” and the price score drops for opacity — not because the product is expensive.
We do not copy third-party rankings. Marketplace stars or review-site scores do not become our methodology.
We do not sell placement. No vendor pays to appear, climb, or get highlighted. If an affiliate link ever exists, it will be labeled on the profile and will not change the score.
We do not run lab tests. Worth repeating: this is critical reading of public sources, not a technical benchmark.

How profiles age

Each profile shows the date of the last review. When a vendor changes the product, we revise and the date moves with it. If a source disappears, the claim that depended on it comes out. Found something stale or wrong? Corrections are welcome — we want to be challenged with a better source.