Skip to guide content
SaaS PulseUser guide

Product documentation

SaaS Analytics Dashboard User Guide

Use this guide to understand what each management workspace shows, how to read its signals, and which interactions and states are available.

This portfolio application uses typed sample data. It demonstrates product behavior and engineering decisions; it does not connect to a production SaaS account or Jira tenant.

Overview

SaaS Analytics Dashboard models a multi-workspace management console for reviewing commercial performance, customer risk, and delivery execution in one place.

What to look for

  • The dashboard uses deterministic sample data so every workspace can be reviewed without credentials or external services.
  • Overview supports a quick operating scan; Revenue, Customers, Delivery, and Health provide focused analysis.
  • Settings demonstrates how management alerts and operating thresholds could be configured.

Dashboard / Overview

The executive overview combines the signals a manager is most likely to scan before opening a focused workspace.

What to look for

  • KPI cards track monthly recurring revenue, active accounts, logo churn, and trial conversion with trend context.
  • Revenue composition separates new business and expansion while the MRR series shows the overall direction.
  • Management focus cards link directly to revenue, customer, delivery, and health follow-up views.
  • Operating pulse summarizes customer and commercial movement, while Refresh re-runs the current data queries.

Revenue

Revenue isolates recurring-revenue movement so acquisition, expansion, churn, and account growth can be compared without the density of the overview.

What to look for

  • Summary cards show current MRR, new business, expansion, and month-over-month growth.
  • The composition chart pairs bars for new business and expansion with the MRR trend; a text summary exposes the same key insight accessibly.
  • Revenue history provides exact monthly values for MRR, acquisition, expansion, churn, and customer count.
  • Watch items call out expansion momentum, churn pressure, and the latest account-base size.

Customers

Customers supports account triage through search, segmentation, health context, and paginated results.

What to look for

  • Search matches customer records, while lifecycle-status and plan filters narrow the current segment.
  • Clear filters restores the full segment and pagination moves through eight accounts at a time.
  • Health score, product usage, MRR, plan, status, and ownership make each account actionable.
  • Loading preserves the page structure; empty, error, and retry states explain what happened and how to recover.

Delivery

Delivery presents Jira-like sample signals for release readiness and flow analysis; it is not connected to a live Jira workspace.

What to look for

  • Sprint predictability compares completed and planned points, while cycle and lead time expose flow speed.
  • Blocked work, escaped bugs, scope change, and team confidence frame release risk.
  • The weekly trend compares committed, completed, created, and resolved work with blocker counts.
  • The risk queue prioritizes issue status, owner, age, customer impact, and the management signal requiring attention.

Health

Health turns account activity, billing status, and health scores into a customer-success follow-up view.

What to look for

  • Summary metrics show average health, low usage, past-due accounts, and customers above the healthy threshold.
  • The distribution groups accounts into Healthy, Watch, and Risk bands with accessible meter values.
  • The risk queue orders the lowest-health accounts first and includes usage, MRR, owner, region, and last activity.
  • The workspace supports prioritization; it does not modify customer records or send outreach.

Settings

Settings demonstrates manager-facing alert preferences and guardrails with an immediate preview of the enabled rules.

What to look for

  • Alert subscriptions cover delivery risk, customer health, and revenue variance review.
  • Guardrails set the blocker limit, churn budget, and health-risk threshold used by the preview.
  • Reset defaults restores the initial values, and the data-source panel identifies live-shaped demo and Jira sample inputs.
  • Settings are session-local demo state. Reloading the page restores defaults; no account or backend persistence is implied.

Accessibility and responsive behavior

The interface is designed to remain understandable across input methods, color schemes, data states, and viewport sizes.

What to look for

  • Semantic landmarks, heading hierarchy, labelled controls, visible focus, and keyboard-reachable navigation support non-pointer use.
  • Charts include text summaries, tables use captions and headers, and status changes expose meaningful loading, error, empty, and retry content.
  • Desktop layouts favor scan density; mobile navigation remains reachable and dense tables become scrollable regions or compact cards.
  • The light or dark theme follows the saved choice, then the system preference, and the theme action always describes the available change.

Technical resources

Product guidance stays here. Generated API details, coverage evidence, architecture, and deployment notes have their own focused surfaces.