Founders and operators
Use it to connect growth, retention, and expansion before deciding where product or commercial attention is needed.
Concept Preview
Fictional sample dataSaaS Overview
MRR$84.2k+6.4%
Active accounts2,418+91
Churn2.7%-0.3 pt
Expansion$9.6k+8.1%
Recurring revenue trend
Plan distribution
Who This Dashboard Is For
The screen works best when it supports a recurring operating review rather than trying to serve every department at once.
Product leaders
Use account and adoption signals to identify where activation, engagement, or plan design may be creating friction.
Customer success teams
Use health segments, upcoming renewals, and recent account activity to prioritize conversations without treating a score as a substitute for judgment.
KPIs and Data
Use a small set of metrics with definitions that remain stable across reporting periods. A number without a cohort, comparison, or time window is easy to misread.
Monthly recurring revenue
- What it measures
- The normalized recurring subscription value active during the selected month.
- Why it belongs
- MRR shows the current revenue base and makes new, expansion, contraction, and churn movements comparable.
- How to present it
- Lead with a large value, period-over-period change, and a compact trend. Provide a movement breakdown nearby rather than hiding it in a tooltip.
Logo churn rate
- What it measures
- The share of starting customer accounts that canceled during the period.
- Why it belongs
- Revenue can grow while customer loss quietly worsens, so logo churn deserves independent visibility.
- How to present it
- Show the rate, the lost-account count, and a trailing trend. Label the cohort and exclude trial expirations only when the definition says so.
Net revenue retention
- What it measures
- Ending recurring revenue from an existing cohort after expansion, contraction, and churn.
- Why it belongs
- NRR reveals whether the installed customer base compounds or shrinks before new sales are added.
- How to present it
- Use a percentage with a clear 100% reference and a cohort note. Pair it with the expansion and contraction amounts that explain the result.
Activation rate
- What it measures
- The share of eligible new accounts that completed a defined value-producing action.
- Why it belongs
- Activation links acquisition to product adoption and can provide an earlier signal than retention.
- How to present it
- Display a funnel or cohort bars with the qualifying action written beside the metric. Never label a generic login as activation unless it represents real value.
Recommended Layout
Move from overall business health to its causes, then to accounts that require attention.
Health summary
Place MRR, active accounts, churn, and expansion in a restrained top row with one shared reporting period.
Movement and retention
Use the widest middle area for recurring-revenue movement and retention cohorts because these explain the headline values.
Plan and adoption mix
Keep plan distribution, activation, and feature adoption beside the main trend so operators can compare commercial and product signals.
Account attention queue
End with renewals, health changes, failed onboarding steps, or other review items that lead to a clear next action.
Features and Components
The interface should support comparison and investigation while staying useful as a static frontend when no integration is attached.
- A reporting-period control with the active range repeated in chart labels and exports.
- Revenue movement cards for new, expansion, contraction, and churned MRR.
- Retention cohorts with accessible text values in addition to color intensity.
- Plan and lifecycle filters that retain a visible “all accounts” baseline.
- An account detail slide-over for context without losing the dashboard position.
Mistakes to Avoid
Subscription dashboards become misleading when commercial definitions are treated as decoration.
- Mixing billing metrics.Do not place bookings, cash collected, recognized revenue, ARR, and MRR together without explicit labels and definitions.
- Hiding the denominator.A churn or activation percentage needs the eligible cohort and count so a small sample cannot look more certain than it is.
- Using one health score.A composite score can aid sorting, but show the behaviors and account events that produced it.
- Implying connected systems.A polished card does not create billing, analytics, or customer-success data; those services must be integrated separately.
VibeCodePack Missions Used
These exact feature titles were verified in the inspected VibeCodePack source files. The mapping recommends a frontend mission combination; it does not expose the private instructions inside those files.
Minimalist KPI Card Grid with Trend Indicators
Structures the top-level revenue, account, retention, and expansion summary.
E-commerce Sales Dashboard with Revenue Forecasting
Provides a verified source pattern for visually separating historical and forecast-style revenue segments.
Subscription Management Interface with Pause/Cancel Options
Supports account-plan and subscription-management surfaces linked from the dashboard.
User Management Table with Inline Editing Capabilities
Maps to an account roster, while real permissions and persistence remain project responsibilities.
Activity Feed Timeline with Expandable Details
Organizes significant account and subscription events into a readable sequence.
Sidebar with Integrated User Dashboard Widgets
Supplies a compact navigation and summary pattern for a multi-view SaaS workspace.
User Notification Center with Categorized Alerts
Groups renewals, account risks, and operational notices without crowding the primary metrics.
Build This Dashboard With Claude Code
Begin with a metric dictionary and the decisions this screen must support. Then give Claude Code separate, bounded missions for the KPI layer, retention view, account table, navigation, and alert states. Review each result against the existing codebase before combining the pieces.
The 75-mission Obsidian-ready vault is designed to provide that structure through instructions, constraints, build steps, and verification gates. It does not supply billing records, product events, customer data, or a complete SaaS backend.
VibeCodePack supports structured frontend dashboard and UI workflows. Your project must separately provide and validate production databases, APIs, authentication, payments, permissions, live data, and backend services.
Keep exploring