Skip to main content
All articles

CRM adoption: what to measure instead of logins.

Below Enterprise, HubSpot's activity log filters by Login and Security Activity. So the one adoption number your CRM will hand you at your tier is the one that proves the least, and teams end up measuring the thing that was available rather than the thing that matters.

Toni MedicToni MedicSalestructSeptember 9, 20269 min readCRM & Pipeline
The short version
Illustration of five identical desks seen from above, each with a laptop, four of them closed and dark and one open and lit.
Five seats, five licences, one screen actually open. Every one of those five logged in this week.

Ask most teams how CRM adoption is going and you get a login number. Ninety percent of seats active this month, which sounds like adoption and is not.

There's a reason everyone reaches for it, and it isn't laziness. It's the only number the software will give them.

The short version

  1. HubSpot documents that on Starter or Professional, users "will be able to filter by Login or Security Activity". Categories covering what people did to records are Enterprise.
  2. So at the tier most teams buy, logins are visible and behaviour is not. The available metric became the reported metric.
  3. A login proves somebody opened the software. It says nothing about whether the record they opened is now truer than it was.
  4. Adoption is better read from the record than from the user: can it answer a question without a phone call?
  5. Four signals work at any tier and need no reporting feature: deal age accuracy, next-step presence, close-date drift, and the handover test.

What is CRM adoption?

CRM adoption is the extent to which a team's real selling activity is reflected in the CRM rather than in inboxes, notebooks and people's heads. It is a property of the records, not of the users.

That distinction is the whole post. A team can be in the system daily and the system can still be unable to tell you anything, which is the state most companies are actually in when they say adoption is fine.

The metric you can get is not the metric you want

HubSpot's account activity documentation sets out what each tier can see. In its own words, users in a Starter or Professional account "will be able to filter by Login or Security Activity". The categories that cover what people actually did, listed as "Approval, Content, Workflows, and more", are Enterprise.

So a 20-person company on Professional can see that Anna logged in on Tuesday. It cannot see that Anna edited four close dates, deleted a contact, or moved a deal backwards.

That produces a specific and very common failure: the team reports the number the tool exposes, the number looks healthy, and nobody notices that the pipeline is maintained by two people and ignored by six. The available metric became the reported metric, which is a pattern worth watching for anywhere, not just here.

Illustration of a tall glass measuring cylinder filled only at the bottom, with a hand above it adding a single drop from a dropper.
Measuring the thing you can reach rather than the thing you need. The reading is accurate and it is not the answer.

Four signals that work at any tier

None of these needs a reporting feature, an Enterprise upgrade, or a dashboard. They are all readable from the records you already have, which is the point.

SignalHow to read itWhat a bad reading looks like
Deal age against the rep's memoryTake five open deals. Compare the last activity date with when the rep says they last spoke to the accountA gap measured in weeks. The CRM is a Friday filing exercise, not a record
Open deals with a dated next stepCount them, as a share of all open dealsUnder about half. The pipeline is a list of hopes with amounts attached
Close-date driftCount deals that have moved their close date more than twiceAny meaningful number. The date is being set to satisfy the field, not to describe the buyer
The handover testGive one live deal to someone who has never touched it. No asking the ownerThey need the owner for anything material. That part of your process lives in a person, not the system

Run the handover test first if you only run one. It takes about ten minutes and it states the problem more precisely than any dashboard will.

The pattern in all four: you are reading the record, not the user. A record that can answer a question is adoption. A user who logged in is attendance.

None of this needs an upgrade. It needs somebody to open five deals and be honest about what they find, which is also why it rarely happens.

Common questions

CRM adoption is the extent to which a team's real selling activity is reflected in the CRM rather than in inboxes, notebooks and people's heads. It is a property of the records rather than of the users, which is why login rates describe it so badly: a team can be in the software every day while the records remain unable to answer a basic question about a live deal.
Because a login proves somebody opened the software and nothing more. It cannot distinguish a rep who updated four deals from one who checked a phone number and left. Logins get reported because they are usually the only thing exposed: HubSpot documents that Starter and Professional accounts can filter account activity by Login or Security Activity only, with behavioural categories reserved for Enterprise.
Read the records rather than the users. Four signals need no reporting feature: the gap between a deal's last activity date and when the rep actually last spoke to the account, the share of open deals carrying a dated next step, how many deals have moved their close date more than twice, and whether a colleague can pick up a live deal using the CRM alone.
Take one live deal and ask someone who has never touched it to pick it up using only what is in the CRM, without asking the owner. Whatever they cannot answer is the part of your sales process that lives in a person rather than in the system. It is the fastest adoption diagnostic available and it costs about ten minutes.
Aim for most of them, and treat anything below about half as a failure. A dated next step is the one field a rep cannot fabricate retroactively, so its absence across a pipeline means the records are being maintained for reporting rather than for selling, and any forecast built on that pipeline is describing intentions rather than a process.

Sources

  1. HubSpot, View and export account activity history. States that "users in a Starter or Professional account will be able to filter by Login or Security Activity", with Enterprise accounts able to filter by further categories including Approval, Content and Workflows. Page states last updated 22 June 2026. Fetched and read 9 September 2026 (2026)

How these were checked

The tier and category facts above come from that single HubSpot page, opened directly rather than through a search summary. The four signals in this post are method rather than vendor behaviour, and they are stated as such: they need no reporting feature and no particular product.