Skip to main content
Feature Usage shows what the account is actually doing in your product, expressed in your own feature vocabulary rather than raw event names.

​
Why it reads in your words

Superhawk maps product events onto the feature catalog you define for your workspace. That is what turns contract_created and clause_library_opened into “Contract creation” and “Clause library”, grouped into the modules you sell. If usage looks wrong or a feature is missing, the feature catalog is where to fix it. See Features & Modules.

​
What you see

  • Adopted features — what they use, and how heavily
  • Not explored — features available to them that they have never touched
  • Trend — whether usage of a feature is growing, flat, or falling
  • Depth — whether they use a feature occasionally or as part of their routine

​
Reading it

The gap is the point. A list of what someone uses is mildly interesting. The list of what they pay for and never open is where expansion and churn both live. Falling usage of a core feature outranks flat usage of a peripheral one. A customer whose contract creation has halved is in more trouble than one who never adopted reporting. Breadth predicts stickiness. An account using one feature deeply is easier to displace than one using five moderately, even at the same total volume.