Aartha logoAartha

What is product adoption?

Also known as: User adoption, Feature adoption

Product adoption is the extent to which customers actively and habitually use a product to accomplish their work. It is measured through breadth (how many users), depth (how much of the product), and frequency (how regularly) rather than by logins alone.

Formula

How to calculate product adoption

Adoption rate = (Active users ÷ Provisioned users) × 100
Active users
Users performing a meaningful action within the period — not merely logging in
Provisioned users
Users with licenses or seats available to them

Worked example

An account has 200 licensed seats and 130 users performed a core action last month. Adoption rate = (130 ÷ 200) × 100 = 65%.

In practice

What you need to know about product adoption

Logins are not adoption

A login measures access, not value. The meaningful denominator is a core action — the thing the product exists to do. Defining that action per product and per role, then measuring against it, converts adoption from a vanity metric into a predictor. Teams reporting login-based adoption typically discover their numbers have no correlation with renewal.

Breadth, depth, and frequency behave differently

Breadth of adoption across users is the strongest protection against champion turnover, because value is distributed. Depth across features raises switching cost. Frequency indicates whether the product has become habitual. An account can score well on one and badly on another, and the mix tells you which risk you face: a single power user is a concentration risk, while broad shallow use suggests value has not deepened.

Adoption without outcome is still risk

Heavy usage that does not produce a business result the customer can point to is fragile. When a budget review comes, usage statistics are a weak defence compared with a named outcome. Adoption is a means to value, not a substitute for it.

How to improve it

Improving product adoption

01

Define a core action per role

An administrator, an analyst, and an executive use the product differently. Measuring all three against the same action mislabels healthy accounts as unhealthy.

02

Watch unused seats

Provisioned but inactive licenses are the most visible target in any budget review and a reliable predictor of contraction at renewal.

03

Look for adoption concentration

If a large share of account activity comes from one or two users, the account is one resignation away from becoming dormant.

FAQ

Product adoption questions, answered

How do you measure product adoption?+

Measure the percentage of provisioned users performing a meaningful core action within a period, then layer in depth of feature use and frequency. Avoid login-based measurement — access is not usage, and login-based adoption metrics typically show little correlation with renewal outcomes.

What is a good product adoption rate?+

It depends on how seats were sold and what role users hold. Products sold as company-wide licences often show lower percentage adoption than those sold seat-by-seat, without being less healthy. Compare accounts against similar accounts in your own base, and treat trajectory as more informative than level.

Can an account have high adoption and still churn?+

Yes, and it happens frequently. Usage concentrated in one or two individuals leaves the account exposed to their departure, and heavy use that never produced a demonstrable business outcome is difficult to defend in a budget review. Adoption reduces churn risk only when it is broad and tied to a named result.

Your next account move is already in the signals

Know the metric. Know why it moved.

Aartha keeps a cited, time-aware memory of every account — so a health change or a churn signal comes with the evidence behind it.