Subscription Billing

Manage plan, seats, billing cycle, payment method, usage, and the cost impact before changing a subscription. The screen connects Plan and Usage so product teams can find the “Change plan” action while checking plan and seats.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Business plan · annual and 84 active seats, rather than an empty visual shell.

Subscription Billing
Use this template in Figr

Template facts

Screen

Form

Primary action

Change plan

Pattern

Form

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product teams need a clear “Change plan” action without losing sight of plan, seats and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Change plan is clearly available where the task happens.
  • Main view: Plan keeps the starting point obvious.
  • Connected view: Usage supplies nearby context.
  • Metric: Plan is visible with a meaningful value.
  • Another signal: Seats helps people judge what to do next.
  • Representative record: Business plan · annual makes the example specific.
  • Second record: 84 active seats shows the pattern works beyond one item.

States worth designing

  • Missing required details; show what people can do instead of leaving a blank panel.
  • Loading plan without changing the layout unexpectedly.
  • Invalid or conflicting entry; explain the problem and preserve work.
  • Permission denied for usage; clarify who can continue.
  • Success after choosing Change plan; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Plan → Usage → Change plan → Review outcome

Patterns used

Form, Plan, Usage, Invoices, accessible states, contextual actions

Why these choices work

Put requirements beside each field and show validation near the source of the error. Keep entered details if saving fails.

In this design, people should be able to compare Business plan · annual with 84 active seats. Make plan clear, then use seats to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Change plan” action. The happy path alone is not enough.

Related UI examples: Invoice Management, Expense Management, Budget Planning.

Start from this in Figr

Design a subscription billing screen for our existing software product. Use our real design-system tokens, components and product language. Show Plan and Usage, include believable records such as Business plan · annual, and make change plan easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr