Should adoption be measured by assigned seats or active users?

mbrooks

For a generic SaaS product, imagine 200 purchased seats, 150 assigned seats, and 90 people who completed a core workflow this month. Different denominators tell different stories, and a single adoption percentage could hide either unused licenses or onboarding friction.

Which measures would you present to an account owner, and how would you label them? Would you include both breadth of usage and repeat usage? I am looking for a practical way to explain the numbers without turning a routine review into a lesson in analytics terminology.

lrichardson

I would show seat assignment as 150 of 200 purchased, then meaningful usage as 90 of 150 assigned. Those answer different questions and should keep their own labels. Add a repeat-use measure with a defined time window if the workflow is expected to recur. Avoid calling a login alone meaningful adoption.