Who this template is for
SaaS founders, internal-tool teams and developers planning an operations or business analytics interface.
Choose the decision before the chart
Write down what the user should do after reading each metric. Revenue might help a founder assess growth; overdue tasks might help an operator prioritise work. Give every figure a unit, time period and comparison so an attractive number does not become an ambiguous one.
Design for missing and imperfect data
A convincing dashboard needs more than a successful state. Plan what appears while data loads, when the selected period is empty, and when a source is unavailable. Tables should preserve meaningful labels on small screens, and charts need a readable explanation beyond colour alone.
Connect data deliberately
Orbit uses illustrative data. Before using this design with a business, implement authenticated data access, server-side authorisation, time-zone handling and reliable metric calculations. Never rely on hiding a card in the browser to protect a confidential number.
Before you launch
- Define the owner, unit and time window of every metric.
- Replace sample figures with validated data sources.
- Include loading, empty and error states.
- Verify permissions for each account and reporting endpoint.