Revenue Operations

Watch pipeline hygiene, conversion, handoff quality, and process gaps across the revenue team. The screen connects Overview and Pipeline so sales teams can find the “Review pipeline” action while checking pipeline coverage and stage hygiene.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Lead to qualified · 41% and Qualified to discovery · 68%, rather than an empty visual shell.

Revenue Operations
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Review pipeline

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Sales teams need a clear “Review pipeline” action without losing sight of pipeline coverage, stage hygiene and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Review pipeline is clearly available where the task happens.
  • Main view: Overview keeps the starting point obvious.
  • Connected view: Pipeline supplies nearby context.
  • Metric: Pipeline coverage is visible with a meaningful value.
  • Another signal: Stage hygiene helps people judge what to do next.
  • Representative record: Lead to qualified · 41% makes the example specific.
  • Second record: Qualified to discovery · 68% shows the pattern works beyond one item.

States worth designing

  • No data for the chosen period; show what people can do instead of leaving a blank panel.
  • Loading overview without changing the layout unexpectedly.
  • Partial or delayed metrics; explain the problem and preserve work.
  • Permission denied for pipeline; clarify who can continue.
  • Success after choosing Review pipeline; 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

Overview → Pipeline → Review pipeline → Review outcome

Patterns used

Analytics, Overview, Pipeline, Process, accessible states, contextual actions

Why these choices work

Make time ranges, filters and metric units clear. Show the data behind each trend so readers can test what changed.

In this design, people should be able to compare Lead to qualified · 41% with Qualified to discovery · 68%. Make pipeline coverage clear, then use stage hygiene 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 “Review pipeline” action. The happy path alone is not enough.

Related UI examples: Territory Management, Quote Builder, Sales Forecasting.

Start from this in Figr

Design a revenue operations screen for our existing software product. Use our real design-system tokens, components and product language. Show Overview and Pipeline, include believable records such as Lead to qualified · 41%, and make review pipeline easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr