Usage And Billing

Use usage to understand adoption

flowchart LR
    Activity["Workspace activity"] --> Usage["Usage view"]
    Usage --> Decision["Admin and rollout decisions"]

Usage and billing views help administrators understand adoption, workflow concentration, and where AI-heavy or review-heavy activity may deserve closer attention.

What usage does tell you

Usage is useful when teams need to:

• review a quick summary of current activity
• understand which workflow areas are driving usage
• compare current usage against recent rollout or process changes

What usage does not tell you

Usage is not the pricing control plane.

It does not by itself define:

• which plan a customer should buy
• what governance depth is included
• when a team should move from a focused rollout to a broader governed operating model
• which commercial terms apply to the account

Those decisions belong in the customer agreement.

Read usage with packaging in mind

The right question is usually not How many events happened?

It is:

• is the current plan still the right operational fit
• is the team using TrialStack as a focused study workspace or a broader operating system
• is adoption pressure revealing a need for more governance, standardization, or rollout support

Common mistake

The main mistake is treating usage as a billing-only surface. In practice it is an operational signal about adoption, AI intensity, workflow concentration, and whether the current rollout model still matches how the team is actually working.