Sales Forecasting

Compare commit, best case, and pipeline coverage while exposing slips and manager judgment. The screen connects Forecast and Pipeline so sales teams can find the “Update forecast” action while checking commit and best case.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Enterprise · 72% coverage and Mid-market · 61% coverage, rather than an empty visual shell.

Sales Forecasting
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Update forecast

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 “Update forecast” action without losing sight of commit, best case and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Update forecast is clearly available where the task happens.
  • Main view: Forecast keeps the starting point obvious.
  • Connected view: Pipeline supplies nearby context.
  • Metric: Commit is visible with a meaningful value.
  • Another signal: Best case helps people judge what to do next.
  • Representative record: Enterprise · 72% coverage makes the example specific.
  • Second record: Mid-market · 61% coverage 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 forecast 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 Update forecast; 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

Forecast → Pipeline → Update forecast → Review outcome

Patterns used

Analytics, Forecast, Pipeline, Teams, 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 Enterprise · 72% coverage with Mid-market · 61% coverage. Make commit clear, then use best case 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 “Update forecast” action. The happy path alone is not enough.

Related UI examples: Contact Import, Territory Management, Account Detail.

Start from this in Figr

Design a sales forecasting screen for our existing software product. Use our real design-system tokens, components and product language. Show Forecast and Pipeline, include believable records such as Enterprise · 72% coverage, and make update forecast easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr