Module heat

Active seconds per module over 30 days, ranked most to least used, including the modules with zero.

What it is

A ranked bar list of every module in the product with the share of active time each took. Modules with no time are still listed, because a zero is the interesting result — it names the part of the product an account never opened.

Also called: which features get used · most used module · least used part of the app

See it
Module heat
Won
30%
Avg cycle
20d
Pipeline
$383k
JanSep
A most-to-least list of modules with proportional bars, the zero-time ones at the bottom. SuccessPanel.tsx. Sample data — no customer information appears here.
How it works
  1. 1Each session carries a map of module to active seconds; those are summed across the window.
  2. 2Every known module id is included, sorted by seconds descending, with a share of total.
  3. 3The platform-only module is excluded from tenant views.
Why we built it

The usage module lists 'module heat (active seconds per module — most and least used)' as a first-class output, and the ladder categories treat the top module as a headline stat. Keeping zero-time modules in the list is what makes it an adoption signal rather than a popularity chart.

The problem
  • Unused modules were invisible, so nobody knew what to train on.
  • Adoption could not be measured per feature area.
Sound familiar?
What you get
The untouched part of the product is named, which is where onboarding help goes.
Time share per module shows where the work actually happens.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →