Plan Upgrade

Compare plans, understand usage limits, estimate the next invoice, and upgrade without losing existing workspace settings. This example brings Plans and Usage together so account administrators can find the next task without losing context.

It includes representative records such as Pro plan · current and Business · recommended. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Plan Upgrade
Use this template in Figr

Template facts

Screen

Settings

Primary action

Upgrade plan

Pattern

Settings

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 upgrade plan while keeping current plan, monthly usage and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Plans gives users an obvious place to start.
  • Supporting view: Usage keeps the related context close.
  • Primary action: Upgrade plan stays visible when people need it.
  • First signal: Current plan shows a useful value (Pro).
  • Second signal: Monthly usage gives additional context (78%).
  • Sample record: Pro plan · current.
  • Next record: Business · recommended.

States worth designing

  • Default preferences: say what changed, protect progress, and offer a clear next step.
  • Unsaved changes: say what changed, protect progress, and offer a clear next step.
  • Policy blocks edit: say what changed, protect progress, and offer a clear next step.
  • Changes applied: say what changed, protect progress, and offer a clear next step.
  • Restricted settings: say what changed, protect progress, and offer a clear next step.
  • Connectivity interrupted: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Plans → Usage → Upgrade plan → Review outcome

Patterns used

Settings, Plans, Usage, contextual actions, error recovery

Why these choices work

Separate safe everyday choices from risky changes, show who can edit them, and confirm irreversible actions.

Pay attention to plans and usage. People need to distinguish Pro plan · current from Business · recommended. Keep current plan 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 “Upgrade plan”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Payment Methods, Usage Metering, Billing History.

Start from this in Figr

Design a plan upgrade screen inside our existing product. Use our current components, tokens and content language. Include Plans and Usage views, credible records like Pro plan · current, and a clear “Upgrade plan” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr