Usage Metering

Track billable product usage against included limits, overages, forecasts, and workspace-level consumption before the invoice closes. This example brings Overview and By workspace together so account administrators can find the next task without losing context.

It includes representative records such as API requests · 64% and Storage · 81%. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Usage Metering
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Set alert

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Finance and operations teams need to set alert while keeping usage, requests and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Overview gives users an obvious place to start.
  • Supporting view: By workspace keeps the related context close.
  • Primary action: Set alert stays visible when people need it.
  • First signal: Usage shows a useful value (78%).
  • Second signal: Requests gives additional context (3.8M).
  • Sample record: API requests · 64%.
  • Next record: Storage · 81%.

States worth designing

  • No results for the selected range: say what changed, protect progress, and offer a clear next step.
  • Refreshing with old values visible: say what changed, protect progress, and offer a clear next step.
  • Metric source unavailable: say what changed, protect progress, and offer a clear next step.
  • Filter changed the interpretation: say what changed, protect progress, and offer a clear next step.
  • Export preparing: say what changed, protect progress, and offer a clear next step.
  • Restricted data hidden: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Overview → By workspace → Set alert → Review outcome

Patterns used

Analytics, Overview, By workspace, contextual actions, error recovery

Why these choices work

Keep the time range and metric definition visible. Let people see which segment or filter produced the result, then explain missing or delayed data.

Pay attention to overview and by workspace. People need to distinguish API requests · 64% from Storage · 81%. Keep usage visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Set alert”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Payment Methods, Billing History, Plan Upgrade.

Start from this in Figr

Design a usage metering screen inside our existing product. Use our current components, tokens and content language. Include Overview and By workspace views, credible records like API requests · 64%, and a clear “Set alert” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr